Skip to content
Ankit Raminwar

Open to full-stack roles

Ankit Raminwar — Full-stack software engineerFrom interface
to infrastructure.

I build complete products at BridgeNext: React and TypeScript applications, NestJS and GraphQL APIs, SQL and offline-first data, and the AWS and Azure infrastructure they run on. Outside work, I ship my own apps to the Play Store and Chrome Web Store.

system.maplive trace
Web appReact · TypeScriptIdentityCognito · RBACMobile appExpo · React NativeApp shellModule FederationAPI gatewayGraphQL · RESTLocal storeSQLite · FTS5ServicesNestJS · Node.jsServerlessAzure FunctionsSyncSupabase · RLSPostgreSQLrelationalMSSQLrelationalBlob · CDNstoragecloud · AWS · Azure · CI/CD · GitHub Actions

Shipping with

  • React
  • TypeScript
  • Next.js
  • Redux
  • Angular
  • Tailwind CSS
  • Vite
  • Expo
  • PWA
  • Jest
  • Cypress
  • Node.js
  • NestJS
  • GraphQL
  • Apollo
  • .NET
  • PostgreSQL
  • MSSQL
  • SQLite
  • Supabase
  • AWS
  • Azure
  • GitHub Actions
shipping production software at BridgeNext since January 2022
4+ yrs
from intern to Software Development Engineer — three promotions
27 mo
applications consolidated into one PWA behind a single sign-on
13 → 1
independent products on Google Play and the Chrome Web Store
2 live

01Selected work

Systems for enterprise clients, and products I ship on my own.

Each case study covers the problem, what I owned, the architecture and the trade-offs. Client work is under NDA, so it is shown as live system diagrams rather than screenshots.

Enterprise2024 — present

React micro-frontends for a logistics product, composed at runtime with Module Federation so each domain ships without redeploying the whole application.

  1. Host shell
  2. Module Federation
  3. Domain remotes
  4. Shared UI
  • React
  • TypeScript
  • Redux
  • React Suspense
  • Module Federation

Software Development Engineer · frontend

Enterprise2022 — 2024

Consolidated 13 separate applications into one installable PWA with a single AWS Cognito sign-in and role-based onboarding.

  1. 13 apps
  2. Cognito SSO
  3. RBAC onboarding
  4. One PWA
  • React
  • PWA
  • AWS Cognito
  • RBAC
  • Vite

Associate Software Development Engineer

Independent productLive

An offline-first devotional library for Android — aartis, mantras and stotras in Hindi, Marathi and English, with full-text search and no network required to read.

  1. CDN collections
  2. Sync + de-dupe
  3. SQLite · FTS5
  4. Offline UI
  • Expo SDK 54
  • React Native
  • TypeScript (strict)
  • SQLite + FTS5
  • Zustand

Solo: product, design system, mobile, data

EnterpriseSince 2024

A serverless pipeline that turns an HR spreadsheet into personalised appraisal letters — rendered as PDFs, stored, and emailed in batches.

  1. Excel upload
  2. Azure Function
  3. Velocity → PDF
  4. MSSQL + email
  • Azure Functions
  • Node.js
  • Azure Blob Storage
  • VelocityJS
  • MSSQL

Software Development Engineer · backend & architecture

More work

Independent product

Hisab Kitab

An offline-first personal finance app — every write lands in local SQLite first and syncs to Supabase in the background.

  1. Local write
  2. SQLite
  3. Background sync
  4. Supabase + RLS
Read case study

Enterprise

Property management platform

Angular micro-frontends with Module Federation on .NET services, alongside a migration of legacy systems to Microsoft Azure.

  1. Angular MFEs
  2. Module Federation
  3. .NET services
  4. Azure
Read case study

Independent product

Chotu Pet

A pixel companion that lives on every page you visit and evolves through five stages based on your browsing — a Manifest V3 Chrome extension.

  1. Browsing activity
  2. Evolution rules
  3. Persisted state
  4. Page overlay
Read case study

02Across the stack

I work at every layer a request passes through.

Follow a request from the browser to the cloud. Each layer shows what I build there and where I have done it.

Layer 1 of 6 · Interface

Product interfaces

Where users meet the system. Rendering, interaction, accessibility and perceived speed.

What I build here

  • Component architecture with typed props and shared libraries
  • Responsive, accessible UI that holds up across devices
  • State with Redux, Context and hooks — local by default, global when earned

Tools

  • React
  • TypeScript
  • Next.js
  • Tailwind

Across every layer → Jest · Cypress · SonarQube · CI

03Experience

One company, four roles, steadily more ownership.

I joined BridgeNext (formerly Emtec Technologies) as an intern in January 2022 and was promoted three times in 27 months, from implementing features to owning architecture and delivery across the stack.

  1. InternJan 2022
  2. TraineeJul 2022
  3. AssociateOct 2022
  4. SDEApr 2024
  • Apr 2024 — Present

    Software Development Engineer

    Architecture and full-stack delivery across micro-frontends, serverless automation and cloud migration.

    • Delivered logistics-domain micro-frontends with React, Redux and Module Federation
    • Contributed to the architecture of a serverless HR automation system on Azure Functions
    • Optimised legacy applications and supported their migration to Microsoft Azure

    Case studiesLogistics micro-frontend platformHR appraisal automationProperty management platform

    • React
    • TypeScript
    • Redux
    • Module Federation
    • Angular
    • Azure Functions
    • MSSQL
  • Oct 2022 — Apr 2024

    Associate Software Development Engineer

    Owned features across enterprise applications, with a focus on performance, reuse and test coverage.

    • Built a PWA that consolidated 13 applications for a sports platform
    • Integrated AWS Cognito for unified SSO and role-based onboarding
    • Increased test coverage with Jest and Cypress

    Case studiesSports platform: 13 apps, one PWA

    • React
    • PWA
    • AWS Cognito
    • Vite
    • Jest
    • Cypress
  • Jul 2022 — Sep 2022

    Trainee Software Development Engineer

    Converted from internship to a full-time track; ramped up on enterprise frameworks and agile delivery.

  • Jan 2022 — Jun 2022

    Software Development Intern

    Hands-on full-stack web development, implementing features alongside senior engineers.

Full journey: education & certifications

04How I think

I don’t start with the framework. I start with the problem.

Six working principles, each tied to a project where it made a difference.

  1. 01

    Find the real constraint first.

    Thirteen apps did not need a new UI library. They needed one identity and one entry point. The stack follows from that.

    In practice → Sports platform

  2. 02

    Draw the boundaries before the components.

    Where a system splits decides who can ship independently. I draw micro-frontend and API boundaries along domains, not pages.

    In practice → Logistics micro-frontends

  3. 03

    Treat the network as optional.

    Remote modules, APIs and mobile signal all fail. Suspense fallbacks, local-first data and background sync keep the product usable when they do.

    In practice → Aarti Sangrah

  4. 04

    Automate the second time.

    If a person does the same careful thing for every row of a spreadsheet, that is a pipeline waiting to be written.

    In practice → HR automation

  5. 05

    Test the paths that pay the bills.

    Coverage numbers matter less than whether sign-in, onboarding and the core workflow are protected. Jest for logic, Cypress for the journeys.

    In practice → Sports platform

  6. 06

    Make the expensive path lazy.

    Users pay for every byte up front. Code-split by route and by remote, defer what is below the fold, and measure before optimising.

    In practice → Logistics micro-frontends

05Toolkit

Grouped by what it is for, and honest about depth.

Strong means used daily and shipped repeatedly. Working knowledge means shipped with, comfortable without a reference. Exploring means actively learning.

  • Strong
  • Working knowledge
  • Exploring

Frontend

Product interfaces and the architecture that keeps them fast

  • React— Strong
  • TypeScript— Strong
  • JavaScript— Strong
  • Redux— Strong
  • Tailwind CSS— Strong
  • Vite— Strong
  • Next.js— Working knowledge
  • Angular— Working knowledge
  • React Native / Expo— Working knowledge

Architecture

How large frontends are split, composed and secured

  • Micro-frontends— Strong
  • Module Federation— Strong
  • PWA— Strong
  • SSO / RBAC— Working knowledge
  • Offline-first sync— Working knowledge

Backend & APIs

The contracts and services the interface depends on

  • GraphQL / Apollo— Strong
  • REST API design— Strong
  • Node.js— Working knowledge
  • NestJS— Working knowledge
  • Azure Functions— Working knowledge
  • .NET / ASP.NET Core— Exploring

Data

Where state lives — on the server and on the device

  • MSSQL— Working knowledge
  • PostgreSQL— Working knowledge
  • SQLite— Working knowledge
  • Supabase— Working knowledge

Cloud & delivery

Getting code to production and keeping it observable

  • Microsoft Azure— Working knowledge
  • AWS (Cognito)— Working knowledge
  • CI/CD · GitHub Actions— Working knowledge
  • New Relic— Working knowledge
  • LaunchDarkly— Working knowledge

Quality

Confidence to change things

  • Jest— Strong
  • Cypress— Working knowledge
  • SonarQube— Working knowledge
  • Zod— Working knowledge

AI engineering

Using and building with LLMs

  • AI-assisted development— Strong
  • MCP tooling— Working knowledge
  • LLM features & agents— Exploring

06Now

What I’m building and learning right now.

  • Offline-first mobile

    Shipping

    Sync engines, conflict handling and on-device search in Expo + SQLite. It is the common thread through Aarti Sangrah and Hisab Kitab.

  • AI-assisted engineering

    Daily

    Coding agents and MCP tooling in the everyday loop, from design systems to refactors. The skill is knowing what to delegate and what to review.

  • LLM application engineering

    Learning

    Agents, tool use and retrieval: the backend patterns for building product features on top of language models.

  • .NET 8 Web APIs

    Learning

    Completed an ASP.NET Core Web API course in December 2025, to go deeper on the services side of the .NET systems I integrate with.

07Contact

Hiring a full-stack engineer?

I’m most useful on products that need one person across the whole stack: the interface, the API contract, the data model, auth and deployment. Send me the role and the hardest part of it.

Open to full-stack roles · Pune, India

Esc
↑↓ navigate↵ open