Security Engineer

In 2026, we're on the verge of an "infinite software crisis." How will we support, maintain, and operate the explosion in application development?

Our answer is Sazabi: the AI-native observability platform for fast-moving engineering teams.

Sazabi gives teams a single place to ask questions about their production systems in plain language, automatically visualize what's happening, and get to the root cause 10x faster. No tedious instrumentation. No dashboard configuration. No alert tuning. Just answers.

We're backed by tastemakers from the world's top AI companies: Vercel, Graphite, Daytona, Browserbase, LangChain, Mastra, Replit, and more.

• Design and implement security across our entire stack (infra, app, data, and AI systems)

• Own authentication, authorization, and tenant isolation from first principles

• Build secure-by-default systems for log ingestion, storage, and querying

• Identify and mitigate risks in an AI-native product (prompt injection, data leakage, model misuse)

• Lead incident response and postmortems for security-related events

• Establish security practices without slowing down engineering velocity

• Work closely with engineering to embed security into everyday development—not bolt it on later

• Strong experience in application and/or infrastructure security at a modern SaaS company

• Deep understanding of common vulnerabilities (OWASP, auth flaws, data exfiltration, etc.)

• Experience securing distributed systems and APIs

• Comfort working in fast-moving, ambiguous environments without predefined processes

• Pragmatic mindset: you know when to push hard on security vs. unblock shipping

• Bonus: experience with AI/LLM security, observability systems, or developer tools

Our stack is TypeScript end-to-end. We use PostgreSQL for relational data, Temporal for durable execution, and the Vercel AI SDK to orchestrate our AI agents against the latest models. At the infrastructure layer, we use Terraform, Kubernetes, and AWS.

Some of the most interesting engineering problems we grapple with are:

• AI agents at production scale

• Log processing at scale

• Multi-region data architecture

• Real-time streaming infrastructure

• Evals and reinforcement learning

• Zero-downtime deployments and fast rollbacks

• Competitive salary and equity

• Free lunches (in-office only)

• Health, dental, and vision insurance

• Unlimited paid time off

• Paid parental leave

Our team comes from Brex, Y Combinator, Rootly, Google, Doppel, and other top tech companies. We move fast and hold a high bar for both the product and each other.

We operate according to six values:

1. Integrity. We say what we mean, do what we say, and own our mistakes.

2. Urgency. We treat every week like it matters, because it does.

3. Craftsmanship. We care deeply about the quality of our work.

4. Service. We're here to make developers’ and our teammates’ lives easier.

5. Kindness. We're direct, and we move fast, but we treat each other well.

6. Fun. We genuinely enjoy working together. If you don't love what you're building and who you’re building it with, what's the point?

You can find out more about us here:

• Watch our launch video

• Read the manifesto

• Follow us on X and LinkedIn

Sazabi is more than just a tool. It’s also a philosophy. We're taking a radically different approach to observability, centered on three big ideas:

1. Less is more. Most observability platforms drown you in dashboards and modules that you don’t need. We believe observability needs less UI, not more. Sazabi surfaces exactly the information you need in a simple, beautiful chat interface.

2. Logs are all you need. The “three pillars of observability” idea is outdated. Sazabi accepts only one kind of telemetry: logs. This simplifies the instrumentation and product experience dramatically.

3. Monitoring is dead. Creating and maintaining static alerts for a fast-evolving system is a fool’s errand. The future is agentic anomaly detection: AI agents that automatically check your app for issues 24-7.

We came to these beliefs the hard way — after years of building infrastructure and responding to incidents with tools that offered plenty of bells and whistles, but no clear answers when it counted most.

If this way of thinking resonates with you, come build with us.