SDE-3

About Zenskar

Zenskar is an AI-native revenue automation platform built to handle real-world complexity.

It sits between your CRM and ERP automating everything in between: billing, revenue recognition, collections, usage metering, and analytics. Across any pricing model, any entity structure, any currency.

Our vision: Zero-Touch Finance. Agents execute. Humans supervise. Finance teams set the rules. Zenskar runs them.

Founded by Apurv Bansal and Saurabh Agarwal , second-time founders whose previous startups were acquired by Snapdeal and Gaana. The team brings experience from Google, Deutsche Bank, Elevation Capital, IIT Bombay, IIT Delhi, and Harvard Business School.

We have 5x'd revenue in the past year. We are default alive .

Funding

We raised $15M in Series A funding in April 2026, led by Susquehanna Venture Capital, Bessemer Venture Partners, Shine Capital, and Rho, with participation from Rocketship, J-Ventures, Future Back Ventures by Bain & Company, and Converge.

The funding is being used to expand our Agents Marketplace and scale operations, not headcount.

📰 Read the announcement →

https://youtu.be/jRb2ybvrSwU?si=vuLLgUY_MFdRzDMl

See how Zenskar automates the full order-to-cash cycle, from contract to cash,

without spreadsheets, workarounds, or engineering tickets.*

The Problem We're Solving

Finance teams aren't struggling because they lack AI tools. They're struggling because the systems underneath those tools were built for a simpler world. These systems label real-world complexity as edge cases and force teams into costly, error-prone workarounds: revenue leakage, delayed collections, audit risk, and finance teams buried in grunt work.

Bolting AI onto these broken foundations is as good as a Ferrari engine on a horse-drawn carriage. Zenskar is purpose-built from the ground up: the architecture handles complexity natively, so AI actually works.

It combines foundational flexibility + deterministic calculation + purpose-built AI agents to deliver end-to-end automation across the order-to-cash cycle - without workarounds, without engineering tickets.

The B2B billing and revenue automation market is $2B today, projected to reach $10B by 2030 .

What Customers Say

"We're saving 200+ hours/quarter on invoicing and receivables by completely automating our recurring billing."

Noy Kalansky, Finance Controller, Pontera

"Zenskar automates revenue recognition accurately for our value-based billing: agents reducing manual hours by 70%."

Matt Barnard, VP Finance, Vertice

"Zenskar’s agents automated 90% of our billing, integrated with our CRM, and accelerated revenue collection by a month."

Ming Lui, VP Finance, Yembo

"Sardine had spent 4 years running billing in-house for high-volume, usage-based pricing. Zenskar took care of it all."

Sardine team

"We launched our product 4 months faster instead of building an in-house system for our usage-based pricing."

Kshitij Gupta, CEO, 100ms

About the role

We’re looking for a senior, hands-on engineer who can own meaningful product and technical problems from the first unclear conversation to a healthy production rollout.

This is primary a backend role. This is not a role where seniority means moving away from code.

You will not have direct reports by default. Your leverage comes from sound decisions, clear execution, strong reviews, and making it easier for other engineers to contribute.

Billing experience is not required. A healthy respect for correctness is.

What you'll walk into

Our backend is primarily Python and Postgres on AWS, running a multi-tenant platform. Prior experience with this exact stack is useful, but not required.

The software moves money and sits between customers’ CRM and ERP systems. The interesting failures are often not loud exceptions—they are retries, duplicate actions, partial state, unclear audit trails, slow workflows, and an edge case that quietly creates the wrong invoice.

At the same time, finance teams should not need to understand our architecture to use the product. SDE3 engineers help make complex rules feel simple without hiding operational risk.

Projects you might work on

The exact project depends on product priorities, but SDE3-sized work could include:

• •Building multi dimensional pricing model in core billing engine to help support our clients’ complex billing needs
• •Scale our clickhouse server to handle 5x data growth we foresee over the next year.
• •Make our CRM/ERP integrations reliable by ensuring retries, idempotency, status visibility, recovery, and customer-facing failure states are present.
• •Build AI Agent to help parse contract PDFs reliably

Your first 30 days

The first month is about building context quickly while remaining useful. By the end of 30 days, we expect you to have:

• •Learned the core journey from customer contracts and usage data to invoices and revenue workflows.
• •Shipped several safe changes, including at least one production bug fix.
• •Participated in a real production investigation and understood the relevant logs, metrics, and operational tools.
• •Reviewed code and established working relationships with product, design, solutions, and engineering peers.
• •Identified one medium-sized problem to own and written or contributed to a clear technical plan.
• •Asked enough questions to expose assumptions rather than quietly building the wrong thing.

By 90 days

By the end of 90 days, you should be operating as the clear owner of a meaningful project or milestone. That means you can:

• •Turn an ambiguous goal into an agreed scope, design, delivery plan, and set of explicit risks.
• •Make and defend decisions across APIs, data, failure modes, reliability, and operability.
• •Break work down so one or more engineers can contribute effectively.
• •Plan migration, backward compatibility, rollout, monitoring, and recovery—not bolt them on after implementation.
• •Ship a meaningful milestone and verify its correctness and product outcome in production.
• •Own at least one difficult production investigation through diagnosis, mitigation, and follow-up.
• •Provide useful code and design reviews that improve both the implementation and the engineer.
• •Explain what should happen next: remaining risks, technical debt, product gaps, and the next sensible investment.

A strong 90-day outcome is not “completed every ticket.” It is “created clarity, shipped something meaningful, and left the system and team easier to operate.”

Who you are

• •You have roughly 5–7 years of professional software-development experience; scope and evidence matter more than an exact year count.
• •You have personally shipped and operated production systems used by real customers.
• •You remain comfortable coding, debugging, reviewing changes, and reading unfamiliar systems.
• •You have deep backend experience and can work across APIs, data, asynchronous processing, infrastructure, and production operations.
• •You have owned at least one substantial project through production and can explain your personal decisions and outcomes.
• •You work effectively with product, design, customer-facing teams, and engineers with different levels of experience.
• •You have helped other engineers become more effective through reviews, pairing, planning, or mentorship.

Good to have

None of these are mandatory:

• •Python, Postgres, AWS, or distributed-systems experience.
• •AWS, Docker, CI/CD, background jobs, or event-driven systems.
• •Experience with multi-tenant B2B software and external integrations.
• •Hands-on observability using logs, traces, metrics, and production profiling.
• •Billing, payments, accounting, fintech, or revenue-automation exposure.
• •Experience using AI coding tools without outsourcing judgment or understanding.

Location

• •Hybrid - 3 days per week
• •Office Location: Indiranagar, Bengaluru.
• •Address: 3rd Floor, A wing No 1, Carlton Towers, HAL Old Airport Rd, HAL 2nd Stage, Indiranagar, Bengaluru, Karnataka 560008.

Interview process

Ou