Build technology that connects healthcare.

Responsibilities

• Perform API Manager lifecycle work: create and version APIs, maintain the catalog, build custom APIs, guide product teams, and manage throughput and rate limits.
• Administer the API platform (short of the operating system), including API Manager, Identity Server, and Micro Integrator modules across Dev, Sandbox, QA, UAT, Staging, and Production.
• Test platform behavior on lower and upper environments before and after monthly Linux patch windows applied by Networking.
• Implement authentication, authorization, and provisioning into enterprise identity (OKTA / SailPoint) using SAML 2.0, OAuth2 / OpenID Connect, and SCIM 2.0.
• Default new interfaces to REST; version, authenticate, rate-limit, observe, and catalog them before production.
• Secure data in transit with TLS 1.2+ and data at rest with approved encryption; respond to in-scope help-desk tickets.
• Turn availability signals and platform logs into owned remediation work, and write API / microservice-transfer documentation for future-state products.

Required qualifications

• At least 5 years building and operating APIs in production, including a gateway or manager—not only application code.
• Production experience with API lifecycle, rate limiting, cataloging, and versioning.
• Implemented SAML, OAuth2 or OpenID Connect, and SCIM (or close equivalents you can explain at the protocol level).
• Comfortable testing application behavior around OS patches applied by another team.
• Able to obtain High Risk Public Trust (Tier 4) for production administration and identity-API access.

Preferred qualifications

• WSO2 API Manager, Identity Server, and Micro Integrator, including version upgrades while staying on N or N-1.
• OKTA, SailPoint, or Entra ID integration through a gateway.
• High-traffic public API experience (on the order of millions of requests a month).
• AWS-hosted API infrastructure and RHEL application troubleshooting (without owning OS patching).

Responsibilities

• Capture each request in ServiceNow SPM with problem statement, users, systems touched, desired outcome, and urgency; return incomplete packages within two business days.
• Classify work with the Portfolio Manager: standard change, enhancement, new product, research/prototype, or duplicate/retire; apply security, Section 508, privacy, and data-sharing flags.
• Run human-centered design for internal users: interviews, artifact review, and synthesis of usability notes and support tickets into validated problem statements.
• Write user stories with acceptance criteria, Section 508 notes, security notes, and a definition of done that includes pipeline success, documentation, and operational handover.
• Publish easy-to-follow documentation for future-state products and draft a clear “how to request a solution” article.
• Support board packages with user-impact and outcome language; track customer-experience and mission outcome measures.
• Support change management with two-way feedback, champions, and a clear record when resistance threatens delivery.

Required qualifications

• Qualifies for GSA labor category Computer Systems Analyst Senior: bachelor’s degree and 14 years of relevant experience, or 18 years without the degree.
• A record of business analysis that produced shipped requirements—not only workshop notes.
• Hands-on human-centered design with internal enterprise users: interview guides, synthesis, and problem statements a team actually used.
• Ability to write user stories and acceptance criteria that include accessibility and security.
• Functional use of a demand or ticketing system such as ServiceNow.
• Able to obtain a DOJ Public Trust.

Preferred qualifications

• Section 508 applied while writing the story, not after development.
• Experience in grants, justice, or other high-stakes government missions.
• ServiceNow SPM demand records and governance workflows.
• Facilitation of product teams that already have their own boards.

Compensation reference from posting: $77,436 per annum or $68.87 per hour (1099).

Responsibilities

• Set the engineering bar for pipelines, branching, scanning, and release.
• Run two-week Scrum sprints for build work and a Kanban board for production incidents; attend working sessions regularly to capture work items.
• Hold roughly 40% of capacity for run work (lifecycle, patch-test, Jenkins/Ansible sustainment, scans, monitoring response, tickets) and about 60% for build work.
• Install a common pipeline pattern in Azure DevOps (and Jenkins until retirement): commit, build, test, SCA/SAST, secrets scan, container build, IaC, non-prod deploy, Section 508 checks where UI exists, change record, production deploy, and verification.
• Inventory Jenkins jobs, freeze new Jenkins work, migrate valuable jobs, and retire the rest through alternatives analysis.
• Own CI/CD security-scan intake; critical findings follow a seven-day containment standard.
• Support Authority to Operate packages with living evidence; publish pipeline health monthly and coach product teams.

Required qualifications

• At least 5 years leading DevOps or DevSecOps and data-integration work.
• Production ownership of Azure DevOps pipelines (or comparable), including branch policy, test plans, and artifacts.
• A release process you can draw: quality gates, change record, rollback, and monitoring proof.
• Experience coordinating with separate network/security teams rather than owning OS and SOC yourself.
• Able to obtain High Risk Public Trust if privileged administration is in the seat, and to be named as Key personnel.

Preferred qualifications

• Azure DevOps, GitHub, AWS, or API-management certification—or equivalent delivered work.
• Jenkins and Ansible in a legacy estate you later migrated.
• WSO2 or another API gateway in production.
• Section 508 checks inside a pipeline.
• Federal cloud constraints: encryption, least privilege, and no public generative-AI tools for agency data.

Responsibilities

• Perform enterprise, application, software, data, solution, technical, and business architecture for products in scope.
• Administer the Enterprise Architecture Repository: content, user support, monthly completeness, and integration with ServiceNow.
• Own alternatives analysis for IT demand requests (typical volume 8–12 analyses/year), covering keep, extend, buy, build, retire, or combine.
• Publish target-state architecture and a standards backlog each quarter (API-first, containers/IaC, one toolchain per capability, elastic scale, documented commercial exit paths).
• Approve feasibility scores, recommend standards to governance boards, and keep current state runnable (API platform, Jenkins, Ansible, Azure DevOps).
• Require time-boxed spikes when architecture uncertainty is high; evaluate emerging tools with the same criteria as any other product.
• Support Authority to Operate evidence while Security remains the risk owner; prefer FedRAMP for new products.

Required qualifications

• At least 5 years of solution and enterprise architecture, including current-state and target-state work in a regulated environment.
• A portfolio of alternatives analyses that compare keep, extend, buy, build, and retire with cost, risk, and lock-in called out.
• Hands-on familiarity with an enterprise architecture repository and connecting architecture decisions to a demand system such as ServiceNow.
• Ability to review an API contract, pipeline, or short proof of concept as board-ready evidence.
• Able to obtain a DOJ Public Trust and to be named as Key personnel.

Preferred qualifications

• Experience with WSO2, Azure DevOps, AWS GovCloud, or a federal enterprise-architecture repository.
• TOGAF, FEAF, or equivalent practice shown through delivered artifacts.
• Experience writing standards product teams can follow without a meeting.
• FinOps or tool-rationalization analyses that led to a real retirement.

Responsibilities

• Score each request for feasibility, current-state fit, target-state alignment, cost band, user impact, and risk using published criteria.
• Produce the solution architecture recommendation and assessment record for Enterprise Architect approval.
• Charter and run time-boxed spikes (typically five business days) when a tool, integration, or AI use is unproven.
• Embed research, prototyping, piloting, and code-based proofs of concept inside architecture decisions; PoCs are productized or retired within one quarter.
• Shape backlog hierarchy with the DevOps lead: portfolio epic → product epic → feature → user story → task.
• Design REST APIs with explicit resource models, versioning, pagination, and error contracts; prefer FedRAMP products and document exit paths.
• Flag username/password logins for movement onto enterprise identity through SAML, OAuth2, or SCIM; pair with the Business Analyst on human-centered design notes when users are affected.

Required qualifications

• At least 5 years of solution architecture that produced implemented systems—not only reference models.
• Evidence of hands-on prototyping: an API contract, a pipeline, or a short proof of concept you built or directly led.
• Ability to write a feasibility score a portfolio manager and board can compare across requests.
• Working knowledge of REST, authentication patterns (SAML, OAuth2, OpenID Connect), and integration constraints in a regulated environment.

Preferred qualifications

• WSO2 API Manager, Azure DevOps, AWS, or federal identity integration (OKTA, SailPoint, Entra ID).
• Section 508 built into solution design rather than tested at the end.
• Experience retiring or refusing a tool after a spike—not only adopting one.
• Human-centered design paired with architecture for internal government users.

Responsibilities

• Stabilize legacy Jenkins jobs used in CI/CD, add monitoring, migrate valuable jobs into Azure DevOps, and retire unused jobs through alternatives analysis—no new Jenkins jobs.
• Maintain Ansible Tower playbooks for application-level desired state on Linux components and support patch testing around Networking’s monthly OS window.
• Own the AWS container registry path: signed and scanned images only, promotion through environments, and no unregistered production containers.
• Implement infrastructure-as-code and compliance-as-code so security and configuration baselines travel with the pipeline.
• Apply the common pipeline pattern (SCA, SAST, secrets scanning, and accessibility checks where UI exists).
• Set Git / Azure Repos branch policies, reviewed merges, and signed commits where required.
• Build operational dashboards for pipeline health and feed post-deploy verification; right-size non-production environments and flag idle spend for FinOps.

Required qualifications

• At least 5 years of platform automation in production, with substantial Jenkins or Azure DevOps and Ansible (or equivalent desired-state tooling).
• AWS production experience, including container images and environment promotion; GovCloud experience is strongly aligned.
• Infrastructure-as-code you can show, with a rollback story.
• Discipline about the OS-owner boundary: you test and configure the application platform; you do not patch the host.
• Able to obtain a DOJ Public Trust at the tier required for privileged access.

Preferred qualifications

• Ansible Tower, Jenkins on AWS, and an AWS container registry in the same environment.
• A Jenkins-to-Azure-DevOps migration you personally executed.
• Secrets scanning, image signing, and policy-as-code in the pipeline.
• FinOps evidence tied to monthly cost reporting.
• AWS, Azure DevOps, or GitHub certification—or equivalent depth.

Responsibilities

• Serve as the single contractor lead to the COR for roadmap, risks, staffing, and monthly status; act as Quality Manager for the order.
• Own ServiceNow SPM functional data (calendars, templates, metadata, and demand/project/product records)—without administering the ServiceNow platform.
• Run the six-stage intake process: intake, triage, assess, recommend, prioritize, and record the board decision.
• Prepare, facilitate, and close PRB, ARB, SWG, Engineering Review Board, and related steering groups.
• Maintain the integrated portfolio roadmap (refresh monthly, baseline quarterly) and escalate unresolved cross-team blockers with recommended decisions.
• Protect the dual track: about 40% of DevOps/API/Platform capacity stays on production; reset sprint scope when Severity-1 events consume build capacity.
• Lead monthly status meetings; attend bi-weekly Portfolio Review Board in person in Washington, DC; deliver Transition In package by Day 90.

Required qualifications

• Qualifies for GSA labor category Information Technology Project Manager Senior: bachelor’s degree and 14 years of relevant experience, or 18 years without the degree.
• At least 5 years leading product or portfolio management in a federal or similarly regulated environment.
• Demonstrated ownership of an integrated roadmap, dependency management, and executive status reporting.
• Hands-on functional use of ServiceNow SPM or an equivalent demand/project system (platform admin not required).
• Experience preparing decision packages for governance boards and writing decision memos non-technical executives can use.
• Able to obtain a DOJ Public Trust; U.S. citizen, lawful permanent resident, or work authorization DOJ will accept.
• Available full-time Monday–Friday, including bi-weekly in-person board support in Washington, DC; able to commit as Key personnel.