> Markdown version of [/jobs/ext/4674587-lead-software-engineer-federated-graphql](https://www.wearedevelopers.com/jobs/ext/4674587-lead-software-engineer-federated-graphql). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Lead Software Engineer (Federated GraphQL) - **Company:** The Information Technology - **Location:** Richardson, TX, United States - **Experience:** Expert - **Salary:** $123,000 - $142,000 - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Code Review, Databases, Load Testing, OpenShift, Software Engineering, TypeScript, AI Coding Agents, Backend, Event Driven Architecture, Kubernetes, Graphql, Dynatrace, Golang - **Published:** November 11, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=862f12f3caaef3d7 ## About the Role * 6+ years of software engineering experience. * Production experience with federated GraphQL: designing entities and keys, composing and evolving schemas across teams, for example with Apollo Federation or similar. * Passion for the work and a collaborative approach: you pair, give thoughtful code reviews, and welcome healthy debate with teammates and partner teams. * Backend development in one or more of Go, Java or Node.js/TypeScript. * Picks up new languages and technologies quickly. * Uses AI coding assistants effectively in day-to-day work. * Integrated services that call other systems, handling slow or failing dependencies, for example with timeouts, retries and batching. * Builds for the long term: automated unit, integration and end-to-end tests that catch regressions and keep the code safe to change. Desired, not required * Led federated GraphQL adoption or schema governance across multiple teams. * Go GraphQL (gqlgen) or Java GraphQL (Spring for GraphQL, Netflix DGS). * Temporal, or another durable workflow engine, for long-running processes. * Diagnosed and fixed a latency or throughput problem using an APM tool such as Dynatrace or OpenTelemetry. * Built APIs on Kubernetes or OpenShift, and AWS. * Worked with canonical or industry data models, such as ACORD. * Insurance experience is a plus, not a requirement. * gRPC, event-driven systems or caching. ## Description The Policy Graph team is building the GraphQL layer that unifies policy data across State Farm's lines of business and policy systems, making it accessible to applications, digital experiences, and AI. We're building this from the ground up, defining the schemas, engineering patterns, and architecture that will support enterprise-wide access to policy data. The technical challenges are significant. Policy data varies by state, line of business, and underlying system, spanning legacy platforms and multiple generations of modernization efforts. Our job is to bring that complexity into a consistent, modernized data model exposed through a performant and scalable graph. We're currently prototyping in TypeScript, but the production stack is still open. TypeScript, Go, Java, or a combination will be evaluated based on performance, scalability, and engineering tradeoffs. We're looking for engineers who have built and run federated GraphQL in production and want to help shape it at enterprise scale. What you'll do * Bring federated GraphQL expertise to the team: entity design, schema composition and evolution, and patterns other domains can follow. * Design the Policy GraphQL schema with architects and data model stewards. * Work closely with partner teams: architecture, consuming domains, policy administration system teams and the GraphQL platform team. * Build federated subgraphs that read close to the source: straight from databases, policy administration system APIs, or a read model we own. * Own performance against p99 targets: load test, profile and tune., The technical challenges are significant. Policy data varies by state, line of business, and underlying system, spanning legacy platforms and multiple generations of modernization efforts. Our job is to bring that complexity into a consistent, modernized data model exposed through a performant and scalable graph. We're currently prototyping in TypeScript, but the production stack is still open. TypeScript, Go, Java, or a combination will be evaluated based on performance, scalability, and engineering tradeoffs. We're looking for engineers who have built and run federated GraphQL in production and want to help shape it at enterprise scale. What you'll do * Bring federated GraphQL expertise to the team: entity design, schema composition and evolution, and patterns other domains can follow. * Design the Policy GraphQL schema with architects and data model stewards. * Work closely with partner teams: architecture, consuming domains, policy administration system teams and the GraphQL platform team. * Build federated subgraphs that read close to the source: straight from databases, policy administration system APIs, or a read model we own. * Own performance against p99 targets: load test, profile and tune.