> Markdown version of [/jobs/ext/4549220-software-engineer](https://www.wearedevelopers.com/jobs/ext/4549220-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Engineer

- **Company:** Dow
- **Location:** New York, NY, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Amazon Web Services, JIRA, Cloud Computing, Software Quality, Code Review, Cursor, Github, PostgreSQL, Node.Js, Open Source Technology, Scrum Methodology, Microsoft Copilot, Next.js, TypeScript, ReactJS, System Availability, Palantir Foundry, AI Coding Agents, Material UI, AWS Fargate, Figma, Claude
- **Published:** November 3, 2026
- **Apply:** https://startup.jobs/senior-software-engineer-kaizen-labs-10658433

## About the Role

* 5+ years of professional engineering experience, with a track record of owning complex features and systems, not just executing on them
 * Deep fluency in React / Next.js and Node.js / TypeScript / Postgres: not just comfortable, but fast
 * AI coding tools (Cursor, Copilot, Claude) are already baked into how you work. You're not planning to explore them someday; you've shipped with them
 * Something real you've built: a product, an open source project, a thing you couldn't stop working on
 * You operate well with ambiguity. You don't wait to be handed the answer.
 * You actually care whether the person on the other end of the screen has a good experience

Strong Candidates May Also...

 * You've touched federal, state, or local government tech, or you understand the constraints of building for regulated, high-stakes environments
 * Hands-on experience with Palantir Foundry or AIP: you've modeled against the ontology or shipped pipelines or AIP agents
 * Cloud deployment experience (AWS, Vercel, GitHub Actions, ECS/Fargate)
 * Exposure to design systems and component libraries: you know the difference between a component that's functional and one that's right
 * You've led technical work in an early-stage environment where figuring it out was the job

## Description

This is not a ticket-grinder role. You're not here to implement Figma specs, collect your JIRA points, and wait for the next sprint planning. You're here to move fast, make real calls, and ship things that matter. You'll be one of a small number of engineers working directly on the highest-leverage features on our platform: intelligent intake flows, AI-powered case routing, constituent-facing portals that replace decade-old government interfaces. At the senior level, you'll also set technical direction, mentor teammates, and drive decisions that stick.

You'll pair with design leadership that cares deeply about craft and won't let you ship something half-baked. You'll engage directly with federal agency stakeholders. You'll translate what government users actually need into a product that delivers it.

And you'll be expected to use AI tooling not as a party trick, but as a force multiplier. Cursor, Claude, Copilot: these should already be embedded in how you think and work. The engineers we're hiring here move 3 to 5x faster because of how deeply they've internalized these tools. That's the bar., * AI-powered product surfaces: intelligent intake flows, real-time constituent assistants, automated case routing, agency operator dashboards

 * Direct engagement with federal agency stakeholders, translating messy real-world requirements into clean, shippable product
 * Platform reliability and performance at government scale: real users, real SLAs, no hiding
 * Technical direction and the bar on code quality: your decisions become the patterns the rest of the team builds on
 * Mentorship of earlier-career engineers through code review, pairing, and direct technical feedback