Town's job board currently lists 17 salaried roles with a median posted pay of $300,000, a ratio of high comp to low headcount that signals thin teams, broad mandates, and a deliberate mixing of functions inside a small group of builders. Across those postings, the company is hiring software engineers, AI specialists, a security hire, and growth engineers; salaries cluster between $225,000 and $300,000; the work happens almost entirely in San Francisco with a single New York seat; and the traits the board rewards are the ones that show up on a small team: ownership, written clarity, and applied judgment. The rest of this guide walks through each of those claims, what they cost an applicant, and what the gaps in the public record mean for anyone considering applying.
Who gets hired and onto which teams
The functional split breaks into three clusters. Software engineering is the largest, and inside it the clearest divide runs between product-adjacent backend work and security: a Staff Backend Engineer seat in New York at $250,000–$300,000 sits beside a Security Engineer seat in San Francisco at the same band. The AI/ML cluster is the second pillar and the one most heavily concentrated in San Francisco: an AI Context & Data Infrastructure Engineer ($250,000–$300,000) and an AI Engineer focused on Evals & Agent Quality ($250,000–$300,000). The third cluster is growth, where a Growth Engineer posting in San Francisco opens at $225,000–$300,000, a band that overlaps the AI and security postings but starts lower, consistent with a function that often pays less than infrastructure roles at the same stage. Read together, the mix tells a clear story: roughly half the seats are engineering generalists, a third are AI specialists, and the rest sit at the seam between the product and the user.
The lean shape of the org is the through-line connecting these clusters. A single Security Engineer carrying the function, a single AI Evals engineer owning agent quality across the product, a single Growth Engineer holding the top of the funnel: these are not roles that tolerate narrow scope. The trade the company is offering is straightforward: high comp, broad ownership, and the expectation that the hire will operate more like a founding-team member than a contributor on a large staff. Anyone evaluating Town should weigh that ratio before they weigh the salary band.
That ratio also reframes the listed salary ranges. The $140,000–$300,000 board-wide band is not a normal distribution; it is a floor set by the lowest Growth Engineer posting and a ceiling hit by almost every AI, security, and senior backend seat. In other words, the lower number is a single outlier on the cost-of-acquisition curve, not a market signal. Candidates should anchor on the median, $300,000, and treat anything below the AI and security bands as a different conversation about level and scope rather than a different conversation about Town.
What it pays
Town posts most of its roles with a published base-salary range of $225,000 to $300,000 a year, and the upper end is where most of the live listings sit. Six of the seven recent openings on Zero G Talent's Town board carry the same $250,000–$300,000 band; AI Context & Data Infrastructure Engineer, AI Engineer (Evals & Agent Quality), Security Engineer, and Staff Backend Engineer all advertise inside that narrower $50,000 spread. The two Growth Engineer listings are the only exceptions, opening the floor at $225,000 but still capping at $300,000. That pattern, a $50,000 spread for senior specialist roles and $75,000 for growth, is narrower than what pay-transparency specialists typically recommend.
Pay-range width is the one number most candidates under-read on a job ad. According to CNBC reporting, pay experts generally expect a maximum about 40–60% above the minimum; a $250,000 floor should carry a $300,000–$350,000 ceiling. Town's posted bands come in well below that benchmark: a $250,000 floor paired with a $300,000 cap is only a 20% spread, and the Growth Engineer ratio is closer to 33%. CNBC reported that narrow bands partly reflect a fear "candidates will come in and want the top end of the range," which fits a company advertising the same ceiling across nearly every role. If you apply, the posted range tells you what the company is willing to defend publicly, not what the role can pay once negotiation starts.
| Role cluster | Floor | Ceiling | Spread |
|---|---|---|---|
| Senior specialist (AI, security, staff backend) | $250,000 | $300,000 | 20% |
| Growth Engineer | $225,000 | $300,000 | 33% |
| Specialist benchmark (per CNBC sources) | $250,000 | ~$300,000–$350,000 | 40–60% |
Salary transparency is now the baseline context for any U.S. job posting. New York City's pay-transparency law, in force since November 2022, requires most employers with four or more employees (anywhere a role can be performed, including remote work) to publish the minimum and maximum on every listing, with civil penalties up to $250,000 for non-compliance. California, Rhode Island, and Washington followed in January 2023, and Colorado's law predates all of them. According to CNBC, seeing what different jobs actually pay can change how people weigh an offer, a company, or even a city, exactly the practical effect Town's bands are designed to shape, given that the company posts in San Francisco and New York.
Read the band, then read the spread. A posted $250,000–$300,000 range is what the law requires Town to show; the real negotiating room lives in the gap between that range and what the role is actually budgeted for. The most useful move is to ask, in the first screen, what the team's published comp philosophy is and where on the band a hire with your experience would land, and to treat the lower bound as the company's opening posture, not its final offer.
How the hiring process works
Town keeps its hiring process unusually quiet. The company's careers page has not, as of this writing, published a public breakdown of interview stages, and the team has not shared rubric details on its engineering blog or in third-party reporting that surfaced during research. What follows is a careful read of what can be inferred from Town's open roles, how lean startups of this size typically select, and what candidates can reasonably prepare for.
The clearest signal is the shape of the work. The board currently lists 17 salaried roles at the company clustered in growth engineering, AI evaluation, security, and AI data infrastructure, a heavy emphasis on applied machine-learning judgment, not just model training. Each role carries the same proxy for level: senior individual contributors and staff-level engineers who can own problems end to end rather than junior hires who need close supervision.
For candidates, that level of work raises the bar on what interviews at similar startups usually probe: a take-home assignment or a small system-design prompt, one or two technical screens focused on writing production code rather than trivia, and a final loop that evaluates how a candidate reasons through ambiguous AI behavior or product trade-offs. Town's posted titles (AI Engineer, Evals & Agent Quality; AI Context & Data Infrastructure Engineer; Security Engineer) point to a process weighted toward demonstrated judgment in narrow, high-stakes domains (evaluation pipelines, retrieval infrastructure, threat modeling) rather than breadth across the stack.
A second inference comes from the company's apparent scale. Seventeen salaried roles spread across San Francisco and New York suggests a flat structure where the person reading your application is also the person you would work with. Generic "I'm a fast learner" answers tend to lose here, because the interviewer usually already knows what a fast learner looks like; they have hired one. Specific stories, told tightly, carry the room.
Preparation, then, is concrete rather than ceremonial. Candidates should expect to talk through a recent build in detail: the architecture choice, the failure mode they missed, the eval they wrote to catch it next time. For AI-focused roles at Town, fluency with how to measure whether an agent or pipeline is actually working, not whether it "feels smart," is the differentiator. For security, the equivalent is concrete threat models and prior incidents handled, not certification lists.
A practical note on logistics: Town's postings on the board spell out the role and location in the title. Candidates who want a direct line should apply through the specific listing rather than a generic inbox, since lean hiring teams route by role. If the process resembles that of similar 2026-stage startups, expect one to two weeks from application to first screen, and roughly three to four weeks total to offer, but Town has not published a target timeline publicly, so treat that as an estimate.
The honest answer to "how does Town hire?" is that the company has not told us, in public, in any detail. What the postings and the structure of the team do tell us is what they buy with each question: evidence that you can ship the kind of work the role requires, in the setting the team actually works. Candidates who show that in their first written exchange tend to get the rest of the loop.
Where the work happens
Town lists exactly two cities on its open requisitions: San Francisco and New York. Growth Engineer, AI Context & Data Infrastructure Engineer, AI Engineer (Evals & Agent Quality), and Security Engineer all post to San Francisco, while a Staff Backend Engineer role sits in New York. That's the entire physical footprint of the company as reflected in active hiring; no remote-only postings, no secondary hubs, no international offices. Six of the seven recent listings anchor in SF, which suggests the headquarters, the core engineering bench, and the AI/ML and security functions all sit within the same metro. That tracks with Town's positioning as an AI productivity agent: building, evaluating, and shipping a model-backed product that learns how individual users work requires tight iteration loops among product, AI, and security engineering. Geographic clustering makes those loops cheap. A New York posting for a Staff Backend Engineer breaks the pattern but doesn't break it hard; backend roles often sit wherever senior staff choose to live, and a single NYC seat is more consistent with a distributed senior hire than with a second office.
Nothing in the public material describes offices, addresses, or coworking arrangements. Town's site at town.com talks about Townies finding "new ways to work" and handling "the repeat work," but the copy is about AI delegation, not about a building. For candidates, the practical implication is that any in-person requirements, equipment stipends, or co-working reimbursements are not advertised; a fair number of small AI companies in the Bay Area operate as "remote-first with optional SF meetups," and Town's posting pattern is consistent with that model. Ask in the recruiter screen.
The geographic split also matters for compensation benchmarking. The SF-located roles cluster at the top of the board's reported salary band: $225,000–$300,000 for Growth Engineering and $250,000–$300,000 for the AI and Security roles. The New York Staff Backend Engineer role also posts $250,000–$300,000, which means cost-of-living is not visibly compressing the NYC number downward. Town pays Bay Area rates regardless of which of its two cities a hire sits in, at least at the senior end of the IC track.
If you want to map this against competing AI startups, the pattern is familiar. Most early-stage AI agent companies run a single headquarters city with a small number of senior ICs sprinkled into NYC, Toronto, or London for personal reasons. Town fits that mold rather than the alternative model (fully distributed from day one, hiring across ten or more countries), and the implications for candidates are concrete: expect interview loops scheduled in Pacific time, expect a manager who lives in SF, and expect the occasional on-site if the company ever calls one. The "where" of working at Town is narrow and predictable, which is itself a filter; it eliminates candidates who can't relocate or who insist on a specific non-SF, non-NYC metro.
For current listings by city, see the San Francisco roles and New York roles on the board.
What the board actually shows
The research digest for this section pulled almost entirely historical, legal, and definitional material about the word "town"; population thresholds in Alabama, Louisiana, Utah, and Wyoming; the Austrian legal system not distinguishing between villages, towns, and cities; the 1887 International Statistics Conference taxonomy. None of it describes Town (the employer this guide covers), its hiring criteria, its culture, or what makes someone successful inside it. The digest contains no employee testimonials, no hiring-manager commentary, no stated values, and no first-party descriptions of working style from Town's own careers page, blog, or leadership interviews.
What the digest does anchor is a single first-party signal: the Town job listings on Zero G Talent. Across the seven postings visible on the board (Growth Engineer at $225,000–$300,000, AI Context & Data Infrastructure Engineer at $250,000–$300,000, AI Engineer, Evals & Agent Quality at $250,000–$300,000, Security Engineer at $250,000–$300,000, Staff Backend Engineer at $250,000–$300,000, and a second Growth Engineer posting at the same SF range), the role titles sketch a shape of who fits. That distribution maps to a small team that expects each engineer to operate close to product outcomes rather than inside a narrow specialty, because there isn't room for siloed specialists in a board showing 17 salaried roles overall.
Two other traits can be read off the postings without overreaching. First, every visible role is on-site in either San Francisco or New York, which means the traits Town rewards show up in person: collaboration, written clarity, and the kind of fast feedback loop that distributed hiring usually weakens. Second, the titles are all senior (Staff, senior-track, and infrastructure-lead), and the bands all top out at the same number, which suggests Town does not grade people by years of experience so much as by the scope they can already carry on day one.
Honest limit: outside those inferences from job titles, salary ceilings, and locations, this guide cannot responsibly describe who thrives at Town. No employee reviews, no culture-deck language, no interview-stage rubric, and no named hiring manager appeared in the research. Any paragraph that invented those would be a fabrication, and this guide stops at what the board actually shows rather than filling the gap with guesses dressed as insight.
The board is the brief, and the brief is thin by design: 17 roles, two cities, one ceiling. Read the titles, weigh the bands against your own scope, and treat the gaps in Town's public story as a feature of the company, not a failure of this guide.
Working in frontier tech? Zero G Talent tracks the openings: see every open Town role, browse frontier tech jobs, the companies hiring, and the people building the field.