Backend Developer Experience: 2–4 years Location: Bangalore (in-office)
Stack: Java 17, Spring Boot, PostgreSQL
Reports to: CTO
About the Role Zenalyst builds an enterprise agentic execution layer for the CFO's office — treasury, procure-to-pay and collections automation for large organisations.
You will work on the Java backend gateway: the service layer that sits between our agent runtime and customer financial data. It is the only path to customer data in the system, and it is where correctness, tenant isolation and bank integration all live. Nothing reaches a customer database without going through code you will own.
This is a systems role, not a CRUD role. If you have never had to think about what happens when a bank API times out halfway through a statement sync, you will learn quickly here.
Responsibilities Build and own Spring Boot services in the backend gateway — the single exit path from our agent runtime to customer data
Work on the multi-tenant data layer, where isolation is enforced by physical database connection selected from the verified JWT principal, not by query filters
Build and maintain bank connectors over mTLS — statement fetch, balance retrieval, bulk async sync, watermarking and resumption
Implement transaction ingestion: normalisation, multi-tier fingerprinting for deduplication, and classification pipelines
Design and evolve PostgreSQL schemas for treasury domain objects — accounts, transactions, entities, projects — and write migrations in Flyway
Build the safe execution layer for machine-generated SQL: AST inspection, table allow-lists, read-only transactions, row caps and column-level PII stripping
Build scheduled and long-running jobs on JobRunr — sync jobs, reconciliation runs, batch imports
Instrument everything with OpenTelemetry; trace context propagates end to end and we expect you to keep it that way
Debug production issues across the Java backend, the Python agent engine boundary, and bank connector failures
Requirements Essential




2–4 years building production backend services in Java, with Spring Boot
Strong PostgreSQL — schema design, indexing, query tuning, transactions and isolation levels
Solid understanding of concurrency in the JVM, and of async or reactive clients
REST API design, JWT-based authentication, and a real understanding of and TLS
Experience with a migration tool (Flyway or Liquibase) and with Git-based team workflows
Ability to reason about failure: retries, idempotency, partial failure, and what "exactly once" actually costs
Clear written communication — architecture and decisions are documented here, not verbal
Strongly preferred
Any hands-on work with mTLS, client certificates, or certificate lifecycle management
Integration experience with banks, ERPs (SAP, Oracle, Tally) or payment systems
Docker, CI/CD (GitHub Actions), and cloud deployment on Azure or AWS
Familiarity with OpenTelemetry, distributed tracing, or structured observability
Working knowledge of Python — our agent engine is FastAPI, and you will read across the boundary
Nice to have
Exposure to LLM APIs, RAG, agent frameworks or the Model Context Protocol
Redis, message queues, or event-driven job processing
Experience in a regulated or audited setting (ISO 27001, SOC 2)
Who This Suits You should be someone who reads a stack trace before asking, who is uncomfortable shipping code they cannot explain, and who finds correctness under failure more interesting than shipping features fast. Our system moves real money for real enterprises — the standard is high and the feedback loop is short.
What We Offer End-to-end ownership of services, not tickets
Genuinely hard problems: multi-tenancy at the physical database level, bank integration, deterministic control over AI-driven execution
Direct access to founders and the CTO; short decision cycles
Competitive fixed compensation plus ESOP
Apply Send your CV to [email protected] with the subject line "Backend Developer — [Your Name]". Include a GitHub profile or something you have built

📌 Back End Developer (Bengaluru)
🏢 Zenalyst.AI
📍 Bengaluru