Pre-Sales Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No metadata like Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting: - Intro: "Build the demo that wins the deal. Harmoney is scaling across Europe, and enterprise opportunities are getting bigger and more technical. So we're hiring our first dedicated Pre-Sales Engineer: someone who turns complex prospect requirements into sharp, tailored demos and proofs-of-value. Not slideware. Not the same scripted demo on repeat. You build what the customer needs to see. You'll work on a product trusted by organizations such as Belfius, Baloise, AG Insurance, and Swiss Life. More importantly, you'll join a team that's ambitious, supportive, and genuinely enjoys building great things together. 🎯 Your impact Regulation is driving demand: AMLR lands in July 2027, with AMLA and DORA close behind. Prospects no longer want a slide about what our platform could do, they want to see their own use case running. You are the person who makes that happen, in days rather than weeks, and who turns a technical conversation into a signed deal. You sit between Sales, Product and Engineering. You report to the Head of Sales & CRO and work side by side with Account Executives across Belgium, France, the UK and beyond. 🚀" That's about the role / impact. Could be "About the role" section. Then "What You'll Do" bullet list. Then "You'll thrive in this role if you..." bullet list (requirements/qualifications/skills). Then "Nice to have" bullet list. Then "Why Harmoney?" bullet list (benefits, etc). Also includes "Competitive salary: salary band B4: €3,500 to €5,500 gross per month", "Company car (BMW) or mobility budget", "Wide range of benefits: net allowance, pension plan, hospitalisation & group insurance, meal & eco vouchers, ...", "Flexible hybrid working from our Ghent HQ, with travel to prospects across Europe", "32 days of annual leave", "Laptop, smartphone, phone subscription and everything you need to do your best work", "Long-term freelance collaboration also possible". Also "Our first dedicated pre-sales hire, with room to shape and scale the function and a path towards a leadership role", "Work at the frontier of AI-driven configuration on a real RegTech platform". Those are benefits. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: we have intro paragraph(s). Good. - Responsibilities: "What You'll Do" list. - Requirements: maybe "You'll thrive in this role if you..." includes required qualifications/experience. Could be Requirements. - Qualifications: maybe overlapping; but we can separate: Requirements (experience, years), Qualifications (education? none). Might be thin. Could combine. - Skills: maybe list of technical skills: JSON, YAML, low-code, AI tools, etc. Could be extracted from requirements. - Benefits: "Why Harmoney?" list. - Pay: salary band. - Schedule: flexible hybrid working, 32 days annual leave maybe schedule? Could be considered schedule. But we have "Flexible hybrid working from our Ghent HQ, with travel to prospects across Europe" and "32 days of annual leave". That's more about work arrangement and leave. Could be Schedule. We must not create sections with filler like "not specified". So we include only those with real content. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. No Job ID. We must output only HTML fragment. Let's craft:

  About the role

  ... (intro paragraph(s) combined).

  Responsibilities

  • Build bespoke demo environments end to end on our JSON low-code layer, pre-loaded with realistic synthetic data
  • Use Claude Code and other AI tools to accelerate configuration, and maintain a reusable library of skills, agents and demo templates per segment
  • Act as the technical counterpart to Account Executives across the full sales cycle: capability demos, deep-dive sessions, security and architecture reviews, integration mockups
  • Maintain a working knowledge of the Harmoney codebase and feed prioritised pre-sales signals back to product
  • Set the standard for how pre-sales works at Harmoney as the function grows

  Requirements

  • 3+ years in pre-sales, solutions engineering, technical consulting or a comparable hybrid technical and commercial role, ideally in B2B SaaS, RegTech or financial services software
  • Comfortable with structured configuration (JSON, YAML, low-code) and reading code, without needing to be a full-stack developer
  • Hands-on experience with modern AI coding tools such as Claude Code, Cursor or Lovable
  • Track record of shipping demo environments or proofs-of-value that materially contributed to closed deals
  • Fluent in English; Dutch or French is a strong asset for client-facing work in Benelux and France
  • Output‑oriented: you ship demos and move deals rather than polishing indefinitely
  • Technically curious: you are not afraid to open the editor and learn the codebase
  • Commercially aware: you spend your effort where it shifts pipeline
  Maybe we also need Qualifications? Could be same as Requirements; but we could add a Qualifications section for education? Not present. Could skip Qualifications if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it". So we can omit Qualifications if none. Skills: maybe we can extract specific skills: JSON, YAML, low-code, Claude Code, AI tools, etc. But those are already in Requirements. Could still have Skills section with those. However we risk duplication. Better to combine Requirements and Skills? But we need to follow headings list; we can include Skills if we have distinct content. Let's see if there is a distinct list of skills: "Have hands-on experience with modern AI coding tools such as Claude Code, Cursor or Lovable", "comfortable with structured configuration (JSON, YAML, low-code) and reading code", "Fluent in English. Dutch or French is a strong asset". Those are skills. Could put them in Skills. But we already have Requirements covering experience and personal attributes. Could split: Requirements = experience years, track record; Skills = technical and language skills. Let's do that. Thus:

  Skills

  • Structured configuration (JSON, YAML, low‑code) and ability to read code
  • Experience with AI coding tools such as Claude Code, Cursor or Lovable
  • Fluent in English; Dutch or French is a strong asset
  Now Benefits:

  Benefits

  • Opportunity to shape and scale the pre‑sales function as the first dedicated hire, with a path towards a leadership role
  • Work at the frontier of AI‑driven configuration on a real RegTech platform
  • Wide range of benefits: net allowance, pension plan, hospitalisation & group insurance, meal & eco vouchers, …
  • Laptop, smartphone, phone subscription and everything you need to do your best work
  • Long‑term freelance collaboration also possible
  Pay:

  Pay

  Competitive salary: salary band B4: €3,500 to €5,500 gross per month

  Company car (BMW) or mobility budget

  Schedule:

  Schedule

  • Flexible hybrid working from the Ghent HQ, with travel to prospects across Europe
  • 32 days of annual leave
  We should also include maybe "Regulation is driving demand: AMLR lands in July 2027, with AMLA and DORA close behind." That's part of About the role. Let's craft About the role paragraph(s). Combine the intro and impact paragraphs. About the role paragraph: "Build the demo that wins the deal. Harmoney is scaling across Europe, and enterprise opportunities are getting bigger and more technical. We are hiring our first dedicated Pre‑Sales Engineer to turn complex prospect requirements into sharp, tailored demos and proofs‑of‑value — not slideware, not the same scripted demo on repeat. You’ll work on a product trusted by organizations such as Belfius, Baloise, AG Insurance, and Swiss Life, joining an ambitious, supportive team that enjoys building great things together. Regulation is driving demand: AMLR lands in July 2027, with AMLA and DORA close behind. Prospects want to see their own use case running, and you make that happen in days rather than weeks, turning technical conversations into signed deals. You sit between Sales, Product and Engineering, reporting to the Head of Sales & CRO and working side‑by‑side with Account Executives across Belgium, France, the UK and beyond." That seems good. Now ensure we didn't include any boilerplate like "No recruitment agencies please." That's at end; we should remove. Also remove "📩 Interested? Send us your details and a short introduction. We'd love to hear from you." That's application instruction; remove. Now produce HTML fragment. Check for any repeated content: Ensure we didn't miss any substantive info: "You'll work on a product trusted by organizations such as Belfius, Baloise, AG Insurance, and Swiss Life." included. "More importantly, you'll join a team that's ambitious, supportive, and genuinely enjoys building great things together." included. "Regulation is driving demand: AMLR lands in July 2027, with AMLA and DORA close behind." included. "Prospects no longer want a slide about what our platform could do, they want to see their own use case running." included. "You are the person who makes that happen, in days rather than weeks, and who turns a technical conversation into a signed deal." included. "You sit between Sales, Product and Engineering. You report to the Head of Sales & CRO and work side by side with Account Executives across Belgium, France, the UK and beyond." included. Now responsibilities list: we captured all bullet points from "What You'll Do". Let's verify: - Build bespoke demo environments end to end on our JSON low-code layer, pre-loaded with realistic synthetic data - Use Claude Code and other AI tools to accelerate configuration, and maintain a reusable library of skills, agents and demo templates per segment - Act as the technical counterpart to Account Executives across the full sales cycle: capability demos, deep-dive sessions, security and architecture reviews, integration mockups - Maintain a working knowledge of the Harmoney codebase and feed prioritised pre-sales signals back to product - Set the standard for how pre-sales works at Harmoney as the function grows Yes. Requirements list: we captured: - 3+ years in pre-sales, solutions engineering, technical consulting or a comparable hybrid technical and commercial role, ideally in B2B SaaS, RegTech or financial services software - Comfortable with structured configuration (JSON, YAML, low-code) and reading code, without needing to be a full-stack developer - Hands-on experience with modern AI coding tools such as Claude Code, Cursor or Lovable - Track record of shipping demo environments