End-to-end tournament ops for federations — registration through live rankings, white-label ready.
Read case studyOpen to 1–2 new engagements
The senior engineer who owns your SaaS from idea to production.
I partner with founders and CTOs to ship MVPs, AI features, and ongoing product work — Next.js, NestJS, Postgres, Stripe, LLMs — with code your next hire can extend.
Replies within 1 business day. No pitch deck required — a short brief is enough.
- 5+ years shipping
- Live SaaS products
- AI in production
- Next.js · NestJS · Postgres
Selected work
Products in the wild
Live apps first — full engineering stories live on dedicated pages so this page stays readable.
Sentiment analysis productized into a paid portal — auth, Stripe, AWS.
Read case studyIngredient → recipe AI with OpenAI, Stripe payments, and Firebase auth.
Read case studyReview-driven brand discovery — full-stack Next.js shipped to production.
Read case studyHow we engage
Three ways to work together
Pick the shape that matches your stage — not a menu of every technology I’ve touched.
Fixed-scope project
Ship an MVP
Best for: Founders validating a SaaS idea in the next 6–10 weeks
A production-ready web product with auth, core workflows, and a deploy you can put in front of users or investors.
- Product scoping & architecture
- Auth + core features
- Admin / dashboard when needed
- Deployed staging + production
2–6 week sprint
Add AI that ships
Best for: Teams with a product that needs LLM features — not a prototype
RAG, agents, or streaming AI wired into real UX, with cost/latency considered and a path to iterate.
- Use-case & model selection
- Prompt / RAG architecture
- Streaming UX
- Eval loops & guardrails basics
Retainer / part-time embed
Ongoing product engineering
Best for: Startups that need a senior full-stack owner without a full-time hire yet
A long-term partner who owns features end-to-end — frontend, API, data, billing — and communicates like a teammate.
- Weekly shipping cadence
- Architecture decisions documented
- Code a future hire can extend
- Priority support on production issues
Depth underneath the offer
Product surface
- Next.js
- React
- TypeScript
- Dashboards
- SEO
Systems
- NestJS
- Node
- GraphQL
- Postgres
- Redis
- AWS
Monetization & AI
- Stripe
- Auth
- OpenAI
- Claude
- RAG
- Agents
Process
What the first month looks like
Clear phases, deliverables, and what I need from you — so $50k doesn’t disappear into ambiguity.
- 013–5 days
Discovery
We pressure-test the problem, users, constraints, and what “done” means for this engagement — before architecture or code.
You get
- Written problem brief
- Success metrics
- Scope boundaries (in / out)
Your part: Share context, users, and constraints. Decide go / no-go.
- 023–7 days
Architecture
Stack, data model, and delivery plan that can ship now and survive your next hire — documented, not tribal knowledge.
You get
- Architecture notes
- Milestone plan
- Risks called out early
Your part: Approve direction. Flag non-negotiables (compliance, budget, timeline).
- 03Ongoing sprints
Build in slices
Weekly demos of working software. Async updates in writing. No black-box weeks.
You get
- Shippable increments
- Staging you can click
- Clear open questions
Your part: Give feedback fast. Prioritize ruthlessly when scope moves.
- 04Handoff or retain
Launch & steady state
Production deploy, basics monitored, and either a clean handoff or continued ownership — your call.
You get
- Production release
- Handoff notes / runbook
- Option to retain
Your part: Launch decision. Choose handoff vs ongoing partnership.
Working together
What it’s like after you say yes
Not personality adjectives — operating norms that protect your budget and timeline.
You talk to one owner
No agency telephone. I scope, build, and ship the slice we agreed — frontend through API when the product needs it.
Proof: Sr. engineer across Spadasoft, Zweidevs, and eBridge — 5+ years
Code your next hire can read
I optimize for a maintainable codebase, not a clever demo. Decisions that matter get written down.
Proof: GraphQL/Nest systems tuned for real traffic — not throwaway APIs
Business outcomes over tickets
We define what shipping unlocks (users, revenue, fundraising demo) and cut work that doesn’t move that needle.
Proof: Shipped billing, auth, and AI into products people can pay for
Async-first, overlap when it counts
Written updates by default. Live calls for decisions and demos. Timezone: Pakistan (UTC+5) with US/EU-friendly windows.
Proof: Remote collaboration across multiple product teams since 2021
Experience
5+ years shipping production software
From associate work in 2021 to senior roles owning backends, Electron products, and SaaS features founders put in front of customers.
Feb 2025 – Present
Sr. Software Engineer
Spadasoft · Lahore, Pakistan
Building NestJS/GraphQL backends and production SaaS surfaces — real-time paths, cloud deploys on AWS/Azure/Vercel, and features that ship to paying users.
Apr 2023 – Jan 2025
Sr. Software Engineer
Zweidevs · Lahore, Pakistan
Led Electron desktop products, CI/CD discipline, WebSocket realtime systems, and Stripe/Highcharts integrations across client SaaS work.
Jul 2021 – Mar 2023
Software Engineer
eBridge Technologies · Lahore, Pakistan
Shipped React + Node products end-to-end: Tailwind/Ant Design UI, a reusable component library adopted by the frontend team, API work, and performance basics (lazy load, code splitting).
About
A product engineer, not a ticket queue
Where I came from, how I decide, and how we stay aligned once money is on the line.
- Experience
- 5+ years
- Based in
- Lahore, Pakistan (UTC+5)
- Companies
- Spadasoft · Zweidevs · eBridge
- Building
- RankKar.app
For 5+ years I've learned engineering by shipping — first small apps, then production systems customers actually depended on. That path took me through eBridge, Zweidevs, and Spadasoft as a senior engineer: NestJS/GraphQL backends, Electron products, React/Next frontends, Stripe, real-time features, and cloud deploys.
What I enjoy building is the unglamorous middle of SaaS — architecture trade-offs, billing edge cases, AI that has to work on a Tuesday afternoon, and interfaces that don’t need a walkthrough. I’m also shipping RankKar, so I feel the founder side of “will this ship?” every week.
How I decide: start from the business outcome, pick the simplest architecture that can scale, and deliver in demos you can show investors or customers. How we stay aligned: written updates, honest timelines, and code the next engineer can extend without archaeology.
If you need someone to own a product slice end-to-end — not disappear into a backlog — let’s talk.
Engineering notes
How I think when AI and deadlines collide
Writing that shows judgment — the thing you can’t fake on a sales call.
FAQ
Questions founders ask before spending
Straight answers — including when I’m the wrong hire.
What does a $50k engagement typically cover?
Usually a substantial MVP slice or several months of embedded product engineering — auth, core workflows, billing, AI features, and production deploys. Exact scope depends on complexity; discovery makes that concrete before you commit.
Do you only do greenfield?
No. I join existing codebases often — especially Next.js / Node / Nest stacks. I’ll tell you quickly if the architecture is salvageable or if we’re burning money.
How do you work with my designer / co-founder?
I take designs or wireframes when you have them; otherwise I ship clean, usable UI and iterate from feedback. Non-technical founders get plain-language updates, not Jira noise.
What are you a bad fit for?
Pure staff-aug ticket queues with no product ownership, native-only mobile as the primary surface, or projects that need a 10-person team on day one. I’ll say no rather than stretch.
How fast can we start?
Usually within 1–2 weeks after a fit call, subject to current capacity. I keep 1–2 engagement slots open at a time so focus stays high.
Contact
Tell me what you're building
Send a short brief. I'll reply with whether I'm a fit, rough shape of an engagement, and — if it makes sense — a time to talk. No discovery theater.
- 1.You send context (product, timeline, budget band).
- 2.I reply within one business day with a clear yes / no / maybe.
- 3.If yes: a 30-min call, then a written proposal.
We're likely a fit if…
- SaaS / web product (not pure native-only)
- You want an owner, not a ticket-taker
- You have a clear goal and are ready to invest in shipping it
- You can give feedback within a few days