Strategic Solutions Architect

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. We have location, workplace, etc. Should we include location? Not a heading; we can put in a short

. The instructions: do NOT repeat job title as heading; do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and workplace in a

. We need sections: About the role (maybe intro paragraph). Responsibilities (list of duties). Requirements (maybe qualifications). Qualifications? Might overlap. Skills (list of skills). Benefits (if present). Pay (if present). Schedule (if present). The posting includes "Why Atlas Tech?" which mentions competitive compensation, comprehensive benefits, opportunities to work on impactful projects, collaborative environment, quotes. Also later: "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." So we have benefits and compensation mentioned but not specific numbers. We should include Benefits section if there is real content: they mention comprehensive benefits, generous benefits package, opportunities to work on impactful projects, collaborative environment, learning, training resources, education reimbursement. That's substantive. Pay: they mention competitive compensation, competitive salary but no specific numbers. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Does "competitive compensation" count as stating them? It's vague but it's stating that there is competitive compensation. It's not a specific number but it's a statement. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive compensation" is somewhat vague but not exactly those placeholders. It's a statement that they offer competitive compensation. I'd say we can include Pay section with that statement. However they also say "competitive salary". So we can include Pay with that statement. Schedule: they mention "Hybrid preferred, remote is optional based on location". That's schedule info. So we can include Schedule section. Thus sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine qualifications and skills? But we have separate headings for Requirements, Qualifications, Skills. We need to decide what to put where. The posting includes "You Have" list: citizenship, clearance, degree, experience, abilities, etc. That's qualifications/requirements. Also "You Will" list is responsibilities. Then there is a list of skills/expertise: networking, compute, storage, cybersecurity, machine learning, data science, software engineering, cloud architecture, Zero Trust, etc. That's skills. So we can map: - About the role: introductory paragraph(s) before "You Will". That includes first paragraph about role, location, workplace maybe. - Responsibilities: the "You Will" bullet points (list). We'll output

• for each. - Requirements: maybe the "You Have" list that includes citizenship, clearance, degree, experience, etc. That's more like qualifications. But we have separate Qualifications heading. Could split: Requirements = mandatory items (citizenship, clearance, degree, experience). Qualifications = preferred items (DoD/DHS experience, etc). However the instruction says prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But we have to use headings only if real content. We could have Requirements and Qualifications both if we have content. But we risk thin sections. Let's see content: "You Have" list includes many items: U.S Citizenship is a requirement; Active Secret Clearance preferred; Bachelor’s Degree ... preferred; equivalent experience considered; 5+ years of experience designing IT solutions; experience within DoW or DHS environments preferred; Demonstrated ability to communicate complex technical concepts to executive and technical audiences; Strong understanding of networking, compute, storage, and cybersecurity; Demonstrated expertise in machine learning, data science, software engineering, and cloud architecture; Experience with Zero Trust architectures, identity, and secure access solutions; Experience designing solutions across hybrid cloud, edge, and on-premises environments; Familiarity with non-FAR based acquisition pathways, e.g. OTAs, Rapid Capabilities Offices, etc.; Familiarity with resilient communications, SDN, SD-LAN, SD-WAN, SASE, and secure mobility; Ability to create architecture diagrams and technical documentation; Exposure to DevSecOps, automation, and infrastructure-as-code is a plus; Excellent written, verbal, and presentation skills. That's a mix of requirements and qualifications. Could treat all as Requirements. Then Skills could be separate: maybe the technical expertise list (networking, compute, storage, cybersecurity, machine learning, data science, software engineering, cloud architecture, Zero Trust, etc.) But that overlaps. Better to follow the headings given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to allocate content accordingly. About the role: introductory paragraph(s) describing role, location, workplace. Responsibilities: the "You Will" list. Requirements: maybe the mandatory items: U.S Citizenship is a requirement; Active Secret Clearance preferred? Actually preferred not required. But we could put citizenship requirement, 5+ years experience, bachelor's degree preferred (maybe qualification). Hmm. Qualifications: maybe the preferred items: DoD/DHS experience, etc. Skills: technical skills list: networking, compute, storage, cybersecurity, machine learning, data science, software engineering, cloud architecture, Zero Trust, identity, secure access, hybrid cloud/edge/on-prem, non-FAR pathways, resilient comms, SDN, etc., architecture diagrams, DevSecOps, automation, IaC, communication skills. Benefits: from "Why Atlas Tech?" and later statements: competitive compensation, comprehensive benefits, opportunities to work on impactful projects, collaborative, innovative environment, transparency, learning, training resources, education reimbursement, generous benefits package, opportunity to make positive impact. Pay: competitive salary, competitive compensation. Schedule: Hybrid preferred, remote optional based on location. We must not include boilerplate like EEO, accessibility, etc. Now produce HTML fragment. We'll need to wrap each section in

  heading then content. For lists, use

  • . For prose,

    . We need to ensure we don't repeat job title. Let's craft. About the role: combine first paragraph: "Atlas Tech is seeking a Strategic Solutions Architect to support our growing portfolio of defense, federal, and commercial technology solutions. This role plays a critical part in shaping technical strategies during the sales lifecycle through partnering closely with clients, business development teams, and technical delivery groups to transform complex requirements into tailored, achievable solutions. The ideal candidate combines strong technical expertise with exceptional communication skills and thrives in environments where innovation and clarity are essential." Then location and workplace: maybe a separate

    with "Location: Charleston, SC / Alexandria, VA / Virginia Beach, VA. Workplace: Hybrid preferred, remote is optional based on location." That seems fine. Responsibilities: list each bullet from "You Will". Let's extract them: - Conduct technical discovery and scoping sessions with prospective clients to understand mission challenges, technology gaps, and desired outcomes - Identify and qualify new business opportunities through direct client interaction, market awareness, and technical capability alignment - Build strong relationships with customer stakeholders, capturing insights that drive solution strategy and pursuit planning - Serve as a trusted technical advisor during early opportunity shaping, influencing requirements and positioning Atlas Tech capabilities - Translate customer needs into tailored architectures, technical roadmaps, and solution concepts - Develop and present solution briefs, white papers, and conceptual designs that clearly articulate mission value - Collaborate with Atlas Tech Operations, Innovation, and Engineering to ensure solution feasibility, compliance, and competitive differentiation - Create architecture diagrams, system models, interface designs, and other solution artifacts for proposals and customer engagements - Support Business Development and Capture Teams through technical strategy, competitive analysis, and solution development - Collaborate with Operations in opportunity shaping to align solution strategies with innovation, technical readiness, customer timelines, and delivery risk, maintaining competitive technical strength - Lead or contribute to the technical portions of Enhanced White Papers, RPPs, RFPs, and RFI responses - Conduct capability demonstrations, proof-of-concepts, and technology evaluations that highlight Atlas Tech’s strengths - Present solutions to customer executives, technical teams, and review boards in clear and compelling ways - Maintain a strong awareness of industry trends, emerging technologies, and mission-focused capabilities relevant to Atlas Tech’s markets - Help refine and evolve Atlas Tech’s offerings based on customer feedback and market signals - Contribute to internal solution development efforts, including new capabilities, service offerings, and GTM strategies That's many items. We'll output as

    • each. Requirements: maybe list mandatory: U.S Citizenship is a requirement; Bachelor’s Degree in Engineering, Computer Science, Information Technology, or related field preferred; equivalent experience considered; 5+ years of experience designing IT solutions; Experience within DoD or DHS environments preferred? Actually that's preferred. But we can include as requirement? Might be okay. But we need to avoid thin sections. Let's include: U.S Citizenship is a requirement; 5+ years of experience designing IT solutions; Bachelor’s Degree in Engineering, Computer Science, Information Technology, or related field preferred; equivalent experience considered. That's four items. Qualifications: maybe list preferred qualifications: Active Secret Clearance preferred; experience within DoD or DHS environments preferred; Demonstrated ability to communicate complex technical concepts to executive and technical audiences; Strong understanding of networking, compute, storage, and cybersecurity; Demonstrated expertise in machine learning, data science, software engineering, and cloud architecture; Experience with Zero Trust architectures, identity, and secure access solutions; Experience designing solutions across hybrid cloud, edge, and on-premises environments; Familiarity with non-FAR based acquisition pathways, e.g. OTAs, Rapid Capabilities Offices, etc.; Familiarity with resilient communications, SDN, SD-LAN, SD-WAN, SASE, and secure mobility; Ability to create architecture diagrams and technical documentation; Exposure to DevSecOps, automation, and infrastructure-as-code is a plus; Excellent written, verbal, and presentation skills. That's many but okay. Skills: maybe we could separate technical skills from soft skills. But we already put communication skills in qualifications. Could make Skills: networking, compute, storage, cybersecurity, machine learning, data science, software engineering, cloud architecture, Zero Trust, identity, secure access, hybrid cloud/edge/on-prem, non-FAR pathways, resilient communications, SDN, SD-LAN, SD-WAN, SASE, secure mobility, architecture diagrams, DevSecOps, automation, infrastructure-as-code. That's a list. But we already listed many of those in qualifications. Might be duplication. To avoid duplication, maybe we combine qualifications and skills into one section? But we have to follow headings if content exists. Could decide to not include Skills section if it's too similar to Qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we should combine Requirements and Qualifications into one section called "Requirements & Qualifications"? But headings are fixed list; we cannot create custom heading. We must use only those headings. If we think Skills is redundant, we could omit it. But we need to ensure we preserve all substantive information. If we omit Skills, we lose the explicit list of technical skills. However those are already captured in Qualifications (which includes many technical skills). So we could omit Skills and still preserve info. Let's see: Qualifications list includes: Strong understanding of networking, compute, storage, and cybersecurity; Demonstrated expertise in machine learning, data science, software engineering, and cloud architecture; Experience with Zero Trust architectures, identity, and secure access solutions; Experience designing solutions across hybrid cloud, edge, and on-premises environments;