Why This Role Matters:
The AI Platform is an enabling team that builds reusable capabilities for every AI program at Geisinger. Most of those capabilities have a user-facing surface — dashboards, configuration interfaces, review tools, developer portals and each of those surfaces is the moment a program team, a governance reviewer, or a platform engineer decides whether the platform is helping them or getting in their way. Slow, ugly, or inaccessible internal applications quietly kill adoption and adoption is what the platform is measured on. The application portfolio will evolve as platform capabilities evolve; the constant is that someone has to own the bar for what those applications look and feel like.
This is an individual contributor role with a broad surface area. You are the senior frontend voice for the AI Platform, the steward of the design system, and the engineer accountable for whether the applications actually feel good to use.
What You Will Own:
The frontend architecture and the shared design system / component library used across every AI Platform application — visual and interaction consistency.
RBAC-aware interfaces — making sure program teams, governance stakeholders, leadership, and platform engineers each see the right data and controls based on their role
The backend-for-frontend layer — API patterns, data contracts with MLOps, and the seams where the UI meets the platform
Application-level testing strategy — unit, integration, and end-to-end suites that the platform's deployment verification pipeline can trigger automatically
Usage telemetry and analytics — instrumenting every application for adoption, feature engagement, error rates, and load times, and surfacing the insights that inform the platform roadmap
Frontend performance — bundle optimization, caching, lazy loading, and load-time budgets for internal applications where slow UIs erode trust
UX quality gates — defining and enforcing the bar that no application ships below
Shape of the Work
This role lives at three altitudes:
With the design system (hands-on build).Own the shared component library and the patterns underneath it. Build accessibility in from the start, not as a remediation pass. Make the design system something other engineers want to consume because it makes their work faster, not because they're forced to.
With application teams (collaborative delivery).Build the user-facing applications in the platform's portfolio alongside the MLOps engineers who own the backend logic. Negotiate API contracts, RBAC implementations, and data shapes with the integration engineer and the platform engineer so the UI and the backend evolve together. Today's portfolio is one set of applications; tomorrow's will be another, and you'll own the interface layer through the transitions.
With the data the applications generate (product instinct).Wire telemetry into every surface and read it. Page views, feature engagement, drop-off, error rates, load times. Bring evidence to the platform's roadmap conversations: which features get used, where users get stuck, which application surfaces deserve more investment and which ones to retire. Use what you instrument to drive what you build next.
Today's Application Portfolio:
The platform team currently maintains a small, growing set of internal applications. Examples of what's on the floor right now:
AnAI Scorecarddashboard displaying per-initiative status across Performance, Adoption, Outcome, and Equity pillars
AnLLM-as-Judge evaluation toolfor configuring evaluation criteria, reviewing judge outputs, and tracking eval results over time
Developer portals and internal tooling— documentation sites, onboarding flows, and self-service interfaces for the platform's standard delivery path
Expect the portfolio to grow and shift as new platform capabilities come online. The role is the application layer of the AI Platform, not these specific applications.
Key Technologies:
React 18 (frontend framework)
Mantine and/or MUI (component library foundations for the design system)
FastAPI (backend-for-frontend APIs)
SQLAlchemy (ORM / database access)
Docker (containerization)
Jest, React Testing Library, Playwright or Cypress (testing)
OpenTelemetry and application-level metrics (telemetry and observability)
Collaboration Points:
MLOps Engineers— consume their APIs for the Scorecard and Eval Tool; align on data contracts, feature requirements, and API versioning
Sr. Platform Engineer— coordinate on deployment targets (ECS/Fargate), CDN, environment configuration, IDP self-service provisioning, and SSO/authentication infrastructure
Sr. Software Engineer (Integration)— align on shared API design patterns, authentication flows, and RBAC implementation
AI Platform Team Lead— direct manager; partner on roadmap, priorities, and architecture reviews
Work is typically performed in an office or remote environment. Accountable for satisfying all job specific obligations and complying with all organization policies and procedures. The specific statements in this profile are not intended to be all-inclusive. They represent typical elements considered necessary to successfully perform the job.
*Relevant experience may be a combination of related work experience and degree obtained (Associate’s Degree = 2 years; Bachelor’s Degree = 4 years; Master’s Degree = 6 years).
Required Qualifications:
5+ years of full stack engineering experience shipping production web applications, including at least 2 years where you were the senior frontend voice on a team or product
Deep proficiency in modern React (hooks, context, suspense, performance patterns) and the surrounding ecosystem
Hands-on experience designing or substantially evolving a shared component library or design system used by more than one application
Strong fluency in Python and FastAPI (or comparable Python web framework experience) for backend-for-frontend work
Demonstrated ownership of accessibility (WCAG 2.1 AA) as a first-class engineering concern, not a final-week checklist
Experience implementing role-based access controls and permission-aware views in real applications
A real testing practice: unit, integration, and E2E with one of Playwright or Cypress
Experience instrumenting applications with usage telemetry and using that data to inform product decisions
Strong written communication — you will write technical specs, design system documentation, and API contracts that other engineers rely on
Bachelor's degree in Computer Science, a related technical field, or equivalent professional experience
Preferred Qualifications:
Experience as the founding or lead frontend engineer on an internal-tools or platform-engineering team
Experience with Mantine, MUI, or comparable enterprise component libraries
Production experience with OpenTelemetry on the frontend or comparable observability tooling
Familiarity with healthcare data, clinical workflows, or regulated-industry environments
Experience integrating with enterprise SSO / IdP systems as a consumer (not necessarily as the implementer)
Exposure to AI/ML application interfaces — model evaluation tooling, monitoring dashboards, or LLM application UX