Information Technology Specialist (Enterprise Architecture)

The Application Programming Interface (API) Lead Architect position is in the Office of the Deputy Director, Case Management Modernization (CMM) Program Office. The CMMPO drives change management and adoption practices to achieve delivery of a modernized, efficient, and secure case management environment. This role designs solutions, works with resources across teams, and applies knowledge to deliver solutions that support the judiciary's mission and operational excellence.

The API Lead Architect position is responsible for the technical strategy of standardizing API design, versioning, and service contracts for cross-service integration. This role will design the API library for the case management application, enabling integration of core case management components across third-party systems. This is a hands-on architectural design role. Key Responsibilities Defining and maintaining program-wide API standards, including contract conventions, versioning, and deprecation policies. Overseeing cross-service integration decisions, ensuring architectural alignment across multiple pods, and managing technical escalations. Collaborating with the development leads to institutionalizing API guardrails, CI/CD expectations, and quality review checkpoints. Coordinating with the Chief Architect and other workstream leads to ensure API patterns support enterprise non-functional targets and roadmap delivery. Identifying and implementing an API catalog capability for the maintenance and discovery of APIs for third-party system integrations Balancing team capacity against program demands, ensuring the team is allocated effectively to support high-priority integration efforts. Providing design-time API reviews for pod teams and documenting approved patterns and decisions to reduce rework and integration defects. Driving cross-pod adoption of API standards by identifying gaps, escalating necessary noncompliance, and enabling teams to implement immediate solutions. Running an API functional chapter to synchronize embedded engineers on API decisions, upcoming changes, and external API integration needs. Maintaining API playbooks and review checklists aligned to Development Chapter engineering guardrails and publishing reusable guidance for pod team.