01I build scalable, end-to-end products — from interface craft to back-end systems and the cloud infrastructure nobody thinks about until it’s on fire. Four years turning complicated requirements into software people actually enjoy using.
A cross-section of things I've designed and built end to end — real-time systems, data tooling, the odd drag-and-drop chatbot canvas. Open any card for the full story, not just the highlight reel.
01
04Teleport
Visa applications are one of the last places on the internet still run on PDFs and prayer. Teleport turns that into a form that…
The metric that actually matters to me: not whether a project shipped, but whether the team would call again.
REPLACE THIS before this goes anywhere near a client — a placeholder quote is worse than no quote. Two or three sentences works best: the problem, what got delivered, what changed because of it.
REPLACE THIS. Specific beats flattering every time — a number, a timeline, a thing that was blocked and now isn't, lands harder than 'great to work with.'
REPLACE THIS. No written testimonials yet? Email two past clients and ask — most people are more willing to write three kind sentences than you'd expect.
Four areas I get hired for most. Real engagements rarely stay inside one lane — most quietly touch two or three of these at once.
Full-Stack Product Engineering
From `git init` to real users, with nobody handing off in the middle and hoping the seams hold.
- Next.js / React
- TypeScript
- Design systems
Backend & API Architecture
Services that stay upright when traffic actually shows up. Clean boundaries, sensible caching, and APIs your front-end team won't complain about in standup.
- Node.js / Nest.js
- REST & GraphQL
- PostgreSQL / Redis
Cloud Infrastructure & DevOps
Containers, pipelines and deploys dull enough to run on a Friday afternoon without anyone holding their breath.
- AWS
- Docker / Kubernetes
- CI/CD
AI-Powered Features
Language models aimed at a real user problem — not bolted on because someone on the board asked what we're doing about AI.
- LLM integration
- RAG pipelines
- Prompt engineering
How the work goes
- 01
Understand
Find the actual problem, which is almost never the one written in the brief.
- 02
Architect
Design the smallest thing that solves it and won't need apologising for in six months.
- 03
Build
Ship in slices small enough to actually review. Typed, tested, and boring in the good way.
- 04
Refine
Measure, tighten, and leave the codebase tidier than I found it. Non-negotiable.
Three ways to bring me in. Not sure which fits? Describe the problem and I'll tell you honestly which one I'd pick — even when it's the cheaper option.
Project build
A defined scope, shipped end to end, no vanishing after the demo.
Custom quote
Teams with a product to launch and a deadline that isn't hypothetical.
- Discovery and technical scoping
- Architecture and data modelling
- Full build — front-end, API, database
- Deployment and CI/CD setup
- Handover docs and a walkthrough call
Monthly retainer
PopularOngoing engineering capacity, minus the hiring-and-onboarding tax.
Custom quote
Teams shipping continuously who need a senior pair of hands they don't have to babysit.
- Agreed capacity each month
- Priority turnaround on blockers
- Weekly planning and demo calls
- Direct access on Slack or Discord
- Pause or cancel with 2 weeks' notice
Consulting & audit
A short, focused look before you commit real money to a build.
Custom quote
Teams who suspect something's wrong under the hood and would like to know before it's expensive.
- Codebase and architecture review
- Performance and scalability audit
- Written findings and recommendations
- Prioritised action plan
- Follow-up call to talk it through
Roles, teams, and the specific messes I was brought in to sort out.
REPLACE — your role · Company name
2024 — PresentReplace with what you were actually brought in to fix, what you built, and what changed because you did. One or two honest sentences beat five vague ones.
- Key result
- Key technology
REPLACE — your role · Company name
2022 — 2024Same deal — the specific thing you shipped, not the job description. Nobody's impressed by 'collaborated cross-functionally.'
- Key result
- Key technology
The short version — how I actually work, and what four years of shipping things taught me the hard way.
I'm Akash — a Software Engineer and Full-Stack Developer with a Computer Science degree and four years spent building systems that hold up once real users show up and do things nobody planned for. My work spans front-end craft, back-end architecture and cloud infrastructure, which mostly means I can carry a product from a blank repo to production without handing the hard parts to someone else and hoping for the best.
I treat every project as a problem to solve first and a codebase to write second — in that order, always. That means efficient, maintainable code that actually serves the business goal, and an interface people don't have to think about, which is rather the point.
Away from the editor I'm watching films, losing to friends at video games, and chasing whatever new piece of technology has hijacked my attention this week — it changes more often than I'd like to admit.
- Years building
- 4+
- Products shipped
- 6
- Technologies
- 19+

Toolkit
Frontend
- React
- Next.js
- TypeScript
- Tailwind CSS
- Redux
Backend
- Node.js
- Express.js
- Nest.js
- REST API
- GraphQL
Data
- PostgreSQL
- MongoDB
- MySQL
- Redis
Cloud & DevOps
- AWS
- Docker
- Kubernetes
- CI/CD
Quality
- Jest
- Cypress
- Playwright
Languages
- TypeScript
- JavaScript
- Python
- Java
- C/C++
The questions that come up on nearly every first call — answered here so we can skip to the interesting part.
Something not covered here?
Ask me directlySend a note through the form or by email with a little context on what you're building — the more specific, the better my first response will be. If it looks like a fit we'll do a short call to talk through scope, constraints and timing, and I'll follow up with a written proposal covering approach, milestones and cost. No sales deck, no discovery workshop you have to pay for.
Have a product in mind, a system that needs untangling, or a role you think I'd fit? Send a note — I read everything, and you won't get a form letter back.
- Current status
- Available for new projects
- Starting from
- Next 2 weeks
- Reply time
- Within 24 hours




