Platform Engineer, AI Observability

**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 team runs a shared observability platform for LLM-based applications, currently built on Langfuse. This role owns it as a product: what capability it offers, how it is configured, and where it goes next. That means deciding which of the platform’s features are enabled and why, how organisations, projects and access are structured, and what the defaults are for retention, sampling and redaction. It means judging at each upgrade which new upstream capability is worth adopting, rather than only keeping the version current, and setting that capability up properly when it lands so it is genuinely usable rather than merely switched on. It also means looking ahead: assessing additional or replacement backends as the estate grows and requirements change, running the spikes, and making a recommendation with evidence behind it. Keeping the platform running is a separate role. This one is judged on what the platform can do for the teams using it, and on whether the configuration decisions behind it still look right a year later. It is a hands-on technical role. The person is expected to configure, test and evaluate the platform themselves, and to arrive at a view rather than collect requirements and pass them on.

What You’ll Do

Own what the platform offers.

• Decide which features are enabled, for whom, and why, and keep that decision under review as the platform and its users change.
• Own the tenancy model: how organisations, projects and environments are structured, how access maps onto existing teams, and what the naming and ownership conventions are.
• Set the defaults that shape the data, including retention, sampling, payload trimming and redaction, balancing what is useful to keep against what should never be stored.
• Define what the platform exposes to the systems around it, so the integrations built against it have a stable and deliberate surface.

Keep the capability current.

• Track upstream releases and decide what is worth adopting, distinguishing genuinely useful capability from noise
• Configure and test new capability before it is offered to teams, including piloting it with a willing team where the change is significant.
• Retire configuration and features that are not earning their place.
• Work with the reliability engineer on upgrades: this role decides what to adopt and how it should be configured, while execution of the migration and its rollback sits with them.

Look ahead.

• Assess additional or replacement backends as requirements grow. Langfuse is the current backend and the assumption is that it stays, but the role is expected to know where it falls short and what else the market offers, whether for telemetry storage, metrics or evaluation.
• Run the spikes and proofs of concept, define the criteria in advance, and make recommendations that show the working rather than the conclusion alone.
• Understand the cost and scaling consequences of configuration and architecture choices, and make them explicit when recommending a change.
• Document what the platform offers and when to use what, so teams can serve themselves rather than asking.

What You Bring

• Hands-on ownership of an observability or developer-tooling product, as the person who configured and administered it rather than a user of it. Langfuse is ideal, another LLM observability product is close behind, and a comparable APM, tracing or analytics platform is acceptable.
• Configuration and administration of self-hosted software at organisation scale, covering te…