AI Engineer

Certa (certa.ai http://certa.ai) is an AI-native third-party risk management platform that unifies the full third-party lifecycle, from onboarding through continuous monitoring and offboarding. Enterprises from the Fortune 500 to fast-growing startups use our no-code platform to manage vendors, suppliers, and partners across risk, compliance, and ESG. Trusted by Honeywell, Uber, MARS, and Boeing, we’ve processed over 10 million entities for 100,000+ users across 120+ countries.

At Certa, AI agents do real work for enterprise risk and procurement teams: Studio designs workflows, Data Agent answers questions over customer data, and Risk Agent assesses third parties. The model is the same one everyone can buy - the harness is what makes ours do the job reliably, safely, and cheaply, and you’ll own that harness. This isn’t a “build AI features” role: you own an agent end to end and you’re measured on whether it does the task - success rate, latency, cost per task, and what customers stop doing by hand. It’s a small team with high ownership, where you’ll work directly with PMs, design, and customers, and be trusted to make the call.

WHAT YOU’LL DO

- Own the agent loop: Step control, planning, retries, error feedback, subagents, and parallel tool calls for long, multi-step tasks.

- Design tools & actions: Build the tools, MCP servers, and skills our agents use - narrow, well-described, permissioned, and safe to call against customer data.

- Engineer context: Decide what the model sees on every step - compaction, memory, retrieval-as-a-tool, and how agents read large enterprise records without drowning.

- Build evals that gate every change: Golden sets, regression suites, and trace-based scoring wired into CI, so no prompt, model, or harness change ships blind.

- Own model choices & the runtime: Route across models on capability, latency, and cost, running new model launches through the eval suite and re-tuning the harness when the frontier moves, with durable sessions, sandboxed execution, nested-trace observability, token budgets, and graceful fallbacks for multi-tenant enterprise customers.

- Own the backend systems: Design services end to end (data model, APIs, storage choice, failure modes), build async pipelines (queues, workers, retries, idempotency, backpressure), and make them fast and cheap at scale (caching, batching, indexing, p95/p99 latency budgets) on multi-tenant AWS with isolation, least-privilege access, PII handling, and audit trails.

- Own it in production: Write the design doc, weigh the trade-offs, defend them in review, and own the service in production.

WHAT SUCCESS LOOKS LIKE

- Day 30 - Backend: Own one Studio backend service end to end and ship a production change (a new API, a pipeline fix, or a performance improvement) with a measurable result, such as a lower p95 latency or error rate, and join its on-call rotation.