Sazabi
AI-native observability — agents that read your logs, find production issues, and open the fix as a PR
Last verified August 17, 2026 · Updated daily
What Sazabi is building
Sazabi is observability rebuilt for teams that ship AI-generated code continuously. The thesis: Cursor, Claude Code, and Codex transformed how software gets written, but the second half of engineering — monitoring, debugging, incident response — is stuck in the pre-AI era of hand-configured dashboards, brittle instrumentation, and noisy alerts. Instead, Sazabi deploys AI agents that learn a team's logs, infrastructure, and codebase, then proactively detect, investigate, and resolve production issues — including opening pull requests with fixes, or launching a Cursor cloud agent to ship the change. The architecture is deliberately logs-first: founder Sherwood Callaway's view is that 'logs are just events, metrics are aggregated events and traces are basically correlated events,' so Sazabi accepts only logs (stdout/stderr, OpenTelemetry-compatible) and derives metrics and traces on the back end, with an AI-compressed storage layer that summarizes an hour of logs into a queryable package. Chat is the primary interface (Slack is the main entry point), plus a CLI that gives your coding agent visibility into observability data. Closed alpha: 50 teams onboarded in two weeks, 8,000 background investigations, 2,000 issues detected, 200 PRs opened. Integrations with 35+ hosting services including Vercel, AWS, GCP, Cloudflare, Neon, and Supabase.
Why this matters
The angel list is the signal: 60+ operators from Vercel, Cursor, OpenAI, Anthropic, GitHub, and Replit are exactly the people who see where AI-era developer tooling is going, and they put money in. J2 Ventures GP Christine Keung supplied the category-defining frame: 'If Datadog defined observability during the cloud-native era, Sazabi is defining it for the AI-native one.' Hunter Walk of Homebrew, who backed code-review platform Graphite early, said Sazabi 'reminds me of Graphite in the early days.' Callaway's own positioning: 'Sazabi is what Datadog would look like if it were built in 2026 instead of 2010.' The company deliberately targets early- and growth-stage startups rather than enterprises locked into legacy stacks, and differentiates from AI-SRE startups like Traversal and Resolve by owning its own storage layer instead of sitting on top of Datadog. The counterweight to know: Datadog and Grafana are incumbents actively adding AI features, so Sazabi is betting a rebuilt-from-first-principles product beats bolted-on AI.
Open roles at Sazabi
4 positions we're tracking. Roles are re-checked daily and removed when filled.
Founding Backend/Infrastructure Engineer
First seen last month
AI/Agents Engineer
First seen last month
Product Engineer (Full-Stack)
First seen last month
Developer Relations Engineer
First seen last month
Know when Sazabi is hiring before anyone else
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching Sazabi
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+Hiring outlook
The announcement explicitly earmarks funding to 'expand its engineering team, accelerate product development, and deepen integrations.' A small post-YC team with strong alpha traction (50 teams in two weeks) hires founding engineers immediately — and the 60+ angels from Cursor, Vercel, and OpenAI form a referral network you'd be competing against, so move fast.
Working at Sazabi
Since 2025, Sazabi has built AI-native observability — agents that read your logs, find production issues, and open the fix as a PR. The team is now <50 people. Working at a B2B, Infrastructure company at this stage means broad remit, direct access to founders, and equity that still means something if the company works out.
The majority of roles are in San Francisco, CA, USA.
How to actually get hired at Sazabi
Why applying the normal way doesn't work
Sazabi is <50 people. No recruiter, no HR. Your application goes to a founder juggling everything. Cold outreach is how you actually get seen.
Who to contact at Sazabi
Founding team
Callaway is a two-time Y Combinator founder — his previous company, Opkit, a phone call automation platform, was acquired — and a software engineer with more than a decade in infrastructure, DevOps, and observability roles at VC-backed startups including Crunchbase and Brex, where he helped start the company's infrastructure and observability engineering teams. That Brex experience is the founding story: even with best-in-class tooling, incident response meant manually digging through data, and his instinct ('whenever there was a problem in production, I would reach for a log stream,' as he told Business Insider) became Sazabi's logs-first architecture. He took Sazabi through YC's Spring 2026 batch and assembled a team including early Brex infrastructure engineers and past observability founders. The classic pattern investors love and Hunter Walk named explicitly: a technical second-time founder solving a problem he personally lived.
What to show them
Built LLM agents that operate on large, messy real-world data — log analysis, root-cause investigation, code understanding, or automated PR generation. Their alpha stats (8,000 investigations → 2,000 detections → 200 PRs) imply hard problems in precision and noise reduction; showing you've built agents where false positives have a cost is the differentiator.
A cold email that works at Sazabi
What Sazabi screens for
Callaway's origin story is the credibility hook: he built infrastructure and observability at Brex and Crunchbase over a decade, and Sazabi came directly from grappling with the limits of best-in-class tools at Brex. His previous YC company, Opkit (phone call automation), was acquired. Their manifesto invokes The Bitter Lesson — 'logs are all you need' — and quoting that framing, or his line 'AI has changed how software gets written. Now it is changing how software gets operated,' shows you did the reading. Bonus: the platform is targeted at exactly the teams using Claude Code and Cursor, so being a heavy user of those tools is itself relevant context.
A tailored CV beats a generic one. Use Sazabi's job description language to clear filters.
Don't make these mistakes
Don't pitch experience maintaining traditional dashboard-heavy observability stacks as your headline — the product's entire premise (spelled out in their public manifesto at sazabi.com/blog/manifesto) is that that world is over. And don't be vague about logs: the logs-first architecture is a deliberate, contrarian design choice (trading the classic three-pillars model for log-derived everything), and candidates who don't engage with that tradeoff haven't understood the product.
Mistakes that kill Sazabi applications
Generic CVs stand out at a <50-person company — and not in a good way. Fastest path to rejection.
Don't open with what you want. Open with what Sazabi is dealing with right now — The angel list is the signal: 60+ operators from Vercel, Cursor, OpenAI, Anthropic, GitHub, and Replit are exactly the people who see where AI-era developer tooling is going, and they put money in, and what you'd do about it.
Applying and waiting = silence. Follow up at day five — it roughly doubles your odds of a reply.
Applying to Sazabi? Get the contact, not the form.
The Sazabi interview process
3 stages · 7 days typical · take-home: no · modelled from similar companies
We don't yet have verified candidate reports for Sazabi. What follows is the typical process for a <50-person B2B, Infrastructure company — treat it as a model, not confirmed detail.
Interview stages
Intro Call
Video call · 30 min
Culture fit and role expectations
Founder or hiring manager
Technical Deep Dive
Video call or in-person · 60 min
Past projects and problem-solving approach
Technical founder or lead
Final Round
In-person or video · 45 min
Team fit and offer discussion
Founding team
Sazabi interview timeline
Expect days total. Compared to similar B2B, Infrastructure companies (10 days median), Sazabi is faster.
Interviewed at Sazabi?
Tell us how it went — stages, questions, timeline. Takes 90 seconds and it's how this page stays accurate for the next person.
Submit your Sazabi interview experience →Sazabi jobs, frequently asked questions
How many jobs does Sazabi have open?
As of July 2026, Sazabi has 4 open positions.
Does Sazabi hire remotely?
Sazabi doesn't have remote openings at the moment. All roles are in San Francisco, CA, USA.
What roles is Sazabi hiring for?
Sazabi is hiring across Engineering. The most recent opening is Founding Backend/Infrastructure Engineer.
How do I apply for a job at Sazabi?
Apply via the links above. For tips, read our guide on how to get hired at Sazabi.
Does Sazabi respond to cold emails?
Response rate data for Sazabi not yet confirmed.
Who is the hiring manager at Sazabi?
At this size, hiring is usually run by a founder or department head.
What ATS does Sazabi use?
Sazabi uses Ashby.
How competitive is it to get hired at Sazabi?
Typical applicant count for B2B, Infrastructure roles (<50 people): 50-100 in two weeks. Apply fast.
How many rounds is the Sazabi interview?
3 stages: Intro Call, Technical Deep Dive, Final Round.
Is the Sazabi interview hard?
Expect relevant experience and culture fit, not algorithm trivia. Candidates report Final Round as the toughest stage.
Does Sazabi give a take-home task?
No, Sazabi does not include a take-home stage.
How long does Sazabi take to get back to you?
Around 7 days across the full process.
What should I prepare for the Sazabi interview?
Focus on relevant experience and culture fit. At <50 people, they're testing whether you can operate without process, not whether you memorised algorithms.
Where is Sazabi based?
Sazabi is headquartered in San Francisco, CA, USA.
Get Sazabi roles before they're posted
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching Sazabi
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+