Pinty Jangid · engineering

Independent software engineer

I design and build software that actually ships.

Twelve months of prototypes is not a product. I take an idea from the first sketch to something live on the web, on the App Store, and running in production — the architecture, the code, the interface, and the deployment pipeline that keeps it standing.

Healthcare platforms Mobile apps AI features Developer tooling Cloud & deployment

01 — What I do

One engineer, the whole stack — so nothing falls between the handoffs.

Most software fails in the gaps: between design and code, between backend and mobile, between "it works on my machine" and a real deployment. I work across all of it.

01

Product engineering

Full web applications, front to back — an interface people can actually use, an API that holds up, and a data model that will not need rewriting in a year.

AngularReactSpring BootPostgreSQL

02

Mobile apps

One Flutter codebase, both stores. Built, signed, submitted and shipped — including the certificates, review paperwork and release process nobody warns you about.

FlutteriOSAndroidStore releases

03

AI features that behave

Summaries, risk scoring, trend analysis and assistants wired into a real product — with guardrails, citation checks and evaluation, so the model cannot invent things your users will believe.

LLM integrationFastAPIRAGGuardrails

04

Developer tooling

Static analysis, architecture diagrams and CI gates for codebases nobody remembers writing. I publish open source in this space, and I build it for teams too.

TypeScriptStatic analysisCIMCP

05

Interface & design systems

Design tokens, a component library and a consistent visual language — so the tenth screen takes an afternoon instead of a fortnight, and looks like the first nine.

Design tokensComponent librariesAccessibility

06

Cloud, deployment & care

Containers, pipelines, environments and monitoring. Plus the unglamorous part: being there when the deploy goes sideways at an inconvenient hour.

DockerAWSCI/CDMonitoring

How engagements work

03 — Toolkit

Chosen for the problem, not the résumé.

Frontend

AngularReactTypeScriptViteTailwindPWA

Backend

JavaSpring BootPythonFastAPINodePostgreSQL

Mobile & AI

FlutterDartLLM APIsRetrievalEvaluation

Delivery

DockerAWSGitHub ActionsTomcatFirebase

04 — How I work

Small steps, visible early, no surprises at the end.

01

A conversation, then a written scope

We talk for half an hour about what you are trying to change. You get back a short written scope — what gets built, what does not, what it costs, and when. Free, and yours to keep whether or not we work together.

02

The thinnest version that proves it

The first milestone is always something you can open and click, not a document. It settles the arguments a specification cannot.

03

Build in the open

A staging environment from week one, updated as work lands. You see progress continuously instead of a reveal at the end, which is when bad news gets expensive.

04

Ship it, then hand it over properly

Production deployment, monitoring, and documentation written for whoever comes next — including you. No lock-in: the code, the accounts and the pipeline are yours.

Next step

Have something you want built properly?

Tell me what you are trying to make. If I am not the right person for it, I will say so and point you somewhere better.

Start a conversation