Careers at Kaizen Labs: Teams, Pay and How to Get Hired

Who gets hired and onto which teams

Kaizen Labs is hiring fast. The company, which builds modern software for local, state, and federal agencies, listed 17 open roles on its careers page in early September 2026, up from 11 two months earlier — a 55% jump that the tracking site Engradar flagged as "accelerating." Median time those postings stay open is 32 days, so the seats fill quickly once a role goes live. The career page frames the work in blunt terms: "Come work on America's most important problem. We're building the infrastructure that government runs on." That mandate connects every team the company is staffing.

Kaizen Labs employs around 45 people, per RocketReach's database, sitting in a Series A–stage company roughly 1 to 50 employees in size. The leadership bench listed in public records is small: Kj Shah as Co-Founder and COO, Luis Avila as Senior Recruiter, and Michael Atkinson as Head of Sales. That 45-person headcount, paired with 17 open seats, means roughly one in three people at the company is a recent or imminent hire — a startup-style ratio that shapes how teams form.

The team's reach extends beyond its size. Engradar's late-2026 breakdown split openings across other (4), engineering (3), marketing (3), design (2), people/HR (2), operations (1), and legal (1). The "other" bucket includes senior capture and proposal roles, an IT Operations Manager contract position, and a Government Contracts Administrator contract role — work tied directly to Kaizen's federal contracts. Engineering remains the largest single discipline by seat count, consistent with a company whose stated product is AI-native software replacing 1990s-era government systems.

Seniority skews senior. Engradar's snapshot showed 8 unspecified-level roles, 8 senior roles, and 1 director-level role open at once. Several director-tier seats sit on the careers site itself — a Head of Government Affairs in Washington, D.C., a Chief Technology Officer in New York, a Head of Brand & Storytelling in New York, a Head of Talent in New York, and a Customer Support Operations Manager who owns a function. The presence of three to four C-suite or "Head of" postings simultaneously signals a company building out its executive layer, not backfilling it.

Geographically, the work concentrates in two cities. ZiplineJobs' listings put 9 of 11 tracked roles in New York and 1 in Washington, with the rest untagged. The Kaizen corporate office sits at 17 W 20th St, 5th floor, in Manhattan; the Washington presence exists to be near federal agency buyers. Several roles appear across both — Senior Proposal Writer, Federal Growth Lead (DoW), Federal Growth Lead (FedCiv), Senior Cleared Software Engineer (TS/SCI), Senior Security Engineer, IT Operations Manager, Security Compliance Program Manager, and Forward Deployed Software Engineer, Cleared — reflecting how federal work pulls candidates between the two hubs.

Newest openings cluster where federal go-to-market is heating up. Engradar's 28-day window found the most new seats in "other" (3), marketing (3), and legal (2) — categories that align with Kaizen's push to staff the capture, brand, and contracts functions needed to win federal procurement. Engineering hiring has kept pace but hasn't been the single biggest growth area over that month, which tracks with a company that already has product engineering staffed and is now building the muscle to sell to the government.

The practical picture for a candidate: Kaizen Labs is a roughly 45-person, New York–anchored, federal-focused startup that is currently filling about one in three of its seats, hiring across engineering, design, marketing, people, legal, and operations, with a deliberate tilt toward senior and head-of-level talent and a clear geographic split between New York for product and Washington for federal delivery.

What it pays

Recruiting from Scratch reports a $200,000 median across 11 public roles spanning 2025–2026, with a published range of $161K to $260K. On Zero G Talent's own board, 14 salaried postings tell a tighter, more current story: a band of roughly $140K to $280K with a $189K median. The spread reflects role mix more than negotiation room. Compliance, content, and program-management roles sit at the floor; cleared software engineering and security sit in the upper-middle; talent leadership tops the chart.

The clearest signal of where the company spends its salary dollars is the Head of Talent posting at $250K–$300K, the only role on the board that crosses the $280K ceiling set by cleared engineers. Three engineering tracks cluster tightly at $220K–$280K across two cities and two clearance levels, suggesting comp is calibrated to clearance and seniority tier, not to title flourish. If you hold an active TS/SCI and can deploy forward, the band moves with you rather than locking you to a specific office.

The middle of the range is where most candidates will land. Security Compliance Program Manager posts at $155K–$190K, a figure worth noting because it puts a non-engineering, governance-focused role roughly $40K below the cleared-engineer floor. The Founding Filmmaker & Video Lead, at $140K–$180K, anchors the bottom of the board. Built In's January 2026 reporting describes the company's approach as one that "boosts total comp with unusually rich, NYC-centric benefits" — heavily subsidized health coverage, generous paid parental leave, multiple stipends, and a winter break — which effectively raises real take-home pay in ways the salary numbers alone don't capture. The tradeoff Built In flags is concrete: those benefits are calibrated to a New York employee, so dependents and family costs can land harder on staff outside that footprint.

Equity is the part of the package Kaizen Labs discloses least. Built In's January 2026 review explicitly calls out "limited public clarity on equity size/vesting and 401(k) match," and the company's own postings don't list grant sizes or vesting schedules alongside salary bands. Levels.fyi accepts anonymous and verified compensation submissions for Kaizen Labs and was last updated September 4, 2026 — the most direct way for candidates to pressure-test the public bands against what current and former staff actually report receiving. Candidates who care about the equity slice should treat it as a negotiation item, not a known quantity. Confirm grant size, strike price, cliff, and total vesting window in the offer stage; the upside is real but undocumented.

For applicants deciding whether to apply, the practical read is this: base pay is competitive with similar cleared-engineering and security shops in New York and D.C., the benefits package meaningfully closes the gap with higher-paying peers, and the equity math is something only an offer letter will resolve. Negotiate against the posted band rather than the median, because the band (not the median) is what each individual role is funded to pay.

The funnel, and what gets candidates through it

Kaizen Labs runs a 3-to-6-week funnel built around peer panels, blind screening, and a deliberate "is the need real?" gate before any search opens. That last piece is unusual: the company's own writing on team scaling treats hiring as a last resort, not a default. Per its post on adding people to teams, "hiring works when three conditions are met: the need will last, no one on the team has the capacity to take it on, and the team can onboard someone well." If any of those fail, the recommendation is to reorganize or develop internally. So by the time a candidate sees a posting, the bar has already been raised — the role exists because someone in the company argued it had to.

Internal mobility comes first. New openings move through KaizenOS, the company's internal web app, before they hit public job boards. Once a role is public, the screening stage strips identifying details from the resume (name and past employers come off) so the first pass weighs skills and experience only. Kaizen describes this blind review as the foundation of fairness, not as a gimmick, and calls the screening chat "not a pass/fail test; it's a starting point for a conversation about how you think, how you solve problems, and how you approach the work."

The interview loop runs on fellow Kaizens rather than a siloed recruiting team. "Building an amazing team is everyone's job," the company writes on its hiring-process blog, and the panel reflects that: developers, designers, and project leads all sit in. The format skips brainteasers and gotcha questions in favor of practical, real-world problems. For roles touching government clients — including cleared postings on our board, like the Forward Deployed Software Engineer (TS/SCI) and Senior Cleared Software Engineer (TS/SCI) — there's an optional client-facing instance at the end, framed as a chemistry check rather than a re-interview.

What the company says it rewards in candidates maps directly onto the panel structure. Thinking out loud and explaining tradeoffs matters; silence reads as disengagement rather than humility. Advice shared in a Fireship technical-interview walkthrough put it this way: "What's really important is that I think out loud and explain my decisions throughout the process… saying something is almost always better than saying nothing at all." The same source recommended avoiding language-specific magic in technical screens and asking a clarifying question when stuck rather than freezing. That style (collaborative, transparent, willing to surface uncertainty) is what the panel format is built to surface.

Kaizen reports an annual turnover rate of 5%, with 0% among "key players," and frames that retention as the output of a hiring process that screens for alignment, not just credentials. Independent Glassdoor and Indeed pages for Kaizen and KaizenLAB carry thin volumes (8 to 23 interview reviews depending on the entity) so the company's own claims should be read as the primary signal, with third-party candidate-experience anecdotes as secondary color.

Two patterns count as soft disqualifiers. First, a candidate who treats the process as adversarial reads as a culture mismatch in a model that explicitly bills itself as a two-way street and invites them to grill the company back. Second, a candidate who can't articulate how they've weighed a real tradeoff (build vs. buy, ship vs. polish, hire vs. develop) misses the practical-problems framing the loop is built around. The strongest applications on Kaizen's recent board — Head of Talent, Senior Security Engineer, Forward Deployed Software Engineer, Founding Filmmaker & Video Lead — cluster in New York or Washington, D.C., in bands from $140k to $300k. That mix tells you what the panel is screening for: senior, cleared, or founding-level hires who can defend judgment calls in front of peers and clients, not entry-level generalists.

If you're weighing whether to apply, the practical move is the one Kaizen itself uses internally: clarify the problem first, then commit to the loop.

Where the work actually happens

Kaizen Labs runs a remote-friendly operation, but the company's geographic footprint concentrates in two specific metros: New York City and Washington, D.C. The Head of Talent role and several engineering and security positions on the company's job board are tagged to New York, while cleared engineering work points to D.C. as its own hiring locus. That two-city shape — financial-product nerve center on one end, federal-customer delivery on the other — mirrors the company's stated mission of building infrastructure for government, where proximity to agency buyers matters as much as proximity to capital.

The primary physical site is a single Manhattan office at 17 W 20th Street, on the fifth floor of a building in the Flatiron district. Every job posting that names a location names New York, and the company's hiring page makes the in-office requirement explicit for at least some roles. The Founding Filmmaker & Video Lead listing, for example, requires candidates to reside in New York or commute into the city and to work out of the office at least three days a week — Tuesday through Thursday. Other roles on the board list Washington, D.C., alongside New York, or Washington, D.C., alone, reflecting how federal work pulls the company between the two hubs.

The D.C. presence works differently. The Forward Deployed Software Engineer, Cleared (TS/SCI) listing sits in Washington, D.C., and the role's clearance requirement implies a customer base that demands physical proximity to federal agencies — work that can't happen from a coworking space in Brooklyn. For cleared engineering, "remote" effectively means the D.C. metro area rather than anywhere in the country, because the people, the SCIFs, and the program offices are there.

Beyond the two main hubs, the company has light corporate-filing footprints in other states — Kaizen Laboratories Inc. is registered in Frisco, Texas, and in West Virginia, according to state corporate records. Those registrations look more like statutory paperwork than operating offices: nothing in the job listings, the careers page, or the company's own site points to staff sitting in either location. Treat them as legal-entity traces, not as sites.

The travel layer sits on top of the office policy. The careers page flags "periodic travel to be on-site with the team (agency visits, offsites, DC trips)" for roles with in-office requirements. Read literally, that means a New York–anchored hire should expect trips to D.C. for customer work and occasional company offsites, and a D.C.-anchored cleared engineer should expect the inverse.

Third-party reviews describe the firm's strengths as "Time Off Access, Remote or Hybrid Flexibility, and Wellbeing Programs," but the same reviews flag "Time Pressure and role-dependent Workload or Staffing variability, with some Remote or Hybrid Limitations for NYC-centric roles." The flexibility is real and broadly available, but it stops at the New York office door for those roles: NYC-anchored postings require Tuesday-through-Thursday presence regardless of how well remote work has gone.

For candidates evaluating an offer, the practical read is straightforward. Expect a hybrid schedule anchored to the Manhattan office three days a week if the role is tagged New York with that requirement. Expect a D.C.-area anchor if the role requires an active clearance. Expect travel on top of that for agency-facing work and company offsites. And don't assume the Texas and West Virginia filings translate into remote work options in those states — the operating footprint is a two-city company, with everything else built around it.

Who thrives at Kaizen

Reading job listings, recruiting emails, and company-published case material side by side, those five phrases aren't decorative copy — they're the rubric against which the company's own records say candidates are evaluated. A strong application reads as a calm, specific demonstration of those traits rather than a polished pitch of unrelated experience.

The strongest signal of fit is mission orientation. Kaizen's work centers on modernizing resident-facing public services, with documented deployments for Maryland DNR and Pima County, and case materials that call out improved usability, bilingual access, and smoother reservations once systems went live. Employees who thrive treat those outcomes (not a generic "AI startup" pitch) as the reason they want the job. The company's Series A, $21M led by NEA with participation from a16z, Accel, and 776, signals runway and multi-state growth plans, but it also signals a specific kind of customer: slow government procurement cycles, lumpy revenue, and roles that may shift as processes evolve. The considerations section on the company's workplace profile flags that dynamic explicitly as change fatigue. People who do well are the ones who can absorb that ambiguity without treating it as a problem to fix in their first month.

Technical depth matters, but the role mix on the board suggests it's breadth (not narrow specialization) that maps onto Kaizen's hiring needs. That range — security-cleared engineering, compliance, recruiting leadership, and a creative production role on the same board — tells you the company values people who can operate at the seam between technical delivery and government customer realities. A candidate who can talk fluently about both halves of that equation is reading the room correctly.

There's a tension worth naming plainly. The published values emphasize clarity, ownership, and willingness to help, yet at least one detailed candidate account describes a disorganized, last-minute-changing interview process routed through an external recruiter. The lived candidate experience has not yet caught up with the stated norms. Candidates who thrive appear to be the ones who can extend the company some grace on that gap while still holding it accountable — people who show up to a rescheduled final round with the same preparation they brought to the first one.

The most useful preparation is concrete. Read the Maryland DNR and Pima County case studies before the screen. Be ready to discuss how you'd improve usability or bilingual access in a reservation flow, not how you'd "scale an AI platform." And expect to be evaluated on whether you operate with collective ownership — whether you ask who else needs to be in the room before volunteering an answer, and whether you flag a blocker as soon as you see it rather than after a deadline slips.

The clearest next step for an applicant: pull the company's published values into a single document and write one paragraph beneath each that maps a specific past project to that value, then use those paragraphs to anchor every interview answer.

Working in frontier tech? Zero G Talent tracks the openings: see every open Kaizen Labs role, browse frontier tech jobs, the companies hiring, and the people building the field.