Senior Marketing Technology Project Manager: Future Opportunities

We need to produce HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "The Role", "Who You Are", "What You'll Do", "What Success Looks Like", "Requirements", "How You Consult", "Tools You'll Use", "Qualifications", "Benefits". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should map content to appropriate headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? It says e.g., meaning examples. We should use headings that match the content. Likely we should use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits". However the posting includes sections like "Who We Are", "The Role", "Who You Are", "What You'll Do", "What Success Looks Like", "Requirements", "How You Consult", "Tools You'll Use", "Qualifications", "Benefits". We need to decide which headings to output. We must include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to include sections that have content. We should not repeat the job title as a heading. No Job ID. We need to preserve all substantive information. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a note before you apply: "A note before you apply: We're not actively hiring for this role today, but we're building relationships ahead of upcoming client work. If your background fits, we'd like to start a conversation now so we're ready to move when a project lands!" That's basically application instruction? It's a note about not actively hiring. Might be considered boilerplate? It's not exactly EEO but it's a note about hiring status. The instruction says remove application instructions. This note is about not actively hiring, but it's still a note before you apply. Likely we should remove it. Also "Who We Are" is substantive. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  As a Senior Project Manager, you own integrated project plans, budgets, risk mitigation, and change control for medium to large marketing technology engagements. You select and tailor methodology (Agile, Waterfall, Hybrid) based on what the project needs. You manage vendor delivery, enforce governance, present risks and options to client leadership, and write for multiple audiences—executive summaries, decision memos, steering committee decks. You mentor Project Managers and elevate Stitch's delivery standards through your own execution.

  But maybe "About the role" corresponds to "The Role". Could also have "Who You Are" as "About you"? But we have limited headings. We could have sections: About the role (The Role), Responsibilities (What You'll Do), Requirements (Requirements + Qualifications?), Skills (Tools You'll Use?), Benefits (Benefits). Also maybe "Qualifications" separate. But we need to avoid duplication. Let's map: - About the role: combine "Who We Are" and "The Role"? Actually "Who We Are" is about company. Could be "About the company". But not in list. Might be okay to have "About the role" for the role description. "Who We Are" could be omitted? It's substantive about company. Could be placed under "About the role" or maybe we create a section "About the company"? Not in allowed headings but we could still use

  with any heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those. Thus we need to map content to those headings. Let's decide sections: - About the role: includes description of role (The Role) and maybe Who You Are? Actually Who You Are is about candidate traits. Could be part of "About the role" or "Requirements". But we have separate Requirements and Qualifications. - Responsibilities: What You'll Do (list of duties). Also maybe "What Success Looks Like" could be part of responsibilities? But it's about outcomes. Could be separate but we don't have a heading for success. Could incorporate into Responsibilities. - Requirements: includes Requirements section (the bullet list). Also maybe "How You Consult" and "Tools You'll Use" could be skills. - Qualifications: includes Qualifications section (experience, certifications, etc.) - Skills: could include Tools You'll Use and maybe How You Consult (consulting approach). But we could also put Tools under Skills. - Benefits: Benefits section. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information. So we must include all details from each section. Let's extract content: Who We Are: - At Stitch, we're building something extraordinary. As a fast-growing team of passionate marketing technologists, architects, and strategists, we bring together our diverse backgrounds and experiences to work towards one common goal: make marketers' lives easier with Braze. - Customer engagement is becoming increasingly complex, but with the right technology, processes, and strategies in place, marketers can achieve great things. We're motivated to be drivers of what the future of martech looks like by building solutions that work. - We're all in on Braze as the leading customer engagement platform and the cornerstone of the modern martech stack. As an Orbit-level certified Braze partner (the highest level of partnership), we work alongside marketers from some of the world's most beloved brands to stitch together innovative solutions, better processes, and smarter strategies that make marketing magic happen in Braze. The Role: - As a Senior Project Manager, you own integrated project plans, budgets, risk mitigation, and change control for medium to large marketing technology engagements. - You select and tailor methodology (Agile, Waterfall, Hybrid) based on what the project needs. - You manage vendor delivery, enforce governance, present risks and options to client leadership, and write for multiple audiences—executive summaries, decision memos, steering committee decks. - You mentor Project Managers and elevate Stitch's delivery standards through your own execution. Who You Are: - First and foremost, you're motivated by impact. To be the best CRM consultancy in the world, we have to be motivated by performance—both in how our work drives outcomes for our customers, and for how our work drives outcomes for Stitch. - This means you're not content with status quo—you're always looking towards what's next and seeking opportunities to grow yourself, grow our customers, and grow Stitch. - You have relentless standards and uphold them unapologetically. - You move nimbly, take ownership, drive things forward, and make the people around you better. - If this sounds like you, you will thrive here. What You'll Do (Responsibilities): - Own integrated project plans: scope, schedule, cost, dependencies. Manage critical path and scenario planning - Own budgets and forecasts. Track burn, perform variance analysis, re-baseline when needed. Support SOW and change management - Own risk mitigation and issue resolution. Write risks with cause → event → impact. Document mitigation vs. contingency - Own change control. Write change requests that clearly justify scope, cost, and timeline impact - Select and tailor Stitch's SEW delivery methodology based on project context, client maturity, and team capability - Design project dashboards and automated reporting. Produce executive updates that surface risk, not just activity - Manage cross-team dependencies and vendor delivery. Enforce governance at the project level - Write for multiple audiences: executive summaries, decision memos, steering committee decks, detailed delivery plans - Mentor and provide feedback for Project Managers. Manage your time to meet billable targets of 36+ hours per week - Travel up to 20% for client meetings, workshops, and onsite engagements What Success Looks Like: - Your projects are consistently on track—and when they're not, leadership hears from you first with a recovery plan already in motion - Clients trust your governance. Steering committee meetings are productive, not adversarial - Your financial management is precise—forecasts are accurate, variance is explained, and budget integrity is maintained - Project Managers you mentor are growing faster because of your coaching Requirements (What You Bring): - PM tool mastery: setup, reporting, and hygiene in ClickUp, MS Project, Smartsheet, Jira, or equivalent - Agile, Waterfall, and Hybrid—select and tailor per project - Budget ownership: forecasting, variance analysis, EAC, burn tracking - RAID ownership: proactive risk modeling, mitigation planning, and structured issue surfacing - Change control: scope boundaries, requirements traceability, assumption documentation - Marketing technology domain knowledge: 2-5 years with Braze or comparable platforms - Net new platform implementation experience preferred: you've led or co-led at least one full-lifecycle implementation (discovery through launch) - Passion for leveraging AI to help drive more efficient documentation (e.g., Gemini, Claude) - Documentation mastery: project charters, integrated plans, dependency maps, risk registers, go/no-go briefs, closure reports - Governance: stage gates, compliance checklists, audit logs, PMO standards How You Consult At Senior, you're managing outcomes, not tasks. How you communicate and build trust determines whether clients see Stitch as a vendor or a partner - Translate delivery complexity into business language. Lead meetings that drive decisions, not just updates - Build relationships at multiple levels. Communicate effectively with C-suite, project leads, and technical teams - Present risks with recommendations and tradeoffs, not just alerts - Navigate scope boundaries with confidence — knowing when to hold firm and when to adapt - Own outcomes. Lead without being asked. Identify what needs doing and do it - Share feedback with peers that raises the standard for how the team delivers Tools You'll Use: - ClickUp, MS Project, Smartsheet, Jira, Confluence (proficient in multiple) - PSOHub for time and project tracking. Slides / Powerpoint for executive reporting - Sheets / Excel for budgets and forecasting Qualifications: - 5-9 years of project or program management consulting experience and applicable experience in new implementation of enterprise marketing technology (e.g., Braze, Salesforce Marketing Cloud, Adobe, Oracle) - PM certifications (PMP, SAFe, Scrum Master, or equivalent) are a plus - Demonstrated experience managing budgets, vendors, and cross-functional teams - Client-facing experience within an agency or consultancy required - Knowledge of AI code editors (e.g., Cursor) and data integration platforms (e.g., Snowflake, Databricks) is a plus - Must be eligible to work in the United States, Canada, or United Kingdom without visa sponsorship Benefits: - Flexible PTO Policy - Paid Sick time - Medical, dental, vision and life insurance - Monthly tech stipend - Paid parental leave - Paid bereavement leave - Mental well-being support - In-person onboarding experience during your first week at our HQ in Indianapolis, Indiana Now we need to produce HTML with

  headings and

  or

  • . We need to decide which sections to include. Potential sections: - About the role (could combine Who We Are + The Role + Who You Are? But that mixes company and candidate traits. Might be too much. But we could split: