Implementation Consultant / Functional Analyst

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. Must preserve all substantive info. We need to parse the posting. Let's extract content: Intro: "You've lived inside a KYC process. Now come build better ones. If you've ever tracked client onboarding across seven spreadsheets, chased a UBO structure through three registries, or quietly hoped nobody would audit the folder called final_v4_DEF, you already understand our customers better than most consultants ever will. Harmoney is the compliance orchestrator for the whole counterparty lifecycle: onboarding, monitoring, offboarding, in one auditable flow. €10M Series A raised, and Belfius, Baloise, AG Insurance and Swiss Life already run on us. Your job is to turn what compliance teams need into software that actually does it. 🎯 The job, in one line You sit between customer, product and engineering, and you're the reason a live implementation actually works. 🚀" That's about the role. Then "What you'll do" bullet list: - Sit with compliance and risk teams, understand their real process, and translate it into user stories that engineers can build. - Configure the Harmoney platform to fit their KYC and AML workflows. Configuration, not custom code. - Own testing and validation before the customer signs off. If it breaks in production, you'd rather have found it first. - Push back when a customer asks for something that should be a product feature instead of a one-off. Scalable beats bespoke. - Write the user guides and knowledge base articles, so the answer exists before the question does. 😬 Then "The honest part" paragraph about juggling multiple implementations, etc. Then "You'll thrive here if you" bullet list: - Have hands-on experience in KYC and AML. You've done the work yourself: client onboarding, screening, EDD, alert handling. Compliance officer, analyst, MLRO team, onboarding specialist. This one is non-negotiable. - Have 2+ years as a business, functional, product or delivery analyst, or as an implementation consultant. - Like turning ambiguity into structure, and can hold your ground in a requirements workshop. - Are comfortable in Jira and Confluence. - Speak fluent English plus native-level Dutch or French. - Take ownership without waiting to be asked. 🌟 Then "Nice to have" bullet list: - Experience with TPRM (third party risk management). - REST APIs, Postman or browser DevTools. - Software testing and QA. - AI tools you actually use to work faster. Then "What you get" bullet list: - Salary scale C1 (3.000 - 5.300 eur gross/month), plus a Tesla Model Y or mobility budget, 32 days of annual leave, MacBook and smartphone - A flat, down-to-earth team with approachable leadership and real ownership - Complex, real-world problems and a modern stack, so your brain stays busy - Hybrid from our Ghent office, flexible on location for the right person Then "Interested? Send us your details and a short introduction. We'd love to hear your story. No recruitment agencies please." We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. About the role: The intro paragraph(s) describing role: "You've lived inside a KYC process..." and "The job, in one line..." That fits. Responsibilities: The "What you'll do" list. Requirements: Could be the "You'll thrive here if you" list (mandatory). Also maybe "Nice to have" could be Skills? But we have separate Skills section. Usually Requirements = mandatory qualifications. Qualifications could be education? Not present. Could treat "You'll thrive here if you" as Requirements (mandatory). Qualifications maybe not present; we could omit if no specific content. Skills: Could be the "Nice to have" list (skills). Or we could put Jira, Confluence, etc as Skills. But we need to follow instruction: include a section only when posting has real specific content. So we need to decide. We have mandatory experience: hands-on KYC/AML, 2+ years as business/functional/product/delivery analyst or implementation consultant, like turning ambiguity, comfortable in Jira/Confluence, speak fluent English + native-level Dutch/French, take ownership. That's more like Requirements/Qualifications. We could map: - About the role: intro. - Responsibilities: "What you'll do". - Requirements: mandatory experience list. - Qualifications: maybe education? Not present, so omit. - Skills: Nice to have list (TPRM, REST APIs, Postman, DevTools, software testing/QA, AI tools). - Benefits: "What you get" list (salary, Tesla/mobility budget, leave, MacBook/smartphone, flat team, complex problems, hybrid). - Pay: Could be part of Benefits but we have separate Pay section if salary specified. The posting includes salary scale. So we should have Pay section with salary details. Benefits could be other non-salary perks. - Schedule: Hybrid from Ghent office, flexible on location. That's schedule info. Thus we need sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not include Qualifications if no content. We must not repeat job title. We must not include Job ID etc. We must not include boilerplate like EEO etc (none present). We must output only HTML fragment. We need to use

for section headings. Use

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

  for prose. Thus:

  About the role

  ...

  Responsibilities:

  Responsibilities

  • ...
  ...
  Requirements:

  Requirements

  • ...
  ...
  Skills:

  Skills

  • ...
  ...
  Benefits:

  Benefits

  • ...
  ...
  Pay:

  Pay

  Salary scale C1 (3.000 - 5.300 eur gross/month), plus a Tesla Model Y or mobility budget

  maybe include that as Pay. But note Tesla/mobility budget also appears in Benefits; we need to avoid duplication. The "What you get" includes salary, Tesla/mobility, leave, MacBook/smartphone, flat team, complex problems, hybrid. We could split: Pay = salary scale; Benefits = other items (Tesla/mobility budget, leave, MacBook/smartphone, flat team, complex problems, hybrid). However Tesla/mobility could be considered benefit. But we need to avoid duplication. Let's allocate: Pay: salary scale only. Benefits: Tesla Model Y or mobility budget, 32 days of annual leave, MacBook and smartphone, flat down-to-earth team with approachable leadership and real ownership, complex real-world problems and a modern stack, hybrid from Ghent office flexible on location for right person. Schedule: maybe we already included hybrid in Benefits; but schedule section could be about hybrid/location. However we already used hybrid in Benefits. Could move hybrid to Schedule and keep other benefits. Let's decide: Schedule: Hybrid from our Ghent office, flexible on location for the right person. Benefits: Tesla Model Y or mobility budget, 32 days annual leave, MacBook and smartphone, flat down-to-earth team, complex real-world problems and modern stack. Thus we avoid duplication. Now we need to ensure we preserve all substantive information. Let's list all pieces: Intro paragraph: "You've lived inside a KYC process. Now come build better ones. If you've ever tracked client onboarding across seven spreadsheets, chased a UBO structure through three registries, or quietly hoped nobody would audit the folder called final_v4_DEF, you already understand our customers better than most consultants ever will. Harmoney is the compliance orchestrator for the whole counterparty lifecycle: onboarding, monitoring, offboarding, in one auditable flow. €10M Series A raised, and Belfius, Baloise, AG Insurance and Swiss Life already run on us. Your job is to turn what compliance teams need into software that actually does it. 🎯 The job, in one line You sit between customer, product and engineering, and you're the reason a live implementation actually works. 🚀" We need to keep that as prose. Responsibilities list: - Sit with compliance and risk teams, understand their real process, and translate it into user stories that engineers can build. - Configure the Harmoney platform to fit their KYC and AML workflows. Configuration, not custom code. - Own testing and validation before the customer signs off. If it breaks in production, you'd rather have found it first. - Push back when a customer asks for something that should be a product feature instead of a one-off. Scalable beats bespoke. - Write the user guides and knowledge base articles, so the answer exists before the question does. 😬 Requirements list (mandatory): - Have hands-on experience in KYC and AML. You've done the work yourself: client onboarding, screening, EDD, alert handling. Compliance officer, analyst, MLRO team, onboarding specialist. This one is non-negotiable. - Have 2+ years as a business, functional, product or delivery analyst, or as an implementation consultant. - Like turning ambiguity into structure, and can hold your ground in a requirements workshop. - Are comfortable in Jira and Confluence. - Speak fluent English plus native-level Dutch or French. - Take ownership without waiting to be asked. 🌟 Skills list (nice to have): - Experience with TPRM (third party risk management). - REST APIs, Postman or browser DevTools. - Software testing and QA. - AI tools you actually use to work faster. Benefits list: - Tesla Model Y or mobility budget - 32 days of annual leave - MacBook and smartphone - A flat, down-to-earth team with approachable leadership and real ownership - Complex, real-world problems and a modern stack, so your brain stays busy Pay: - Salary scale C1 (3.000 - 5.300 eur gross/month) Schedule: - Hybrid from our Ghent office, flexible on location for the right person We also have the closing line: "Interested? Send us your details and a short introduction. We'd love to hear your story. No recruitment agencies please." This is application instruction; we must remove application instructions per rules. So we drop that. Now we need to output HTML fragment with headings and content. We must not include any extra text outside HTML. Let's craft. Be careful to escape any special characters? Not needed. We'll produce:

  About the role

  You've lived inside a KYC process. Now come build better ones. If you've ever tracked client onboarding across seven spreadsheets, chased a UBO structure through three registries, or quietly hoped nobody would audit the folder called final_v4_DEF, you already understand our customers better than most consultants ever will. Harmoney is the compliance orchestrator for the whole counterparty lifecycle: onboarding, monitoring, offboarding, in one auditable flow. €10M Series A raised, and Belfius, Baloise, AG Insurance and Swiss Life already run on us. Your job is to turn what compliance teams need into software that actually does it. 🎯 The job, in one line You sit between customer, product and engineering, and you're the reason a live implementation actually works. 🚀