FULLSTACK DEVELOPER _CLAUDE

**Location: Remote Type: Full-time / 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 — including 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-centred practices.

We are proud to be Great Place to Work® certified for three consecutive years, hold a top Glassdoor rating, and were named among the “Top 50 Most Promising Healthcare Solution Providers” by CIOReview. 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

We are hiring a Fullstack Developer who knows the Claude platform from the inside — how Claude Enterprise, Claude Code and Cowork are administered, how skills, plugins and MCP connectors are built, packaged, scoped and distributed, and how access and permissions actually flow through them.

You will be embedded with a large enterprise client as part of a small engineering pod, alongside engineers who own other enterprise AI platforms. You will own the path by which new data connectors, skills and plugins reach users: from intake through access group creation, identity provider synchronisation, connector registration, per-tool permission scoping, testing, documentation and closure with the requester. You will review third-party components for security and quality before release, and replace manual console work with automated, repeatable pipelines.

This is not an administration role. Most of your time goes into building: the backend services, data mappings and integrations that wire the platform into the client’s systems, and the internal tooling that gives platform owners visibility and control over how AI capabilities are being used. You should be as strong in the backend — APIs, identity, data, infrastructure as code — as you are in the UI.

You won’t wait for a refined backlog or a separate platform team. You will take a vague request, work out what is actually needed, build it, and stand it up in production yourself. This is a builder role for engineers who combine solid fullstack fundamentals with a deep, practical understanding of the Claude platform and its extension model.

What You’ll Do

Build & Integrate

• Design and build the backend services, APIs and data mappings that connect Claude to enterprise systems — identity, data sources, ticketing and the connectors in between.
• Build internal tooling and admin interfaces (React / Next.js over Python or TypeScript backends) that give platform owners visibility into usage and control over which capabilities are available to whom.
• Build MCP servers, skills and plugins for the client’s own use cases, and LLM-powered services and agents on whichever orchestration framework fits (LangGraph, Claude Agent SDK, AutoGen, Semantic Kernel, OpenAI Agents SDK or similar), integrating models through APIs, tool calling / MCP and structured outputs.
• Take a vague request from a business or platform owner, work out what is actually needed, ship a working version quickly, and harden what survives contact with real users.

Own Connector & Skill Requests End to End

• Own data connector and skill requests for the enterprise Claude platform from intake through to closure with the requester.
• Create access groups and manage identity provider synchronisation (SSO / SCIM with Okta or Entra ID) so access follows existing team and group structures.
• Register connectors and apply per-tool permission scoping, granting only the access each capability needs.
• Test each connector and skill before release, document what it does and how to use it, and close the loop with the requester.

Configure, Distribute & Review Platform Capabilities

• Configure and distribute skills and plugins to the right audience — enterprise-wide, group-scoped or on request — with a clear understanding of the scoping controls and what each one actually gates.
• Conduct security and quality reviews of third-party and externally authored skills, plugins and connectors before release: dependencies, bundled scripts, and exposure to prompt injection or data exfiltration.
• Define remediation or …