Solution Architect
VMD Corp · McLean, VA · 2 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections only if real content. No job title heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
From posting: There's description about role (first paragraph). Could be "About the role". Then "Key Responsibilities include:" list. Then "Required Qualifications Include:" list. Then "Preferred Qualifications:" list. Then "About Xcelerate Solutions:" description (company info). Also maybe "Pay" and "Schedule" not present. Benefits not present. Skills maybe implied but not explicit list. Could combine qualifications and skills? The instruction: Use sections only when posting has real, specific content. So we can have sections: About the role, Responsibilities, Requirements (maybe combine required qualifications), Qualifications (preferred), About the company (maybe not a standard heading but we could use About the role? Actually About the role is separate; we could have About the company as maybe not in list; but allowed headings are limited to those given. We could put company info under About the role? Might not be a standard heading; but we could still use About the role? Might be misrepresent. Better to include only sections that match given headings and have content.
We have content for About the role (initial description). Responsibilities (list). Requirements (maybe required qualifications). Qualifications (preferred). Possibly Skills (could be derived from required qualifications but not explicit list). Better to omit Skills if not explicit.
Benefits, Pay, Schedule: none.
Thus output:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use others? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
From posting: There's description about role (first paragraph). Could be "About the role". Then "Key Responsibilities include:" list. Then "Required Qualifications Include:" list. Then "Preferred Qualifications:" list. Then "About Xcelerate Solutions:" description (company info). Also maybe "Pay" and "Schedule" not present. Benefits not present. Skills maybe implied but not explicit list. Could combine qualifications and skills? The instruction: Use sections only when posting has real, specific content. So we can have sections: About the role, Responsibilities, Requirements (maybe combine required qualifications), Qualifications (preferred), About the company (maybe not a standard heading but we could use About the role? Actually About the role is separate; we could have About the company as maybe not in list; but allowed headings are limited to those given. We could put company info under About the role? Might not be a standard heading; but we could still use About the role? Might be misrepresent. Better to include only sections that match given headings and have content.
We have content for About the role (initial description). Responsibilities (list). Requirements (maybe required qualifications). Qualifications (preferred). Possibly Skills (could be derived from required qualifications but not explicit list). Better to omit Skills if not explicit.
Benefits, Pay, Schedule: none.
Thus output:
About the role
...
Responsibilities
- ... each bullet
Requirements
- ... required qualifications bullets
Qualifications
- ... preferred qualifications bullets
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use others? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could still include About the role and put company info there? Might be okay but could be considered filler. Better to include a section About the role for role description, and maybe another section About the company not allowed. Could we omit company description? That would lose substantive info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must include company description somewhere. If we cannot create a heading not in list, we could embed it in a
without heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't forbid other headings, but suggests using those for sections. Could we add a heading like About the company? It's not in the list but maybe acceptable as it's similar. However they said "e.g." meaning examples, not exhaustive. So we can use other headings if needed. Safer to use About the company as heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, About the company.
We need to ensure no filler like "commensurate with experience". Not present.
Now extract content.
About the role: first paragraph: "Xcelerate solutions is seeking a highly skilled and customer-focused Technical Solution Architect to support our business development and sales teams in securing new opportunities. This role bridges the gap between complex technical solutions and customer business needs, serving as a trusted technical advisor throughout the sales cycle. The ideal candidate brings a strong technical background, excellent communication skills, and a consultative approach to solution development."
That's the role description.
Responsibilities: list after "Key Responsibilities include:" then bullet points with subheadings? Actually they have headings within responsibilities: "Agile & Delivery Alignment:", "Cloud & DevSecOps Expertise:", "Solution Development & Capture Support:" each with sentences. We need to turn each into
- items. Should we preserve the subheadings as part of li text? Yes.
Thus each bullet: start with the heading then the description.
Let's extract:
Agile & Delivery Alignment: Architect solutions that enable Agile and SAFe-aligned delivery, including sprint planning, backlog prioritization, and metrics-driven reporting. Integrate technical architecture with Agile program structures (Product Owners, Scrum Teams, PI Planning, etc.). Ensure solution readiness for MVP and incremental deliveries per Agile Acquisition Frameworks (e.g., TechFAR, Digital Services Playbook)
Cloud & DevSecOps Expertise: Design cloud-native and hybrid architectures using AWS GovCloud, Azure Government, or GCP in compliance with FedRAMP, FISMA, and agency-specific controls. Incorporate Infrastructure as Code (IaC), CI/CD pipelines (e.g., Jenkins, GitLab CI, GitHub Actions), and containerized workloads (Docker, Kubernetes). Define and implement DevSecOps pipelines and automated testing frameworks across development and staging environments.
Solution Development & Capture Support: Lead the design of scalable, secure, and modular solution architectures aligned to solicitation requirements and government enterprise environments. Serve as lead technical writer and architect for RFPs, RFIs, white papers, and oral presentations. Conduct customer discovery sessions and produce compliance-driven artifacts such as system architecture diagrams, technical volumes, and basis of estimates (BOEs). Participate in solutioning sessions, color team reviews, and technical strategy workshops with capture/proposal teams. Present technical solutions to government evaluators and internal leadership during orals and solution walkthroughs. Translate business and mission objectives into technical solutions using cloud services, microservices, and APIs.
Now Required Qualifications Include: list after that.
"Prior experience leading or contributing to technical proposal development, especially in response to government RFPs.
Bachelor’s degree in Computer Science, Engineering, or a related technical field.
7–10 years of experience in a solution architecture, software engineering, or pre-sales technical role supporting federal agencies.
Demonstrated experience architecting enterprise-grade applications using modern programming languages (e.g., Java, Python, .NET Core, Node.js).
Hands-on experience with one or more cloud platforms (AWS, Azure, or GCP) in government environments.
Strong understanding of Agile, DevSecOps, and continuous delivery in federal IT programs.
Must be able to work independently in a fast-paced proposal environment with overlapping deadlines."
Preferred Qualifications: list after that.
"Active Secret or Top Secret clearance.
Certifications such as:AWS Certified Solutions Architect – ProfessionalMicrosoft Certified: Azure Solutions Architect ExpertCertified Scrum Professional (CSP) or SAFe AgilistSecurity+ or CISSPFamiliarity with federal systems development lifecycles (SDLCs) and compliance standards (e.g., NIST 800-53, CMMC, 508 compliance).
Experience supporting agencies such as DHS, DoD, DoJ, DoS"
Note there is missing spaces after colons; we keep as is.
About Xcelerate Solutions: paragraph.
"Founded in 2009 and headquartered in McLean, VA, Xcelerate Solutions (www.xceleratesolutions.com) is one of America's fastest-growing companies. Xcelerate’s culture is defined by our diversified workforce of dynamic and versatile professionals, supported with growth and development opportunities that contribute to individual and company growth. This strong commitment to our employees has been recognized by our inclusion on the Washington Business Journal’s “50 Best Places to Work” list as well as being a “Great Place to Work” certified company with a 4.6 star, and a 99% CEO approval Glassdoor rating. Come find out why Xcelerate Solutions is one of the DC Metro top employers!"
Then EEO etc which we remove.
Now produce HTML.
We'll wrap each section:
About the role
...
Responsibilities
- Agile & Delivery Alignment: Architect solutions that enable Agile and SAFe-aligned delivery, including sprint planning, backlog prioritization, and metrics-driven reporting. Integrate technical architecture with Agile program structures (Product Owners, Scrum Teams, PI Planning, etc.). Ensure solution readiness for MVP and incremental deliveries per Agile Acquisition Frameworks (e.g., TechFAR, Digital Services Playbook)
- Cloud & DevSecOps Expertise: Design cloud-native and hybrid architectures using AWS GovCloud, Azure Government, or GCP in compliance with FedRAMP, FISMA, and agency-specific controls. Incorporate Infrastructure as Code (IaC), CI/CD pipelines (e.g., Jenkins, GitLab CI, GitHub Actions), and containerized workloads (Docker, Kubernetes). Define and implement DevSecOps pipelines and automated testing frameworks across development and staging environments.
- Solution Development & Capture Support: Lead the design of scalable, secure, and modular solution architectures aligned to solicitation requirements and government enterprise environments. Serve as lead technical writer and architect for RFPs, RFIs, white papers, and oral presentations. Conduct customer discovery sessions and produce compliance-driven artifacts such as system architecture diagrams, technical volumes, and basis of estimates (BOEs). Participate in solutioning sessions, color team reviews, and technical strategy workshops with capture/proposal teams. Present technical solutions to government evaluators and internal leadership during orals and solution walkthroughs. Translate business and mission objectives into technical solutions using cloud services, microservices, and APIs.
Requirements
- Prior experience leading or contributing to technical proposal development, especially in response to government RFPs.
- Bachelor’s degree in Computer Science, Engineering, or a related technical field.
- 7–10 years of experience in a solution architecture, software engineering, or pre-sales technical role supporting federal agencies.
- Demonstrated experience architecting enterprise-grade applications using modern programming languages (e.g., Java, Python, .NET Core, Node.js).
- Hands-on experience with one or more cloud platforms (AWS, Azure, or GCP) in government environments.
- Strong understanding of Agile, DevSecOps, and continuous delivery in federal IT programs.
- Must be able to work independently in a fast-paced proposal environment with overlapping deadlines.
Qualifications
- Active Secret or Top Secret clearance.
- Certifications such as:AWS Certified Solutions Architect – ProfessionalMicrosoft Certified: Azure Solutions Architect ExpertCertified Scrum Professional (CSP) or SAFe AgilistSecurity+ or CISSP
- Familiarity with federal systems development lifecycles (SDLCs) and compliance standards (e.g., NIST 800-53, CMMC, 508 compliance).
- Experience supporting agencies such as DHS, DoD, DoJ, DoS
About the company
Founded in 2009 and headquartered in McLean, VA, Xcelerate Solutions (www.xceleratesolutions.com) is one of America's fastest-growing companies. Xcelerate’s culture is defined by our diversified workforce of dynamic and versatile professionals, supported with growth and development opportunities that contribute to individual and company growth. This strong commitment to our employees has been recognized by our inclusion
for prose. It doesn't forbid other headings, but suggests using those for sections. Could we add a heading like About the company? It's not in the list but maybe acceptable as it's similar. However they said "e.g." meaning examples, not exhaustive. So we can use other headings if needed. Safer to use About the company as heading. Thus sections: About the role, Responsibilities, Requirements, Qualifications, About the company. We need to ensure no filler like "commensurate with experience". Not present. Now extract content. About the role: first paragraph: "Xcelerate solutions is seeking a highly skilled and customer-focused Technical Solution Architect to support our business development and sales teams in securing new opportunities. This role bridges the gap between complex technical solutions and customer business needs, serving as a trusted technical advisor throughout the sales cycle. The ideal candidate brings a strong technical background, excellent communication skills, and a consultative approach to solution development." That's the role description. Responsibilities: list after "Key Responsibilities include:" then bullet points with subheadings? Actually they have headings within responsibilities: "Agile & Delivery Alignment:", "Cloud & DevSecOps Expertise:", "Solution Development & Capture Support:" each with sentences. We need to turn each into
About the role
...
Responsibilities
- Agile & Delivery Alignment: Architect solutions that enable Agile and SAFe-aligned delivery, including sprint planning, backlog prioritization, and metrics-driven reporting. Integrate technical architecture with Agile program structures (Product Owners, Scrum Teams, PI Planning, etc.). Ensure solution readiness for MVP and incremental deliveries per Agile Acquisition Frameworks (e.g., TechFAR, Digital Services Playbook)
- Cloud & DevSecOps Expertise: Design cloud-native and hybrid architectures using AWS GovCloud, Azure Government, or GCP in compliance with FedRAMP, FISMA, and agency-specific controls. Incorporate Infrastructure as Code (IaC), CI/CD pipelines (e.g., Jenkins, GitLab CI, GitHub Actions), and containerized workloads (Docker, Kubernetes). Define and implement DevSecOps pipelines and automated testing frameworks across development and staging environments.
- Solution Development & Capture Support: Lead the design of scalable, secure, and modular solution architectures aligned to solicitation requirements and government enterprise environments. Serve as lead technical writer and architect for RFPs, RFIs, white papers, and oral presentations. Conduct customer discovery sessions and produce compliance-driven artifacts such as system architecture diagrams, technical volumes, and basis of estimates (BOEs). Participate in solutioning sessions, color team reviews, and technical strategy workshops with capture/proposal teams. Present technical solutions to government evaluators and internal leadership during orals and solution walkthroughs. Translate business and mission objectives into technical solutions using cloud services, microservices, and APIs.
Requirements
- Prior experience leading or contributing to technical proposal development, especially in response to government RFPs.
- Bachelor’s degree in Computer Science, Engineering, or a related technical field.
- 7–10 years of experience in a solution architecture, software engineering, or pre-sales technical role supporting federal agencies.
- Demonstrated experience architecting enterprise-grade applications using modern programming languages (e.g., Java, Python, .NET Core, Node.js).
- Hands-on experience with one or more cloud platforms (AWS, Azure, or GCP) in government environments.
- Strong understanding of Agile, DevSecOps, and continuous delivery in federal IT programs.
- Must be able to work independently in a fast-paced proposal environment with overlapping deadlines.
Qualifications
- Active Secret or Top Secret clearance.
- Certifications such as:AWS Certified Solutions Architect – ProfessionalMicrosoft Certified: Azure Solutions Architect ExpertCertified Scrum Professional (CSP) or SAFe AgilistSecurity+ or CISSP
- Familiarity with federal systems development lifecycles (SDLCs) and compliance standards (e.g., NIST 800-53, CMMC, 508 compliance).
- Experience supporting agencies such as DHS, DoD, DoJ, DoS
About the company
Founded in 2009 and headquartered in McLean, VA, Xcelerate Solutions (www.xceleratesolutions.com) is one of America's fastest-growing companies. Xcelerate’s culture is defined by our diversified workforce of dynamic and versatile professionals, supported with growth and development opportunities that contribute to individual and company growth. This strong commitment to our employees has been recognized by our inclusion