Rohaan Ashraf APIs · Full-stack · AI integrations
Remote-first · worldwide flexible hours · async-friendly
An independent practice · shipping production software since 2025

Software that ships, scales, and stays shipped.

I design, build, and deploy REST APIs and full-stack web apps for founders and product teams who need systems that work on day one and on day three-hundred. Node, NestJS, Express, TypeScript across the MERN and MEAN stacks; Python on hand for the AI work. PostgreSQL when it should be, MongoDB when it must be. Plan, prompt, review, test, then ship.

R.A., engineer
Now booking · Q2 / Q3 2026 REST APIs & server-side services NestJS · Node · TypeScript AI integrations & GPT workflows Full-stack with React & Next.js Remote · async-friendly Now booking · Q2 / Q3 2026 REST APIs & server-side services NestJS · Node · TypeScript AI integrations & GPT workflows Full-stack with React & Next.js Remote · async-friendly
read the portfolio 01
Section 002

The Contents

a reader's guide
  1. i. A short note on how I work, and what I build prologue 003
  2. ii. Selected client work, five engagements portfolio 004
  3. iii. Case study · FirstAidTag, a system on the wrist long form 008
  4. iv. Services I'm currently taking on engagement 011
  5. v. How we work together · begin a project engage 014
I build the kind of software you forget you're paying for: the one that doesn't page you on a Sunday, doesn't break in the demo, and doesn't need rewriting in six months.
R.A., on the only kind worth shipping
Section 004

Selected Work · five engagements

2023 · 2026
end of selected work · for the rest, see GitHub or write
Section 008 a case study · in production

FirstAidTag,
or, a backend
worn on the wrist.

An AI-powered medical-health band built on a Node service, with a Python AI layer alongside it: vitals tracked, phone data synced, life-saving updates written back to a physical NFC tag. Live at firstaidtag.ca.

Treat every byte on the tag like a promise: honest, current, and ready for the medic who reads it on the worst day.

on the design of the FirstAidTag sync layer
II.

The shape of the system.

FirstAidTag is a Node service with a Python AI layer that bridges three worlds: a React Native mobile client, the AI that reasons about a wearer's vitals, and a physical NFC tag any phone can read offline. The hard part is keeping all three in agreement, gracefully, when the network isn't.

Fig. 1 · The shape of the system, drawn in three bands: client, service, and the physical world it writes to.

The outcomes, plainly stated.

i. REST endpoints, shipped 0
ii. Vital signals, modelled 0
iii. NFC write & read flows 0
iv. AI inferences, served daily 0
v. Sync reliability, percent 0

Honest figures, by the practice's count. Fuller numbers on request.

V.

In short.

FirstAidTag is the kind of system I take pleasure in shipping: hardware, software, and AI agreeing quietly so the person wearing it never has to think about any of it. I'd like to build the next one for you.

Start a similar project
Section 011

Services · what the practice takes on

four offerings
№ 01 · server-side typical · 2–6 weeks

APIs & server-side services.

The thing I do most. NestJS or Express on Node + TypeScript, Postgres or Mongo, JWT auth, webhooks, third-party integrations. Documented, tested, and handed over.

shipped on a calendar
№ 02 · ai · integrations typical · 1–4 weeks

AI features, tastefully integrated.

GPT-backed automations, NLP on real product data, AI-assisted internal tools. Planned, prompted, reviewed, and shipped, not dropped in and forgotten.

scoped, not sprinkled
№ 03 · full-stack typical · 4–10 weeks

Full-stack web apps, end to end.

When you need the API and a UI on top. Next.js or React on the front, the same careful engineering underneath, deployed to Vercel or whatever fits.

idea to live URL
№ 04 · custom CRM typical · 4–8 weeks

Custom CRMs, built around the work.

For teams that have outgrown the spreadsheet but don't fit off-the-shelf CRMs. Customer ledgers, automated invoicing, tax-compliant flows (FBR-ready), dashboards that surface the numbers you actually look at. Built around your process, not someone else's.

tailored, not templated
Section 014

How We Work & How to Engage

begin a project
Rohaan Ashraf, engineer
Plate I. Rohaan Ashraf, engineer, photographed for the portfolio.

A short note on the practice.

The practice is one engineer (me, Rohaan), currently working full-time as an Associate Software Engineer at Infinitiv.AI and taking on a small number of outside engagements each quarter. That keeps the work careful and the calendar honest.

I write in TypeScript and JavaScript on Node, reach for Python when AI work calls for it, commit to main through pull requests, and treat the README as part of the deliverable.

Begin a project.

The way the work goes.

01 · Brief
A short call. What, why, and by when.
02 · Proposal
Scope, schedule, price. In writing.
03 · Build
Weekly demos. No surprises at the end.
04 · Handover
Code, docs, and a quiet deploy.
05 · After
30 days of support, gratis.
now booking · Q2 / Q3 2026

Let's build it.

Begin the engagement a reply within two hours · the practice · 2026