Team Lead - Sales Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting: It includes sections: "Our Mission", "The Role", "What You'll Do", "What's Different About This Role", "About You", "A Few Things To Note". Also mentions benefits, schedule (work Tuesdays, Wednesdays & Thursdays in-person). Benefits: "competitive geo-localised benefits", links to UK and US benefits packages. No explicit pay or salary. So we should not create Pay section because not specified. Benefits: we have mention of benefits, we can include Benefits section with that info. Schedule: we have specific schedule: work Tuesdays, Wednesdays & Thursdays in-person at offices. So we can include Schedule section. Responsibilities: likely "What You'll Do" bullet points. Also "The Role" paragraph maybe overview. We'll combine. Requirements/Qualifications/Skills: "About You" includes experience, track record, etc. Could be Requirements. Also "What's Different About This Role" maybe more about role specifics but could be part of Responsibilities. We'll treat "About You" as Requirements/Qualifications. We need to use

• for any list of duties/requirements/benefits. So we need to convert bullet points into lists. We must preserve ALL substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format as HTML. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some legal note at end about auto-generated advertisement, etc. That's boilerplate; we should remove. Also "Find out more about the team and life at Omnea here." maybe not needed? It's a link; but it's not boilerplate? It's a call to action; maybe considered application instruction? It's not exactly instruction to apply, but it's a link to team info. Might be considered not essential? The instruction says remove application instructions. This is not exactly application instruction but could be considered promotional. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Find out more about the team and life at Omnea here." is not application instruction; it's just a link. Might keep but it's not substantive? It's a pointer to more info; but we are to preserve ALL substantive information. This is not substantive about the role; it's a referral. Could drop as it's not essential. Safer to drop. Also "We sometimes use AI note-takers..." that's about interview process; could be considered application instruction? It's about opting out. Might be considered application instruction; better to remove. Also "Legal note: if you are viewing this posting outside of the Omnea careers' page..." that's legal boilerplate; remove. Also "We're commercial, ambitious..." that's culture; maybe keep as part of About You? It's not a requirement but could be considered part of mission. Might be considered boilerplate? It's not legal/EEO. It's about values. Could keep as part of About Omnea? But we have no section for mission. Could include under "About the role"? Not sure. The instruction says we can include sections only when posting has real specific content. The mission paragraph at start is substantive about company. Could be included as a brief intro maybe as

  before sections? The instruction says output only HTML fragment; we can include

  for prose. So we can include a brief intro paragraph about mission. We must not repeat job title as heading. No job title given explicitly; we can ignore. We need to decide headings: We'll have: -

  About the role

  maybe containing overview paragraph from "The Role" and maybe mission? But "About the role" could be summary. -

  Responsibilities

  with
  of duties from "What You'll Do". -

  Requirements

  (or Qualifications) with
  from "About You". -

  Benefits

  with

  about competitive geo-localised benefits and links. -

  Schedule

  with

  about Tuesdays, Wednesdays & Thursdays in-person. We should not include Pay because not specified. We must not create sections with filler like "commensurate with experience". We have actual content. Now we need to extract bullet points. From "What You'll Do": - Own the deals that need your experience most: personally lead Omnea's largest, highest-stakes enterprise deals, running discovery across Heads of Procurement, IT, Security, and Finance and translating it into a technical narrative that justifies a strategic investment. - Present at the most senior level: take POC outcomes and implementation roadmaps directly to executives up to C-level, framing the conversation around measurable ROI. - Take the deals nobody else has seen before: step into the new vertical or unusually political buying committee, because you're the one with the pattern-matching to navigate it. - Multiply that experience through the team: sit in on discovery calls, demos, and POC reviews across your pod, coaching in the moment and after the fact so the same mistake doesn't get made twice. - Build the playbook: turn recurring deal patterns and objections into demo frameworks and talk tracks the whole team can use, so what you know doesn't stay with you. - Call when to step in: decide when an SC should run a deal solo and when you need to step in alongside them, and make that call fast enough that it doesn't cost the deal. - Help scale the team: give input into hiring, onboarding, and ramp for new SCs as the team grows. - Be the voice of the team: bring product gaps, competitive pressure, and what's landing back to Product and GTM leadership as one voice, not multiple separate opinions. That's 8 bullet points. Now "What's Different About This Role" includes bullet-like sentences but not explicit bullet list. Could be considered part of responsibilities or additional details. Might incorporate into responsibilities as additional points. But we can also treat as part of "About the role" overview. However we need to preserve all substantive information. So we should include those points somewhere. Could add them under Responsibilities as additional bullets. Let's extract: - Career-defining scope: help build Omnea's GTM and Solution Consulting function from the ground up in the U.S., with a direct hand in shaping the team itself, at a company that's still writing its playbook, rather than handing you one. - Own both sides of the role: you'll own complex enterprise deals end to end while also carrying accountability for a pod's output, influencing how individual deals get won and how the function operates as it scales. - Shape the team's strategy and growth: help define how the team expands, what skills it hires for, and how it operates day to day. - We're a flat, high-bar team where senior hires are expected to be self-directed from day one - you'll be trusted with real ownership from the moment you walk through the doors. - Impact at scale: the company is on an incredibly strong growth trajectory with enterprise momentum behind it, so the scope to create visible impact - through your own deals and through the team you build - is significant rather than incremental. - A genuinely meritocratic culture: high standards, direct feedback, and performance recognized quickly, with equity upside that reflects the level of ownership you carry, across both deals and people. These are substantive; we can add them as responsibilities or as a separate section like "What's Different". But we only have allowed headings list; we could add a section "What's Different" 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 says e.g., implying those are examples but we should stick to those? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. The "What's Different About This Role" could be part of About the role or Responsibilities. I'd put them under About the role as additional prose. Now "About You" bullet points: - Someone who thrives in this role is highly ambitious, genuinely energized by ambiguity, and wants to influence & define how this function works from the ground up. - They're also an exceptional individual contributor first: whatever they've been trusted with before - they've delivered on it, and now they want that experience to shape more than just their own deals. - 7-9 years in enterprise sales engineering, solutions engineering, or senior technical consulting, ideally in B2B SaaS - with experience growing & building teams - A track record owning high-contract-value enterprise deals end to end - you know that winning one takes strategic positioning and deep discovery - Comfortable working across large organizations with stakeholders at every level - Experience mentoring, coaching, or informally leading other SCs or SEs, or setting solution strategy and standards in a high-growth environment - An excellent communicator who can explain the same system to a procurement analyst and a CTO, and be credible to both - Proven as a top-performing individual contributor, with the ambition to go further: shaping how the Solution Consulting function operates and grows, whether that's by going deeper as a principal-level SC or by taking on ownership of a team - Able to work from our New York office at least three days per week We can turn these into

  • under Requirements. Now benefits: "We offer competitive geo-localised benefits, and you can check out our UK Benefits Package here and our US Benefits Package here." Also maybe mention "We work Tuesdays, Wednesdays & Thursdays in-person at our offices." That's schedule. Thus Benefits section:

    We offer competitive geo-localised benefits. You can review the UK Benefits Package and US Benefits Package.

    But we should not invent URLs; we can keep the text "here" as placeholder? The instruction says preserve ALL substantive information; we should keep the phrase "here" as is, but we cannot invent URLs. We can keep as plain text: "you can check out our UK Benefits Package here and our US Benefits Package here." That's fine. Schedule:

    We work Tuesdays, Wednesdays & Thursdays in-person at our offices.

    Now we need to include an introductory paragraph about mission maybe as

    before sections. Let's craft:

    At Omnea, we’re reinventing how enterprise businesses operate, starting with procurement – where a single purchase can drag on for months, trigger 50+ emails, and pull in Finance, Legal, Security, and IT just to get something approved. We’ve raised $75M from Khosla Ventures, Insight Partners, and Accel to change that. Our AI-native platform connects every person, step, and system so buying is fast, safe, and efficient – one place to request, automated approvals and renewals, real-time supplier risk, and complete spend visibility. The opportunity is massive. Every enterprise on the planet has this problem and nobody has solved it. We’ve 10x’d ARR to double-digit millions in 18 months and are trusted by global enterprises like Spotify, MongoDB, Monzo, and Albertsons. We’re now the 4th fastest growing startup in Europe & the Sunday Times' #1 Best Medium Sized Tech Company To Work for. Our team previously scaled Tessian (cybersecurity tech, backed by Sequ