Our teams
How we run engineering
You built it, you monitor it, you fix it.
Engineers at Intempt build and maintain a production AI platform serving real customers. This is not a research or prototype environment. You built it, you monitor it, you fix it when it breaks.
⚡ What engineering owns
- Production-quality code. End-to-end service ownership -- build, deploy, monitor, fix
- RCA after every Critical and Major incident
- Push back on bad specs before picking up a ticket. Collaborate with PMs on requirements first
🤖 AI tooling
Engineers run Claude Code sessions with harness and loop engineering for backend services -- multi-agent workflows, automated code review, test generation, and deployment checks. Lovable handles frontend prototyping and full builds. Cursor for inline AI-assisted editing. Claude on claude.ai for architecture discussions, debugging sessions, and design reviews. Every engineer has AI agents running alongside them throughout the day. The expectation on output reflects this -- you ship more because you work with AI, not because you work longer.
🔧 Service ownership
Every service has a clear owner. That owner writes the code, monitors it in production, responds when it breaks, and files the RCA. No throwing code over the wall to an ops team. See our Engineering Principles for the technical standards behind this.
🛡️ On-call
On-call is opt-in and compensated. Team members who participate receive 15% of their daily rate per on-call day, plus incident-based multipliers for production issues. Rotation is weekly among those who opt in. No penalty for not participating -- teams coordinate coverage among themselves.
🎧 Customer support
Engineers don't respond to support tickets directly. Customer support is AI-first. Confirmed bugs and infrastructure issues land in the engineering backlog as regular tickets. If a customer ticket identifies a production incident, it follows the incident escalation protocol.