Software Engineer with Clearance (TS, TS/CSI)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes:
- About Gallatin (company description) – not a required heading but could be "About Gallatin"? The instructions say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list "About Gallatin" but we could include as a heading? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can include other headings if appropriate? Probably we should stick to those categories. The posting has "About Gallatin" and "About The Role". We could treat "About The Role" as a heading (maybe "About the role"). The "About Gallatin" could be omitted or placed in a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can include other headings if appropriate? Probably we should stick to those categories. The posting has "About Gallatin" and "About The Role". We could treat "About The Role" as a heading (maybe "About the role"). The "About Gallatin" could be omitted or placed in a
without heading? The instruction: "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." It doesn't forbid other headings. But they gave examples; we can include "About Gallatin" as a heading if we want, but better to follow the examples: maybe we include "About the role" (they have "About The Role") and then sections like Responsibilities (What You'll Do), Requirements (What We're Looking For), Qualifications (maybe same as Requirements), Skills (Technical Proficiency etc), Benefits (Why Gallatin? plus compensation details), Pay (Compensation range), Schedule (maybe not present). We need to avoid sections with filler like "commensurate with experience" etc. Pay section: they have compensation range $80K - $210K and also statement "Compensation: Gallatin offers competitive compensation commensurate with experience." That's filler; we should not include Pay section if only filler? But they also give a range, which is substantive. So we can include Pay with the range. However we must not include placeholder like "commensurate with experience". We can include the range and maybe mention equity grant, healthcare, 401k, unlimited PTO as benefits. So Benefits section can include those. Schedule: not mentioned; we should not create Schedule section. We need to preserve all substantive information; not invent or summarize away detail. So we need to include details from each section. Let's parse content: About Gallatin: paragraph about rebuilding logistics infrastructure, AI systems, etc. About The Role: paragraph about cleared engineers, building demo-able end-to-end flows, collaborate with team, etc. What You'll Do: bullet list (but in prose). Items: - Build and deliver features that support our mission statement - Extend our existing API layer with performant CRUD methods, with a focus on performance and accuracy - Collaborate with UX team and backend developers on rapid feature buildouts - Contribute tested, production-ready code that passes our CI/CD pipeline - Technical depth in at least one of these areas is preferred: Typescript, Python, SQL, Vue.js - Design and maintain data models and pipelines that power our Navigator platform - Define and evolve relational database schemas and to represent complex real-world entities - Build data pipelines to ingest, transform, and distribute data between systems - Leverage our semantic data modeling SDK to architect efficient storage and retrieval methods - Collaborate with cross-functional teammates to improve our systems and practices - Work closely with product managers, UX designers, and other engineers to ensure features and data models align with user needs and mission outcomes. - Contribute to engineering best practices: from code reviews and documentation, to refining CI/CD pipelines, helping us foster a culture of excellence. - Help define best practices, continuously improve CI/CD workflows, while keeping DX at the forefront! What We’re Looking For: bullet list: - Candidates with Top Secret Clearance (TS or TS/SCI preferred) - Technical Proficiency - Comfortable debugging and navigating issues across the entire tech stack - Familiarity with HTTP request codes - Experience developing backend APIs or services in a strongly-typed language - Data modeling and architecture - Hands-on experience with relational databases – designing schemas, writing efficient queries, and ensuring data integrity and performance - Experience with processing data streams and/or building or maintaining data pipelines/ETL processes to handle complex data flows between multiple systems - Great communicator - Experience working closely with diverse teams (engineering, product, design) to drive projects to completion - Clear and concise communication, whether in designing system architecture or everyday documentation - Growth mindset - Always seeing to learn and stay current with industry trends and tools - Bonus Points: - Experience building offline-first or progressive web applications (PWAs) that operate smoothly with limited or intermittent connectivity. - Hands-on experience with DevOps or Infrastructure-as-Code (CI/CD pipelines, Docker/Kubernetes, Terraform, etc.) - Experience with cloud-based architecture such as AWS, Azure, Palantir Foundry - Contributions to open-source projects Mission and Identity: paragraph about mission. Why Gallatin?: paragraph about mission and compensation details: "Compensation: Gallatin offers competitive compensation commensurate with experience. Actual compensation may vary based on experience, skills, and location. In addition to base salary, we offer a generous equity grant, full healthcare coverage, 401k, unlimited PTO, and the perks of working in a high-caliber, mission-driven environment." Then EEO boilerplate etc to remove. Compensation Range: $80K - $210K We need to output HTML with sections: maybe:
About Gallatin
...
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
maybe combine technical proficiency etc? Could be separate but we can put under Requirements. But we need to avoid thin sections. Perhaps combine Requirements and Skills into one? But they said prefer few substantive sections over many thin ones. We could have: - About Gallatin - About the role - Responsibilities - Requirements (including technical skills, clearance, etc) - Benefits (including equity, healthcare, 401k, unlimited PTO, mission-driven environment) - Pay (range $80K - $210K) We should not include Schedule. We must not include filler like "commensurate with experience" in Pay section; we can just give the range. For Benefits we can list equity grant, full healthcare coverage, 401k, unlimited PTO, and mention mission-driven environment. We need to preserve all substantive information: we must not lose details like "Top Secret Clearance (TS or TS/SCI preferred)", "Technical Proficiency", etc. So we need to include those in Requirements. We need to ensure we don't repeat the job title as heading; we aren't. We must not include boilerplate like EEO, scam warning, etc. We need to output only HTML fragment. Let's craft. First, About Gallatin paragraph: combine the two sentences? Actually there is a paragraph: "About Gallatin At Gallatin, we are rebuilding logistics infrastructure for the national security missions of the United States and allied partners. We build AI systems that determine how logistics decisions are made — not just how they're executed. From factory to foxhole, we operate at the layer where data becomes decisions, and decisions make the advantage." We'll put that in. About the role: paragraph: "About The Role We are looking for cleared (TS or TS/SCI required) engineers who can build demo-able end-to-end flows that make resupply operations smarter, faster, and more resilient. You'll collaborate daily with a top notch team of engineers who value thoughtful design and practical impact. If you’re looking to build systems that go beyond the usual SaaS cloud-based product, this could be your next chapter." We'll put that. Responsibilities: list items from "What You'll Do". We'll convert each sentence to
- ... ...
- for benefits.
Pay: we have range $80K - $210K.