Backend Developer

ZenteiQ. AI Platform Engineering Backend Engineer Mid-Level / Senior Full-time Bengaluru (Onsite) You are an engineer who gets uncomfortable when a service does something it cannot explain, when there is no trace, no metric, no clear reason a job took four times longer than expected. You build backends that are boring in the best sense: predictable under load, observable when something goes wrong, and straightforward for the next engineer to operate. You do not reach for complexity until simplicity has genuinely failed.

The Problem You Will Own: ZenteiQ is building AI infrastructure for scientific and domain-expert users, a platform where models get registered, evaluated, promoted, and served under real production conditions. Right now, the core APIs, data layer, and async job infrastructure need an engineer who can take them from working to production-grade: reliable schema design, event-driven workflows that handle failure gracefully, and services that remain operable as load increases. You will own the backend platform layer end-to-end from the database schema to the Kafka consumer to the Kubernetes deployment, and be the person who sets the quality bar for how the rest of the team writes and ships services.

Responsibilities:

• Design and build the REST APIs that power the model registry, evaluation execution, and promotion workflows with clean OpenAPI specs, explicit versioning, and error handling that gives callers enough information to recover.
• Own the PostgreSQL data layer: schema design with proper indexing and constraints, migration strategy, and query optimisation that holds up as data volume grows.
• Build the async job infrastructure: Celery workers on Redis, Airflow DAGs for orchestration, and make them sufficiently observable that on-call is not a guessing game.
• Design and maintain the event-driven components (Kafka / Pub/Sub) with the reliability properties that distributed systems demand: idempotency, backpressure handling, deadletter queues, and retry logic.
• Ensure every service is containerised, deployable on Kubernetes (GKE), and ships with the logging, metrics, and tracing that lets you debug a production incident in under thirty minutes.
• Write architecture decision records for non-obvious choices and API documentation that a new team member can follow without asking you to walk them through it.

Requirements:

• You have shipped Python backend services to production and can point to specific decisions: schema design, caching strategy, async pattern that you made and stand behind.
• You understand PostgreSQL well enough to look at a slow query, explain why it is slow, and fix it, not just add an index and hope.
• You have built or maintained an event-driven system (Kafka, Pub/Sub, or equivalent) and can articulate what happens when a consumer falls behind or a message is processed twice.