Project Manager Jobs
5 genuine, current openings aggregated from public job boards — Remotive, Jobicy, Arbeitnow and RemoteOK. JobStraight never reposts stale listings: each card links straight to the original posting. Before you apply, paste the job into TrueFit to see your honest fit score, tailor your resume in Resume Studio, and rehearse with AceCoach — all free.
What Makes Us Unique At Cloudbeds, we're not just building software, we’re transforming hospitality. Our intelligently designed platform powers properties across 150 countries, pro…
Executive Operations & Project Manager Location: Los Angeles, CA (Hybrid) Job Type: Independent Contractor (1099) Hours: Approximately 10 Hours per Week to Start Compensation: …
Omaze is reinventing fundraising by offering people the chance to win once-in-a-lifetime prizes while raising millions for charities around the world. Since launching in the UK in …
Krisenprojekte | Microsoft-Technologien | Turnaround-Management Hier übernehmen Sie Verantwortung für strategisch wichtige Microsoft-Großprojekte, die aus dem Takt geraten sind – u…
Under the supervision of a Production Manager or Production Lead, the Project Coordinator, Production provides back-office (non-customer facing) support in a specific timezone to e…
Before you apply
Application volume is the defining feature of this market. LinkedIn has been reported to process around 11,000 job applications per minute — roughly a 45% year-on-year rise — and recruiters describe receiving 300–500 applications on a popular role within three days. The practical consequence is that being a plausible candidate is no longer enough; you need to be an obvious one for the specific posting.
Two checks are worth doing before every application. First, the knockouts — work authorisation, years of experience, location and on-site expectations are filterable fields, and failing one ends the application regardless of how strong the rest is. Second, keyword coverage: make sure every skill you genuinely have that the posting names appears in your resume in the posting's own words. That is coverage, not density, and it never means adding skills you don't have. The widely-repeated claim that ATS software auto-rejects 75% of resumes is a myth traceable to a 2012 sales pitch — what actually filters you is those knockout fields plus a recruiter's six-to-eight-second scan, as our ATS guide explains with sources.
Project Manager interview questions you should be ready for
These are questions that recur in project manager interviews, with the structure of a strong answer. They're from our own question bank — not scraped from review sites.
How do you gather requirements from stakeholders? Conceptual
- Identify every stakeholder group, including the actual end users.
- Interview for the underlying problem, not their proposed solution.
- Document as user stories with clear acceptance criteria.
- Play it back for sign-off so misunderstandings surface early.
Watch out: Writing down the solution someone asked for without probing the need.
At senior level: Discuss resolving conflicting requirements across departments.
Functional vs non-functional requirements — what's the difference? Conceptual
- Functional: what the system must do — 'a user can reset their password'.
- Non-functional: how well — performance, security, availability, accessibility.
- Non-functionals must be measurable ('p95 under 300ms'), not vague ('fast').
- They often drive architecture more than functional ones do.
Watch out: Leaving non-functionals unquantified so they can't be tested.
At senior level: Show how you trade non-functionals against cost and delivery date.
How do you write a good user story? Conceptual
- Use: as a [role], I want [action], so that [benefit].
- Keep it small enough to finish in one sprint.
- Add acceptance criteria in given/when/then form.
- Apply INVEST: independent, negotiable, valuable, estimable, small, testable.
Watch out: A technical task disguised as a story with no user value.
At senior level: Discuss splitting epics along value, not technical layers.
Walk me through mapping and improving a business process. Case
- Map the current state end to end with the people who do the work.
- Quantify each step: time, cost, error rate, handoffs.
- Find the bottleneck and the non-value-adding steps.
- Design a future state and validate with a small pilot.
- Measure after, and document so it sticks.
Watch out: Designing the future state without observing the real work.
At senior level: Discuss change management — processes only improve if people adopt them.
How do you handle conflicting requirements from two departments? Scenario
- Get both stated explicitly with their business rationale.
- Trace each to a measurable objective so it's evidence, not opinion.
- Look for an option satisfying the underlying need of both.
- If genuinely zero-sum, escalate with a clear recommendation.
- Document the decision and communicate to both sides.
Watch out: Pleasing both and shipping an incoherent compromise.
At senior level: Build a standing governance forum to decide these faster.
How would you build a business case for a new system? Case
- State the problem and quantify its current cost.
- Lay out options including 'do nothing' as the baseline.
- Model costs (build, licence, run, change) vs benefits over 3–5 years.
- Show payback, NPV and the key sensitivities.
- Name the risks and mitigations.
Watch out: Only presenting the option you already favour.
At senior level: Stress-test assumptions with a defensible sensitivity analysis.
Predict the full question set for a specific job description →
Listings are aggregated from public feeds and refresh on every site build. JobStraight is not the hiring employer; apply on the linked source page.