Founding Agent Strategist

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes many details: description of role, responsibilities, what you'll do, who you are, nice to have, compensation range. No explicit Benefits, Schedule. So we should include sections: About the role (maybe a brief intro), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (maybe combine? but we need separate headings only if content). The posting includes "Who You Are" which includes experience, skills, traits. Could map to Requirements and Skills. Also "Nice to Have" could be additional qualifications. Pay: compensation range given. So include Pay section. Benefits: none explicit, so omit. Schedule: none explicit, omit. We must not repeat job title as heading. No Job ID. Use

for each section heading. Use

• for lists. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. There's none. We need to output only HTML fragment. Let's extract content: About the role: Could be first paragraph: "Fragment is the AI platform that autonomously streamlines procurement workflows end to end. Within a few months of launch, we signed Fortune 500 companies. Within a year of founding, our customers, all $1B+ revenue enterprises, continue to grow in number and are actively championing us to their networks, and our marketing and CAC to get here has been $0. We're hiring Agent Strategists to own the end-to-end deployment of Fragment's agents inside enterprise customers, from first workshop to live agents resolving work in production. You sit between the customer and our engineering and research teams. You learn their process cold, define the agents that automate it, get them live fast, and stay accountable for the outcomes after go-live." That's about role. Responsibilities: "What You'll Do" bullet points: Customer Discovery & Definition, Customer Facing Delivery Work, Product Work, Strategic Work, Advisor & Expansion. Each has sub-bullets. We need to list them as

  • . Probably each main bullet as li, with internal details maybe as nested ul? But spec says use
    • for any list of duties/requirements/benefits. Could flatten? Better to keep nested lists? Might be okay to have nested
      . We'll produce
      • with heading? But we can't add extra headings inside li besides text. We'll just put the description as text inside li. We'll need to preserve all details. Let's extract each section: Customer Discovery & Definition: - Walk into customers across different industries, different ERPs, and different levels of process maturity, and get productive fast. - Facilitate workshops with enterprise stakeholders to map their procurement and source-to-pay processes and identify the highest-value opportunities for autonomous agents. - Design the agent definitions that automate that work, tailored to each customer's priorities, data, and systems, and design the future-state workflows for how humans and AI agents share the work. - Help customers see what's possible when AI agents handle the work their BPOs and shared services teams do today. Customer Facing Delivery Work: - Be hands-on in launching and configuring customer deployments. - Connect Fragment to customer systems of record (ERP and adjacent procurement systems) so agents operate cleanly against live data. - Own deployment readiness: make sure the process logic, exception handling, and workflow configuration are dialed in before we go live. - Deploy at high velocity, driving rapid time-to-value and measurable ROI from day one, and run each engagement with the project management and iterative delivery that keep momentum and transparency across customer and Fragment teams. - Build the playbooks, process documentation, and implementation frameworks that let us scale delivery beyond your individual involvement. Product Work: - Partner with our engineering team to continuously refine and expand the platform's procurement capabilities. - Bring real-world process knowledge into the product loop, surfacing edge cases, validating automation logic, and ensuring that what we ship holds up against the complexity of actual enterprise procurement environments. - Guide the UX from a practitioner's perspective so the product feels intuitive to the teams who use it daily. - Bring your field learnings back to our research and product teams so the agents and the roadmap keep getting better. Strategic Work: - Help shape Fragment's point of view on what lean procure-to-pay and source-to-pay processes should look like when AI agents are in the loop. - Not incremental optimization of the status quo. A fundamental rethinking of how these processes are designed when autonomous resolution is the default, not the exception. - Contribute to thought leadership and strengthen our go-to-market messaging with operational depth. Advisor & Expansion: - Stay accountable for business KPIs and outcomes after go-live, not just launch. - Serve as a trusted advisor on how customers get the most out of agentic AI across their operations, and unlock new opportunities to expand where agents are deployed. - Bring the autonomous future to life for customers, helping them see not just what agents do today but how autonomous operations reshape their procurement strategy tomorrow. - This is a startup. You'll go deep on source-to-pay processes, but you'll also be pulled into whatever needs to get done. If you need a clearly scoped job description to be comfortable, this isn't the right fit. Who You Are (Requirements/Skills): - This role rewards slope over résumé. The best Agent Strategists learn ridiculously fast, think in systems, and are as comfortable with a VP of Procurement as they are whiteboarding logic with engineers. - Some arrive with deep procurement and deployment experience. Others arrive with raw horsepower and pick up the domain fast. Both work. - You might come from one of these paths: - The practitioner-consultant. You did real procurement or operations work inside a large enterprise, then moved into consulting and built breadth across industries, ERPs, and transformation methodologies. You have the intuition from having lived it and the structure from consulting. - The forward-deployed or solutions engineer. You've deployed complex software into enterprises at a high-growth company, sat in front of customers, owned outcomes, and seen forward-deployed work done well. You may not know procurement yet, but you know how to land a hard product in a messy environment. - The high-slope generalist. You come from top-tier consulting or a top MBA program, you ramp on new domains faster than anyone around you, and you want real ownership instead of slideware. You'll go deep on procurement quickly, because that's how you operate with everything. - Whatever the path, we're looking for 7+ years of relevant experience. - Regardless of background, you are someone who: - Learns ridiculously fast. You can walk into a company you've never seen, sit with their team, and produce a clear process map with decision trees, exception paths, and system touchpoints within days. - Thinks in systems, not tickets, and context-switches across industries and ERP environments without a long ramp. Our customers span electronics manufacturing, energy, automotive, food and beverage, and more, running SAP, Oracle, Coupa, Ariba, and homegrown systems, sometimes all at once. - Translates between practitioners and engineers. You can take a procurement team's messy description of how they handle exceptions and turn it into structured logic an engineering team can build against. - Combines technical literacy (SQL comfort, ERP schemas, a practical understanding of agentic workflows) with strong executive communication. - Is comfortable on-site with clients, thrives in a high-velocity environment, and measures success by customer adoption and expansion. - Takes ownership under pressure, with an instinct to run toward the fire. - Nice to Have: - Experience deploying or configuring enterprise AI or SaaS platforms as an FDE, applied engineer, or deployment specialist - Familiarity with enterprise data pipelines and integrations with existing systems - Exposure to the agentic AI ecosystem, LLMs, or automation platforms - Prior experience at a startup or in a fast-moving, ambiguous environment Pay: Compensation Range: $175K - $235K We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (maybe combine Who You Are), Qualifications (maybe 7+ years experience), Skills (technical literacy etc). But we could also just have Requirements and Skills separate. However we must not create sections with filler. We need to decide what to put. We could map: - About the role: intro paragraph. - Responsibilities: What You'll Do. - Requirements: 7+ years of relevant experience + the paths (practitioner-consultant, forward-deployed, high-slope generalist) maybe. - Qualifications: Learns ridiculously fast, thinks in systems, translates between practitioners and engineers, combines technical literacy with strong executive communication, comfortable on-site, thrives in high-velocity, takes ownership. - Skills: Nice to Have list? Or maybe Skills: technical literacy (SQL comfort, ERP schemas, agentic workflows), executive communication, etc. But we already have those in Qualifications. Could combine. Better to follow typical job posting: Requirements (experience, background), Skills (technical and soft). Qualifications maybe education? Not present. Given limited content, we could have: - About the role - Responsibilities - Requirements (7+ years experience, background paths) - Skills (technical literacy, executive communication, on-site, high-velocity, ownership) - Pay We should not create Qualifications if no distinct content. But we could treat "Learns ridiculously fast..." as Skills. However the spec says we can include sections only when posting has real specific content. We have content for each. Let's decide: About the role: as above. Responsibilities: list of What You'll Do. Requirements: 7+ years relevant experience + the three practitioner paths. Skills: Learns ridiculously fast, thinks in systems, translates between practitioners and engineers, combines technical literacy (SQL comfort, ERP schemas, practical understanding of agentic workflows) with strong executive communication, comfortable on-site with clients, thrives in high-velocity environment, measures success by customer adoption and expansion, takes ownership under pressure, instinct to run toward the fire. Nice to Have could be additional skills but we could incorporate into Skills as "Nice to Have" bullet list. Pay: compensation range. We'll not include Benefits or Schedule. Now produce HTML. We need to wrap each section in

        heading then content. For lists, use

        • . For prose,

          . We'll need to ensure we don't duplicate content. Let's craft. About the role: a paragraph maybe two sentences. We'll put:

          About the role

          Fragment is the AI platform that autonomously streamlines procurement workflows end to end. Within a few months of launch, we signed Fortune 500 companies. Within a year of founding, our customers, all $1B+ revenue enterprises, continue to grow in number and are actively championing us to their networks, and our marketing and CAC to get here has been $0. We're hiring Agent Strategists to own the end-to-end deployment of Fragment's agents inside enterprise customers, from first workshop to live agents resolving work in production. You sit between the customer and our engineering and research teams. You learn their process cold, define the agents that automate it, get them live fast, and stay accountable for the outcomes after go-live.

          Responsibilities:

          Responsibilities

          then
          with each main bullet as
          • . Inside each li we can have multiple sentences; we could also embed
            for subpoints but not required. We'll keep as plain text. We'll need to preserve all details; we can include line breaks inside li using
            maybe but not needed. We'll just write sentences. Let's list each main heading as li with its subpoints as separate sentences. We'll produce: