Project Manager
NewOwn customer implementations from signature to steady state. Every Amhage platform replaces a workflow somebody already depends on, so a rollout is data migration, retraining, and trust rebuilt one conversation at a time.
What you will do
- Run implementations end to end. Scope, schedule, risks, dependencies, and the weekly customer call. You are the single point of accountability for a rollout landing on time and actually being used afterwards.
- Translate between worlds. Sit between an inspection firm's field crew, a practice manager, and our engineering. Turn "the report has to look like what the council expects" into a specification someone can build.
- Own the onboarding record. Tenant provisioning milestones, training completion, sign-off documents, and the compliance artifacts customers need for their own auditors.
- Close the loop on the product. Bring back what broke, what confused people, and what they asked for. In a company this size that feedback becomes the roadmap directly.
- Build the playbook. You will run implementations without one, then write the one that makes the next ten repeatable.
What we are looking for
- Five or more years managing software implementations or technical projects with external customers, not just internal initiatives.
- Comfort in regulated environments. Healthcare, medical imaging, utilities, transportation, or industrial inspection all count. You understand why an audit trail matters.
- Genuinely technical literacy. You do not need to write code, but you need to hold your own on tenant architecture, data migration, and integration constraints without hiding behind an engineer.
- Written clarity. Most of this job is writing that removes ambiguity for other people.
- The temperament for ambiguity. Early stage means the answer frequently does not exist yet and you are the one who has to go find it.
Helpful, not required
- PACS, DICOM, or clinical imaging workflow experience.
- NDT, asset integrity, or NASSCO PACP familiarity.
- PMP, PRINCE2, or equivalent, though we care far more about what you have shipped.
Send a short note about an implementation that went badly and what you did about it. That tells us more than a résumé does. Attach the résumé anyway.