Software Engineer – Product

Why this role exists

Commenda helps companies operate across borders. We handle indirect tax, entity management, transfer pricing, and corporate tax and accounting for multinational businesses, so our customers can hire, sell, and operate in fifty jurisdictions without hiring fifty accountants.

That breadth is why we run as a multi-product company: each product has a GM with a pod of engineers. This model ships what customers ask for. It does not build the things no single pod owns:

• the customer and entity model every product reads from
• the document pipeline every filing runs through
• the integration layer that pulls in accounting data
• permissions and access control
• the AI infrastructure the pods build on

Left to the pods, those get built four different ways, or once and then never touched again.

Core Product owns that layer. The team reports to Adarsh, our Head of Product, who is an engineer and still writes code.

What you'll own

The shared primitives

The data models, services, integrations, and internal tooling every product is built on. Built once, built well, and documented well enough that a pod engineer can pick them up without finding you first. Part of the job is deciding what belongs in the core layer, which means telling a pod no when they want a special case.

Surge capacity

Once or twice a quarter a project matters enough to the company that it outgrows the pod carrying it. You join, get to the shape of the problem fast, ship, and hand it back in better condition than you found it.

The AI development lifecycle

We build with AI agents as a matter of course, and we want them to be good in our codebase. You'll structure the repo for agents, write the evals, define what "reviewable" means for agent-written code, and push on the tooling until the whole engineering org moves faster.

Code quality

The standards, tests, and architecture that keep this a codebase people and agents can move fast in.

Security

We hold customer tax and entity data across dozens of jurisdictions. Access control, tenant isolation, and audit all live in the core layer.

How we'll judge it

• The shared systems work. When something breaks across products, it traces back to you and you fix it.
• The codebase gets easier to work in over time, for people and for agents. Clear boundaries, real tests, conventions that hold.
• Core systems absorb growth in customers, entities, and jurisdictions without a redesign, and without leaking data between tenants.
• Product teams use what you build instead of rolling their own. If they don't, that's a signal about your work.
• Customers get correct results on time. Every filing, registration, and calculation runs through the core layer.

The week-to-week

This is a generalist role. In one week you might redesign the entity model, trace a cross-tenant permissions bug, and rewrite an integration's retry logic. You should want that. You'll form your own opinions and execute on them, with AI doing a lot of the work.

What we're looking for

Required

• An extreme sense of ownership and urgency. You treat a problem in shared infrastructure as yours the moment you see it. You don't wait to be assigned work and you don't let things sit. This is a high-intensity team, and the work sometimes runs into nights and weekends.
• A strong software engineering background, ideally from a venture-backed startup in Bangalore. You've built systems other engineers depended on, and you've lived with your own design decisions long enough to regret a few.
• Attention to the customer outcome and to the system that gets them there. You won't ship a hack that falls over at 10x, and you won't spend a quarter on architecture while a customer's filing is wrong.

Preferred

• You've used AI to automate real knowledge work, or shipped systems where LLMs do production work.
• Background in tax, law, finance, or another detail-dense regulated domain. Our problem space rewards people who like getting the details right.

Where the role sits

You'll work with the Head of Product every day, and with the product GMs and the CTO from time to time. The role is based in Bangalore with the rest of our engineering team. Our US team is split between San Francisco and Seattle.