Who Can Apply
This role is open to people based in United States — Remote, United States. If you live somewhere else, you probably can't be hired for it unless the posting says otherwise.
Role Overview
An overview of this role
As a Lead/Principal Journey Architect on GitLab's Digital Customer Outcomes team, you'll connect programs into customer journeys that drive meaningful actions, retention, consumption and revenue outcomes. You'll own journey design and service blueprints, starting with priority cohorts and expanding across products, personas and named, pooled and digital coverage models. Reporting to the Vice President, Digital Customer Outcomes, you'll join as an individual contributor at L5 (Lead/Staff) or L6 (Principal), depending on your experience and scope. At L5, you'll lead journey design and builds for priority cohorts; at L6, you'll own the journey framework across all products, personas and coverage models with division-wide influence. Digital Orchestration builds and runs journeys day to day; you'll remain accountable for their outcomes and improvement.
What you’ll do
- Design journeys backward from business outcomes to meaningful customer actions, audiences and engagement tactics. Map each cohort's intended path, timing, signals that customers need help and interventions to get them back on track.
- Decide which steps are self-serve, artificial intelligence (AI)-assisted or human-led, and define the handoffs between them. Design across in-product guidance, email, events and community, choosing the right channel for each moment.
This excerpt leaves out GitLab's standard introduction and stops part-way through the role description. Read the full job description on GitLab's site ›
Category
Before You Apply
Never pay money to apply for any job. Legitimate employers don't ask for application fees, training charges, or interviews over Telegram or WhatsApp. Found a closed link or suspicious listing? Report this listing ›