Enterprise Architect - Technical Lead
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive information. Include a section only when posting has real specific content for it. So we need sections: maybe "About the role" (the description of responsibilities), "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have actual content. The posting includes responsibilities (list of contributions). It includes required qualifications (list). It includes preferred experience (list). It includes pay range. It includes benefits mention (but not details). It includes schedule (local to Baltimore, willing to go on client site at least 2 days a week). It includes identity statement (camera, picture) maybe not needed? That's part of application instructions? Might be considered boilerplate? It's about identity verification; maybe we keep as part of "About the role"? Probably not needed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Identity statement about being on camera and picture is part of application process; could be considered application instructions. Likely remove. Also "Learn more about additional Steampunk benefits here." is a link; we can keep benefits mention but not the link? Probably keep benefits mention as prose. The "About Steampunk" paragraph about compensation determination and benefits link: we can include Pay section with salary range. Benefits: we have mention of total compensation package and link to learn more; we can include a Benefits section with that statement (but not the link). However we should not invent details; we can keep the sentence: "Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here." That's somewhat generic but it's actual content. It's not placeholder like "varies". So we can include Benefits section with that sentence.
Schedule: "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week." That's schedule info.
Responsibilities: bullet list of contributions.
Requirements: maybe "Required Qualifications" list.
Preferred Experience: could be under "Preferred Qualifications" or "Skills". But we have a section for Skills maybe. However we have "Required Qualifications" and "Preferred Experience". We could combine into Requirements and Preferred sections. But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (maybe includes required qualifications), Qualifications (maybe includes preferred?), Skills (maybe includes open data standards etc). But we need to avoid duplication. Let's map:
- About the role: maybe a brief paragraph summarizing role? The posting starts: "Steampunk is seeking an Enterprise Architect - Technical Lead to direct technical delivery across data, AI governance, and identity-modernization workstreams for a large federal advisory program, providing enterprise-level architectural guidance within defined procurement-neutrality boundaries." That could be About the role.
- Responsibilities: the list of contributions (Direct how data..., Recommend architectural patterns..., Ensure..., Evaluate..., Review..., Explicitly avoid..., Serve as...). That's a list.
- Requirements: maybe the required qualifications list (Ability to obtain clearance, Bachelor's degree, 12+ years..., Demonstrated experience..., Strong knowledge..., Experience translating..., Demonstrated experience leading..., Excellent communication..., Local to Baltimore...). Actually location is schedule; but we can keep location under Schedule.
- Qualifications: maybe the preferred experience list (OCI constraints, FISMA familiarity, TOGAF certification). Could be under Qualifications or Preferred.
- Skills: maybe the specific skills like open data standards, API design, etc. But those are already in required qualifications. Could combine.
Better to follow typical structure: About the role (summary), Responsibilities (list), Requirements (required qualifications), Qualifications (preferred experience), Skills (maybe not needed), Benefits, Pay, Schedule.
We need to ensure we don't create sections with filler. So we will include sections only if we have substantive content.
Let's extract content:
About the role: "Steampunk is seeking an Enterprise Architect - Technical Lead to direct technical delivery across data, AI governance, and identity-modernization workstreams for a large federal advisory program, providing enterprise-level architectural guidance within defined procurement-neutrality boundaries."
That's a sentence. Good.
Responsibilities: list:
- Direct how data, AI governance, and ICAM workstream technical roles divide and execute their work
- Recommend architectural patterns, reference architectures, and governance standards at the enterprise level
- Ensure all technical recommendations and data outputs use open, standard formats and APIs — including data exports with sufficient structural integrity for independent government reconstruction — avoiding proprietary technologies that create vendor lock-in
- Evaluate AI technologies and platforms for open-source/proprietary status, licensing implications, and technical risk to inform governance and compliance recommendations
- Review and quality-assure technical deliverables produced across the data, AI governance, and ICAM workstreams before client delivery
- Explicitly avoid designing or mandating specific system architectures, or selecting specific commercial products/platforms, at a level of detail that would constrain future competitive procurements
- Serve as the senior technical voice in client engagements on architecture-level recommendations
That's 7 bullet points.
Requirements (Required Qualifications):
- Ability to obtain and maintain a U.S. government security clearance
- Bachelor's degree, preferably in Computer Science, Information Systems, Engineering, or a related field
- 12+ years of enterprise architecture experience, including federal technology environments
- Demonstrated experience providing architectural guidance in an advisory capacity without directing specific vendor or product selection
- Strong knowledge of open data standards, API design, and avoiding proprietary vendor lock-in
- Experience translating enterprise architecture patterns into governance standards for a broad technical team
- Demonstrated experience leading and mentoring multidisciplinary technical teams
- Excellent written and verbal communication skills, including experience presenting architecture-level recommendations to senior government stakeholders
- Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week
Note: location also schedule; but we can keep under Requirements and also maybe schedule separate. However schedule section should contain schedule info; we could move location to Schedule and keep Requirements without location. But the requirement includes location; we could keep it under Requirements and not duplicate. But schedule section expects schedule info; we could still have schedule section with that sentence. If we include location in both, it's duplication. Better to put location under Schedule and remove from Requirements. However the requirement list includes location as part of qualifications; but we can treat location as schedule. The instruction: "Prefer a few substantive sections over many thin ones." So we could have Schedule section with that sentence, and Requirements without location. Let's adjust Requirements list to exclude location.
Thus Requirements:
- Ability to obtain and maintain a U.S. government security clearance
- Bachelor's degree, preferably in Computer Science, Information Systems, Engineering, or a related field
- 12+ years of enterprise architecture experience, including federal technology environments
- Demonstrated experience providing architectural guidance in an advisory capacity without directing specific vendor or product selection
- Strong knowledge of open data standards, API design, and avoiding proprietary vendor lock-in
- Experience translating enterprise architecture patterns into governance standards for a broad technical team
- Demonstrated experience leading and mentoring multidisciplinary technical teams
- Excellent written and verbal communication skills, including experience presenting architecture-level recommendations to senior government stakeholders
Qualifications (Preferred Experience):
- Experience operating under organizational-conflict-of-interest (OCI) constraints on a federal advisory contract
- Familiarity with FISMA and federal system authorization processes
- TOGAF certification or equivalent enterprise architecture credential
Skills: maybe we could list specific skills like open data standards, API design, etc. But those are already in Requirements. Could skip Skills section.
Benefits: The posting says: "About Steampunk Steampunk relies on several factors to determine salary, including but not limited to geographic location, contractual requirements, education, knowledge, skills, competencies, and experience. The projected compensation range for this position is $140,000 to $190,000. The estimate displayed represents a typical annual salary range for this position. Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here."
We have Pay section for salary range. Benefits section can include: "Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here." That's substantive.
Pay: "$140,000 to $190,000" (projected compensation range). Could also mention that salary depends on factors etc. But we can keep simple.
Schedule: "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week."
Now we need to output HTML fragment with
headings and appropriate - for lists,
for prose.
We must not include or . No markdown fences.
Let's craft:
About the role
Steampunk is seeking an Enterprise Architect - Technical Lead to direct technical delivery across data, AI governance, and identity-modernization workstreams for a large federal advisory program, providing enterprise-level architectural guidance within defined procurement-neutrality boundaries.
Responsibilities
- Direct how data, AI governance, and ICAM workstream technical roles divide and execute their work
- Recommend architectural patterns, reference architectures, and governance standards at the enterprise level
- Ensure all technical recommendations and data outputs use open, standard formats and APIs — including data exports with sufficient structural integrity for independent government reconstruction — avoiding proprietary technologies that create vendor lock-in
- Evaluate AI technologies and platforms for open-source/proprietary status, licensing implications, and technical risk to inform governance and compliance recommendations
- Review and quality-assure technical deliverables produced across the data, AI governance, and ICAM workstreams before client delivery
- Explicitly avoid designing or mandating specific system architectures, or selecting specific commercial products/platforms, at a level of detail that would constrain future competitive procurements
- Serve as the senior technical voice in client engagements on architecture-level recommendations
Requirements
- Ability to obtain and maintain a U.S. government security clearance
- Bachelor's degree, preferably in Computer Science, Information Systems, Engineering, or a related field
- 12+ years of enterprise architecture experience, including federal technology environments
- Demonstrated experience providing architectural guidance in an advisory capacity without directing specific vendor or product selection
- Strong knowledge of open data standards, API design, and avoiding proprietary vendor lock-in
- Experience translating enterprise architecture patterns into governance standards for a broad technical team
- Demonstrated experience leading and mentoring multidisciplinary technical teams
- Excellent written and verbal communication skills, including experience presenting architecture-level recommendations to senior government stakeholders
Qualifications
- Experience operating under organizational-conflict-of-interest (OCI) constraints on a federal advisory contract
- Familiarity with FISMA and federal system authorization processes
- TOGAF certification or equivalent enterprise architecture credential
Benefits
Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here.
Pay
$140,000 to $
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive information. Include a section only when posting has real specific content for it. So we need sections: maybe "About the role" (the description of responsibilities), "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have actual content. The posting includes responsibilities (list of contributions). It includes required qualifications (list). It includes preferred experience (list). It includes pay range. It includes benefits mention (but not details). It includes schedule (local to Baltimore, willing to go on client site at least 2 days a week). It includes identity statement (camera, picture) maybe not needed? That's part of application instructions? Might be considered boilerplate? It's about identity verification; maybe we keep as part of "About the role"? Probably not needed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Identity statement about being on camera and picture is part of application process; could be considered application instructions. Likely remove. Also "Learn more about additional Steampunk benefits here." is a link; we can keep benefits mention but not the link? Probably keep benefits mention as prose. The "About Steampunk" paragraph about compensation determination and benefits link: we can include Pay section with salary range. Benefits: we have mention of total compensation package and link to learn more; we can include a Benefits section with that statement (but not the link). However we should not invent details; we can keep the sentence: "Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here." That's somewhat generic but it's actual content. It's not placeholder like "varies". So we can include Benefits section with that sentence. Schedule: "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week." That's schedule info. Responsibilities: bullet list of contributions. Requirements: maybe "Required Qualifications" list. Preferred Experience: could be under "Preferred Qualifications" or "Skills". But we have a section for Skills maybe. However we have "Required Qualifications" and "Preferred Experience". We could combine into Requirements and Preferred sections. But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (maybe includes required qualifications), Qualifications (maybe includes preferred?), Skills (maybe includes open data standards etc). But we need to avoid duplication. Let's map: - About the role: maybe a brief paragraph summarizing role? The posting starts: "Steampunk is seeking an Enterprise Architect - Technical Lead to direct technical delivery across data, AI governance, and identity-modernization workstreams for a large federal advisory program, providing enterprise-level architectural guidance within defined procurement-neutrality boundaries." That could be About the role. - Responsibilities: the list of contributions (Direct how data..., Recommend architectural patterns..., Ensure..., Evaluate..., Review..., Explicitly avoid..., Serve as...). That's a list. - Requirements: maybe the required qualifications list (Ability to obtain clearance, Bachelor's degree, 12+ years..., Demonstrated experience..., Strong knowledge..., Experience translating..., Demonstrated experience leading..., Excellent communication..., Local to Baltimore...). Actually location is schedule; but we can keep location under Schedule. - Qualifications: maybe the preferred experience list (OCI constraints, FISMA familiarity, TOGAF certification). Could be under Qualifications or Preferred. - Skills: maybe the specific skills like open data standards, API design, etc. But those are already in required qualifications. Could combine. Better to follow typical structure: About the role (summary), Responsibilities (list), Requirements (required qualifications), Qualifications (preferred experience), Skills (maybe not needed), Benefits, Pay, Schedule. We need to ensure we don't create sections with filler. So we will include sections only if we have substantive content. Let's extract content: About the role: "Steampunk is seeking an Enterprise Architect - Technical Lead to direct technical delivery across data, AI governance, and identity-modernization workstreams for a large federal advisory program, providing enterprise-level architectural guidance within defined procurement-neutrality boundaries." That's a sentence. Good. Responsibilities: list: - Direct how data, AI governance, and ICAM workstream technical roles divide and execute their work - Recommend architectural patterns, reference architectures, and governance standards at the enterprise level - Ensure all technical recommendations and data outputs use open, standard formats and APIs — including data exports with sufficient structural integrity for independent government reconstruction — avoiding proprietary technologies that create vendor lock-in - Evaluate AI technologies and platforms for open-source/proprietary status, licensing implications, and technical risk to inform governance and compliance recommendations - Review and quality-assure technical deliverables produced across the data, AI governance, and ICAM workstreams before client delivery - Explicitly avoid designing or mandating specific system architectures, or selecting specific commercial products/platforms, at a level of detail that would constrain future competitive procurements - Serve as the senior technical voice in client engagements on architecture-level recommendations That's 7 bullet points. Requirements (Required Qualifications): - Ability to obtain and maintain a U.S. government security clearance - Bachelor's degree, preferably in Computer Science, Information Systems, Engineering, or a related field - 12+ years of enterprise architecture experience, including federal technology environments - Demonstrated experience providing architectural guidance in an advisory capacity without directing specific vendor or product selection - Strong knowledge of open data standards, API design, and avoiding proprietary vendor lock-in - Experience translating enterprise architecture patterns into governance standards for a broad technical team - Demonstrated experience leading and mentoring multidisciplinary technical teams - Excellent written and verbal communication skills, including experience presenting architecture-level recommendations to senior government stakeholders - Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week Note: location also schedule; but we can keep under Requirements and also maybe schedule separate. However schedule section should contain schedule info; we could move location to Schedule and keep Requirements without location. But the requirement includes location; we could keep it under Requirements and not duplicate. But schedule section expects schedule info; we could still have schedule section with that sentence. If we include location in both, it's duplication. Better to put location under Schedule and remove from Requirements. However the requirement list includes location as part of qualifications; but we can treat location as schedule. The instruction: "Prefer a few substantive sections over many thin ones." So we could have Schedule section with that sentence, and Requirements without location. Let's adjust Requirements list to exclude location. Thus Requirements: - Ability to obtain and maintain a U.S. government security clearance - Bachelor's degree, preferably in Computer Science, Information Systems, Engineering, or a related field - 12+ years of enterprise architecture experience, including federal technology environments - Demonstrated experience providing architectural guidance in an advisory capacity without directing specific vendor or product selection - Strong knowledge of open data standards, API design, and avoiding proprietary vendor lock-in - Experience translating enterprise architecture patterns into governance standards for a broad technical team - Demonstrated experience leading and mentoring multidisciplinary technical teams - Excellent written and verbal communication skills, including experience presenting architecture-level recommendations to senior government stakeholders Qualifications (Preferred Experience): - Experience operating under organizational-conflict-of-interest (OCI) constraints on a federal advisory contract - Familiarity with FISMA and federal system authorization processes - TOGAF certification or equivalent enterprise architecture credential Skills: maybe we could list specific skills like open data standards, API design, etc. But those are already in Requirements. Could skip Skills section. Benefits: The posting says: "About Steampunk Steampunk relies on several factors to determine salary, including but not limited to geographic location, contractual requirements, education, knowledge, skills, competencies, and experience. The projected compensation range for this position is $140,000 to $190,000. The estimate displayed represents a typical annual salary range for this position. Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here." We have Pay section for salary range. Benefits section can include: "Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here." That's substantive. Pay: "$140,000 to $190,000" (projected compensation range). Could also mention that salary depends on factors etc. But we can keep simple. Schedule: "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week." Now we need to output HTML fragment with
headings and appropriate - for lists,
for prose.
We must not include or . No markdown fences.
Let's craft:
About the role
Steampunk is seeking an Enterprise Architect - Technical Lead to direct technical delivery across data, AI governance, and identity-modernization workstreams for a large federal advisory program, providing enterprise-level architectural guidance within defined procurement-neutrality boundaries.
Responsibilities
- Direct how data, AI governance, and ICAM workstream technical roles divide and execute their work
- Recommend architectural patterns, reference architectures, and governance standards at the enterprise level
- Ensure all technical recommendations and data outputs use open, standard formats and APIs — including data exports with sufficient structural integrity for independent government reconstruction — avoiding proprietary technologies that create vendor lock-in
- Evaluate AI technologies and platforms for open-source/proprietary status, licensing implications, and technical risk to inform governance and compliance recommendations
- Review and quality-assure technical deliverables produced across the data, AI governance, and ICAM workstreams before client delivery
- Explicitly avoid designing or mandating specific system architectures, or selecting specific commercial products/platforms, at a level of detail that would constrain future competitive procurements
- Serve as the senior technical voice in client engagements on architecture-level recommendations
Requirements
- Ability to obtain and maintain a U.S. government security clearance
- Bachelor's degree, preferably in Computer Science, Information Systems, Engineering, or a related field
- 12+ years of enterprise architecture experience, including federal technology environments
- Demonstrated experience providing architectural guidance in an advisory capacity without directing specific vendor or product selection
- Strong knowledge of open data standards, API design, and avoiding proprietary vendor lock-in
- Experience translating enterprise architecture patterns into governance standards for a broad technical team
- Demonstrated experience leading and mentoring multidisciplinary technical teams
- Excellent written and verbal communication skills, including experience presenting architecture-level recommendations to senior government stakeholders
Qualifications
- Experience operating under organizational-conflict-of-interest (OCI) constraints on a federal advisory contract
- Familiarity with FISMA and federal system authorization processes
- TOGAF certification or equivalent enterprise architecture credential
Benefits
Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here.
Pay
$140,000 to $
for prose. We must not include or . No markdown fences. Let's craft:
About the role
Steampunk is seeking an Enterprise Architect - Technical Lead to direct technical delivery across data, AI governance, and identity-modernization workstreams for a large federal advisory program, providing enterprise-level architectural guidance within defined procurement-neutrality boundaries.
Responsibilities
- Direct how data, AI governance, and ICAM workstream technical roles divide and execute their work
- Recommend architectural patterns, reference architectures, and governance standards at the enterprise level
- Ensure all technical recommendations and data outputs use open, standard formats and APIs — including data exports with sufficient structural integrity for independent government reconstruction — avoiding proprietary technologies that create vendor lock-in
- Evaluate AI technologies and platforms for open-source/proprietary status, licensing implications, and technical risk to inform governance and compliance recommendations
- Review and quality-assure technical deliverables produced across the data, AI governance, and ICAM workstreams before client delivery
- Explicitly avoid designing or mandating specific system architectures, or selecting specific commercial products/platforms, at a level of detail that would constrain future competitive procurements
- Serve as the senior technical voice in client engagements on architecture-level recommendations
Requirements
- Ability to obtain and maintain a U.S. government security clearance
- Bachelor's degree, preferably in Computer Science, Information Systems, Engineering, or a related field
- 12+ years of enterprise architecture experience, including federal technology environments
- Demonstrated experience providing architectural guidance in an advisory capacity without directing specific vendor or product selection
- Strong knowledge of open data standards, API design, and avoiding proprietary vendor lock-in
- Experience translating enterprise architecture patterns into governance standards for a broad technical team
- Demonstrated experience leading and mentoring multidisciplinary technical teams
- Excellent written and verbal communication skills, including experience presenting architecture-level recommendations to senior government stakeholders
Qualifications
- Experience operating under organizational-conflict-of-interest (OCI) constraints on a federal advisory contract
- Familiarity with FISMA and federal system authorization processes
- TOGAF certification or equivalent enterprise architecture credential
Benefits
Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here.
Pay
$140,000 to $