Senior Full-Stack Engineer / Technical Lead
You would own the delivery of our production applications end to end — not a pair of hands working through someone else's plan. From a ticket on the board to code that is deployed, verified, and explained to the client.
Read the four points below first. They are dealbreakers, not preferences.
Four things, stated plainly
If any of these do not work for you, stop here. We would rather you decide now than at the offer stage.
On site, six days a week
Karachi office, six days. Not remote, not hybrid, not negotiable. Equipment is provided.
Eight hours, and you stay when it breaks
Daytime hours now, possibly night hours later. When something is broken or a deadline is close, you stay with it until it is handled.
You own the cloud
AWS is part of this job, not a separate department you file tickets to. You will be the one who responds when production breaks.
The application takes 30 to 40 minutes
It is mostly writing, and every answer is discussed live afterwards. If that sounds like too much, this is not the role for you.
What you own day to day
Several live applications, the infrastructure under them, and the clients who depend on them. Nobody hands you a finished specification.
- Feature and bug work across several live applications — React and Next.js front ends, Node and NestJS back ends, PostgreSQL.
- The AWS side of those applications: access and permissions, deployments, monitoring, and being the one who responds when something breaks.
- Carrying a ticket from the board through to merged, deployed and verified, without being chased for status.
- Writing directly to clients when something needs explaining, including when the news is bad.
- Reviewing other people's pull requests, and within six months leading one or two junior developers.
Not an ordinary senior role
Several live applications, real ownership, and nobody to hand the hard parts to.
Breadth, not depth
Several applications running at once and nobody to hand the infrastructure to. You will not be allowed to be only a front-end person.
You finish things
Deploying and checking it actually worked is part of your task, not a later stage owned by somebody else.
You write to worried people
You will write to non-technical clients and your writing has to settle them down. This is a real requirement, not a soft extra.
AI tooling, and checking it
AI tools are expected, and so is verifying what they produce. We move fast because of them, and we do not ship what we have not checked.
What success looks like
Ship small tickets without help, have read the codebases, and know where each application deploys and how to tell whether a deploy worked.
Own a whole application area, handle its incidents, and communicate with that client directly.
Review other people's work, improve how the team operates, and be the person to call when something breaks.
What you must have
- Real production experience on both front end and back end. Not one and a course in the other.
- Has configured AWS yourself, rather than only working inside a setup someone else built.
- Can debug code you did not write and did not choose.
- Writes clear English. This is non-negotiable, and it is why the application is mostly writing.
- Has personally carried responsibility for something that was live, with users on it.
- Not a pure DevOps role, and not a pure front-end or back-end role.
- Not a role where somebody hands you a finished specification.
- Not remote, and not a job where you close the laptop in the middle of an incident.
Useful, but not required
How we actually hire
No trick tests and no take-home project. We ask you to write about work you have really done, then we talk about it.
The written application
Around 30 to 40 minutes. Mostly long answers about work you have actually done — systems you built, things that broke, what it cost. Write it in your own words.
The live conversation
We pick answers you wrote and ask you to go deeper on each: what the error actually said, why you chose that over the alternative, what you would do differently. If you did the work, this is the easy part.
The decision
We review every application ourselves and move quickly. If it is a strong match, you will hear from us.
Think this is you?
Set aside 30 to 40 minutes and write it in your own words. We read every application ourselves.