Release Notes
The public record of what shipped to hushh.ai and when, kept alongside the releases page on the site so users, the team, and the community read the same account.
TL;DR: Every release is documented in two places by principle: the releases page on hushh.ai and this page. This record begins 2026-09-11 with the careers release, and the full dated history back to the beginning lives on the site.
Status as of 2026-09-11: see body.
Building in the open means a release is written down where anyone can read it, not announced once and forgotten. Our engineering contract makes that a rule: every release is documented twice, on the site and here, the same day.
This page starts on 2026-09-11. The rule had been in place since 2026-08-27 and no page existed, so rather than backfill an account of releases from memory, it begins here, and the complete dated history stays where it has always been generated from the commit history: the releases page on hushh.ai.
2026-09-11 (later) — Nine cities, an honest answer about remote, and what the job pays
Every one of the 129 jobs is now open in San Francisco, Palo Alto, Seattle, Kirkland, Austin, Dallas, Chicago, Miami and New York, and every posting says what the job pays and what comes with it.
The remote claim was wrong, and then wrong the other way
Before today, 125 of the 129 postings told Google the job was done entirely remotely. It was not. That put office jobs in front of people searching specifically for remote work, who would have found out on arrival that the role is five days in a building. Nothing errored; the claim was simply untrue, and untrue claims that produce no error are the ones that last.
The first correction over-swung and marked everything office-based, which was untrue in the other direction, because the customer-facing roles genuinely are remote.
Where it landed matches how the company actually works. Forty roles are remote-friendly: sales, field work, client service, partnerships, and forward-deployed engineering. Those people can be based in any major US city with strong domestic and international airport connections, because the job is being where the customer is. The other eighty-nine are office-first across the nine cities, five days together, and remote-friendly around family arranged one person at a time, which we would rather people used than toughed out.
Where a category was genuinely ambiguous it was left as office-first. Telling someone a job is remote when it is not costs them a great deal more than the reverse.
What comes with the job, on every posting
Indicative pay ranges by market and level, published openly. Stock options for every full-time teammate. An annual bonus, or on-target earnings with uncapped commission for customer-facing roles. Medical, dental and vision for you and your family, plus life and disability cover, on the highest plan tier available to us. A 401(k) with company matching. A budget of AI tokens of your own, because a company that says you should own your AI cannot be the company that rations it. A gym membership and real retailer discounts. And the referral kicker.
What these postings deliberately do not say
No 401(k) match percentage, no premium share, no deductible, no waiting period. The benefits platform and the plan tier are decided; those specific numbers are not, and a job posting is something a person leaves a job on. They will be in an offer letter before anyone signs one. A test fails the build if any of them ever appears in a posting before then.
Verified in production
All 129 postings checked live: every one carrying the nine cities, the pay and benefits, and the working policy that actually applies to it. An office-first role reads five days a week; a sales role reads any major US city.
2026-09-11 — Every role is open, and applying takes about a minute
One hundred and twenty-nine jobs, each with its own page, its own description, and its own application. A reference number and an email the moment you apply. And the postings are visible to Google's jobs box, which until this release they were not.
All seventy-two catalog roles are open, and every one takes a real application
The role catalog had shipped as a map of intended work: seventy-two pages that each said there was no application to submit. Every role is open, every role now has a form on its own page, and the form is three fields. Fifty further roles that had full descriptions, requirements and success criteria, but existed only as rows inside one long page, now have pages of their own as well.
One hundred and twenty-nine jobs. One hundred and twenty-nine addresses.
A reference number, and an email that repeats what you sent
Applications used to arrive in the wrong inbox, and the applicant heard nothing back. Neither failure produced an error, which is why both lasted.
Every application now gets its own reference, and an email that reads back exactly what was stored rather than what the browser reported sending. Applying again to the same role with the same address updates the answers instead of creating a second record, and the reference stays the same. When the confirmation email does not send, the page says so and gives the address to write to, rather than pointing at an inbox nothing is coming to.
Show us everywhere your work lives
A resume, LinkedIn, a portfolio, GitHub, X, YouTube, Instagram, TikTok, Facebook, writing, Dribbble, Behance, and a box for anything else, whether that is a design workshop, a podcast, or a repository someone is proud of. Any of them, none of them. Only a name, an email and the role are required; everything else sits behind one link that opens on request.
The jobs box
Three faults were keeping almost every posting out of Google's jobs results, and not one of them ever produced an error message. A rejected posting simply never appears, which is indistinguishable from nobody searching for it.
The catalog roles carried no location, and location is required. The funded roles declared where a remote applicant could be based without the accompanying field that makes Google read it. And seven jobs shared a single address, competing against each other for one result.
Each job now has one page, one posting and one application. All of them are listed in the sitemap, and there is a feed for the job boards that ingest listings rather than crawling for them.
What this release deliberately does not do
It does not publish a salary it cannot stand behind. Attaching a pay band to a named job is a compensation decision, and those are made by people. Only the bands already published on the compensation page appear in the postings; the rest carry none rather than an estimate.
Verified in production
Every one of the seventy-two catalog roles and all fifty-seven of the new role pages were checked live after the release: each reachable, each carrying its own posting, each offering a working application. Addresses that do not exist return a proper not-found rather than an empty page pretending to be a job.
Sources
- Release notes on hushh.ai
- Open roles
- The role catalog
- Production verification run against hushh.ai on 2026-09-11, recorded in the engineering session that shipped the release.