Enterprise Architect

Job Description

Job Description

Position summary

Keeps the current OJP architecture understandable and writes the target state the boards will use. Produces alternative analyses on working evidence, including code or an API contract when a slide is not enough.

Mission on this order

Stop duplicate products and tool sprawl by making current-state fit, target-state alignment, cost, and lock-in visible before anything is built.

Where the seat sits

Team 1 — Portfolio Governance and Architecture

Reports to the Portfolio / Product Manager. Owns architecture content and the Enterprise Architecture Repository. Architecture standards go to the Standards Working Group or Architecture Review Board for approval.

Full time, predominantly remote on Government equipment. In-person support when the Architecture Review Board or headquarters working session requires it.

Responsibilities

· Perform enterprise, application, software, data, solution, technical, and business architecture for products in this family.

· Administer the existing Government-furnished Enterprise Architecture Repository: content, user support, monthly completeness, and integration with ServiceNow. Every alternatives analysis, standard, and decision lands in the repository the same week as the board decision.

· Own the alternatives analysis for IT demand requests. Typical volume is 8 to 12 analyses a year, each about 80 to 200 hours. Options are keep, extend, buy, build, retire, or combine.

· Publish the target-state architecture and a standards backlog each quarter. Principles: API-first, containers and infrastructure-as-code over one-off servers, one approved toolchain per capability, elastic scale, automatic failure handling, and a documented exit from every commercial product.

· Approve feasibility scores prepared by the Solution Architect. Recommend architecture standards to the Standards Working Group and Architecture Review Board.

· Keep the current state runnable and understood: WSO2 API Manager, legacy Jenkins, Ansible, and the Azure DevOps organization.

· Require a time-boxed spike when architecture uncertainty is high. Review spike results before they become a standard.

· Evaluate blockchain, low-code, no-code, and other emerging tools with the same criteria as any other product.

· Support Authority to Operate evidence for products in this family. The Security team remains the risk owner. FedRAMP is preferred for new products.

· Do not silently change another team’s product. Report defects; the owning team remediates.

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 with connecting architecture decisions to a demand system such as ServiceNow.

· Ability to review an API contract, a pipeline, or a short proof of concept and decide whether it is evidence enough for a board.

· 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 rather than the certificate alone.

· Experience writing standards that product teams can follow without a meeting.

FinOps or tool-rationalization analyses that led to a real retirement.

\nCompany Description

Digital HIE is an information technology company focused on connecting Data, Modernizing digital platforms and Engineering secure solutions for public and private organizations.

Company Description

Digital HIE is an information technology company focused on connecting Data, Modernizing digital platforms and Engineering secure solutions for public and private organizations.