Tech hiring Product, design & quality

Hire project managers who keep delivery honest.

A project manager takes an agreed piece of work and gets it delivered: the plan, the schedule, the budget, the risks and the people who need to know where things stand. We shortlist project managers assessed on how they plan, how early they raise problems and how they handle a slipping date.

01 The role

What you get, when you hire a project manager.

A project manager turns a goal into a plan and then keeps reality close to it. They break the work down, sequence it around dependencies, agree who does what, and track progress against scope, time and cost. When something changes, as it always does, they work out the consequences and make sure the right people decide.

Plans are the easy part. The difficulty is finding out the truth early: the task that has been “90% done” for three weeks, the supplier who has gone quiet, the client adding scope in a side conversation. A good project manager surfaces bad news while there is still time to act on it, and reports status that people can believe.

In software the role sits beside agile delivery, not against it. Many project managers also act as Scrum Master or delivery manager, running sprints while keeping the longer view of milestones, budget and external commitments. What they do not own is the decision about what the product should be. That belongs to a product manager.

What they ship

  1. Project plans with milestones, dependencies and owners
  2. A live risk register with owners and mitigations
  3. Weekly status reports a stakeholder can read in two minutes
  4. Budget and burn tracking against forecast
  5. Change-control decisions showing the effect on date and cost
  6. Release and cutover plans for launches and migrations
  7. Retrospectives and lessons-learned records

02 Skills and stack

The stack, sorted by how much it matters.

Certifications sit in the adjacent column on purpose. A PMP shows that someone knows the vocabulary; it does not show that they have brought a late project home.

Core

The role cannot be done without these.

  • Planning: scope, work breakdown, estimation
  • Scheduling and dependency management
  • Risk and issue management
  • Stakeholder communication and reporting
  • Budget tracking and forecasting
  • Scope and change control
  • Agile delivery: Scrum and Kanban
  • Facilitation and conflict resolution

Tooling

Varies from team to team.

  • Jira or Linear
  • Asana, ClickUp or Monday.com
  • Microsoft Project or Smartsheet
  • Jira Plans or a Gantt tool for timelines
  • Confluence or Notion
  • Slack or Microsoft Teams
  • Miro
  • Excel or Google Sheets for budgets

Adjacent

Useful, not required.

  • PMP, PRINCE2 or Scrum certification
  • Vendor and contract management
  • Procurement
  • Software development lifecycle literacy
  • Release management and CI/CD awareness
  • Capacity planning across teams
  • Business analysis and requirements gathering

03 When to hire one

Hire a project manager for the right problem, or hire someone else.

We would sooner point you to a different role than fill the wrong one. Both lists are worth a minute.

Hire a project manager when

  • A fixed deadline with several teams involved

    A launch, a migration or a client delivery depends on engineering, design, a vendor and legal. Somebody has to hold the whole sequence.

  • Your tech lead spends half the week on status updates

    Chasing tasks and writing reports is taking your most expensive engineer away from engineering. A project manager takes that load.

  • Projects keep finishing late and nobody saw it coming

    The slip was visible in the detail weeks earlier. You need someone whose job is to look at the detail and raise it.

  • You deliver work for clients

    Agencies and consultancies need a named person who manages scope, change requests and client expectations, separate from the people doing the work.

  • Several projects compete for the same people

    Without someone planning capacity across them, every project is priority one and all of them slow down.

Look elsewhere when

  • Nobody has decided what should be built

    A project manager delivers an agreed scope. If the scope itself is the open question, you need someone to own discovery and priorities.

    Hire product managers
  • One small team is working on one product

    A single squad with a capable lead rarely needs a separate project manager. Another engineer is usually the better use of the salary.

    Hire software developers
  • Releases are late because deployment is manual and fragile

    No plan fixes a release process that breaks. Automate the pipeline first.

    Hire DevOps engineers
  • Deadlines slip because bugs are found at the end

    That is a testing gap, not a planning gap. Bring quality checks earlier in the cycle.

    Hire QA testers
  • You have no team for the project manager to manage

    A plan with nobody to carry it out delivers nothing. Start with the people who will do the work, as a team with its own lead.

    See dedicated teams

04 How we assess

Four checks, before a name reaches you.

A CV says what someone claims. We test what they can do, then send you the evidence with the shortlist.

  1. Stage 1

    Profile review

    We look at the projects the candidate has run: size, duration, who the stakeholders were and whether the work shipped. We read for specifics, such as what slipped and how it was recovered, and give little weight to certificates on their own.

  2. Stage 2

    Practical exercise

    For this role the practical exercises carry most weight: a delivery scenario in which the candidate sequences the work, identifies the risks and dependencies, and decides what to tell stakeholders when the plan no longer fits the date.

  3. Stage 3

    Conversation with our team

    Our team asks about a project that went off course: when the candidate first knew, who they told and what they changed. We listen for early escalation, honest reporting and enough understanding of software work to question an estimate.

  4. Stage 4

    Review and levelling

    Reviewers score accuracy, speed, problem-solving, communication and teamwork, then assign a level. For project managers the notes record the size and complexity of delivery the person has run, and whether they have managed external clients or vendors.

  5. Then

    Your shortlist

    Assessed candidates, with notes and scores.

The engine

Evalia

Assessments run on Evalia, the assessment platform we built ourselves. Across the ProDevs network, more than 100,000 assessments have been completed.

See how a hire runs from brief to offer.

05 Seniority

Three levels. What each one can own.

Years of experience are a weak guide. Ask what the person has owned, and who was checking their work.

Junior

Owns a workstream

  • Keeps the board, the plan and the meeting notes accurate and current
  • Chases actions and flags blockers to a senior project manager
  • Runs stand-ups and sprint ceremonies for one team
  • Needs support with budgets, difficult stakeholders and re-planning

Mid-level

Owns a project end to end

  • Plans and runs a multi-month project with one or two teams
  • Maintains the risk register and acts before risks become issues
  • Reports status honestly, including when the date is in doubt
  • Handles change requests and explains their cost in time and money

Senior

Owns a programme or a client account

  • Runs several related projects and the dependencies between them
  • Manages budgets, vendors and contracts at programme level
  • Negotiates scope and dates with executives and clients
  • Sets the delivery process and coaches other project managers

06 Interview questions

Questions for project managers, and what to listen for.

Borrow these for your own interview loop. Beside each is what to listen for.

  1. Tell me about a project that was going to miss its date. When did you know, and what did you do?

    A good answer shows: An early signal they noticed, a clear escalation with options, and a decision about scope, date or people. Candidates who only found out at the end, or who say they have never missed a date, are not describing real projects.

  2. A developer reports a task as 90% done for the third week running. How do you respond?

    A good answer shows: They break the remaining work into pieces that can be seen to be finished, ask what is blocking it and adjust the plan. No blame, but no acceptance of percentages as status either.

  3. The client asks for “one small change” mid-project. Walk me through what happens.

    A good answer shows: They size the change with the team, state its effect on date and cost, and get a decision in writing. Saying yes to protect the relationship is how projects quietly double; a flat no without assessment is no better.

  4. What is on your risk register for a typical software project, and how often do you review it?

    A good answer shows: Concrete risks: key-person dependency, third-party APIs, unclear requirements, late testing, data migration. Each has an owner and a response, and the list is reviewed weekly. A register filled in once at kick-off is paperwork.

  5. How do you report status so that people believe it?

    A good answer shows: Evidence over colour codes: what was finished, what was not, what changed and which decision is needed. They report amber early. Projects that stay green until the week they turn red are the pattern to avoid.

  6. When would you run a project with Scrum, with Kanban, or to a fixed plan?

    A good answer shows: A choice based on how stable the scope is and how fixed the date. Strong candidates mix methods without fuss. Loyalty to one methodology regardless of the work is a weakness.

  7. How do you challenge an estimate when you are not the engineer?

    A good answer shows: With questions, not overrides: what is included, what is assumed, what happened last time. They compare against past delivery and add contingency openly. Cutting the number to fit the plan is the weak answer.

07 Ways to engage

Permanent, team, payroll or project. Four routes to a project manager.

A permanent hire is the usual route, not the only one. Choose by how long the work lasts and who should employ the person.

Placement fee, of first-year salary. One-time.
10–15%
Replacement guarantee on direct hires.
2 weeks
To a first shortlist, for most roles.
48h
  • Direct hire

    A permanent employee on your contract and your payroll. One-time placement fee of 10–15% of first-year salary.

    Tech hiring
  • Dedicated team

    A project manager inside a team we assemble and run for you: product, design and engineering on your roadmap, for a monthly retainer.

    Dedicated teams
  • Outsourcing & payroll

    A full-time person in a country where you have no legal entity. ProDevs employs and pays them: 20% of salary if we find the person for you, or 5% of salary, capped at $500 a month, for payroll and compliance on someone you have already chosen.

    Outsourcing
  • Freelance project

    A defined piece of work with a clear end. You pay the agreed price per milestone through escrow, plus a 5% client fee. Free to post.

    Freelancers

08 Around the role

A project manager is one seat. These are the others.

A project manager sits beside the team, not above it, with no say over how the work is done and full responsibility for knowing where it stands. On larger programmes they report to a delivery lead or directly to the client sponsor.

Product manager
Takes agreed scope and priorities, and reports what they will cost in time.
Engineering lead
Builds the plan from the team’s estimates and protects it from interruptions.
QA tester
Schedules test cycles early enough for defects to be fixed before release.
DevOps engineer
Coordinates release windows, environments and cutover plans.
Client or executive sponsor
Gives a straight account of progress and brings the decisions that need their authority.

09 Client testimonials

Hear it first-hand, from companies that hired.

Founders, operators and executives describe working with ProDevs, in their own words.

10 Questions

Hiring project managers, answered.

Something else? Book a call (opens in a new tab) and ask us directly.

  • What is the difference between a project manager and a product manager?

    A project manager is responsible for delivering an agreed scope on time and within budget. A product manager is responsible for deciding what the scope should be and whether it served users. If your question is “when will it be done?”, you need the first; if it is “what should we build?”, the second.

  • Is a project manager the same as a Scrum Master?

    Not quite. A Scrum Master coaches one team in the Scrum process and removes blockers. A project manager also owns the schedule, budget, risks and reporting across teams and outside parties. In many software companies one person does both, so say in the brief which emphasis you need.

  • Do project managers need certifications such as PMP or PRINCE2?

    They are useful where your clients or sector expect them, for instance government and large corporate work. They show knowledge of method, not a delivery record. We give more weight to the projects a candidate has actually run, and you can list a certification as required if your contracts demand it.

  • Does a software project manager need to be technical?

    They need to understand how software is built: environments, releases, testing, dependencies and why estimates move. They do not need to write code. A project manager who cannot follow a technical discussion ends up relaying messages and cannot judge whether a risk is real.

  • Can a remote project manager run a team in another time zone?

    Yes, provided there are a few hours of shared working time for stand-ups and decisions, and status is written down instead of held in meetings. Agree the overlap hours in the brief. Written, asynchronous reporting is a habit that good remote project managers already have.

  • How does hiring a project manager through ProDevs work?

    You agree a brief with us and, for most roles, see a first shortlist within 48 hours. Most companies find their hire within two to three weeks. The person joins on your contract for a one-time fee of 10–15% of first-year salary, with a two-week replacement guarantee.

Talk to ProDevs

Tell us about the role.

Tell us the level and the stack. We will tell you how quickly we can put assessed project managers in front of you.

Project work

Need it for a project instead?

Not every job needs a full-time hire. Describe the work, get proposals from vetted freelance project managers, and pay per milestone through escrow. Free to post.