Project Manager (Mid-Level, SMB) Hiring Guide
Responsibilities, must-have skills, 30-minute assessment, 6 interview questions, and a scoring rubric for this role.
Role Overview
Function: Oversees end-to-end project execution, from planning through delivery. The Project Manager coordinates cross-functional teams and resources to meet defined project objectives on time and within budget.
Core Focus: Translating business goals into actionable project plans, managing day-to-day project activities, and communicating progress to stakeholders. Emphasis is on delivering projects on schedule and within scope/budget, while managing risks and stakeholder expectations in a hybrid work environment.
Typical SMB Scope: In a 10-400 employee company, a Project Manager often wears multiple hats. They may handle several small to mid-sized projects concurrently, or one larger project, typically valued in the mid five to low seven figures. Projects often involve cross-department collaboration (e.g. IT, marketing, operations) and sometimes external vendors or clients. The PM likely operates independently (no large PMO support), reporting to an executive or operations manager. They establish light-weight processes suitable for an SMB, use affordable SaaS tools, and ensure projects align with company objectives despite limited resources.
Core Responsibilities
Plan and define projects end-to-end: Work with stakeholders to clarify requirements and develop a project plan (scope, schedule, budget) before kickoff
This includes creating a task breakdown, timeline with milestones, and resource allocation.
Clearly assign and manage tasks: Delegate and explain tasks to team members, ensuring each person knows their responsibilities and deadlines
Continuously adjust assignments based on team members' strengths and project needs to keep work balanced.
Monitor progress and adapt plans: Track project activities daily/weekly against the schedule. Update timelines or resource plans as needed to address slippage
If deliverables fall behind, take corrective action (reallocate work, adjust scope, etc.) promptly and transparently.
Coordinate cross-functional collaboration: Liaise with other departments, external partners, or vendors to manage interdependencies
For example, ensure the marketing team's tasks align with the product team's timeline, or that a vendor's deliverables meet the project requirements.
Identify and mitigate risks/issues: Proactively spot potential risks or roadblocks (e.g. resource constraints, technical challenges) and develop mitigation plans. If issues occur, resolve them or escalate per the escalation path
For instance, if a key supplier is delayed, the PM finds alternatives or negotiates timeline adjustments.
Communicate status and updates: Provide regular status reports (weekly written updates and/or meetings) to stakeholders and sponsors
This includes progress against milestones, upcoming tasks, risk status, and any needed decisions. The PM ensures no one is "in the dark" about project health.
Lead team meetings and drive accountability: Run effective project meetings (daily stand-ups, weekly check-ins, etc.), documenting action items and decisions. Follow up with individuals on their deliverables and deadlines, holding team members accountable in a supportive manner (e.g. gentle reminders, offering help for obstacles).
Ensure project closure and improvement: Upon completion, conduct a post-project review. Capture lessons learned and performance metrics (e.g. budget vs actual, schedule variance) to identify improvements . Ensure all deliverables are accepted and all documentation is archived for future reference.
Must-Have Skills
Hard Skills
Project Planning & Scheduling: Ability to create timelines (e.g. Gantt charts), define milestones, and sequence tasks using tools like MS Project or Trello. Should confidently perform critical path analysis and adjust schedules to meet deadlines.
Scope & Requirements Management: Skilled at gathering requirements and defining project scope. Can manage scope changes through change requests, impact analysis, and stakeholder approval to avoid scope creep.
Risk Management: Proficient in identifying project risks (technical, logistical, etc.), assessing their impact/probability, and planning mitigations
Maintains a risk register and proactively updates it throughout the project.
Budgeting & Cost Control: Able to create and manage a project budget, estimate costs, and track expenses against forecasts
Makes cost-conscious decisions and flags budget variances early, adjusting plans to stay within budget.
Project Management Tools & Software: Experienced with common SMB-friendly PM tools - e.g. Microsoft Excel/Project, Google Sheets, Trello, Asana, or Jira - for task tracking and reporting. Comfortable leveraging collaborative tools (Slack, Teams, SharePoint) to coordinate work.
Reporting & Documentation: Strong ability to produce project artifacts: status reports, dashboards, project charters, schedules, meeting minutes, and process documents. Can present data clearly (often in Excel or Slides) and write concise summaries for different audiences.
Quality and Detail Orientation: Capable of implementing basic quality checks (test plans, peer reviews) to ensure deliverables meet requirements. Pays attention to details in plans and reports to catch inconsistencies or errors (e.g. aligns dates, numbers correctly).
Methodological Knowledge: Familiar with project management methodologies (Waterfall and Agile). Knows when to employ a more iterative Agile approach (e.g. for a software project with sprints) versus a linear Waterfall plan, and can blend approaches in an SMB context for practicality.
Stakeholder Management: Adept at managing stakeholder expectations and requirements. Can negotiate priorities or trade-offs, and maintain client/customer satisfaction through proactive communication and delivering on promises.
Soft Skills
- Communication: Exceptional written and verbal communication skills Able to convey project information clearly to all levels - from team members to CEOs - and to listen actively to feedback. Tailors communication style (detailed vs. high-level) based on audience. Organization & Time Management: Highly organized in managing their own and the team's time
Keeps track of many moving parts (tasks, deadlines, documents) systematically. Excellent at prioritizing tasks and helping the team focus on what's most important to meet deadlines.
Leadership & Team Motivation: Demonstrated ability to lead without formal authority Motivates and guides the team toward goals, provides support and clear direction, and resolves blockers. Leads by example, maintaining a positive attitude and work ethic that inspires others.
Problem-Solving & Decision-Making: Strong analytical thinking to solve unexpected problems quickly
Can break down complex issues, evaluate options, and make sound decisions under pressure (e.g. deciding to crash the schedule or reprioritize features when behind).
- Adaptability: Remains calm and flexible in the face of change Can pivot plans when requirements change or setbacks occur, without losing momentum. Embraces new ideas or tools quickly and helps the team adjust (critical in SMBs where priorities can shift). Conflict Resolution & Interpersonal Skills: Skilled in managing and resolving team conflicts or disagreements diplomatically. Uses high emotional intelligence and empathy to understand perspectives , facilitate open dialogue, and find win-win solutions. Maintains strong working relationships across the organization.
Hiring for Attitude
Accountability & Ownership: Takes responsibility for outcomes, good or bad. Doesn't make excuses or blame others - instead, owns mistakes and focuses on solutions . Shows a strong commitment to seeing projects through and delivering on promises.
Proactiveness: Acts ahead of potential problems; doesn't wait to be told. For example, proactively clarifies ambiguous requirements or addresses a risk before it becomes an issue. A "self-starter" who seeks improvements and volunteers for challenges.
Continuous Improvement Mindset: Eager to learn and improve. Seeks feedback, stays updated on project management best practices, and reflects on what could be better. In an SMB, this might mean creatively streamlining processes or adopting a new tool that could benefit the team.
Resilience & Calm Under Pressure: Maintains composure during project crises or tight deadlines. Handles stress without panic, and instills confidence in the team. Bounces back from setbacks quickly, maintaining focus and optimism.
Empathy & Team-Oriented Attitude: Truly cares about team members and stakeholders. Listens to their concerns and perspectives . Willing to pitch in and help others to achieve the collective goal. Prioritizes team success and a positive working environment over ego.
Integrity & Transparency: Honest and ethical, especially with project status. Will not "whitewash" bad news or fudge numbers - communicates truthfully to stakeholders (e.g. if a deadline will slip, they say so and address it). Builds trust by doing the right thing.
Adaptable Work Style: Embraces the SMB culture of wearing multiple hats and dealing with changing priorities. Demonstrates flexibility, whether it's taking on an unexpected task outside their role or adjusting to a new process with a good attitude.
Positive, Can-Do Mindset: Approaches challenges with enthusiasm and a solution mindset. Rather than complaining about constraints (budget, time, etc.), focuses on what can be done. This attitude is contagious and helps maintain morale.
Tools & Systems
Systems / Artifacts
Common Software/Tools:
Productivity Suites: Microsoft 365 (Outlook, Excel, Word, PowerPoint) or Google Workspace (Gmail, Sheets, Docs, Slides) - for emails, scheduling, documentation, and tracking spreadsheets.
Communication & Collaboration: Slack or Microsoft Teams for real-time messaging and team coordination; Zoom/Teams for video meetings. Shared cloud drives (OneDrive, Google Drive, or SharePoint) for document storage and collaboration.
Project Management Tools: Trello, Asana, or Monday.com for task and workflow management (kanban boards, assignments, due dates). Possibly Microsoft Project or Smartsheet for Gantt charts and detailed scheduling (if needed for timeline visualization). For software projects, Jira may be used to track issues and manage sprints.
Other Tools: Simple ticketing or issue tracking systems (Jira, GitHub Issues) if relevant to the project. Time-tracking or resource management tools if the SMB uses them (e.g. Harvest, Toggle). Basic design or diagram tools (Lucidchart, Visio) to map processes or structures when needed.
What to Assess
Situational Judgment Scenarios
Realistic dilemmas a mid-level Project Manager might face in an SMB:
Tight Deadline vs Reality: Your project is falling behind schedule due to an unexpected two-week vendor delay. A key client, however, insists that the original deadline must be met. You must decide how to handle the schedule pressure while maintaining quality and client satisfaction.
Conflicting Priorities: Two high-priority projects from different department heads are assigned to you, both with similar timelines. They also both require the same specialist resource for critical tasks. You're stretched thin and need to allocate resources or negotiate timelines to avoid failure in one or both projects.
Scope Creep Request: Midway through a project, a major client requests an additional feature that was not in scope. They want it included without extending the deadline or increasing budget. You must figure out how to respond to this scope change request in a way that balances client relationship and project constraints.
Critical Team Member Loss: A core team member with specialized knowledge quits unexpectedly in the middle of the project. Their tasks are now unassigned and the project's timeline is at risk. You need to address the knowledge gap and redistribute work, possibly while seeking a replacement or interim solution.
Budget Cut Mid-Project: Halfway through execution, senior management informs you that the project budget is being cut by 20%. You have to adjust the project plan to fit the new budget - potentially de-scoping some deliverables, finding cost savings, or negotiating for more efficient solutions - all while keeping the project objectives achievable.
Underperforming Team Member: One of your team members has been consistently missing deadlines and the quality of their work is causing rework. Other team members are starting to complain that this is dragging the project down. You need to handle this performance issue - whether through coaching, reassigning tasks, or other means - to keep the project on track without demoralizing the team.
Vendor Delay & Stakeholder Pressure: An external vendor responsible for a key component has delivered subpar work and is running weeks late. Stakeholders are getting anxious as this delay jeopardizes the overall timeline. You must work on a contingency plan (perhaps finding an alternative vendor or adjusting the schedule) and communicate a clear plan to stakeholders.
Quality vs Deadline Dilemma: In final testing, you discover a critical defect in the product deliverable just days before the launch date. Fixing it will mean missing the promised deadline, but releasing on time means delivering a flawed product. You must decide whether to push back the deadline (and how to justify it) or find a workaround, balancing quality concerns with stakeholder expectations.
Assessment Tasks
Attention to Detail Tasks
Deterministic task ideas to test the candidate's attention to detail (with exact data setups for error spotting):
Schedule Consistency Check: Present the candidate with a mini schedule snippet that has a dependency error. For example:
Task A: Start March 1, Finish March 5
Task B (depends on Task A): Start March 4, Finish March 8 Here, Task B is scheduled to start before Task A finishes (March 4 vs March 5). Task: Identify the
scheduling inconsistency. (Expected answer: Task B's start date conflicts with its dependency on Task A - B shouldn't start until after A's completion on March 5.)
Progress Report Math Check: Give a short status update excerpt with a miscalculated percentage. For example: "Out of 10 tasks, 5 are completed (60%). The project is on track." Task: Find the error in this report. (Expected answer: The completion percentage is incorrect - 5 out of 10 tasks is 50%, not 60%, indicating a mistake in reporting.)
Budget Sum Verification: Provide a brief project budget table that contains a summation error. For
instance: - Item 1: \$5,000 - Item 2: \$7,000 - Total: \$13,000
Task: Check the budget totals and identify any discrepancy. (Expected: The total is incorrect; \$5k + \$7k = \$12k, not \$13k. The candidate should flag that the budget total is \$1,000 off.)
- (Additional idea if needed: Provide two versions of a requirements list or schedule - one in a brief email summary and one in an attached document - with a small contradiction between them (e.g. a date or figure differs). Ask the candidate to spot the discrepancy. Expected: They identify that, say, the email says delivery on June 30 but the document timeline shows July 5, highlighting the inconsistency.)*
Task 1: Proofread a Status Update - Present a 3-4 sentence project update that contains two factual errors or inconsistencies. For example: "As of Week 4, we have completed 8 out of 15 tasks (about 60%). The project budget spent is \$50,000 of the \$100,000 (25%). We are on track to finish on time." Task:
Identify the errors in the above report. -Expected Answer: The candidate should spot the math mistakes: 8/15 is ~53%, not 60%, and \$50k of \ $100k is 50%, not 25%. Those are clear inaccuracies. They might also note that claiming "on track" is questionable given those numbers, but the obvious errors are the percentages. -Grading: 1 point for each error identified (total 2 points). The answer must specifically state the correct figures or at least that the given percentages are wrong. This checks if they can catch mismatched numbers in a typical report. No partial credit beyond those two points (it's either caught or not).
Task 2: Schedule Alignment Check - Show a tiny table of tasks with dates: e.g. -Design Phase: Start May 1 - End May 5 -Testing Phase (depends on Design): Start May 4 - End May 8 Ask: "Is there anything wrong with this schedule? If so, what?" -Expected Answer: Yes, there is an issue: The Testing phase is set to start on May 4, before the Design phase ends on May 5. That violates the dependency. The candidate should point out that Testing should not start until Design is complete. -Grading: Full credit (2 points) for identifying that the start date of the dependent task is too early. If the candidate just says "Yes, there's an overlap" or "the dates conflict," that's fine. No credit if they don't see the issue or give an unrelated answer. This tests a simple detail in sequencing.
section scoring: total ~4 points across two tasks. You can scale it to your overall scoring system. It's quick, binary identification of errors.)
Overall Scoring Notes for Assessment: Each section yields a sub-score (e.g. Cognitive 3 Qs ~3 points, Hard Skills ~3, SJT ~4, Soft ~5 rubric points, Accuracy ~4; total ~19 points possible, which can be converted to a percentage). It's recommended to set a cutoff (e.g. 70% of points) as a pass threshold for the assessment. Answer keys above ensure deterministic grading for everything except the soft skills prompts, which use a rubric for consistency.
11) Interview Blueprint (30 minutes, 6 questions)
Real-world communication prompts to assess written communication clarity, tone, and completeness:
Email - Project Delay to Client: Scenario: Your project hit a snag that will cause a two-week delay in delivery. Write an email to an external client (or executive sponsor) informing them of the delay. Explain the situation, reassure them by outlining what the team is doing to resolve the issue, and adjust expectations (propose a new delivery date). The tone should be professional, transparent, and solution-focused (no blame-shifting).
Email - Status Update to Stakeholders: Scenario: It's midway through the project, and you owe stakeholders a status report. Draft a concise email update to all stakeholders summarizing progress made, work planned next, and one current risk (e.g. "supplier delay") along with your mitigation plan. Ensure the email is clear to a non-technical audience and instills confidence that you have things under control.
Chat Message - Missed Deadline Discussion: Scenario: A team member under your project missed a critical deadline for a task and hasn't communicated proactively. Compose a Slack/Teams message directly to that team member. In the message, 1) acknowledge the missed deadline, 2) ask if there were blockers or issues, and 3) re-establish a plan (or offer help) to get the task back on track. The tone should be supportive yet firm on the importance of communication and timely delivery.
Chat Message - Team Morale Boost: Scenario: The project team has been working long hours and is under pressure as a deadline nears. Craft a quick team chat message to boost morale. Thank them for their hard work, recognize a specific achievement or milestone they've hit, and remind them of the goal in sight. The tone should be positive, motivating, and appreciative. (This prompt checks the candidate's ability to empathetically communicate with the team.)
Tasks
Deterministic simulation or case-based tasks to assess project management process knowledge. Each task includes expected steps for grading:
Task 1: Risk Assessment Case - Scenario: "You are managing a project to implement a new office IT network. Identify two significant risks that could impact this project, and for each risk, describe a mitigation strategy."
Expected answer (scoring): The candidate should produce at least two plausible risks with clear mitigations. For example:
Risk: Potential hardware delivery delays (network equipment might arrive late). Mitigation: Order hardware early; have backup suppliers on standby; or plan a buffer in the schedule for delivery.
Risk: Network downtime disrupting business operations during the cutover. Mitigation: Schedule cutover during off-hours; communicate and get buy-in on a maintenance window; have a rollback plan in case of issues.
Scoring note: Full credit if they identify relevant risks and provide practical mitigation steps. Partial credit if either the risk is too trivial or mitigation is vague. Look for specificity (e.g. "vendor delay" and "use alternate supplier" is good detail).
Task 2: Scheduling & Critical Path - Scenario: "Below is a list of project tasks, durations, and dependencies. Calculate the minimum project completion time and identify the critical path:
Task A: 3 days (no dependencies)
Task B: 3 days (depends on Task A)
Task C: 2 days (depends on Task A)
Task D: 1 day (depends on Tasks B and C)"*
Expected answer: The candidate should recognize that Tasks B and C can run in parallel after A completes. Task A (3d) must finish first. Then Tasks B and C both start; Task B takes 3d, Task C takes 2d (so B is the longer path). Task D (1d) can only start after both B and C are done - effectively it waits for B (the slower of the two).
Total duration = A (3d) + B (3d) + D (1d) = 7 days.
Critical path = A -> B -> D (7 days). Task C (2d) finishes earlier than B, so it's not on the critical path.
Scoring note: Full credit for correct critical path and duration. If a candidate lists the sequence and gets 7 days, that's correct. Minor arithmetic errors (like saying 6 or 8 days) would be marked wrong as this is a deterministic calculation. The key is understanding parallel vs sequential tasks.
Task 3: Scope Change Procedure - Scenario: "Mid-project, a stakeholder requests a major change: adding a new feature that will require additional work. Describe the steps you would take to manage this scope change."
Expected answer: The candidate's response should outline a clear change control process. For example:
Evaluate Impact: Assess how the requested feature will affect timeline, budget, and resources. (e.g. "This change would add 2 weeks of development and \$10K cost.")
Discuss with Stakeholder: Meet with the requesting stakeholder (and sponsor, if needed) to review the impact. Ensure they understand trade-offs (what might need to be deferred or increased cost).
Get Approval or Decision: Go through formal approval - either the stakeholder agrees to adjust scope/time/budget or defers the change. Document the decision (sign-off on a change request).
Update Project Plan: If approved, incorporate the change: update the schedule, task assignments, and budget. Communicate the new plan to the team so everyone is aware of the change. If not approved, log that decision and continue with original scope.
Communicate to All Stakeholders: Ensure all relevant parties (team, other stakeholders) know about the scope change and the new expectations. Prevent confusion by clearly outlining what's changing.
Scoring note: Look for a structured approach covering analysis, stakeholder communication, and plan adjustment. Full points if they hit the main steps (analysis -> approval -> plan update -> communication). If they simply say "tell the team to do it" without impact analysis or approval, that's a red flag (score low).
Task 4: Multi-Project Prioritization - Scenario: "You are managing two projects that both need the same specialist at the end of March, but you only have one specialist. Both project owners insist their project is top priority. Outline how you would handle this resource conflict."
Expected answer: The candidate should demonstrate a diplomatic and systematic approach, such as:
Assess and Compare Priorities: Speak to both project owners along with higher management if needed. Determine if one project has a harder deadline or higher business value to justify priority.
Resource Leveling Options: See if the specialist's work on one project can be shifted by a few days (e.g. adjust one project's schedule to use the specialist in early April, if possible). Alternately, find a backup resource or split the specialist's time (though splitting may risk both projects).
Escalate if Needed: If both truly cannot budge, bring the conflict to a steering committee or common manager to align on priority - an SMB may rely on a management decision on which project takes precedence.
Communicate Plan: Once decided, communicate to both project teams what the resolution is (e.g. Project X will get specialist at end of March, Project Y delayed by 1 week), and adjust plans accordingly. Keep transparency to maintain trust.
Scoring note: A strong answer will involve communication and negotiation between stakeholders and logical reprioritization. Full credit if they consider business impact and involve management as needed, instead of trying to double-book the specialist (which is unrealistic). Partial credit if they at least acknowledge discussing with stakeholders but might miss escalation or adjusting timelines. No credit if they propose an obviously unviable solution (e.g. "just work the specialist 16-hour days on both projects").
Already have an account? Use template directly
Recommended Interview Questions
- 1
Tell me about a time you had to manage a significant change in project scope or requirements mid-project. How did you handle it, and what was the result?
- 2
Describe a situation where you encountered conflict or a difficult team dynamic on a project team. How did you address the issue, and what was the outcome for the project?
- 3
Walk me through how you create and manage a project schedule for a typical project. What tools do you use, and how do you keep the schedule up to date once the project is in motion?
- 4
How do you approach risk management on a project? Can you give an example of a risk you identified early and how you mitigated it?
- 5
If midway through a project you realize it will likely miss the deadline, what steps would you take and how would you communicate this?
- 6
We all make mistakes or have projects that don't go as planned. Can you tell me about a professional failure or major setback you experienced as a project manager, and how you handled it?
Already have an account? Use flow directly
Scoring Guidance
Weight Distribution: To evaluate candidates holistically, assign weight to each assessment dimension as follows (suggested): -Technical/Hard Skills - 30%: (Combining the Hard Skills test section and technical interview questions). Strong project management fundamentals and tool proficiency are crucial. This includes their performance on scheduling, budgeting, risk tasks, and how they answered technical deep-dives in interview. -Communication Skills - 20%: (Written communication task + verbal communication in interview). Given the PM's role, clear communication is critical. Written tasks and how coherently they express themselves in answers are assessed here. -Problem-Solving/Cognitive Ability - 15%: (Cognitive test section + any analytical thinking shown in interview). This covers their aptitude for quick thinking, numerical reasoning, and structured approach to solving project problems. -Leadership & Soft Skills - 20%: (SJT section + behavioral interview questions). This gauges teamwork, conflict resolution, stakeholder management, adaptability, etc. Weigh their SJT best/worst choices and examples they gave in STAR questions. -Attitude/Cultural Fit - 15%: (Hiring-for-attitude traits in answers + any red flags). This is somewhat subjective but vital. It includes their attitude as seen in the soft skills prompts, how they talk about past experiences (ownership vs. excuses), and overall alignment with the company's values (e.g. accountability, proactiveness). A candidate who scores high here shows positivity, integrity, and growth mindset, which are must-haves for long-term success.
Pass/Fail Criteria for Must-Haves: Certain skills/traits are non-negotiable - if a candidate fails these, they should be disqualified regardless of other scores: -Communication Clarity: If either their written test answers or interview responses demonstrate poor communication (e.g. cannot clearly convey ideas, or heavy language issues that would impede work), that's a fail. A PM must communicate well. -Basic Planning Competence: If the candidate cannot articulate how to create a simple plan/schedule or performs extremely poorly on the scheduling tasks (e.g. completely misses the concept of dependencies or critical path), it's a fail. This is core to the job's function. -Attitude Red Flags: Any strong red flag from section 9 (for example, arrogance, lack of integrity, or blaming others constantly) is cause for rejection. Cultural fit in terms of accountability and collaboration is essential - no score can compensate for a toxic attitude. Interviewers should use their judgment here; if multiple interviewers note a concerning attitude, it should outweigh other scores. -Attention to Detail: If the candidate misses most of the accuracy test issues and also makes a lot of careless mistakes elsewhere (maybe giving inconsistent details in stories, etc.), it indicates they may not be detail-oriented enough for a PM role. That could be a fail, or at least a strong mark against. -Honesty in Experience: If during the interview, inconsistencies arise in their stories or they can't back up what their resume claims, that's an immediate fail (integrity issue).
Scoring Implementation: It's recommended to set a minimum threshold in each major category (e.g. at least 50% in each and the weighted total at least 70%). For example, if someone aces technical but bombs communication or soft skills, they should not pass overall. Conversely, use the weightings to favor well-rounded competence. Each interviewer can score responses 1-5 and the assessment test yields a numeric score; combine these per weights to guide the decision. Ultimately, prioritize must-have dimensions: a candidate who does not meet the bar on communication, planning, or attitude should be rejected
even if other aspects are good. Passing candidates are those with solid scores across all areas, with no must-have flags.
Red Flags
s When Interviewing PMs -Dice Hiring
Art of communication in project management
Project Management Test | TestDome
When to Use This Role
Project Manager (Mid-Level, SMB) is a senior-level role in Operations. Choose this title when you need someone focused on the specific responsibilities outlined above.
How it differs from adjacent roles:
- Construction Project Manager: Function: The Construction Project Manager (CPM) leads and coordinates all phases of building projects from initiation through close-out.
Related Roles
Hiring This Role in Your Industry?
See industry-specific hiring challenges and start a free trial.
Deploy this hiring playbook in your pipeline
Every answer scored against a deterministic rubric. Full audit log included.