Meridian: Forward Deployed Infrastructure Engineer (Senior / Suitland, MD / Hybrid) [TS/SCI]
Spear AI · Suitland, MD · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
First, we need to extract sections.
The posting includes:
- Intro: "As a forward-deployed engineer, you’ll work on-site with customers — writing code, integrating systems, and solving hard problems in the field. You’re part engineer, part technical advisor, and wholly accountable for making the mission succeed. The position requires a current or active U.S. Secret clearance. Spear AI is a growing defense contracting company dedicated to delivering cutting-edge solutions that support our nation’s security. As we expand, we’re building a culture where innovation meets mission-critical work. We operate with a flat organizational structure that empowers every team member to make an impact, collaborate directly with leadership, and contribute to projects that matter. Whether you’re joining our Hardware, Software, or Services division, you’ll work alongside talented professionals who are committed to excellence and advancing the capabilities that keep our nation safe and secure. Spear AI builds sonobuoy sensors that are deployed into the water and collect edge data. We also work with the U.S. Navy to collect and process their SONAR data. You’ll have an opportunity to work on real-world projects that directly impact warfighter capabilities and mission success."
That could be "About the role" or "About the company". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include.
We have content for:
- About the role: description of role, mission, etc.
- Responsibilities: "What You’ll Do" list.
- Requirements: maybe "Who You Are" includes values and traits, but also "Important Skills" and "Nice to have". The posting includes "Important Skills" and "Nice to have". Also "Active Secret clearance required". Also "The position requires a current or active U.S. Secret clearance." So we can put Requirements: includes clearance, maybe some required skills.
- Qualifications: maybe overlapping with Requirements. But we can combine.
- Skills: list of important skills.
- Benefits: "What we offer" list.
- Pay: mention "We offer competitive compensation tailored to your experience, location, and the impact you’ll make." Also "We’re committed to equitable pay and will share a range aligned to your level and geography during the hiring process." Also mention state law salary range upon request. That's specific enough? It says we will share a range upon request. Not a specific number, but it's still content about pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info, albeit not a specific number. It says "We offer competitive compensation tailored to your experience, location, and the impact you’ll make." That's a statement about pay. Also "We’re committed to equitable pay and will share a range aligned to your level and geography during the hiring process." That's also pay. So we can include Pay section with that content.
- Schedule: mention "This is a full-time, exempt position under the Fair Labor Standards Act (FLSA) and is not eligible for overtime pay. Compensation for this position is provided on a salaried basis and is not subject to reduction based on hours worked." That's schedule info (full-time, exempt). So we can include Schedule.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO but there is mention of state law salary range; that's not boilerplate. We'll keep.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details like specific tools: Pulumi, Terraform, Docker, Kubernetes, RHEL, Podman, Helm, GitLab CI/CD, GitHub Actions, AWS, Bash, Python, Go, TypeScript, networking, CMMC, PCI, SOC, Authentik, Keycloak, air-gapped, bare metal, OpenTelemetry, Sentry, SigNoz, edge computing, maritime systems, sensor platforms, AWS GovCloud, government customers, etc.
Also responsibilities list: Design and implement cloud architecture; Develop Infrastructure as Code using Pulumi; Build and maintain GitLab CI/CD and DevSecOps pipelines; Continuously deploy to AWS cloud and air-gapped environments; Monitor applications/services with OpenTelemetry, Sentry, and SigNoz; Enforce CMMC compliance policies and rules; Manage secrets and configuration; Deploy, configure, and troubleshoot infrastructure within customer and air-gapped environments; Support RHEL/Linux-based platforms using Kubernetes, Podman, Docker, and Helm in operational environments; Partner directly with customer engineering teams to integrate, test, and resolve infrastructure issues; Travel to customer sites as needed to support deployments, upgrades, and mission execution.
Also "Who You Are" includes values: fanatical about polish, linted, formatted, fully typed, 100% test coverage, correctness, pride, performance, Lighthouse scores, query speed, dive deep, prototypes, experiments, bleeding edge, upcoming platform features, nightly drops, great teacher, break down concept, make click, get excited.
We need to decide where to put that. Could be under "Qualifications" or "Requirements". The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content goes where.
Typically:
- About the role: overview of role, mission, company.
- Responsibilities: bullet list of duties.
- Requirements: mandatory items (clearance, maybe years experience, etc). Could include "Active Secret clearance required", "Current or active U.S. Secret clearance". Also maybe "Experience supporting classified DoD or Navy environments" is nice to have, not required.
- Qualifications: maybe education, experience? Not explicitly given. Could combine with Requirements.
- Skills: list of important skills (expert in Pulumi/Terraform, Docker/K8s, RHEL, Linux sysadmin, Podman, CI/CD, AWS, scripting, networking, CMMC, etc). Also "Nice to have" could be separate but we could include under Skills as optional.
- Benefits: list from "What we offer".
- Pay: compensation statements.
- Schedule: full-time, exempt.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include.
We have content for:
- About the role: description of role, mission, etc.
- Responsibilities: "What You’ll Do" list.
- Requirements: maybe "Who You Are" includes values and traits, but also "Important Skills" and "Nice to have". The posting includes "Important Skills" and "Nice to have". Also "Active Secret clearance required". Also "The position requires a current or active U.S. Secret clearance." So we can put Requirements: includes clearance, maybe some required skills.
- Qualifications: maybe overlapping with Requirements. But we can combine.
- Skills: list of important skills.
- Benefits: "What we offer" list.
- Pay: mention "We offer competitive compensation tailored to your experience, location, and the impact you’ll make." Also "We’re committed to equitable pay and will share a range aligned to your level and geography during the hiring process." Also mention state law salary range upon request. That's specific enough? It says we will share a range upon request. Not a specific number, but it's still content about pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info, albeit not a specific number. It says "We offer competitive compensation tailored to your experience, location, and the impact you’ll make." That's a statement about pay. Also "We’re committed to equitable pay and will share a range aligned to your level and geography during the hiring process." That's also pay. So we can include Pay section with that content.
- Schedule: mention "This is a full-time, exempt position under the Fair Labor Standards Act (FLSA) and is not eligible for overtime pay. Compensation for this position is provided on a salaried basis and is not subject to reduction based on hours worked." That's schedule info (full-time, exempt). So we can include Schedule.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO but there is mention of state law salary range; that's not boilerplate. We'll keep.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details like specific tools: Pulumi, Terraform, Docker, Kubernetes, RHEL, Podman, Helm, GitLab CI/CD, GitHub Actions, AWS, Bash, Python, Go, TypeScript, networking, CMMC, PCI, SOC, Authentik, Keycloak, air-gapped, bare metal, OpenTelemetry, Sentry, SigNoz, edge computing, maritime systems, sensor platforms, AWS GovCloud, government customers, etc.
Also responsibilities list: Design and implement cloud architecture; Develop Infrastructure as Code using Pulumi; Build and maintain GitLab CI/CD and DevSecOps pipelines; Continuously deploy to AWS cloud and air-gapped environments; Monitor applications/services with OpenTelemetry, Sentry, and SigNoz; Enforce CMMC compliance policies and rules; Manage secrets and configuration; Deploy, configure, and troubleshoot infrastructure within customer and air-gapped environments; Support RHEL/Linux-based platforms using Kubernetes, Podman, Docker, and Helm in operational environments; Partner directly with customer engineering teams to integrate, test, and resolve infrastructure issues; Travel to customer sites as needed to support deployments, upgrades, and mission execution.
Also "Who You Are" includes values: fanatical about polish, linted, formatted, fully typed, 100% test coverage, correctness, pride, performance, Lighthouse scores, query speed, dive deep, prototypes, experiments, bleeding edge, upcoming platform features, nightly drops, great teacher, break down concept, make click, get excited.
We need to decide where to put that. Could be under "Qualifications" or "Requirements". The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content goes where.
Typically:
- About the role: overview of role, mission, company.
- Responsibilities: bullet list of duties.
- Requirements: mandatory items (clearance, maybe years experience, etc). Could include "Active Secret clearance required", "Current or active U.S. Secret clearance". Also maybe "Experience supporting classified DoD or Navy environments" is nice to have, not required.
- Qualifications: maybe education, experience? Not explicitly given. Could combine with Requirements.
- Skills: list of important skills (expert in Pulumi/Terraform, Docker/K8s, RHEL, Linux sysadmin, Podman, CI/CD, AWS, scripting, networking, CMMC, etc). Also "Nice to have" could be separate but we could include under Skills as optional.
- Benefits: list from "What we offer".
- Pay: compensation statements.
- Schedule: full-time, exempt.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- Current or active U.S. Secret clearance ...
Skills
- Expert in Infrastructure as Code using Pulumi or Terraform ...
Benefits
- Unlimited PTO ...
Pay
We offer competitive compensation tailored to your experience, location, and the impact you’ll make. We’re committed to equitable pay and will share a range aligned to your level and geography during the hiring process. In accordance with state law, candidates in jurisdictions such as CA, CO, WA, NY, and others, where applicable, will be provided a good‑faith salary range upon request and throughout the hiring process.
Schedule
This is a full‑time, exempt position under the Fair Labor Standards Act (FLSA) and is not eligible for overtime pay. Compensation for this position is provided on a salaried basis and is not subject to reduction based on hours worked.
We need to ensure we don't duplicate content. Also we need to include "Who You Are" values somewhere. Could be under Requirements or Qualifications. Since we have Requirements and Skills sections, maybe put "Who You Are" under Requirements as personal traits. Or we could create a Qualifications section for those traits. Let's decide: We'll put "Who You Are" under Requirements as they are personal attributes required. Or we could have a Qualifications section for those. The instruction says we can include sections only when posting has real specific content. We have content for both Requirements and Qualifications. We could split: Requirements: clearance, maybe experience? Qualifications: the "Who You Are" traits and maybe education? But there is no explicit education requirement. So maybe we put "Who You Are" under Qualifications. Thus: - Requirements: clearance, maybe "Active Secret clearance required". Also maybe "Experience supporting classified DoD or Navy environments" is nice to have, not required. So we keep only clearance. - Qualifications: the list of personal traits (fanatical about polish, etc). Also maybe "Experience supporting classified DoD or Navy environments" is nice to have, but we could put under Skills as nice to have. But we also have "Important Skills" and "Nice to have". We'll put Important Skills under Skills section. Nice to have could be under Skills as optional, but we could note them as "Nice to have". However we should not invent filler. We can include them as part of Skills list, maybe with a note. Better: Skills section includes both Important Skills and Nice to have, but we can differentiate with subheadings? Not allowed; only