Devzent is open for new projects — free consultation, fixed price after discovery.See what's new
Devzent is open for new projects — free consultation, fixed price after discovery.See what's new
Not another dashboard nobody opens. The software here bills customers, routes kitchen orders, closes the books and keeps shops trading when the internet drops. That constraint is what makes the work interesting.
0
Open roles
1
People today
2026
Founded
Islamabad
Based in
No open roles right now
Devzent is a one-engineer studio as of September 2026, so there is nothing to apply for yet. If you build the kind of software described on this site, send your work anyway — the first hires will come from people we already know.
Nothing that fits?
We keep a standing file for strong engineers and designers. Send your work and tell us what you would want to build here — we read every one.
Send a speculative applicationBenchmarked against the market, adjusted in January and July — no waiting for an annual cycle to catch up with inflation.
Comprehensive medical insurance including spouse, children and parents.
PKR 150,000 a year each for courses, books and conferences, plus paid time to use it.
Core hours 11:00–16:00; the rest is yours. Most engineering roles are two days in the office.
Plus public holidays, and we notice if you are not taking it.
Published engineering levels with explicit criteria. You always know what the next step requires.
MacBook Pro or a high-spec Linux workstation, external displays, and whatever tooling you need.
Every Friday afternoon is for learning, side projects or open-source work. It is protected, not aspirational.
Written by the team, not by marketing. If any of this sounds like a constraint rather than an advantage, we are probably not the right fit — and that is useful to know early.
Every pull request gets a real review. The standard is that the author should learn something, which means reviewers explain rather than dictate.
When something breaks, we write up what happened and what will prevent it. We do not look for who to blame, because that only teaches people to hide problems.
Engineers join discovery calls and demos. Understanding why you are building something makes the thing you build better.
Architecture decisions are argued out and written down. Seniority makes your argument heard, not automatically correct.
No-meeting Wednesdays, async by default, and a genuine expectation that you will not answer Slack at 11pm.