Business Value Consultant

We need to output HTML fragment with sections: About the role? Actually we need to reformat the job posting into clean semantic HTML. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and decide which sections to include. The posting includes: - About Mirakl (company description) - Mirakl in Numbers - Our Values - This role requires candidates to be onsite in our Boston, MA or New York, NY office 4 days a week, with approximately 20% travel. - The Team You'll Join (description) - Your Impact (list of bullet points) - What You'll Bring to the Role (Experience, Skills, Tools Used) - OTE Pay Range - Benefits mention - Additional sections: "We welcome collaborators..." etc (maybe fluff) - Recruitment privacy notice etc (boilerplate to remove) - AI guidelines etc (boilerplate) We need to produce sections: maybe About the role (company description?), Responsibilities (Your Impact), Requirements/Qualifications (Experience, Skills), Benefits, Pay, Schedule. We must not create sections with filler. So we need to see if we have concrete content for each. - About the role: Could be the description of the role (The Team You'll Join, Your Impact). Could be "About the role" heading with prose summarizing role. The posting includes "The Team You'll Join" and "Your Impact". We could combine into About the role section. - Responsibilities: Could be the bullet list under "Your Impact". Those are responsibilities. - Requirements/Qualifications: Could be "What You'll Bring to the Role" which includes Experience, Skills, Tools Used. Could split into Requirements (experience) and Qualifications (skills). But we can combine into one section maybe "Requirements". However guidelines say we can use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content. - Benefits: The posting mentions "Mirakl offers a wide range of competitive benefits including health, dental, 401(k) match plan, commuter, and PTO." That's specific enough to create a Benefits section. - Pay: OTE Pay Range: $97,500 USD - $123,500 USD. That's specific, so we can create Pay section. - Schedule: The posting says "This role requires candidates to be onsite in our Boston, MA or New York, NY office 4 days a week, with approximately 20% travel." That's schedule info (onsite 4 days a week, 20% travel). So we can create Schedule section. We also have "About Mirakl" and "Mirakl in Numbers" and "Our Values". Those are company info, not role-specific. Could be placed under "About the role"? Might be considered "About the company". But guidelines only list certain headings; we could still include a section like "About Mirakl" but not in the list? 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 suggests those as examples. It says "include a section ONLY when the posting has real, specific content for it". So we could include a section like "About Mirakl" if we want, but it's not required. However we might want to keep it concise; maybe we can incorporate company description into About the role section. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from the posting, but we can reformat. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the recruitment privacy notice, AI guidelines, etc. Also "We welcome collaborators..." maybe not boilerplate but it's fluff; but it's substantive? It's generic. Might be considered filler; but we could keep it as part of About the role? It says "We welcome collaborators with their diverse perspectives and experiences to power us forward. These often far exceed conventional job requirements and help us create a culture of continuous learning. If you’re ready to join a global leader powering digital transformation for 450+ of the world’s most innovative retailers and B2B organizations." That's somewhat fluff but still part of posting. Might be okay to keep as prose. We need to output only HTML fragment. Let's structure:

  About the role

  ... combine company description, team, impact, maybe values?

  But we need to keep details: About Mirakl (founded 2012, etc), Mirakl in Numbers, Our Values, The Team You'll Join, Your Impact (bullet list), What You'll Bring to the Role (Experience, Skills, Tools Used), OTE Pay Range, Benefits, Schedule. We could break into multiple sections: About the role (company overview), Responsibilities (Your Impact), Requirements (Experience), Qualifications (Skills), Benefits, Pay, Schedule. But we must avoid thin sections. Let's see if each has enough content. - About the role: Could include company description, numbers, values, team description. That's substantive. - Responsibilities: The bullet list under Your Impact (7 items). Good. - Requirements: Experience bullet points (2-5 years experience, ideally at top-tier consulting, etc). That's substantive. - Qualifications: Skills bullet list (Commercial acumen, etc). That's substantive. - Benefits: health, dental, 401(k) match, commuter, PTO. Good. - Pay: OTE range. Good. - Schedule: onsite 4 days a week, 20% travel. Good. We also have Tools Used list (Excel, PowerPoint, AI tooling, etc). Could be part of Skills or Qualifications. Might be better to put under Skills. We need to use
  • for any list of duties/requirements/benefits. So for Responsibilities, Requirements, Qualifications, Benefits, Tools Used maybe. We need to use

    for prose. We must not repeat job title as heading. Not needed. We must not put Job ID/requisition numbers as headings. None present. We must remove boilerplate: recruitment privacy notice, AI guidelines, etc. Also maybe the line "We welcome collaborators..." is not boilerplate but could be considered fluff; but we can keep as prose. Let's extract content. First, About Mirakl paragraph: "Founded in 2012, Mirakl has been at the forefront of marketplace innovation, empowering every business to compete in the platform economy. Today, Mirakl’s operating system combines an enterprise marketplace solution (Mirakl Platform) that enables retailers and B2B organizations to launch, scale, and operate marketplaces and dropship, AI-powered multichannel selling (Mirakl Connect), retail media (Mirakl Ads) and an agentic commerce infrastructure (Mirakl Nexus). With dual headquarters in Boston and Paris, Mirakl helps a global ecosystem of 450+ marketplaces (B2C and B2B) and a network of over 100k third-party marketplace sellers. Brands like Macy’s, Decathlon, Carrefour, Asos, and Airbus Helicopters use Mirakl to grow their businesses in new and remarkable ways.For more information, visit www.mirakl.com." Then Mirakl in Numbers: "🗓️ Founded in 2012 | Member of French Tech Next40👥 750+ employees in 9 offices worldwide: Paris, Barcelona, Bordeaux, Boston, London, Munich, New York, Sydney, Tokyo" Our Values: "Working at Mirakl means accelerating your career alongside ambitious, passionate, and supportive colleagues. We're proud of the diversity of backgrounds, perspectives, and experiences that make our teams unique.Our 5 values guide how we collaborate:💡 Work Hard Together: Teamwork and collaboration are the foundation of our success🏆 Get Things Done: We prioritize action and efficiency for impactful results🚀 Go Above & Beyond: We tackle challenges proactively and always aim for excellence🎓 Succeed Through Expertise: Knowledge sharing and continuous learning are core to our culture🤝 Satisfy & Empower Clients: We're committed to our clients' success" Then "This role requires candidates to be onsite in our Boston, MA or New York, NY office 4 days a week, with approximately 20% travel." Then "The Team You'll Join" paragraph. Then "Your Impact" bullet list (7 items). Then "What You'll Bring to the Role" with subheadings Experience, Skills, Tools Used. Experience bullet points: - 2–5 years of experience, ideally at a top-tier management consulting firm (MBB or Big Four), or in a strategy / operational strategy role at a retailer, brand or technology company. We are looking for a consultant who has owned end-to-end workstreams with limited manager oversight - Direct experience presenting to, and being challenged by, VP-level stakeholders and above & owning that relationship rather than supporting someone else who did - Curiosity about, or working knowledge of, marketplace, ecommerce and B2B commerce models - Bachelor's degree required - Nice to have: exposure to marketplaces, ecommerce, retail or CPG; an MBA or advanced degree in business, finance or economics Skills bullet points: - Commercial acumen: managing and communicating with VP and C-level stakeholders - Commercial instinct: you understand what moves a deal forward, and can tell the difference between an interesting analysis and a useful one - Presence under pressure: you read a room, tailor the value story to each stakeholder, and hold your position when it's challenged - The consultant toolkit: Excel, PowerPoint and AI - Financial modeling: you can build a model from scratch in excel, explain and defend every assumption in it, and update it live when the facts change - Executive storytelling: decks that are simple, clear and memorable. Always lead with the “what’s the so-what” - AI fluency: you use AI to scale your output without reducing its quality. We expect the bar to be higher when AI is involved - Business expertise: frameworks and commercial models - Structured problem solving: hypothesis-driven and framework-fluent. You bring clarity out of ambiguity, move forward when the data is incomplete, and form a recommendation rather than describing what you found - Transferable expertise: ability to easily move between industries and use cases, understanding quickly what is critical to know, in order to add value in any scenario Tools Used: - Excel for financial modeling, scenario and sensitivity analysis, and business case logic - PowerPoint for executive storytelling - AI tooling (Dust, Claude) for research, data aggregation, analysis and first drafts - Mirakl platform data, industry benchmarks and market research - Salesforce - Google Suite, Slack Then OTE Pay Range: "$