Software Engineer with Clearance (TS, TS/CSI)
or drop it." It doesn't forbid including company description; but we should include only sections with real content. The "About Gallatin" is a paragraph describing company; could be placed as a
before sections? Probably we can include it as a
before headings. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output something like:
About Gallatin: ...
ThenAbout the Role
... (the paragraph about role)
ThenResponsibilities
- list items from "What You'll Do"
Then
- 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.
Requirements
- list items from "What We're Looking For"
Then
Benefits
- list items from "Why Gallatin?" (compensation, equity grant, healthcare, 401k, unlimited PTO, perks)
Then maybe
Pay
Compensation Range: $80K - $210K
But note: "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." That's benefits. Then later "Compensation Range: $80K - $210K". So we could combine into Benefits section, but also separate Pay if we want. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine compensation and benefits into one Benefits section. But also we have a separate Pay section maybe not needed. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state compensation and benefits, so we can have Benefits section that includes compensation details. Pay section could be redundant. So we will have Benefits section containing compensation range and perks. We also have "Mission and Identity" and "Why Gallatin?" which includes mission description; could be part of About the role? But we already have About the role section. The "Mission and Identity" is more about company mission; could be included as aafter About Gallatin? Might be considered boilerplate? It's substantive but not a required heading. Could be included as a paragraph under About Gallatin? But we already have About Gallatin paragraph. We could add another
for Mission and Identity. However instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine company description and mission into a single introductory paragraph(s). We'll just have a
for About Gallatin and then maybe another
for Mission and Identity. We must not include EEO, equal-opportunity, scam-warning, etc. So remove those lines. We must not include application instructions. We must preserve all substantive information. Let's extract content: About Gallatin paragraph: "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." About The Role paragraph: "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." What You'll Do (Responsibilities): - 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 (Requirements): - 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: "We are building the system that enables faster, smarter logistics decisions in contested environments, and we're doing it with a team of seasoned entrepreneurs, operators, and technologists who have built and scaled solutions in this space before. We hold ourselves to an extremely high standard. We value clear thinking, direct communication, and the kind of ownership that doesn't stop until something actually works. Our mission is to create decision advantage when the stakes are the highest. If we succeed, the system doesn't just run; it gets smarter. We're not building AI for its own sake. We're building it because faster, smarter decisions in the most demanding environments on earth can't wait. If you want to work somewhere the stakes are real and the mission is urgent — you'll fit in here." Why Gallatin? (Benefits/Pay): - The logistics infrastructure that supports America's warfighters and humanitarian disaster responders is overdue for transformation, and we are building it. From defense operations to disaster response, we're solving the hardest problems that keep missions moving when it matters most. Join a team where the mission is the point. - 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. - Compensation Range: $80K - $210K Also note: "Gallatin is an equal opportunity employer..." etc remove. Also note: "This position may require the ability to obtain and maintain a U.S. government security clearance. The successful candidate must be able to work in a classified environment when necessary. We comply with the United States Department of Labor's Pay Transparency provision. Note: Due to the nature of certain government contracts held by this organization, U.S. citizenship is a requirement for all positions at Gallatin. Proof of citizenship will be required prior to employment if selected." This is substantive info about clearance and citizenship; should we include? It's not boilerplate; it's a requirement. Could be part of Requirements. We'll add a bullet: "Must be able to obtain and maintain a U.S. government security clearance (TS/SCI). Must be a U.S. citizen." Actually the posting says: "This position may require the ability to obtain and maintain a U.S. government security clearance. The successful candidate must be able to work in a classified environment when necessary." and "U.S. citizenship is a requirement for all positions at Gallatin." So we can include as bullet under Requirements. We also have "We comply with the United States Department of Labor's Pay Transparency provision." That's maybe boilerplate but it's a statement; could be omitted as it's not substantive? Might be considered legal boilerplate; but it's about pay transparency. Might be okay to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is legal but not EEO; it's pay transparency provision. Might be considered legal boilerplate; safer to remove. Thus we will not include that line. Now produce HTML. We'll have:
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.
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.