In my own words

I work across the whole stack. On the backend that usually means Python with FastAPI or Django, SQLAlchemy and Pydantic for modelling and validation, and PostgreSQL or MySQL underneath. On the front end it means React with hooks and context, or Astro when a site has to be fast and search friendly above everything else.

Most of my work starts with an open-ended conversation rather than a written spec. I'm comfortable sitting with clients and researchers who are not engineers, turning what they describe into a data model, an API surface, and an interface they can actually use, then documenting it in language they can rely on long after handover.

I use AI coding tools every day, and I review and test what they produce to exactly the same standard as code I write by hand.

Based in the United States. Open to full-stack engineering roles.

  • API design that holds up

    Typed request and response models, validation on ingest, and every endpoint documented in OpenAPI so the people consuming it never have to guess.

  • Front ends that match the contract

    Component architecture and state management in React, with behaviour verified against the API contract before anything reaches release.

  • Security built in, not bolted on

    JWT authentication, role-based access control, protected routes, session handling, audit logging, and CORS policy across both API and UI.

  • Performance as a requirement

    Core Web Vitals budgets, technical SEO, structured data, and accessibility treated as acceptance criteria rather than a later clean-up pass.

Process

How a project runs, start to finish

The same six steps whether it is a two week client build or a two year platform. The outputs are what you receive, not what I do internally.

  1. Understand the problem, not the feature list

    I start by asking what goes wrong today and who it affects. Most first requests describe a solution someone has already imagined. The useful conversation is the one underneath it.

    A short written summary of the problem, agreed before any code.

  2. Model the data

    Entities, relationships, and the rules that must always hold. Getting this wrong is the most expensive mistake available in a project, so it comes before framework choices, not after.

    A schema you can read, with the constraints written down.

  3. Design the API contract

    Endpoints, request and response shapes, error cases, and permissions. Typed with Pydantic and published as OpenAPI so the front end and any other consumer can build against it immediately.

    A Swagger page that works before the implementation is finished.

  4. Build in thin vertical slices

    One real path at a time, from database through to interface, rather than a finished backend and an empty screen. You see something working early and can redirect it while that is still cheap.

    Working software you can click through, every week.

  5. Test, review, and harden

    PyTest coverage on the logic that matters, validation on every input, authentication and role checks on every protected route, and a pass over performance and accessibility before release.

    A test suite, and a security and performance check you can repeat.

  6. Document and hand over

    Runbooks, environment notes, and behaviour described in plain language. The measure of a good handover is that the next person does not need to call me.

    Documentation your team can act on without me.

Education

Formal background

  • Master of Computer Applications

    Indira Gandhi National Open University

    2020 to 2026 Distance learning India

    Major project: ClinicalPilot AI

  • Bachelor of Science in Physics

    Mahatma Gandhi University

    2016 to 2019 Full time India

    Graduated with distinction, 89 percent

Next step

Want to talk through a specific problem?

The fastest way to find out whether I am useful to you is to describe what you are stuck on. I will tell you what I would do, whether or not you hire me to do it.

  • Replies: Within two working days
  • Based in: the United States
  • Open to: full time, contract, remote or hybrid

Pages

Projects

Writing

Actions