Fullstack Engineer

A bit about axiTrust. And the moonshot we are chasing!

If "surety bond" did not ring an immediate bell, that is the problem and the opportunity.

Every year, thousands of crores of MSME working capital sits locked inside bank guarantees. It is the price businesses pay just to participate: to win a government tender, to bid for a corporate contract, to prove they will deliver. The bank guarantee is how Indian commerce builds trust. It is also slow, expensive and largely inaccessible to the small and mid-sized business that actually does most of the building.

A surety bond does the same job better. It is how a contractor proves to a project owner that they will deliver, without tying up their balance sheet to do it. It is the trust infrastructure that makes tendering work. And in a country running an infrastructure push of the scale India is, the category we are creating has the potential to move GDP, not just metrics.

We are building India's first full-stack surety bond platform for MSMEs, and we are only beginning to discover how far the use case goes. Every industry that runs on contracts, tenders and performance guarantees is a potential home for surety bonds. Every new use case is a new set of relationships to build: Insurers who underwrite the risk, Beneficiaries who accept the bond, Channel Partners who distribute it and MSMEs who finally have access to a tool their larger competitors have always had. This is not a market we are entering. It is a category we are creating.

We were founded in 2024 by serial entrepreneurs and industry veterans who have done this before (ex-founders of numberz, acquired by Chargebee), backed by global VCs and industry veterans, with platform partnerships already running across Government, leading Insurers, corporates and PSUs. We are digital-first and AI-savvy by design. We are also a company where a significant part of the growth happens in person: customer conversations, industry panels and rooms where the right people are making decisions about surety bonds for the first time. Marketing straddles both. The digital engine and the room where it is all being shaped.

We move at the pace of our change-the-world conviction.

Why this role even exists. And why now.

axiTrust is the platform layer that brings the surety bond ecosystem together — connecting businesses applying for bonds with insurers issuing them, on a multi-tenant system designed for a strictly regulated, document-heavy, trust-critical environment. The market is large, the timing is right, and the engineering problems are genuinely interesting.

Our product handles real financial workflows: bond applications, document generation, document e-signing, risk analysis, and integrations with government and partner APIs. The foundation is in place. We are looking for passionate engineers who can take full ownership of features end-to-end, raise the engineering bar, and ship to thought out features to the platform

If this hire works, the platform scales reliably, the codebase gets measurably better over time, and the team ships faster — because there is someone who catches problems before they become incidents and leaves every system they touch cleaner than they found it.

What you will own. All 4 of them.

1. Full-Stack Feature Ownership. You own features from schema design through migration, service logic, REST API, and React interface — with minimal hand-holding and full accountability for outcomes. This is not ticket delivery; it is engineering leadership at the feature level.

2. Security and Access Control. You contribute to RBAC: permission modelling, multi-tenant role scoping, API key management, and audit logging. In fintech, this is foundational, not optional.

3. Third-Party Integration Reliability. You own the reliability of integrations with e-signing, cloud storage, AI pipelines, and external APIs. The product only works when these work. You make sure they do.

4. Codebase and Tech Debt Management. You identify tech debt deliberately, propose refactors, and execute them. You also review with intent — catching logic errors, security gaps, and design issues before they ship, and treating code review as knowledge transfer.

Your first 90 days. No nasty surprises.

The first 30 days. Context before change.

You spend month one orienting, not acting. You read the codebase, meet the team, understand the bond application lifecycle from a customer’s perspective, and trace how data flows across the stack. By the end of week four, you can explain what the platform does, how it is built, and where the sharpest edges are.

Days 30 to 60. First output.

Your first feature ships. It might be small, but it is yours from schema to interface. You have also identified at least one gap in the integration layer or access control model and have a proposal on the table. The team knows how you work.

Days 60 to 90. Something is running. Something is being measured.

You have delivered a second feature, started a meaningful refactor, and presented a 12-month view of what you want to build and improve — with targets you are willing to be held to.

At 12 months. Here is what matters.

The platform is more reliable, more secure, and faster to ship on than when you joined. You own a module or subsystem that would be meaningfully worse without you. The team ships faster because you are in it.

What a week actually looks like.

• 50% Product Engineering. Writing and reviewing TypeScript across the full stack — schema migrations, Express service logic, REST APIs, and React interfaces. You are shipping code most days.
  
• 20% Integration and Reliability Work. Monitoring third-party integrations, debugging production issues across layers, and improving error handling for e-signing, government APIs, and AI pipelines.
  
• 15% Code Review and Knowledge Sharing. Reviewing pull requests with intent — catching security gaps and logic errors before they ship, and helping the team level up through the review process.
  
• 10% Tech Debt and Refactoring. Identifying and addressing structural issues in the codebase deliberately, not reactively.
  
• 5% Architecture and Planning. Thinking through design decisions for upcoming features, discussing schema choices, and keeping documentation current.
  

The people you will work with.

You report to the Engineering Lead and work closely with the product engineering team. There is no direct report in this role; this is an individual contributor position. You work alongside other engineers and collaborate daily on features, reviews, and incidents.

Your primary working relationships are with the product team on feature scope, the founders on platform direction, and external partners on integration requirements — including insurers, e-signing providers, and API vendors .

Requirements

What we hope you bring.

You have 2–5 years of professional engineering experience shipping production systems. You write TypeScript fluently — across both Node.js backend and React frontend — and you understand the type system, not just the syntax. You have built complex stateful UIs in production, designed service layers in Express, written schema migrations from scratch, and have informed opinions on REST API design that you can defend.

Beyond the core stack, experience with TypeORM, BullMQ, Redis, or AWS is a strong advantage. So is a background in fintech, insurance, or any compliance-sensitive product. Familiarity with multi-tenant system design, document generation pipelines, or LLM API integrations in production will make you immediately useful.

What matters more than any specific tool is how you work. You have owned a module or subsystem, not just delivered tickets against it. You know the difference between a quick fix and the right one — and you communicate clearly when you are applying one instead of the other. You can land in an unfamiliar 10,000-line service and orient yourself within the hour.

Our Tech Stack

• Language and Runtime: TypeScript, Node.js
  
• Frontend: React, Vite, Tailwind, Mono-Repo
  
• Backend: Express.js, REST APIs, Layered Middleware Pipelines
  
• Database and ORM: PostgreSQL, TypeORM
  
• Auth and Security: JWT, HMAC-Signed API Keys, PKI and Certs
  
• Jobs and Caching: BullMQ, Redis, ioredis
  
• Documents and PDF: Puppeteer
  
• Cloud and Storage: AWS
  
• AI: Google Vertex AI, Anthropic API, Claude Code, Gemini API
  

What good looks like at six months.

• Multiple features shipped end-to-end with full ownership, from schema to interface, with no production regressions.
  
• At least one third-party integration meaningfully more reliable than when you joined, with documented failure modes and monitoring.
  
• RBAC and access control model extended or improved, with audit logging covering all critical flows.
  
• A prioritised tech debt register exists and at least one meaningful refactor has shipped.
  
• Code reviews are a regular part of your week and other engineers consistently cite them as useful.
  
• The team trusts you to take on an ambiguous problem and come back with a clear path forward, not just a question.
  

The values we actually live by.

I.C.G.R.I.T. is how we work. These values were not written on a retreat and filed away. They have evolved with us over many months. We strive hard that they show up in every interaction, review, every offer letter and more importantly, in every Tuesday afternoon when the easy choice and the right choice are different.

Honestly? This might not be for you if...

• You think working in a regulated, technical, slightly unsexy industry is beneath you.
  
• You want a logo your friends recognise at parties.
  
• You think Friday team socials are a waste of time.
  
• "We have always done it this way" sits comfortably in your vocabulary.
  
• Speed and Agility to take technical decisions to quickly solve business problems does not excite you.
  
• If you feel tech debt should never exist.
  

Benefits

What's on the table. Comp and the rest.

• Competitive fixed and variable pay combo calibrated to your experience. The specific range is shared with shortlisted candidates after the first conversation. ESOPs are part of the package, not a footnote.
  
• Health cover for you and immediate family.
  
• Annual learning budget for courses, conferences or that Python bootcamp you have been eyeing.
  
• A founders' office that talks to Engineering constantly, not every quarter.