Backend Engineer Intern (Node.js / TypeScript)

Company: Valura.Ai

Team: Platform Engineering

Location: [Bangalore/ GIFT City / Remote-India] (hybrid)

Experience: 3 to 6 years Reports to: [Head of Engineering / CTO]

Employment type: Full-time

About Valura

Valura.Ai is a regulated global-investing platform. Investors in India (IFSCA / GIFT City, LRS route) and the UAE use us to buy US equities, bonds, funds and gold from a single app. Behind the app is a real financial system: live brokerage order routing, INR and USD money rails, a double-entry ledger, KYC/AML pipelines, an AI research service, and a partner API used by distributor firms.

You would be joining the team that builds and owns the services in the middle of all of that.

The stack you would actually work in

This is not aspirational. It is what we build on today.

1. Runtime and language: Node.js, TypeScript 5.x, Express
2. Monorepo: Turborepo + pnpm workspaces, with shared internal packages for logging, linting, formatting, TypeScript config and test presets
3. Data: PostgreSQL, including time-series workloads, Prisma as the primary ORM alongside raw SQL where it matters, MongoDB, Redis
4. Migrations: ORM-managed migrations plus SQL migrations for the time-series side
5. Async work: BullMQ queues, scheduled jobs, long-running reconciliation and sync loops
6. Realtime: WebSockets for market data and portfolio streaming
7. Auth: Managed identity provider with separate user pools per tenant type (retail, admin, partner), JWT verification, standard password hashing
8. Cloud: AWS. Object storage and presigned URLs, CDN signed URLs, transactional email, notifications, managed auth
9. Integrations: global broker-dealers and custodians, payment and FX providers, KYC / AML / e-sign vendors in both jurisdictions, and communications providers
10. API docs: OpenAPI, generated from the codebase
11. Testing and quality: Jest and Supertest, Playwright for integration, static analysis, dependency scanning and DAST in the pipeline
12. Delivery: Docker images built from the monorepo, GitHub Actions, containerised deployment on AWS for production and a self-hosted platform for lower environments

The kind of services you would own or contribute to:

These are large, long-lived TypeScript codebases with substantial data models and live customer records behind them.

What you will do

Build product surface

1. Design and ship REST endpoints that the web app, the React Native app and partner integrations depend on. Contract first, documented in OpenAPI, versioned when it needs to be.
2. Model data properly and write the migration that gets there safely, on schemas that already hold live customer and money records.
3. Build the async side: queue workers, scheduled reconciliation jobs, webhook receivers that are idempotent because the sender will retry.

Integrate money and market systems

1. Own integrations with brokers, custodians, payment providers and KYC vendors. Each one has a different auth model, different rate limits, different failure semantics and documentation of varying honesty.
2. Handle the things that make financial integrations hard: partial failures, throttling, out-of-order webhooks, replay, settlement timing, and reconciling your view of the world against theirs every single day.
3. Write code that survives a counterparty being down without corrupting our state.

Correctness, because this is money

1. A bug here is not a bad user experience. It is a wrong balance, a duplicate order or a mis-stated tax figure that an auditor will eventually ask about.
2. Build for idempotency, atomicity and auditability by default. Understand when you need a database transaction and when you need a distributed lock.
3. Write the test. Reconciliation and ledger-adjacent code is not optional-test territory.

Raise the floor

1. We review our own platform regularly and keep a live engineering-quality backlog alongside the product roadmap: authorization coverage, service boundaries, observability and test coverage.
2. You will spend real time on hardening work, not only features. If that sounds like a chore rather than an opportunity, this role will frustrate you.
3. Push shared logic into shared internal packages rather than copy-pasting between services. Reducing duplication across a fast-grown monorepo is ongoing, deliberate work.

Operate what you build

1. Your service, your logs, your alerts, your on-call escalation. Platform provides the paved road; you drive on it.
2. Participate in code review, incident response and postmortems.

What we are looking for

Must have

1. 3+ years building production backend services in Node.js and TypeScript. Strong, idiomatic TypeScript, not JavaScript with a few annotations.
2. Deep Express or equivalent: middleware ordering, error handling, request lifecycle, why your auth middleware is not running on the route you thought it was.
3. Real PostgreSQL skill. You can read a query plan, add the right index, and reason about transaction isolation and locking.
4. Practical ORM experience (Prisma, TypeORM, Drizzle or similar) plus the judgement to drop to raw SQL when the ORM is the wrong tool.
5. Async and distributed fundamentals: queues, retries with backoff, idempotency keys, at-least-once delivery and what it implies.
6. REST API design: resource modelling, status codes, pagination, versioning, error contracts.
7. Testing as a habit. Unit and integration, with Jest/Supertest or equivalent.
8. Comfortable in Docker and a CI pipeline. You can debug a build that works locally and fails in CI.
9. Git and code review discipline in a shared monorepo.

Nice to have

1. Fintech, brokerage, payments, lending or another domain where the numbers have to be right.
2. Third-party financial API integration: brokers, custodians, payment gateways, KYC vendors.
3. Double-entry accounting concepts, reconciliation, settlement cycles, corporate actions.
4. AWS depth: containerised services, managed auth, object storage, email, IAM.
5. WebSockets at scale, market data fan-out, or time-series databases.
6. Python. Some of our services are Python and FastAPI, and you will read across the boundary even if you do not write there.
7. Monorepo tooling: Turborepo, pnpm workspaces, Nx.
8. Security fundamentals: OWASP Top 10, authorization design across multiple tenant types, secrets handling.

How we work, so you can self-select

1. Feature branch to pull request. Every change is reviewed.
2. We write things down. Design notes before big changes, postmortems after incidents.
3. We are a regulated business in two jurisdictions. Some things are slower than you would like and are slow for a reason.
4. Small team, short decision path. You will ship in your first week and own something real inside a month.

How we will evaluate you

1. Intro call (30 min).
2. Technical conversation (60 min): TypeScript and Node depth, SQL and data modelling, and a walk-through of a service you designed.
3. Practical exercise (take-home, timeboxed to ~3 hours, or live pairing): build a small service with a webhook receiver and a queue-backed worker, and make it correct under retries and duplicate delivery. We care about your error handling and your tests more than your feature count.
4. System design round (60 min): a real problem from our domain, for example designing a sync and reconciliation loop against a flaky third-party API.
5. Founder conversation.

No algorithm puzzles unrelated to the job.

Why this role is interesting

1. The problems are genuinely hard and genuinely consequential. Ledgers that must balance, two regulators, live money moving between currencies and counterparties.
2. Breadth: brokerage, payments, KYC, realtime market data, partner APIs, and a growing AI service tier.
3. Engineering quality is treated as roadmap work, not something you campaign for. You get a clear mandate to build things properly.
4. Direct access to founders and to the people who understand the regulation.
5. [Compensation band, ESOP, benefits to be inserted.]

To apply

Send your CV plus a short note on one backend system you built where correctness mattered, and what you did to guarantee it, to [careers@valura.ai].