AI Value Delivery Lead (Partner Motion)

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Within Tldr on us:" which is about company. Should we include "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content: About the company (Within) - could be "About the role"? Not exactly. Could use "About the role" heading for description of role? The posting includes "As an AI Value Delivery Lead for our Partner Motion..." etc. That's role description. Could treat that as "About the role". Then responsibilities: list of duties (What you'll do). Requirements/Qualifications: list of qualifications. Skills maybe not separate. Benefits: listed. Pay: compensation range given. Schedule: not mentioned. So we omit Schedule. We must not repeat job title as heading. Job title is "AI Value Delivery Lead for our Partner Motion". Not to be used as heading. We must not include boilerplate like EEO etc. Remove. We must preserve all substantive info. We need to output only HTML fragment, no /, no markdown fences. Structure:

About the role

then

with prose summarizing role? But we should preserve details; we could put the role description in

paragraphs. Then

Responsibilities

with

• for each duty from "What you'll do". Then

  Qualifications

  with
  • for qualifications list. Then

    Benefits

    with
    • for benefits. Then

      Pay

      with

      containing compensation range. We must not include placeholder text like "commensurate with experience". Not present. Check for duplicated lines: remove. Let's extract content. Company description: "About Within Tldr on us: Series B, $91M raised, 7x growth last year. Digital Transformation gave rise to a $600B consulting Industry. AI Transformation will be 10x bigger and will be delivered through agents. We built that. Our AI discovers how work actually happens across every team and application, Structures it into a living Context Graph, and Improves it continuously. ServiceNow mapped 900+ processes in 9 days. DoorDash captured 3,800+ finance operations in 14 weeks. That's not a project. That's compounding intelligence. OpenAI, Google, DoorDash, and Stripe use Within to transform how they transform. We shipped GPT-4 document chat within 12 hours of OpenAI's API launch. We move fast, reward agency, and care deeply about our customers, our team, and our mission. At Within, you will thrive if: Velocity: You're seeking a culture of rapid iteration and constant change that turns into lasting impact. Agency: You're seeking a role where you can take initiative and embody ownership. Care: You hold yourself to high standards, and enjoy close collaboration with others who care deeply and hold themselves to equally high standards. Energy: You bring drive and optimism to everything you do. You thrive on finding creative solutions to ambiguous problem statements." That's about company and culture; could be part of About the role? Might be better as "About the company" but not in allowed headings. Could incorporate into About the role paragraph. Role description: "Become an industry disruptor, drive exponential impact, and move customers from promise → value, fast. As an AI Value Delivery Lead for our Partner Motion, you build and own a significant part of Within's partner delivery practice - the global systems integrators, Big Four and strategy consultancies, and specialist advisory firms who drive transformation for the Fortune 500 on the Within platform. You'll work alongside senior Delivery Leads and cross-functional teammates to co-architect how Within gets delivered at scale through partners. You run it on their most challenging client engagements to tackle ambiguous problems and scope new solutions as they surface. This is a high-ownership, high-growth role that will require a doer and builder mentality. This is the role we're looking for an individual with 5-7 years of relevant experience as well as:" Then list of qualifications bullet points. Then "What you'll do" list. Then "Who you might be" paragraph. Then "What Success Looks Like - Primary KPIs" list. Then Benefits list. Then Compensation Range. We need to ensure we don't miss any substantive info. Let's extract qualifications bullet list: - Consulting-grade problem structuring: Understanding of great operational design and process engineering, with the judgment to know the right level of structure for the problem in front of you. - Executive presence: Ability to think abstractly and speak at all levels - executive facilitation and storytelling, user journey design, customer experience and product. - Sharp analytical thinking: You structure ambiguous problems fast, reason from data rather than impression, and move between root-cause detail and the executive narrative in one breath. - Design thinking and change management depth: A player-coach who can multiply teams with their experience and make it scalable with AI. - Partner fluency: Comfortable scoping and co-delivering work through a partner ecosystem - briefing a systems integrator or consulting partner, holding their workstream to a bar, and staying accountable for the customer's outcome - Outcome-oriented and creatively scrappy: Hypothesize, hustle, and hone. Knows when to bend frameworks, creates two-way doors, is a technological self-starter, and treats setbacks as learning opportunities. - As a front-line conduit, you'll turn field learnings - including what does and doesn't work with partner-led delivery - into scalable playbooks, product improvements, and customer outcomes. That's a bullet list. Now responsibilities ("What you'll do"): - Drive time-to-value for your customers: Own and execute structured onboarding and implementation sprints that help customers hit their key milestones within 20-30 days. You'll own day-to-day coordination, customer communication, and progress tracking. - Co-deliver through the partner ecosystem: Work alongside systems integrator and consulting partners on indirect-delivery engagements - set scope and quality expectations, stay close enough to the work to catch drift early, and make sure a partner-run implementation still ladders up to a real, measurable customer outcome. - Support strategic advisory and consulting: Partner with senior leads on executive-facing deliverables - journey maps, readouts, change deployment sessions - and grow into leading these independently over time. - Drive new solution experience for customers: Spot the unaddressed problems and expansion opportunities that surface mid-engagement, and turn them into a crisply scoped next solution - a core input to how Sales and Delivery Leads grow the account. - Improve how we work: Spot friction in the implementation process and propose fixes. We expect you to make the playbook better, not just follow it. - Be the connective tissue: Relay field learnings - from direct and partner-led engagements alike - back to Product and Sales. Your observations from the front line are a core input into how Within evolves. Now "Who you might be" paragraph: - You've worked in consulting or a transformation-adjacent delivery role - management consulting, technology/implementation consulting, or a similar advisory environment — with hands-on experience scoping and running structured workstreams end-to-end, not just executing a fixed playbook. - You have a solutioning instinct: given a live customer problem with no pre-built answer, you can shape it into a scoped, sellable next engagement rather than waiting to be told what to build. - You're comfortable in ambiguity. You can scope a problem, make a plan, and execute without waiting for perfect information. - You communicate clearly across levels. You can write a crisp Slack to a user and a clean executive summary. - You actively use automation, no-code tools, and AI workflows, with the curiosity and speed to learn fast. - Bonus: Experience in enterprise SaaS, Six Sigma process design, and/or formal change management. Now "What Success Looks Like - Primary KPIs": - Time-to-value / Onboarding Sprint value-realization attainment across your engagements (SLA) - Partner co-delivery quality and outcomes, for the indirect/partner-led engagements you support - New solution and expansion opportunities scoped and handed off to Sales/Delivery Leads - Internal optimization (process improvements deployed + impact) - NRR & GDR across your partner book - In-person onsite is a part of the hiring process - Enablement design: Build a certification module that takes a consultant from zero to client-ready on one part of the platform - Quality standard: Take a partner-produced client deliverable and show us how you get it to Within standard - Tool prototype: Build an agent or automation using internal tools that addresses a real bottleneck in the partner motion - Customer & executive communication: Present your findings in an Executive Readout format Note: Some of these are more like expectations/success metrics. We'll keep them under Qualifications? Actually they are success metrics; could be under "What Success Looks Like". But allowed headings limited; we could put them under "Qualifications" or maybe under "Responsibilities"? Better to create a section "What Success Looks Like" but not in allowed list. 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? It says use

      for section headings (e.g. ...). Likely they expect only those headings. So we should map content to those headings. The success metrics could be part of Qualifications or Responsibilities. I'd put them under "Qualifications" as they describe expected outcomes. But we already have qualifications list; we could add another

      under Qualifications for success metrics. Or we could create a separate section "Requirements" maybe? But we have qualifications already. Could put success metrics under "Requirements". However the instruction says use those headings as examples; not strict list. I think we can include a section "What Success Looks Like" as a heading if we want, but they said use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests those are the allowed headings. Safer to stick to those. Thus we can have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to include all substantive info. We'll put company description and role overview in About the role paragraph(s). Responsibilities as list. Qualifications will include both the qualification bullet list and the success metrics bullet list (maybe separate subheadings? Not allowed). We'll just combine them into one list; but that may be long but okay. Benefits list as given. Pay: compensation range. We must not include schedule. Now ensure we don't include boilerplate like EEO etc. Remove. Now produce HTML. We'll need to escape any HTML special characters? The text includes symbols like →, &, etc. We'll keep them as is; they are safe inside text nodes. We'll produce:

      About the role

      About Within: Series B, $91M raised, 7x growth last year. Digital Transformation gave rise to a $600B consulting Industry. AI Transformation will be 10x bigger and will be delivered through agents. We built that. Our AI discovers how work actually happens across every team and application, Structures it into a living Context Graph, and Improves it continuously. ServiceNow mapped 900+ processes in 9 days. DoorDash captured 3,800+ finance operations in 14 weeks. That's not a project. That's compounding intelligence. OpenAI, Google, DoorDash, and Stripe use Within to transform how they transform. We shipped GPT-4 document chat within 12 hours of OpenAI's API launch. We move fast, reward agency, and care deeply about our customers, our team, and our mission.