Software Engineer, Cleared (TS/SCI)

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs before "Clearance and Eligibility". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting. Content: - Intro paragraph: "Government technology has failed citizens...". That's about the company/mission. Could be "About the role"? Actually "About the role" heading is for description of role. The intro could be considered "About the role"? But we have a separate "The Role" heading later. The posting includes sections: "Clearance and Eligibility", "The Role", "Location", "What You'll Do", "What You'll Bring", "Strong Candidates May Also...", "What Kaizen Offers" with subsections: Health & Insurance, Family & Time Off, Office & Remote Setup, Wellness, Stipends. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading (not present). No Job ID. We need to include sections only if there is real specific content. We need to decide which sections to include. - About the role: Could include the introductory paragraphs describing the role, mission, maybe "The Role" section. That seems appropriate. - Responsibilities: "What You'll Do" section. - Requirements: Could include "Clearance and Eligibility", "What You'll Bring" (experience), maybe also "Strong Candidates May Also..." as optional but could be part of Requirements or Qualifications. - Qualifications: Could be similar to Requirements; but we need to avoid duplication. Perhaps we put Requirements for mandatory items, Qualifications for preferred? But we have limited headings. - Skills: Could list specific technical skills (React/Next.js, Node.js/TS/Postgres, Palantir, AI coding tools, etc.) - Benefits: "What Kaizen Offers" sections. - Pay: Not mentioned; no salary info. So we should NOT include Pay section. - Schedule: Not mentioned; location hybrid but schedule not specified. So no Schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information; not invent or summarize away detail. Must keep details. We need to format lists with

• for any list of duties/requirements/benefits. Use

  for prose. We need to avoid repeating content; but we must preserve all substantive info. So we need to include everything from the posting, organized under headings. Let's extract content. First, intro paragraphs before "Clearance and Eligibility": "Government technology has failed citizens, public servants, and service members for decades. Kaizen powers America’s application layer. We replace the legacy systems federal agencies run on with modern software, built with craft. The ticketing platform a resident uses to visit a presidential library. The marketplace DoW uses for counter-drone procurement to protect lives and critical infrastructure. The system a Veteran uses to access benefits. We build systems of record, of national consequence. Our AI-native modules and harness allow us to do so in weeks and months, not years. This year, our revenue has grown 35x. Next year, our software will serve over 100 million Americans across dozens of federal agencies. Founded in 2022 and based in New York City and DC, Kaizen has raised $35 million from NEA, a16z, Accel, 776, and Carpenter Capital." That's about the company. Could go under About the role. Next, "Clearance and Eligibility": "This role requires an active Top Secret or TS/SCI clearance. United States citizenship is required, because it is a condition of eligibility for the clearance the role depends on." That's a requirement. Next, "The Role": "Most government software was built for compliance, not for the people who use it. Kaizen is changing that, and the engineers who work here are the reason it's possible. At the senior level, this role carries more than code: you're shaping how AI-native features get designed, scoped, and shipped across a platform that millions of Americans touch when they need something from their government. You'll be one of a small number of engineers with direct influence over what gets built and how: setting technical direction, mentoring teammates, and driving decisions that stick." That's also about the role. Next, "Location": "This is a hybrid role based out of our New York or DC. Candidates must reside in New York or DC or be able to commute to New York City or DC to work out of our office at least three times a week (Tuesdays - Thursdays)." Location info; not a heading we have; maybe we could incorporate into About the role or Responsibilities? But we have no heading for location. Could we put under About the role? It's not about role but location. However we must preserve all substantive info; we could include location as a

  under About the role or maybe under Responsibilities? Better to add a separate section? Not allowed headings besides those list. Could we incorporate location into About the role as a paragraph? That seems okay: About the role can include location details. Next, "What You'll Do": list of responsibilities. We need to turn each bullet into

• . The bullet points are sentences separated by line breaks. We'll make a
  with each as
  • . Next, "What You'll Bring": requirements. List of items. Next, "Strong Candidates May Also...": optional qualifications; could go under Qualifications. Next, "What Kaizen Offers": benefits with subcategories. We need to output Benefits section with maybe subheadings? Not allowed; only

    for section headings. We could keep Benefits as a section and inside we can have

    or

    for each benefit category. But we need to preserve all details. Could we make subheadings using or just plain text? The instruction only says use

    for section headings; doesn't forbid other headings like

    or . But to be safe, we can just use

    with bold text? However we must not invent headings not allowed? It didn't forbid other tags. But to keep simple, we can just list benefits as

    • where each li contains the benefit description (including sub-details). That may lose some structure but preserves all info. We need to ensure we don't omit any detail. Let's extract each piece. **About the role** (maybe combine intro, The Role, Location). We'll produce a few paragraphs. Paragraph 1: Intro about Kaizen. Paragraph 2: The Role description. Paragraph 3: Location. We'll put each as

      . **Responsibilities**: What You'll Do list. Items: - Architect and ship full-stack features end-to-end, from scoping and technical design through build, iteration, and production - Build and integrate against the Palantir stack: Foundry ontologies and pipelines, AIP agents, and Maven Smart System workflows - Build inside classification and data-handling constraints rather than around them - Lead the development of AI-powered product surfaces: intelligent intake flows, real-time constituent assistants, automated case routing, agency operator dashboards - Set technical direction and raise the bar on code quality. Your decisions become the patterns the rest of the team builds on - Engage directly with federal agency stakeholders to translate messy real-world requirements into clean, shippable product - Own platform reliability and performance at government scale: real SLAs, real users, no abstraction layer between you and accountability - Mentor earlier-career engineers through code review, pairing, and direct technical feedback **Requirements**: Clearance and Eligibility + What You'll Bring (mandatory). Also maybe include "3+ years of professional engineering experience..." etc. Let's list: - Active Top Secret or TS/SCI clearance - United States citizenship - 3+ years of professional engineering experience, with a track record of owning complex features and systems, not just executing on them - Hands-on development experience with Palantir Foundry, AIP, or Maven Smart System. You have modeled against the ontology, shipped pipelines or AIP agents, and can say what the platform does well and where you had to work around it - Deep fluency in React / Next.js and Node.js / TypeScript / Postgres. Fast, not just functional - AI coding tools (Cursor, Copilot, Claude) are already baked into how you work. You've shipped with them, and you move measurably faster because of it - You've built something real: a product, an open source project, a system you designed and stood behind - Proven ability to operate in ambiguity: you define the problem as often as you solve it, and you don't stall waiting for the answer to come to you - A genuine orientation toward the end user, the person on the other side of the screen isn't an abstraction to you **Qualifications**: Strong Candidates May Also... list. Items: - Have shipped software inside a classified or otherwise accredited environment, and know where the real friction lives - Have been a Forward Deployed Engineer, or worked a program where Palantir was prime and you were the one making the integration actually work - Have touched federal, state, or local government tech, or have built in other regulated, high-stakes environments where the constraints were real - Have cloud deployment depth: AWS, Vercel, GitHub Actions, ECS/Fargate - Have experience with design systems and component libraries and a clear opinion on when a component is right vs. just functional - Have led technical work in an early-stage environment where the job was figuring it out, not following a playbook **Skills**: Could list specific technical skills from What You'll Bring and maybe others. But we already have many skills in Requirements. However we need a Skills section; we could extract the technical skill set: React/Next.js, Node.js/TypeScript/Postgres, Palantir Foundry, AIP, Maven Smart System, AI coding tools (Cursor, Copilot, Claude), cloud deployment (AWS, Vercel, GitHub Actions, ECS/Fargate), design systems/component libraries. We must not duplicate content? The instruction says preserve ALL substantive information; does not forbid duplication across sections? It says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication might be okay but could be considered redundant. However we could avoid duplication by not repeating same bullets in Skills that are already in Requirements. But we need a Skills section; maybe we can put a concise list of technical skills not covered elsewhere. But we risk omitting some info if we don't include them elsewhere. However the info is already in Requirements; we could still include it in Skills as well, but that would be duplication. The instruction does not explicitly forbid duplication, but says preserve ALL substantive information; duplication preserves it, not losing. It might be acceptable. However they say "Prefer a few substantive sections over many thin ones." Duplication could make sections thin? Not sure. Better to assign Skills to list of technical proficiencies that are explicit: React/Next.js, Node.js/TypeScript/Postgres, Palantir Foundry, AIP, Maven Smart System, AI coding tools, cloud platforms, design systems. We'll keep them. **Benefits**: What Kaizen Offers. We need to capture all benefit details. Let's list them: Health & Insurance: - 100% coverage across the board: medical through Oxford/United (Gold and Platinum PPO plans), dental through Guardian PPO, and vision through Beam — all fully covered for employees, with 100% coverage for dependents. - $100,000 in fully paid life insurance. - FSA and Dependent Care FSA. - One Medical membership, on us — same-day primary care, 24/