Careers
Small team. Work owned end to end.
You own a piece of work from the problem through to it running in production.
You own the whole problem.
Not a ticket, not a slice of one. You are expected to have a view on whether it was the right thing to build, and to say so before it is built.
You will be asked why.
Yours as well as ours. Every decision gets explained, and “it works” is not an explanation.
Small team, visible work.
What you build is seen, used and maintained by the same few people. That suits some and not others, which is worth knowing early.
Systems built from nothing, not someone else’s left to maintain.
Most of what we build starts empty. There is no legacy codebase to work around and no architecture already decided by someone who left. What you build is the thing, and the decisions in it are yours to argue for.
The company is early enough that this matters. What gets built now sets how everything after it works, which is either the appeal or the reason to look elsewhere.
We work in current tooling and we expect people to be able to do the job without AI before they use it to go faster.
We do not post roles. We hire when the right person turns up.
Hiring here is slow and we say no often. That is not a filter we apologise for, and it cuts both ways: nobody is brought in to fill a gap on a rota.
So there is never a wrong time to write. If there is no room when you do, we keep what you send and come back to it, because the room tends to appear before the right person does.
The team works from the Lahore office. Send something that shows how you work rather than a list of what you have used. A person reads it.
If it goes somewhere, there is a conversation, then a day of real work at the office. The day is paid, and it is paid whether or not we make an offer. You are not producing free work for a company that then goes quiet on you.