Interested in this AI/ML Engineer role at Newpage Digital Healthcare solutions?
Apply Now →Skills & Technologies
About This Role
LOCATION: Remote | Type: Contract
About Newpage Solutions
Newpage Solutions is a global digital health innovation company helping people live longer, healthier lives. We partner with life sciences organisations which include, pharmaceutical, biotech and healthcare leaders, to build transformative AI and data driven technologies addressing real-world health challenges.
From strategy and research to UX design and agile development, we deliver and validate impactful solutions using lean, human-centered practices.
We are proud to be a ‘Great Place to Work®’ certified company for the last three consecutive years. We also hold a top Glassdoor rating and are named among the "Top 50 Most Promising Healthcare Solution Providers" by CIOReview. As an organisation, we foster creativity, continuous learning and inclusivity, creating an environment where bold ideas thrive and make a measurable difference in people’s lives.
Your Mission
The organisation runs a shared observability platform for LLM-based applications. This role connects that platform to the systems around it, so that teams get observability as a property of the environment they already work in rather than as something they have to go and set up. Two examples of what that means in practice. When a team is provisioned with LLM credentials or deploys an agent, observability should follow automatically: the project, the credentials, the collection configuration and the ownership metadata all created without anyone raising a request. Separately, where results need to appear somewhere other than the observability tooling, such as an internal agent registry that records each agent alongside its evaluation scores, this role builds and owns that path. This is systems integration engineering. It is not building or operating the collection pipeline and observability backends, which sit with the platform engineering roles, and it is not writing instrumentation inside application teams' codebases. It is the connective tissue between the platform and everything else, and the level of service end users experience depends almost entirely on how well it works..
What You’ll Do
Make observability automatic.
- Integrate with stack provisioning so that granting LLM credentials, model access or deploying an agent creates the corresponding observability without a separate request.
- Wire identity and access through, so project access follows existing team membership and group structure rather than being granted by hand.
- Seed sensible defaults at creation: collection configuration, ownership metadata, retention, and redaction settings appropriate to the workload.
- Handle the whole lifecycle rather than just creation, including ownership changes, decommissioning, and keeping both systems consistent when they drift apart.
Integrate with the systems that consume the data.
- Publish evaluation scores into the internal agent registry, so that a registered agent carries its current results wherever it is looked up.
- Deliver alerts and signals into the tools teams already work in, rather than requiring them to watch another place.
- Agree the data contract for each integration and version it, so that downstream consumers do not break when something changes upstream.
Keep the integrations dependable.
- Build for partial failure: retries, idempotency, backfill, and reconciliation when two systems disagree about the same thing.
- Monitor the integrations themselves, so that a broken feed is noticed here rather than reported by a user.
- Document what each integration does and what it guarantees, so other teams can depend on it without having to ask.
- Turn recurring manual requests into automation, so that the service improves without the team growing
What You Bring
- Backend integration engineering in Python, TypeScript or both. APIs, webhooks, event-driven messaging, queues and authentication flows, to a standard that stands up in production.
- Designing and consuming APIs between internal systems, including agreeing data contracts and evolving a schema without breaking consumers.
- Identity and access integration. OIDC or SSO, service accounts, API key lifecycle, and mapping existing groups to roles and permissions.
- Building for failure. Idempotency, retry and backoff, partial-failure handling, and reconciling state between systems that disagree.
- CI/CD and infrastructure-as-code literacy, enough to hook cleanly into provisioning pipelines owned by other teams.
- Cross-team working, since every integration has an owner on the other side with their own roadmap and their own view of the interface.
- Clear written communication, because an integration nobody understands will not be depended on.
- Nice to have Working knowledge of OpenTelemetry, covering collector pipelines, exporters and attribute conventions, sufficient to integrate with a collection pipeline that someone else operates.
- Nice to have Experience with LLM observability tooling, for example Arize Phoenix, Braintrust, Langfuse or LangSmith.
- Nice to have Familiarity with LLM application architecture, including agents, tool calling and prompt management, sufficient to understand what the data represents.
- Nice to have Experience of data governance or privacy review under regulatory constraints.
What We Offer
At Newpage, we’re building a company that works smart and grows with agility, where driven individuals come together to do work that matters. We offer:
- A people-first culture - Supportive peers, open communication and a strong sense of belonging
- Smart, purposeful collaboration - Work with talented colleagues to create technologies that solve meaningful business challenges
- Balance that lasts - We respect your time and support a healthy integration of work and life
- Room to grow - Opportunities for learning, leadership and career development, shaped around you
- Meaningful rewards - Competitive compensation that recognises both contribution and potential
Ready to Apply?
Let’s build the future of health together. Apply below or reach out to:
More about Newpage
Newpage is a digital health solutions company. We devote ourselves to advancing the quality of life by enhancing health and optimizing the longevity of people. We do this by, passionately building futuristic technologies for global organizations across the healthcare ecosystem. We partake at every stage from problem definition, strategy & service design, user research, UX design, and agile software development – utilizing lean practices to deliver and validate highly innovative digital health solutions that drive user value and business transformation.
Newpage is recognized by ‘CIO’s Review’ as “Top 50 Promising Healthcare Solution Providers” and Great Place to Work Certified (GPTW) 2023 & 2024.
Role Details
About This Role
AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.
Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.
Across the 9,653 AI roles we're tracking, AI/ML Engineer positions make up 76% of the market. At Newpage Digital Healthcare solutions, this role fits into their broader AI and engineering organization.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
What the Work Looks Like
A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
Skills Required
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.
Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
Compensation Benchmarks
AI/ML Engineer roles pay a median of $212,000 based on 11,857 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $193,200.
Across all AI roles, the market median is $213,400. Top-quartile compensation starts at $264,230. The 90th percentile reaches $319,400. For comparison, the highest-paying categories include AI Safety ($253,100) and Research Engineer ($252,000). By seniority level: Entry: $110,408; Mid: $193,200; Senior: $228,700; Director: $272,275; VP: $235,000.
Newpage Digital Healthcare solutions AI Hiring
Newpage Digital Healthcare solutions has 5 open AI roles right now. They're hiring across AI/ML Engineer, AI Agent Developer. Based in Remote, US.
Remote Work Context
Remote AI roles pay a median of $185,906 across 2,124 positions. About 6% of all AI roles offer remote work.
Career Path
Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.
From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.
The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.
What to Expect in Interviews
Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.
When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
AI Hiring Overview
The AI job market has 9,653 open positions tracked in our dataset. By seniority: 193 entry-level, 4,500 mid-level, 3,455 senior, and 1,505 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (568 positions). The remaining 9,010 roles require on-site or hybrid attendance.
The market median for AI roles is $213,400. Top-quartile compensation starts at $264,230. The 90th percentile reaches $319,400. Highest-paying categories: AI Safety ($253,100 median, 57 roles); Research Engineer ($252,000 median, 419 roles); AI Engineering Manager ($251,622 median, 51 roles).
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
The AI Job Market Today
The AI job market spans 9,653 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,301), Data Scientist (441), AI Software Engineer (438). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.
The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (193) are outnumbered by mid-level (4,500) and senior (3,455) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,505 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (568 positions), with 9,010 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.
AI compensation is structured in clear tiers. The market median sits at $213,400. Top-quartile roles start at $264,230, and the 90th percentile reaches $319,400. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.
Category matters for compensation. AI Safety roles lead at $253,100 median, while Prompt Engineer roles sit at $141,440. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.
The most in-demand skills across all AI postings: Python (1,605 postings), Aws (916 postings), Azure (724 postings), Rag (634 postings), Gcp (522 postings), Pytorch (495 postings), Kubernetes (384 postings), Claude (383 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.