Back End Engineer

Role & responsibilities

• Build core APIs: stateless Node.js and TypeScript services that carry the business logic of the Cladbe OS

• Own data integrity: PostgreSQL is the source of truth and the final guard against a double sale. A Redis-compatible store serves live inventory and short-lived holds in front of it

• Engineer for concurrency: locks, idempotency and safe retries that hold up on launch day

• Build event-driven workflows: when a booking is confirmed, the payment schedule, demand letters and inventory updates follow automatically, with Kafka as the event bus and a durable workflow engine running them

• Integrate with an RBI-regulated payment partner for booking and payment-status workflows and reconciliation. Buyer money never sits with Cladbe; your code tracks it, never holds it

• Run what you build: deploy and tune services on Kubernetes, and own tracing and metrics

Must-Have Skills

• Node.js and TypeScript in production

• PostgreSQL in production: transactions, isolation levels, row locking

• Idempotent APIs and safe retries

• At least one message queue or event bus (Kafka, SQS, RabbitMQ etc.) in production

• Ability to debug from logs, metrics and traces

Good to Have

• Graph databases

• Redis-based distributed locks

• Kubernetes in production

• Payments or fintech experience Tech Stack Node.js, TypeScript, PostgreSQL, Redis-compatible store, Kafka, Kubernetes, graph database