Project Manager

About the role

As we take on larger customer onboardings and run more cross-functional launches simultaneously, someone has to make sure nothing falls through. That's you. You'll own the project plan, milestone tracking, customer-facing status updates, and the early warning system when something is going sideways. Typical projects are a mix of customer go-live onboardings and internal product launches, running 6–12 weeks with 5–10 stakeholders each. You'll usually have 5–10 projects running concurrently at different stages. The job is making sure things actually land — not facilitating check-in calls that could have been an email.

What you'll do

• Own the project plan from kickoff to go-live: milestones, owners, dependencies, and due dates — in writing, in a tool everyone can see, updated at least weekly
• Send weekly status updates to customers and internal stakeholders that are concise and clear: what's done, what's next, what's blocked, and what's needed from them
• Identify scope creep before it becomes a delay; surface it to the customer with options and a decision deadline — not an open-ended conversation
• Own the go-live checklist: every prerequisite checked off by the right person before the customer touches the new system
• Track open issues by severity and owner; nothing sits unassigned for more than 24 hours
• Coordinate between engineering, implementation, sales, and customer stakeholders — reduce the need for meetings rather than scheduling more of them
• Surface risks early: a two-week warning is useful; a same-day slip is not; you have a sense for which projects are quietly off-track before they announce it

What we're looking for

• 3+ years managing software implementation or product launch projects from kickoff to go-live — as the person who owned the outcome, not just coordinated logistics
• Organized and proactive: you chase the loose ends nobody else is watching and close them before they become incidents
• Strong communicator who can keep technical and non-technical stakeholders aligned without scheduling a meeting for every decision
• Comfortable in a fast, low-bureaucracy environment where process should serve the project — you run lightweight, useful process, not process theater

Nice to have

• PMP, Scrum, or similar credential (useful context, not a requirement)
• Experience coordinating software rollouts or data migrations for operations-heavy businesses where the go-live date is a hard constraint
• Familiarity with inventory, ERP, or operations software and the customer profile it serves