Presales Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting. Content: - About Locus: description of company. Could be "About the role"? Actually "About the role" is a heading we can use for description of role. The posting includes "The role: We are looking for a leader to build and run our global PreSales organisation ...". That's about the role. So we can put that in

About the role

with paragraphs. - Responsibilities: The "Key Deliverables:" list includes bullet points. Those are responsibilities. So we can have

Responsibilities

with

• each. - Requirements: There's "Required Skills And Experience" which includes bullet points. Those are requirements/skills. Could be split into Requirements and Skills. The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide what content fits where. We have "Must-have Qualifications" list. That's qualifications. Also "Preferred Experience" list. That's preferred qualifications. We also have "Required Skills And Experience" list. That's skills/experience. We need to avoid duplication. Let's map: - Required Skills And Experience (bulleted): * Leading and building teams * Hiring to a raised bar while developing the people already in seat * Coaching in a way that changes behaviour and scales the team * Building depth so that no pursuit depends on one person * Running a diagnostic-led motion * Personally capable of running a business discovery conversation with a Chief Supply Chain Officer or COO and emerging with a quantified value hypothesis. And capable of teaching that skill to others. * Proving value * Specifying and driving reusable proof tooling with engineering, in engineering terms, against real dates * Turning objections into dated, concrete follow-up artifacts * Operating as a GTM leader * Honest technical risk forecasting, including recommending against a bid * Defending win-rate movement with evidence in a leadership or board review These are more like skills/experience. - Must-have Qualifications (bulleted): * 12+ years in enterprise software, with 5+ years leading customer-facing technical teams - PreSales, Solutions Consulting, Solution Architecture, including managing across more than one geography * Direct, hands-on experience in supply chain, logistics, transportation, or a comparably operations-critical enterprise category * A track record of seven-figure enterprise deals where you personally shaped the technical win * Demonstrated asset building: playbooks, POC frameworks, demo environments, certification programmes, or ROI tooling. * Experience leading a technical GTM team through a move upmarket - from transactional deals to enterprise transformation programmes * Comfort operating a distributed team across India, North America, and European time zones, with 30–40% travel * Strong written communication These are qualifications. - Preferred Experience (bulleted): * Experience selling or evaluating AI and agentic capability into enterprise * Exposure to outcome-based or gain-share commercial constructs and what they require of a technical team These could go under "Preferred Qualifications" but we only have Qualifications section; we could include them there as part of qualifications (maybe separate subsection). But instruction: include a section ONLY when posting has real specific content. We have qualifications content, so we can have a Qualifications section that includes both must-have and preferred. Could separate into two sub-sections? Not required; just list. - Benefits: The posting includes "What We Offer Join Locus and become part of a visionary team ... We provide competitive compensation, comprehensive benefits, and a collaborative environment where your expertise will drive both your growth and that of the organization." That's benefits description. So we can have Benefits section with that paragraph. - Pay: Not explicitly stated; only "competitive compensation" but no specific numbers. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It says "competitive compensation" is vague but still states compensation exists. However they said never create Pay section unless posting actually states them. Does "competitive compensation" count as stating? It's not a specific number or range. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It also says "Prefer a few substantive sections over many thin ones." And "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive compensation" is somewhat vague but not exactly placeholder like "commensurate with experience". It's a statement that compensation is competitive. Might be considered substantive? I'd lean to include Benefits section (which mentions competitive compensation and comprehensive benefits). Pay could be omitted because no specific numbers. Schedule: mentions travel 30–40% (under qualifications). That's schedule? Travel percentage could be considered schedule? The instruction says include Schedule section only if posting actually states them. Travel is not exactly schedule (like work hours). Might be considered schedule? Probably not. So we omit Schedule. Thus sections: About the role, Responsibilities, Qualifications (maybe combine Requirements and Skills?), Benefits. Could also have Skills section separate from Requirements. But we have both Required Skills And Experience (skills) and Must-have Qualifications (qualifications). Could split: Responsibilities, Requirements (maybe the Required Skills And Experience), Qualifications (must-have + preferred), Skills (maybe not needed). But to avoid thin sections, we could combine Required Skills And Experience into Qualifications as well. However the instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide. Given we have distinct content for responsibilities, qualifications (must-have + preferred), and skills/experience (the leading and building teams etc). Those are more like skills/experience. Could treat them as Requirements. Let's map: - Responsibilities: Key Deliverables. - Requirements: Required Skills And Experience (the list of leading and building teams etc). This is more like required skills/experience. - Qualifications: Must-have Qualifications + Preferred Experience. - Benefits: What We Offer. - About the role: The role description. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We should not include Skills separately to avoid duplication. Now we need to format. We must not include any boilerplate like EEO etc. The posting ends with "Locus is an equal opportunity employer dedicated to creating a diverse and inclusive workplace." That's boilerplate; remove. Also remove any duplicated lines. Now produce HTML fragment:

  About the role

  We are looking for a leader to build and run our global PreSales organisation as we scale our enterprise business in North America and Europe. It is a role for someone who likes building the discipline, the assets, and the bench that lets a technical GTM function scale beyond the people currently in it.

  But also include location and travel? Those are in qualifications. So fine. Now Responsibilities:

  Responsibilities

  • Discovery and diagnostics - business-led discovery with supply chain, operations, and finance leaders, ahead of any product demonstration
  • Solution design and demonstrations - business-scenario-native, built to the customer's own requirements
  • POCs, benchmarks, and simulations - including the technical proof work that decides competitive bake-offs
  • RFP technical response - architecture, integration, security, and functional depth
  • Value engineering - business-case and TCO modelling alongside the commercial team
  • Field technical enablement - certification and reference architectures for our global Sales & PreSales organisation
  Now Requirements:

  Requirements

  • Leading and building teams
  • Hiring to a raised bar while developing the people already in seat
  • Coaching in a way that changes behaviour and scales the team
  • Building depth so that no pursuit depends on one person
  • Running a diagnostic-led motion
  • Personally capable of running a business discovery conversation with a Chief Supply Chain Officer or COO and emerging with a quantified value hypothesis. And capable of teaching that skill to others.
  • Proving value
  • Specifying and driving reusable proof tooling with engineering, in engineering terms, against real dates
  • Turning objections into dated, concrete follow-up artifacts
  • Operating as a GTM leader
  • Honest technical risk forecasting, including recommending against a bid
  • Defending win-rate movement with evidence in a leadership or board review
  Now Qualifications:

  Qualifications

  • 12+ years in enterprise software, with 5+ years leading customer-facing technical teams - PreSales, Solutions Consulting, Solution Architecture, including managing across more than one geography
  • Direct, hands-on experience in supply chain, logistics, transportation, or a comparably operations-critical enterprise category
  • A track record of seven-figure enterprise deals where you personally shaped the technical win
  • Demonstrated asset building: playbooks, POC frameworks, demo environments, certification programmes, or ROI tooling.
  • Experience leading a technical GTM team through a move upmarket - from transactional deals to enterprise transformation programmes
  • Comfort operating a distributed team across India, North America, and European time zones, with 30–40% travel
  • Strong written communication
  • Preferred: Experience selling or evaluating AI and agentic capability into enterprise
  • Preferred: Exposure to outcome-based or gain-share commercial constructs and what they require of a technical team
  We could mark preferred items with "Preferred:" prefix. Now Benefits:

  Benefits

  Join Locus and become part of a visionary team that is redefining logistics through innovation and smart distribution. We provide competitive compensation, comprehensive benefits, and a collaborative environment where your expertise will drive both your growth and that of the organization.

  We should not include the EEO line. Now ensure no extra sections like Pay, Schedule. Now output only HTML fragment. Check for any leftover boilerplate: The initial "About Locus Battle-tested..." etc is company description; we didn't include that. Should we include it? The instruction: "Preserve ALL substantive information". The company description is substantive. Should we include it? Possibly under "About the company" but we don't have a heading for that. The allowed headings are limited to those list. We could include company description under About the role? Not appropriate. Could we add a section like "About the company"? Not allowed headings. 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 says use those for those sections. It might be okay to add other headings but they'd be non-standard. Safer to stick to allowed headings. However we must preserve ALL substantive information; omitting company description loses info. Could we incorporate company description into About the role paragraph? Might be okay to add a brief sentence about Locus within About the role. But the About Locus paragraph is separate from role description. Could we merge? The role description currently is just the paragraph about looking for a leader. We could prepend a sentence about Locus: "Locus is an agentic Transportation Management System..." etc. That would preserve info. Let's do that. Thus About the role paragraph: combine company description and role description. We need to ensure we don't repeat job title (not present). Good. Now final HTML.