Senior AI Backend Engineer

Senior AI Backend Engineer

Experience: 4+ years designing and shipping production-grade products

Location: San Francisco / Bay Area (Relocation assistance available)

Job Type: Full-time

Klarity (YC S18) is building multimodal AI agents that replace how Fortune 500s understand and transform their operations.

Big companies pay consultants millions to document processes and analyze operations. It takes months and goes stale immediately. We built multimodal AI agents that do it continuously. OpenAI, Google, Door Dash, Service Now and many others are using Klarity to replace that entire process.

We shipped GPT-4 document chat within 12 hours of OpenAI's launch. We believe speed and quality happen together when you're thoughtful about how you build.

We're hiring Senior Backend + Applied AI Engineers to build the core systems that power Klarity's multimodal agents in real enterprise environments. This is a hands‑on engineering role at the intersection of distributed systems and applied AI: you'll design and ship backend services that ingest messy real-world data, orchestrate model/agent workflows, enforce enterprise‑grade security and deliver reliable outcomes at scale.

You’ll work closely with product, design, and other engineers to turn ambitious AI capabilities into production‑grade features that Fortune 500 enterprises can depend on. We care deeply about engineering fundamentals (correctness, observability, security, performance) and equally about iteration speed – because in this space, only the teams who ship quality products & features at incredible velocity win.

You’ll set technical direction for critical subsystems and mentor engineers earlier in their careers – raising the bar for the entire team.

Note: We do not require a CS or Engineering degree. We care about your ability to ship, your systems thinking, and evidence of strong execution – whether through production work, open‑source contributions, research, or high‑quality side projects.

• Backend engineer with sharp product judgment – You design and build services, APIs, data models, and infrastructure that are reliable, observable, secure, and fast. You can explain architectural tradeoffs as fluently as you can debate the right abstraction boundary. You optimize for outcomes – developer velocity, latency, correctness, uptime – and not just for elegance in the abstract. You've been the person teams turn to when a design review needs a tiebreaker.

• Systems thinker with uncommon foresight – You see around corners. While solving today's stated requirements, you anticipate how services will need to evolve – functionally and non‑functionally. You design for the future but build for the present, and you never let architectural dogma slow the team down. You've designed at least one system from scratch that other engineers now build on top of and is used in production  establish patterns and conventions that become team defaults.

• Applied AI builder who ships to production – You're energized by LLMs, multimodal agents, orchestration protocols, and the messy work of making the entire AI stack reliable. You think instinctively in terms of evals, model regression tests, traceability, and exception handling. You've shipped multiple AI‑powered features to production and have hard‑won opinions about orchestration patterns, eval frameworks, and failure modes at scale.

• AI‑native developer across the entire SDLC – You wield tools like Cursor, Claude Code, and Copilot as extensions of your craft. You are extremely confident to run concurrent agents doing your chores reliably. You use AI to generate technical designs, scaffold APIs, draft schemas, write tests, and build migration plans. You've built custom workflows and internal tooling around AI‑assisted development that others on your team have adopted.

• Ship with velocity and craft – You find the shortest path to get features into users' hands while obsessing over the details that create trust. You balance the tradeoff between taking shortcuts and just enough tech debt to pay off in the next sprint or two. You believe speed and quality aren't opposites – they happen together when…