Solutions Consultant, Mirakl Connect

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Mirakl" but we should not repeat job title. The instructions: 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. We need to parse the posting and extract sections: About Mirakl (company description) maybe not needed? The role description: "Your Impact As a Solutions Consultant on the Mirakl Connect team..." then "What You'll Do at Mirakl" list of duties. Then "Qualifications" list. Then "KPIs / Success Metrics". Then "Below you will find the reasonably estimated annual On-Target Earnings (OTE) range for this role." Then "In addition, Mirakl offers a wide range of competitive benefits including health, dental, 401(k) match plan, commuter, and PTO." Then OTE Pay Range $82,500—$104,500 USD. We need sections: maybe "About the role" (could combine Your Impact and What You'll Do). "Responsibilities" (the bullet list). "Qualifications" (the bullet list). "Pay" (OTE range). "Benefits" (list of benefits). Possibly "KPIs / Success Metrics" could be a section but not in the prescribed headings list; but we could treat as "Requirements"? Actually KPIs are not requirements but success metrics. The instruction says use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About the role (overview), Responsibilities (duties), Qualifications (requirements), Benefits, Pay. Possibly also "Skills" but we have none explicit. We could include "Requirements" maybe same as Qualifications? But we have Qualifications section already. Could also include "Requirements" for KPIs? Not needed. We must not create sections with filler. So we will include sections where we have content. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

  About the role

  As a Solutions Consultant on the Mirakl Connect team, you will own the onboarding experience for customers adopting Catalog Transformer - guiding them from contract signature through launch and early value realization. As the primary post-sales partner, you'll ensure customers are successfully configured, trained, and positioned to achieve their marketplace growth goals. Beyond implementation, you'll act as a trusted advisor, helping customers understand marketplace best practices, identify expansion opportunities, and maximize the value they receive from Mirakl Connect. While the role is primarily focused on post-sales onboarding, you'll also partner with Sales on strategic opportunities and collaborate with Marketplace Operators to support customer growth across the Connect ecosystem. You'll play a key role in continuously improving our onboarding motion by refining processes, capturing customer feedback, and leveraging AI and automation to deliver a scalable, best-in-class customer experience.

  Responsibilities

  • Own the end-to-end onboarding experience for Catalog Transformer customers, from kickoff through successful launch and adoption.
  • Serve as the primary post-sales contact, building trusted relationships and ensuring customers achieve value quickly.
  • Lead onboarding sessions, implementation workshops, product demonstrations, and customer training.
  • Proactively identify risks, remove blockers, and coordinate with cross-functional teams to keep implementations on track.
  • Become a subject matter expert on Catalog Transformer, advising customers on best practices and successful implementation strategies.
  • Partner with Customer Success, Product, Support, Sales, Partnerships, and Marketplace Operators to deliver a seamless customer experience.
  • Work with Marketplace Operators to help customers identify and execute marketplace expansion opportunities.
  • Support Sales on strategic or technically complex opportunities requiring product or onboarding expertise.
  • Create and maintain onboarding playbooks, documentation, and customer enablement resources.
  • Leverage AI and automation tools (e.g. Salesforce, Dust, Claude, Make) to improve onboarding quality, documentation, and operational efficiency.
  • Capture customer feedback and continuously improve onboarding processes, reducing time-to-launch while increasing customer adoption.

  Qualifications

  • 3+ years of experience in Solutions Consulting, Customer Success, Implementation, Professional Services, or a similar customer-facing SaaS role.
  • Experience leading customer onboarding or implementation projects from kickoff through successful launch.
  • Strong project management, communication, and presentation skills.
  • Ability to manage multiple customer engagements while building trusted customer relationships.
  • Strong problem-solving skills and experience collaborating across cross-functional teams.
  • Experience working with APIs and integrations.
  • Experience leveraging AI tools to improve productivity or customer outcomes is a plus.
  • Entrepreneurial mindset with a passion for delivering exceptional customer experiences in a fast-paced environment.

  Pay

  OTE Pay Range $82,500—$104,500 USD

  Benefits

  • health
  • dental
  • 401(k) match plan
  • commuter
  • PTO
  We might also include a short paragraph about Mirakl? The instruction says do not repeat job title as heading; but we could include a brief "About Mirakl" as part of About the role? Probably not needed. The "About Mirakl" is company description; could be considered "About the role"? Might be okay to include as a paragraph under About the role. But we already have a paragraph describing role impact. Could also add a brief company overview as part of About the role. However we must preserve all substantive information; we should not drop the Mirakl description. The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include the Mirakl description somewhere. Could add a short paragraph before the role impact, maybe as part of About the role section. The About the role section could contain both company overview and role impact. That seems fine. Thus modify About the role paragraph to include company description: "Founded in 2012, Mirakl has been at the forefront of marketplace innovation..." etc. Then role impact. Let's craft:

  About the role

  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. As a Solutions Consultant on the Mirakl Connect team, you will own the onboarding experience for customers adopting Catalog Transformer - guiding them from contract signature through launch and early value realization. As the primary post-sales partner, you'll ensure customers are successfully configured, trained, and positioned to achieve their marketplace growth goals. Beyond implementation, you'll act as a trusted advisor, helping customers understand marketplace best practices, identify expansion opportunities, and maximize the value they receive from Mirakl Connect. While the role is primarily focused on post-sales onboarding, you'll also partner with Sales on strategic opportunities and collaborate with Marketplace Operators to support customer growth across the Connect ecosystem. You'll play a key role in continuously improving our onboarding motion by refining processes, capturing customer feedback, and leveraging AI and automation to deliver a scalable, best-in-class customer experience.

  That covers company description and role impact. Now ensure we didn't include any boilerplate like "We welcome collaborators..." etc. That's near the end after OTE. That is basically EEO/diversity statement; we should remove. Also remove lines about data processing, AI guidelines, etc. Also remove "Below you will find the reasonably estimated annual On-Target Earnings (OTE) range for this role." We can keep the OTE line but maybe we need to keep the sentence? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The sentence "Below you will find the reasonably estimated annual On-Target Earnings (OTE) range for this role." is somewhat meta but still substantive? It's describing where the pay range is. Could be considered boilerplate but it's part of the compensation description. Might keep it as part of Pay section. However we already have Pay section with the range; we could include that sentence as part of the Pay paragraph. But it's not necessary; we could just give the range. The instruction says preserve ALL substantive information; the sentence is substantive? It's describing that below you will find the range. If we omit it, we are not losing any substantive info about compensation; we still give the range. The sentence is just a label; I'd say it's okay to omit as it's not adding new info. But to be safe, we could include it as part of Pay paragraph: "Below you will find the reasonably estimated annual On-Target Earnings (OTE) range for this role. OTE Pay Range $82,500—$104,500 USD". That preserves. Similarly for benefits: "In addition, Mirakl offers a wide range of competitive benefits including health, dental, 401(k) match plan, commuter, and PTO." We can keep that sentence plus list. Thus Benefits section:

  In addition, Mirakl offers a wide range of competitive benefits including health, dental, 401(k) match plan, commuter, and PTO.

  plus maybe a list? But we already have list; we could keep sentence and list. However that may be redundant. Better to keep sentence as intro and then list. Thus Benefits section:

  Benefits

  In addition, Mirakl offers a wide range of competitive benefits including health, dental, 401(k) match plan, commuter, and PTO.

  • health
  • dental>
  • 401(k) match plan
  • commuter
  • PTO
  But note we repeated health etc. Might be duplication. Could just keep list and omit sentence. The instruction says preserve ALL substantive information; the sentence is substantive (describes benefits). If we drop it, we lose that sentence. But we could incorporate the sentence into the list? Not ideal.