Jobs · Maryland

Systems Architect, Advisor

Peraton · Windsor Mill, MD · 1 mo ago
Hybrid$135k–$216k/yrFull-time
We need to output HTML fragment with sections: About the role (but we must not repeat job title as heading; we have "About The Role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We have content: "About Peraton" (company description) maybe not needed? It's not a section heading per list; we can include as

maybe. Then "About The Role" repeated twice. We need to include a section heading for About the role? The instruction says we can use heading "About the role". It's a section heading. So we should output

About the role

then content. We must preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. Remove "EEO:Equal opportunity employer..." etc. Also remove "Application Statements:" maybe considered boilerplate? It's about application period, on-camera interview, AI prohibition. That might be considered application instructions; we should remove application instructions. The instruction says remove application instructions. So we should drop the "Application Statements:" paragraph. Also remove "EEO:" line. We need to include sections: About the role (maybe includes description), Responsibilities (the "What you'll do:" bullet list), Qualifications (maybe split into Required Skills and Preferred Qualifications), Benefits (Benefits Statement), Pay (Target Salary Range). Possibly Schedule not present, so omit. We must not create sections with filler like "commensurate with experience". We have actual salary range and benefits. We need to use
  • for any list of duties/requirements/benefits. So responsibilities list: each bullet after "What you'll do:" is a sentence; we can make each as
  • . Qualifications: Required Skills list: each bullet? The text: "Required Skills: Minimum of 8 years with BS/BA.8+ years of architect experience of complex enterprise or mission systems within federal, defense, or intelligence environments.US Citizen with the ability to obtain a Public Trust clearance.Experience creating and managing enterprise architecture artifacts using industry-standard architecture. frameworks and modeling methodologies.Strong background in systems engineering, solution design, and multi-domain integration.Hands-on familiarity with cloud architectures, microservices, data engineering, and cybersecurity principles.Proven ability to partner with senior leaders, including IT Directors, CIO organizations, and program executives." It seems like a run-on; we need to split into sensible items. Could break by periods. We'll produce
    • Minimum of 8 years with BS/BA.
    • etc. But need to preserve all info. We'll just split at periods. Preferred Qualifications: "Active public trust clearanceMaster's DegreePMP, ITIL, SAFe, or cloud certifications". We'll split. Benefits: "Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits." We'll make a
      • for each benefit? Could list them as items. We'll split by commas and "and". Might be lengthy but okay. Pay: "Target Salary Range: $135,000 - $216,000. This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay." We'll put that as

        maybe, but instruction: Use

        • for any list of duties/requirements/benefits, and

          for prose. So Pay is prose, not a list, so

          . Benefits is a list, so

          • . Responsibilities list:
            • . Qualifications: we have Required Skills and Preferred Qualifications; both are lists, so
              • . Could also have a heading "Qualifications" then subheadings? Not required; we can just have one Qualifications section with two sublists maybe with headings? But we only allowed headings from list; we could add

                Required Skills

                and

                Preferred Qualifications

                as subheadings? The instruction says use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We could have Qualifications heading and then inside we can have

                for prose? But we have list items; we could just put

                • directly under Qualifications heading. For Preferred Qualifications we could also include under same list? Might be ambiguous. Better to have two sections: Required Skills and Preferred Qualifications as separate headings? Not in the list but maybe acceptable as they are subcategories. However instruction: "Use

                  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. Safer to stick to those examples. So we could have a single Qualifications section and include both required and preferred as list items, maybe differentiate with text inside
                • . Eg:
                • Required: Minimum of 8 years with BS/BA.
                • etc. And
                • Preferred: Active public trust clearance
                • . That preserves info. Similarly Skills: we could have Skills section but we already have qualifications covering skills; maybe we can omit Skills. We need to include About the role section: we have description about role: "The Defense Mission and Health Solutions team, Benefits, Claims & Integrity Solutions Operating Unit seeks a Lead System Architect to support our Health and Human Services (HHS) and Centers for Medicare and Medicaid Services (CMS) customer delivery and be part of the leadership for CMS Consumer Information and Insurance Oversight (CCIIO) initiatives. The Lead System Architect will support mission-critical programs within a fast-paced, highly collaborative environment. In this role, you will define and guide the architectural vision for complex enterprise systems, ensuring alignment with customer objectives, program leadership, and corporate technology strategies. This position works closely with the IT Director to drive modernization initiatives, strengthen architecture governance, and ensure end-to-end technical integrity across the enterprise." We'll put that as

                  under About the role. Now Responsibilities: list each bullet from "What you'll do:" which includes multiple sentences separated by line breaks? Actually it's a paragraph with line breaks? The text: "Design and maintain the end-to-end technical architecture for a large-scale federal eligibility processing platform, spanning document intake, verification workflows, case management, and consumer communications across cloud and on-premises environmentsLead architecture decisions for containerized application deployments, ensuring system integrations between BPM platforms, rules engines, OCR/ICR document processing, and federal data exchange APIs meet CMS security and performance requirementsEvaluate, recommend, and obtain approval for new COTS and AI/ML tools that enhance operational throughput including intelligent document processing, robotic process automation, and analytics platforms while ensuring FedRAMP authorization compliancePartner with the IT Director, program leadership, and CMS stakeholders to translate evolving policy requirements (e.g., new federal mandates, regulatory changes) into actionable system design updates with minimal disruption to production operationsOwn the system security posture including ATO maintenance, FISMA compliance, vulnerability remediation SLAs, and data loss prevention controlsDrive data architecture decisions for a central database, including schema design, file synchronization with federal exchange systems, and API integration with external data sources" It seems missing punctuation; we can split by capital letters after a lowercase? Better to split by each verb phrase. We'll just make each sentence as an item by splitting at the capital letter after a period? There are no periods. We'll insert periods logically: We can treat each clause separated by a capital letter after a lowercase? Eg: "Design and maintain..." then "Lead architecture decisions..." then "Evaluate, recommend..." then "Partner with..." then "Own the system..." then "Drive data architecture...". We'll make six items. Now Benefits: list each benefit: medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, company paid holidays. Also note "A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits." That's a link; we can include as

                • maybe. Now Pay: we have paragraph. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

                  About the role

                  ... (the role description)

                  Responsibilities

                  • Design and maintain the end-to-end technical architecture for a large-scale federal eligibility processing platform, spanning document intake, verification workflows, case management, and consumer communications across cloud and on-premises environments.
                  • Lead architecture decisions for containerized application deployments, ensuring system integrations between BPM platforms, rules engines, OCR/ICR document processing, and federal data exchange APIs meet CMS security and performance requirements.
                  • Evaluate, recommend, and obtain approval for new COTS and AI/ML tools that enhance operational throughput including intelligent document processing, robotic process automation, and analytics platforms while ensuring FedRAMP authorization compliance.
                  • Partner with the IT Director, program leadership, and CMS stakeholders to translate evolving policy requirements (e.g., new federal mandates, regulatory changes) into actionable system design updates with minimal disruption to production operations.
                  • Own the system security posture including ATO maintenance, FISMA compliance, vulnerability remediation SLAs, and data loss prevention controls.
                  • Drive data architecture decisions for a central database, including schema design, file synchronization with federal exchange systems, and API integration with external data sources.

                  Qualifications

                  • Required: Minimum of 8 years with BS/BA.
                  • Required: 8+ years of architect experience of complex enterprise or mission systems within federal, defense, or intelligence environments.
                  • Required: US Citizen with the ability to obtain a Public Trust clearance.
                  • Required: Experience creating and managing enterprise architecture artifacts using industry-standard architecture frameworks and modeling methodologies.
                  • Required: Strong background in systems engineering, solution design, and multi-domain integration.
                  • Required: Hands-on familiarity with cloud architectures, microservices, data engineering, and cybersecurity principles.
                  • Required: Proven ability to partner with senior leaders, including IT Directors, CIO organizations, and program executives.
                  • Preferred: Active public trust clearance.
                  • Preferred: Master's Degree.
                  • Preferred: PMP, ITIL, SAFe, or cloud certifications.

                  Benefits

                  • Medical
                  • Dental
                  • Vision
                  • Life
                  • Health savings account
                  • Short/long term disability
                  • EAP
                  • Parental leave
                  • 401(k)
                  • Paid time off (PTO) for vacation
                  • Company paid holidays
                  • Full listing of available benefits:

Similar jobs

Advisor IT Systems Advisor

EnbridgeHouston, TX· 3 wk ago
Information Technology$82k–$120k/yrapply on enbridge.wd3.myworkdayjobs.com