Mission

The Project Manager, Front-End & Technical Delivery owns the execution system that keeps Kargo's Engineering and Product Development teams shipping on time and in sync. This role brings structure, clarity, and accountability to front-end and technical initiatives — from sprint planning through post-release follow-up. When this role is firing, cross-functional teams are aligned, blockers are caught before they land, and delivery is predictable enough that leadership stops asking for status updates.

This is a hybrid role requiring onsite presence 4 days per week.

Outcomes — What Success Looks Like in 6–12 Months

• A trusted delivery system is built and actively used — Sprint boards, roadmap timelines, and release calendars are accurate, current, and treated as the single source of truth by Engineering, Product, and QA — not maintained in parallel with shadow trackers
• Delivery blockers drop measurably — Cross-team dependencies, capacity constraints, and risks are identified and addressed proactively; the team is resolving blockers before they become delays, not after
• Agile ceremonies drive real outcomes — Stand-ups are tight and purposeful, retrospectives produce process changes that stick, and sprint planning yields commitments teams actually execute against
• Release readiness is a repeatable process, not a scramble — A consistent go-live workflow is established; stakeholders are never surprised by launch timing, scope changes are communicated early, and post-release learnings are captured and used
• Execution backbone reputation is earned — Engineering, Product, and QA consistently cite this PM as the person who makes delivery happen — with accountability and clarity, not bureaucratic overhead

Skills — Core Technical Capabilities

Required

• 3–5 years of project management experience working directly inside software engineering teams — embedded in the delivery cadence, not coordinating from a distance
• Strong command of Agile methodology and the full SDLC; hands-on proficiency with Jira or equivalent for managing sprint boards, backlogs, and roadmap timelines
• Proven ability to manage concurrent workstreams and drive sprint commitments end-to-end — from scope definition through release and retrospective
• Ability to identify and manage cross-team dependencies and risks credibly; comfortable engaging with engineers on technical concepts without needing to implement them

Preferred

• Background in ad tech or another complex, high-throughput technical environment where delivery failures have direct revenue consequences
• Experience supporting workflow tools, ad servers, CMS platforms, or SaaS-based products

Competencies — Behaviors We Like to See

Ownership Without Prompting

• Takes full accountability for delivery from kickoff through post-release — surfaces risks early and follows through without being chased
• Communicates proactively when timelines shift; stakeholders hear about changes from this PM before they have to ask

Clarity That Moves People

• Gives precise, timely status updates and translates technical complexity into language that cross-functional partners can act on
• Documents decisions and action items consistently — nothing falls through the cracks, and no one has to reconstruct what was decided in last week's meeting

Bias for Action Under Pressure

• Drives delivery forward without waiting for perfect conditions; breaks large, ambiguous initiatives into incremental workstreams that keep momentum going
• Stays effective when scope shifts, incidents happen, or deadlines compress — doesn't lose the thread when things get hard

Low-Ego Team Navigation

• Manages competing priorities across Engineering, Product, and QA without creating friction or playing favorites
• Builds trust with globally distributed teams through consistency, follow-through, and a deliberate commitment to keeping overhead low