Technical Project Manager

What you'll do

Client Engagement & Delivery

• Own multiple concurrent client engagements from kickoff through delivery and handoff. Accountable for scope, timeline, and client satisfaction end to end.
• Serve as primary point of contact for external stakeholders: set expectations, run status communications, manage escalations, and translate technical constraints into client-friendly terms.
• Translate business requirements into technical scope and push back when scope creep, unrealistic timelines, or under-resourced asks threaten delivery. Drive change orders and protect engagement margin.
• Track budget vs. actuals, utilization, and delivery risk across engagements. Flag slippage before it becomes a missed date or a margin problem.
• Manage dependencies and unblock the engineering team without micromanaging.
• Maintain project artifacts, timelines, and documentation across all engagements.
• Carry 15–20+ concurrent projects without losing fidelity on any of them. On-time delivery across all customer-facing launches is the standard.

Internal CS Operations & PS Delivery

• Run daily PS developer standups, manage Jira Kanban workflow and board architecture, and distribute workload across the engineering team.
• Own Pro Serv Customer Care ticket triage and resolution. Goal: 90%+ resolved within 5 business days. Make developer assignment calls and track to closure.
• Triage inbound Tech Services float requests from CS and Sales float demo requests. Make TAM assignment decisions in coordination with the Senior Director.
• Serve as trained CS launch backup when team members are on leave. Absorb the coverage without dropping PS delivery commitments.

Financial Tracking & Vendor Oversight

• Own PS financial tracking across HubSpot, SOWs, waived fees, and contract-included projects. Produce the monthly Finance report — every active project, SOW status, and dollar amount tied to HubSpot so Finance knows exactly when to invoice.
• Serve as primary vendor owner for Vibes' core PS vendors: approve invoices before Finance pays and oversee relationships with additional vendors in the PS ecosystem.

Reporting & Cross-Functional Coordination

• Own biweekly sprint review updates and rollup reporting to Tech Services and CS leadership. Present PS delivery status to the full Technology org in sprint reviews.

What you'll bring

Required

• 3–5 years managing client-facing technical delivery projects in a SaaS, professional services, or consulting environment.
• Proven stakeholder management — comfortable setting expectations, saying no diplomatically, and absorbing client pressure without passing it to the team.
• Jira or Linear fluency, comfort navigating engineering systems like GitLab.
• Demonstrated ability to carry 15–20 concurrent projects without dropping fidelity.
• Commercial fluency: SOWs, change orders, billable hours, and budget-vs-actuals math.
• Enough technical depth — APIs, integrations, deployment pipelines to challenge estimates, understand what "done" actually means, and coordinate developers without micromanaging.
• Adaptable methodology: agile where it helps, structured where it doesn't, without dogma in either direction.
• Experience coordinating across technical and non-technical stakeholders simultaneously — developers, TAMs, CS, Sales, and Finance all have different languages and different pressures.
• Strong written communication for async, documented coordination.

Preferred

• PMP certification.
• HubSpot experience, SOW tracking, project financial reporting, or CRM-adjacent workflows.
• Familiarity with mobile marketing platforms, messaging technology (SMS/MMS/RCS), or enterprise SaaS integrations.
• Vendor invoice management or financial oversight experience.
• Comfort with AI productivity tooling (Jira Rovo, Claude, Looker AI) or a track record of adopting and evangelizing new tools.

Signs you'll thrive here

• Ownership bias — you chase problems to closure rather than logging them and waiting.
• You navigate conflict between client demands and team capacity without burning either side.
• You've recovered a sideways engagement and can narrate the mechanics: re-scoping, escalation, expectation reset.
• You build systems that run without you having to explain them — documentation, process, Jira hygiene.
• You get traction with teams that don't report to you — influence is your primary tool, not authority.