Ohmak Consulting LLP has partnered with Off Ramp Hub to build operations software for community banks and credit unions in the United States. The platform spans loan and deposit origination, compliance and exception management, client relationship management, and synchronization with core banking systems. It is a multi-tenant system in which each client institution runs as an isolated deployment.

The software sits in the middle of how a bank actually operates — a loan officer opens it to move an application forward, a client uses it to upload documents and sign them, an operations team uses it to clear exceptions before a cutoff. When it is wrong, someone's mortgage application stalls. That is the standard the engineering work is held to.

Why this role exists The platform is past the stage where features can be built by whoever is nearest to them. We have services in production, a real schema with real data in it, and customers who depend on both. We need engineers who can take a change from "a banker described a problem" to "it is live and correct," across the UI, the API, and the database, without handing it off three times on the way.

This is not a front-end role with occasional backend work, and it is not a backend role that sometimes touches

React. It is one job.

What you'll work on The platform is three services:

A customer-facing web application — the interface for everything the platform does. Next.js and React, organized as a monorepo of shared feature packages. Origination flows, the client-facing portal, relationship and analytics views, and internal configuration tooling all live here.

A REST API — NestJS over PostgreSQL. The domain model, the business logic, the integrations with core banking systems and third-party services, and the audit trail.



A background job service — scheduled data ingestion and ETL. You will touch this when a feature depends on ingested or scheduled data. You are not expected to own it. Most features you build will span the first two. Some will span all three.

What we're hiring for

You have done most of this in production, not only in tutorials or coursework.

Required

TypeScript on both sides of HTTP. You write React, and you write the service it calls. You are comfortable in the type system — generics, unions, narrowing — without turning every file into a puzzle.

React, in depth . Component composition, hooks, render behavior, and why something re-rendered when you did not expect it to. Experience with a modern data-fetching layer such as TanStack Query, SWR, or equivalent.

A Node API framework in production. NestJS is ideal. Express or Fastify with substantial production experience is fine. You understand dependency injection, middleware, request lifecycle, and how to structure a service that has outgrown a single file.

Relational data. You can design a schema, write the change, and reason about what it does to existing rows. PostgreSQL specifically is required. Prisma or an equivalent ORM — and the judgment to know when to drop to SQL.

Product UI that is more than a CRUD page. Forms, multi-step flows, client state, and the edge cases: resume later, empty, error, permissions.





Working in existing systems. You read the current code and data before proposing a design. You extend what is there. You do not rewrite as a first move, and you can tell the difference between code that is bad and code that is unfamiliar.

Judgment. The smallest change that is correct. Reuse before adding. No new dependency or abstraction unless the current one is actually insufficient.

Verification. You run the check. You do not ship on "this should work."

AI in the loop. You already use LLMs as part of how you ship — drafting, exploring an unfamiliar codebase, writing tests, reviewing a diff — and you treat the output as a draft you still have to verify. We are not hiring someone who pastes generated code they cannot explain. You will be asked to explain code you wrote, including the parts a model helped with.

Communication in written English , sufficient to specify a problem, argue for an approach, and disagree clearly in a pull request.

Strongly preferred

Experience in a regulated or operationally sensitive domain: banking, lending, insurance, healthcare, or identity.

Next.js App Router, Prisma, MUI, and TanStack Query specifically.

Monorepo work — Turborepo, Nx, or equivalent — including the dependency and versioning problems that come with shared packages.

Third-party integration work where you owned the failure handling, not just the happy path.

Experience with a state machine library such as XState for complex flows.

Practical

AWS: Enough IAM to not be dangerous.

Docker and GitHub Actions.

Python, for the background job layer. It is ancillary to this role.

SQL beyond ORM output: window functions, CTEs, materialized views, query plans

📌 Full Stack Engineer (Pune)
🏢 Ohmak Consulting
📍 Pune