Senior API Integration Developer -- Enterprise API Gateway

Job Description

Job Description

POSITION OVERVIEW

The Senior API Integration Developer owns the application side of the Customer's enterprise API gateway program: designing the service contracts that pass through the gateway, onboarding and refactoring upstream applications to be consumed through it, and extending gateway behavior with custom policy modules where the standard plugin set falls short. The work is hands-on development, from API design through containerized deployment and the regression validation that proves a migrated route behaves as it did before. This position requires an active Moderate Background Investigation (MBI) suitability determination at start.

RESPONSIBILITIES

• Design, build, and maintain RESTful services and API contracts published through the enterprise gateway, including OpenAPI specifications and versioning
• Onboard and refactor upstream applications to be consumed through the gateway, preserving functionality and external interfaces through the cutover
• Implement token-based authentication and authorization in application code — OAuth 2.0 flows, JWT issuance and validation, claim and session handling
• Develop custom gateway plugins and policy modules where standard functionality does not meet the requirement
• Make the client-side and service-layer changes that gateway-mediated authentication and routing require
• Package and deploy services as containers on Red Hat OpenShift and promote them through Customer environments under Government change control
• Remediate vulnerable and out-of-support dependencies across supported applications, working findings with cybersecurity
• Execute regression and smoke validation against every changed route and component before release
• Produce interface designs, technical documentation, and architectural decision records for systems as delivered
• Troubleshoot end to end across gateway, service, database, and client layers
• Deliver in Agile ceremonies alongside Government product owners and other contractor teams

REQUIRED QUALIFICATIONS

• Active MBI suitability determination, current and transferable as of your start date
• U.S. citizenship, as required for Customer contractor personnel
• Ten years of hands-on application development and systems integration in production, including three years supporting a Federal system subject to FISMA
• Java and Spring Boot depth, building and consuming RESTful APIs and microservices at enterprise scale
• Demonstrated integration of applications with an API gateway or reverse proxy, including routing, authentication, and rate limiting behavior
• Working command of OAuth 2.0, OpenID Connect, JWT validation, SAML federation, and TLS in application code
• Front-end development in ReactJS or Angular sufficient to change how a client authenticates against and consumes a gateway-fronted API
• Container packaging and deployment on Kubernetes or Red Hat OpenShift
• Experience migrating a production application onto new hosting or a new access path with functionality and external interfaces preserved
• Dependency and vulnerability remediation across a supported application portfolio
• Regression and smoke validation of changed components, with defensible evidence of what was tested
• CI/CD pipeline work in Jenkins, GitHub Actions, or Azure DevOps, with Git-based source control
• Relational database proficiency and SQL performance troubleshooting
• Technical writing — interface control documents, design artifacts, and decision records that hold up under Government review
• Bachelor's degree in Computer Science, Engineering, or Information Systems, or equivalent hands-on experience

PREFERRED QUALIFICATIONS

• An active vendor certification on the program's API gateway platform, or willingness to earn it within 90 days of start with training provided
• Development in Lua or Python sufficient to build custom gateway policy modules
• Prior support to a Federal financial or tax administration program
• Single sign-on integration against an enterprise identity provider such as ADFS, Ping Federate, or CA SiteMinder
• GraphQL, SOAP, or event-driven interfaces alongside REST
• An active cloud or platform certification such as AWS, Azure, or a Java or Spring credential
• Contribution to an SSP or other Federal authorization artifact