Senior engineer · Founder-friendly · KL, MY

I help founders turn rough ideas into production-ready software.

8+ years shipping scalable web apps, SaaS products, and AI workflows. I work end-to-end — from spec and architecture to backend, frontend, and deployment — so you can go from idea to launch with one technical partner.

Kuala Lumpur, MY · GMT+8 Snappymob, prev. enterprise SaaS 8+ years
~/founder-build — zsh — 80×24
founder-build ×
spec.md
architecture.md
$
01 / where i help most

The four problems I get hired to solve.

Most founders I work with land on one of these. If any sound familiar, we should talk.

ISSUE-001open· assigned: @meher

You have an idea but no technical roadmap.

I turn rough product concepts into clear specs, system architecture, and an MVP plan you can actually ship — without 6 weeks of slideware.

discoveryspecsarchitecture
ISSUE-002open· assigned: @meher

Your MVP is slow, messy, or hard to extend.

I refactor full-stack codebases, stabilise CI/CD, fix the data model, and bring the system back into a state where adding features is fast again.

refactorstabilityspeed
ISSUE-003open· assigned: @meher

You need someone who can own the whole build.

Frontend, backend, database, cloud, auth, deploy, monitoring — one technical partner instead of coordinating three contractors who don’t talk to each other.

full-stackownershipdelivery
ISSUE-004open· assigned: @meher

You want AI leverage without AI chaos.

I use Claude, Cursor, and agent CLIs daily — but every output gets reviewed, tested, and architected by a human who’s been shipping for 8 years.

ai-assistedreviewjudgment
02 / build process

From idea to shipped product — without skipping steps.

Eight stages. None of them get hand-waved away. AI helps; it doesn't replace any of them.

pipeline · default-branch/ build-process.ymllast run: 2m ago · all stages passing
stage 01

Idea

Understand the business goal, users, and constraints.

stage 02

Spec

Translate into clear, developer-ready scope and tasks.

stage 03

Architect

Data model, API boundaries, auth, infra plan.

stage 04

UI

Frontend with React / Next.js. Real interactions, not mockups.

stage 05

Backend

Node.js / NestJS. APIs, jobs, integrations, data.

stage 06

Test

Jest, Cypress, integration, manual smoke. Real coverage.

stage 07

Ship

Docker, AWS, CI/CD. Observability before launch.

stage 08

Iterate

Read logs, listen to users, improve what matters.

[10:24:11]INFO discovery call · 45min · captured 12 user stories
[10:24:18]OK spec.md generated · 6 milestones · 38 tickets
[10:24:22]INFO architecture: monolith → modular, Postgres, S3, queue worker
[10:24:31]OK ci/cd: github actions → ECS · zero-downtime deploys configured
[10:24:39]WARN ai-suggested cache layer rejected · simpler memoization sufficient
[10:24:44]OK production: monitored · 99.8% uptime · ready for users
03 / signature approach

AI-assisted, human-owned engineering.

I use AI agents and CLI workflows for leverage — never as autopilot. Founders get faster delivery without losing the engineering quality that keeps a product alive in year two.

Founder Goal
the business outcome we're building toward
input
Architect Agent
system design, data model, API boundaries
auto
Coder Agent
implements modules under defined contracts
auto
Reviewer Agent
static analysis, style, anti-patterns
auto
Tester Agent
writes + runs tests, finds edge cases
auto
Human Judgment
architecture, security, trade-offs, what NOT to build
human
Production Release
shipped, monitored, owned end-to-end
ok

Speed without losing the plot.

The AI handles the volume work — boilerplate, scaffolds, drafts, test stubs. I handle the decisions that matter: what to build, how to structure it, what to refuse to build, and when “the agent’s suggestion” is actually a maintenance bomb six months out.

Founders don’t need a pure prompter or a pure engineer. They need someone who can hold both.

01.AI for speed, not for judgment. Architecture and trade-offs stay human.
02.Every output gets reviewed. If I wouldn’t merge it from a junior, I don’t merge it from an agent.
03.Tests are the contract. Generated code earns trust the same way human code does.
04.Boring works. Postgres, queues, monoliths — chosen on merit, not novelty.
04 / how i can help

Eight ways founders & teams hire me.

Most engagements blend a few of these. Some are 4-week projects, some are 6-month embedded partnerships.

MVP development

Idea → working product. 4–10 week sprints with weekly demos and a real launch at the end.

SaaS product build

Multi-tenant, billing, auth, dashboards. The non-glamorous backbone that paid SaaS needs.

Full-stack feature delivery

Drop into an existing team and ship vertical slices — frontend, API, data, deploy.

Backend & API architecture

Data model, contracts, jobs, queues. Designed to scale before scale is a problem.

AI workflow integration

Agents, RAG, CLI automation, prompt pipelines — integrated into your real codebase, not a demo.

Developer tooling & CLIs

Internal tools, scripts, CLIs that make your team faster every week, not just once.

Technical planning

Turning rough product ideas into engineering scope, milestones, and honest estimates.

Production debugging

Things on fire? I read logs, fix the root cause, and write the runbook so it doesn't repeat.

05 / build artifacts

Public work — code you can read.

A few open repos. Most client work is private — these are the projects with public code to look at.

raj-khan/aiagentflow.devpublic
Site & resources for the aiagentflow project — agentic engineering workflows.
aboutDocumentation and resources for orchestrating multi-agent software engineering with structured pipelines, checkpoints, and review.
TypeScriptNext.jsAgentic
raj-khan/nextjs-supabase-saas-boilerplatepublic
Reusable architecture and engineering conventions for Next.js + Supabase SaaS.
aboutCoding-agent workflow, repo structure, and opinionated conventions I reach for when starting a new SaaS — auth, database, and deploy patterns included.
TypeScriptNext.jsSupabaseSaaS
raj-khan/pre-school-keyboardpublic
A playful browser typing game built for one child — large keys, voice feedback, emoji reactions.
aboutBuilt for my own kid. Each key press shows the character in large text, speaks it aloud, changes colors, and shows a friendly emoji. A small project that taught me a lot about input latency and audio cues.
TypeScriptWeb AudioReact
raj-khan/meher-jqpublic
Command-line JSON processor — a jq-style tool written from scratch in C.
aboutExploration of how jq-style streaming JSON filtering works under the hood — built for learning, not as a jq replacement.
CCLIJSON
06 / mission log

Eight years. Real production. Real users.

Enterprise systems, SaaS products, and internal tools — owned end-to-end across frontend, backend, and infrastructure.

8+ yrs
shipping production code
2022 — now
Senior Software EngineerSnappymob · Kuala Lumpur, Malaysia
● active
2022
PHP DeveloperWipro Bangladesh Limited · Dhaka
○ shipped
2019 — 2022
Software DeveloperSCT-Bangla Limited · Dhaka
○ shipped
2017 — 2019
Full-Stack Web DeveloperBangladesh Software Development (BSD) · Dhaka
○ shipped
07 / capabilities

What I bring to the build.

No percentage bars. Just tools I actually use to ship every week.

Product Engineering
MVPsSaaSDashboardsInternal toolsSpec → ship
Frontend
ReactNext.jsTypeScriptTailwindDesign systems
Backend
Node.jsNestJSRESTGraphQLPostgreSQLQueues
Cloud & DevOps
AWS ECSS3DockerGitHub ActionsCI/CDObservability
AI Workflow
ClaudeCursorAgentic CLIPrompt designEval loops
Quality
Code reviewTestingArchitectureMaintainabilitySecurity basics
08 / open source

I build & experiment in public.

A few public repos around AI-assisted engineering, CLI tools, and developer workflows. Most client work lives in private repos — these are the ones you can read.

$ founder contact --to meher

Got an idea you want to turn into real software?

If you're a founder, startup, or team with a product idea, an AI workflow problem, or a build that's stalled — let's talk. I reply within a day, in your timezone.