Technical Project Manager
Run two to three client engagements end to end: sprint cadence, scope, client communication, and the honest status reporting that keeps projects out of trouble. Technical enough to follow the architecture conversation.
What you'd be doing here
We're hiring a technical project manager to run client engagements the way we promise clients they'll be run: two-week sprints, demoable output every cycle, and status reports that say what's actually true. You'll own two to three concurrent projects, each with a squad of three to six engineers, for clients in the GCC, UK, and US.
The 'technical' in the title is real. You don't need to write production code, but you do need to follow an architecture discussion, understand why a migration is risky, and translate between a client CTO and your engineers without losing meaning in either direction. Our PMs earn their squads' respect by understanding the work, not by forwarding messages.
You'll work from our Lahore office alongside the delivery leads and squads you coordinate. Client calls cluster in late afternoons and evenings to overlap with Gulf and Western time zones, and we structure the rest of the day around that reality rather than pretending it doesn't exist.
What you'll own
Run sprint planning, standups, reviews, and retrospectives for two to three client squads.
Own scope: break work into a prioritized backlog with the client, and manage change requests honestly.
Send weekly status reports that name risks early instead of hiding them until they're crises.
Track budget and timeline against plan, and escalate deviations while they're still cheap to fix.
Run client calls across GCC, UK, and US time zones, and keep decisions documented.
Unblock engineers by chasing dependencies, decisions, and access so they can build.
Coordinate releases with QA and DevOps, including client sign-off and rollback plans.
Contribute to proposals and estimates for new engagements with the delivery leads.
What we're looking for
4+ years managing software projects with external clients, ideally in an agency or services setting.
Working technical literacy: you can follow API, database, and deployment discussions and ask good questions.
A track record of delivering projects on scoped budgets and timelines, including some that got hard.
Excellent written and spoken English; most of your clients will be outside Pakistan.
Fluency with agile practice as a tool rather than a ritual: you adapt process to the project.
Experience with Jira, Linear, or similar tools, including reporting that stakeholders actually read.
Bonus points, not blockers
If some of these describe you, mention it. If none do, apply anyway.
A past life as a developer, QA engineer, or business analyst.
Scrum or project management certification such as PSM, PMP, or PRINCE2.
Experience with fixed-price and time-and-materials commercial models.
Exposure to GCC clients and business culture.
Tools you'll work with
Four steps, no surprises
We designed the process to respect your time and show you ours: every step mirrors how we actually work.
Application review
Apply through the form on this page. We read every application ourselves and reply within a week, including when the answer is no.
Technical interview
A conversation with senior engineers about systems you have built, decisions you made, and trade-offs you would make differently. No trick puzzles.
Practical exercise
A small, time-boxed task close to real project work, reviewed together like a normal code review. We evaluate how you think, communicate, and take feedback.
Culture conversation & offer
A final discussion with a delivery lead about how you like to work, followed by a clear written offer. The whole process typically takes two to three weeks.
Apply for Technical Project Manager
Fill in the form below and we'll get back to you within a week, whatever the answer.
Prefer email? Send your CV to info@rndsol.com with the role in the subject line.