Careers at Whawit
Whawit is an AI-powered observability, incident-management and incident-AI platform. It ingests logs, metrics and errors from the providers a team already uses, runs AI analysis over them, and drives the rest of the incident lifecycle — on-call schedules, escalation, and the integrations where the work actually happens. We are building the part of the job that usually falls to whoever is awake at three in the morning.
How we work
Rather than describe a culture, here is what is verifiably true of the codebase you would be joining.
One repository
Everything Whawit runs on lives in a single pnpm + Turborepo monorepo — backend, frontends, marketing site, collector, VS Code extension, infrastructure and docs. It replaced roughly thirteen separate repositories. One lockfile, one place to look.
TypeScript, end to end
NestJS on the backend, React on the product and admin frontends, Next.js for the marketing site, all on Node 22. Nobody has to change languages to follow a bug from a chart into the service that produced it.
A small, legible stack
MongoDB for state, Redis and BullMQ for the asynchronous work, feature modules on the backend and a feature-first layout on the frontends. There is not much ceremony between an idea and the code that implements it.
You ship to production
Merging to main is a deploy. A path-filtered GitHub Actions workflow builds the backend and releases it to Cloud Run; the frontends are published by Cloudflare Pages, with a workflow in the repository that builds the product, admin and marketing apps together on every change. That is a real responsibility, and it is also why the loop is short.
Credentials are handled seriously
Secrets do not belong in source. They live in GCP Secret Manager and are pulled into a gitignored local .env on demand, so a developer machine holds a credential only because someone asked for it. Every push and pull request is scanned for secrets.
Open roles
No roles are listed here right now
Write to us anyway. Tell us what you have built and what you would want to own here. If there is something to talk about, we will get back to you.
[email protected]Nothing here fits, but you still want in
Then write to us. An email is the whole application — there is no form and no portal on this site. Tell us what you have built, what you would want to own here, and what you think we have got wrong about incident response. A few honest paragraphs and a link to your work are worth more to us than a polished cover letter.
Write to [email protected]Anything you send us is personal data. Our Privacy Policy covers how we handle it.