Pre-Sales Solutions Consultant, Mirakl Connect
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 decide which sections to include: The posting includes "About Mirakl" (company description), "Your Impact" (role description), "What You'll Do at Mirakl" (responsibilities), "Qualifications", "KPIs / Success Metrics", "OTE Pay Range", benefits mention, schedule (4 days on-site per week). Also location: Boston office, permanent position, 4 days on-site per week.
We should not include sections like "About the role" if we have "Your Impact" and "What You'll Do". Could combine? But we must follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
- About the role: Could be the "Your Impact" section describing role impact. Or we could treat "About Mirakl" as company description not needed? The instruction says use headings for those specific labels; we can include only those with real content.
We have content for:
- About the role: description of role impact (Your Impact). Could be used.
- Responsibilities: "What You'll Do at Mirakl" bullet list.
- Requirements: Qualifications section.
- Skills: maybe not separate; but we could include skills within Qualifications? The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Skills? But we need to follow headings; we can include Qualifications as Requirements? Actually Qualifications is separate heading. We could have Qualifications and maybe Skills not needed if content overlaps.
- Benefits: posting mentions "Mirakl offers a wide range of competitive benefits including health, dental, 401(k) match plan, commuter, and PTO." So we have benefits content.
- Pay: OTE Pay Range $82,500—$104,500 USD.
- Schedule: "This is a permanent position based in our Boston office, with 4 days on-site per week." So schedule: 4 days on-site per week, permanent, Boston.
We also have location info; could be part of Schedule or a separate paragraph.
We must not include filler like "commensurate with experience". Not present.
We need to remove boilerplate: the "About Mirakl" company description maybe not needed as a heading? Could be included as a brief intro paragraph before sections? The instruction says output only HTML fragment; we can include a
for company overview if we want, but not as a heading. It's substantive. We'll keep it as a
before sections.
Also "Mirakl in Numbers" etc maybe not needed; but it's substantive about company size. Could keep as
but maybe not needed. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep all substantive info, but we can format as paragraphs or lists. The "Mirakl in Numbers" includes founded year, employees, offices, values list. That's substantive. Could be included as a
or
. But we need to avoid creating sections unless real content. We could include a brief paragraph summarizing that info. However the instruction says prefer a few substantive sections over many thin ones. So maybe we keep only the main sections (About the role, Responsibilities, Requirements, Benefits, Pay, Schedule) and embed other details like company overview within About the role paragraph or as a preceding . But we must preserve all substantive info; we cannot drop details like employee count, offices, values, etc. So we need to include them somewhere.
We could include a
before sections that contains the company overview: Founded 2012, mission, dual HQ, employees, offices, values list, etc. That preserves info.
Then sections:
About the role
with paragraph from "Your Impact": description of role impact.
Responsibilities
with - list from "What You'll Do at Mirakl".
Requirements
with - list from Qualifications.
Maybe also include KPIs/Success Metrics as a subsection? Could be part of Responsibilities or Requirements? It's about success metrics; could be its own section but not in prescribed headings. Could embed within Responsibilities as a list? But better to add a section "Performance Metrics" not in list; but instruction says prefer few substantive sections; we could add a
Success Metrics
though not in the given examples but maybe allowed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we can add other headings if needed. But to keep few sections, maybe incorporate KPIs into Responsibilities or Requirements? Might be okay to add a separate section for KPIs.
Benefits: we have benefits.
Pay: OTE Pay Range.
Schedule: location and on-site days.
We also have "This is a permanent position based in our Boston office, with 4 days on-site per week." That's schedule.
We also have "Find out more about our benefits here." link; we can drop as boilerplate? It's a link to benefits; but we already have benefits summary; we can drop the link.
We also have "Below you will find the reasonably estimated annual On-Target Earnings (OTE) range for this role." That's intro to Pay; we can incorporate.
We also have "We welcome collaborators..." etc; that's fluff; maybe drop as boilerplate? It's somewhat generic; but it's substantive about culture. Could be included in About the role paragraph? Might be considered boilerplate; but it's about culture. Safer to keep as a
maybe under About the role? But we already have About the role paragraph; we could add another
after that about culture. However instruction: prefer few substantive sections; we could add a
after About the role.
We also have "As part of our recruitment process..." etc; that's legal/privacy; drop.
We also have AI guidelines; drop.
Now craft HTML.
We'll start with a
for company overview: include founding, mission, dual HQ, employees, offices, values list (maybe as
). Then About the role
with paragraph from Your Impact.
Then Responsibilities
with - each bullet from What You'll Do.
Then
Requirements
with - each bullet from Qualifications.
Then
Benefits
with listing health, dental, 401(k) match, commuter, PTO.
Then
Pay
with OTE Pay Range $82,500—$104,500 USD.
Then
Schedule
with Permanent position based in Boston office; 4 days on-site per week.
We might also include KPIs as a
Success Metrics
with - list.
But that adds another section; still okay.
We need to ensure we don't repeat content.
Let's extract bullets.
From "What You'll Do at Mirakl":
- Partner with Account Executives throughout the sales cycle to qualify opportunities, understand customer needs, and define the appropriate solution approach.
- Lead discovery sessions with prospects and customers to uncover business objectives, current processes, pain points, technical requirements, and success criteria.
- Deliver compelling, tailored product demonstrations and presentations that connect Catalog Transformer and Mirakl Connect capabilities to customer business outcomes.
- Collaborate with Sales on proposals, responses to RFPs and RFIs, proof-of-concept planning, security and technical questionnaires, and other strategic deal activities.
- Work closely with Product, Engineering, Support, Partnerships, and Marketplace Operators to validate solution feasibility and ensure a smooth customer experience.
- Support the transition from closed-won to onboarding, ensuring that customer goals, requirements, solution decisions, and success criteria are clearly documented and communicated.
- Own or support the onboarding experience for Catalog Transformer customers, from kickoff through successful launch and early adoption.
- Create and maintain sales and onboarding assets, including discovery guides, demo flows, solution templates, playbooks, case studies, and customer-facing documentation.
- Capture customer and prospect feedback to influence product priorities, positioning, competitive insights, and go-to-market strategy.
- Leverage AI and automation tools, such as Salesforce, Dust, Claude, and Make, to improve sales effectiveness, documentation quality, solution consistency, and operational efficiency.
- Contribute to continuous improvement of the Solutions Consulting and onboarding motions by sharing best practices, analyzing performance, and reducing friction across the customer journey.
That's many bullets; we keep all.
Qualifications bullets:
- 3+ years of experience in Solutions Consulting, Sales Engineering, Pre-Sales, Implementation, Professional Services, Customer Success, or a similar customer-facing SaaS role.
- Strong presentation and product demonstration skills, with the ability to tailor a message to different audiences and levels of seniority.
- Experience partnering closely with Account Executives and contributing to opportunity strategy, qualification, proposals, or RFP responses.
- Ability to manage multiple opportunities and customer engagements while maintaining a high level of organization and follow-through.
- Strong problem-solving skills and the ability to collaborate effectively across Sales, Product, Engineering, Support, and Partnerships.
- Experience working with Shopify, APIs, integrations, data flows, or other technical concepts relevant to SaaS implementations.
- Experience in marketplaces, ecommerce, retail, catalog management, product data, or digital transformation is a plus.
- Experience leveraging AI tools to improve productivity, sales effectiveness, or customer outcomes is a plus.
KPIs / Success Metrics bullets:
- Discovery, demo, and proposal effectiveness
- Successful handoff from Sales to Onboarding
- Time-to-Launch
- Customer Adoption and Activation
- Time-to-First Value
- Customer Satisfaction (CSAT)
- Quality and reuse of sales and onboarding assets
- Process improvement and operational efficiency
Now company overview 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
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 decide which sections to include: The posting includes "About Mirakl" (company description), "Your Impact" (role description), "What You'll Do at Mirakl" (responsibilities), "Qualifications", "KPIs / Success Metrics", "OTE Pay Range", benefits mention, schedule (4 days on-site per week). Also location: Boston office, permanent position, 4 days on-site per week. We should not include sections like "About the role" if we have "Your Impact" and "What You'll Do". Could combine? But we must follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. - About the role: Could be the "Your Impact" section describing role impact. Or we could treat "About Mirakl" as company description not needed? The instruction says use headings for those specific labels; we can include only those with real content. We have content for: - About the role: description of role impact (Your Impact). Could be used. - Responsibilities: "What You'll Do at Mirakl" bullet list. - Requirements: Qualifications section. - Skills: maybe not separate; but we could include skills within Qualifications? The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Skills? But we need to follow headings; we can include Qualifications as Requirements? Actually Qualifications is separate heading. We could have Qualifications and maybe Skills not needed if content overlaps. - Benefits: posting mentions "Mirakl offers a wide range of competitive benefits including health, dental, 401(k) match plan, commuter, and PTO." So we have benefits content. - Pay: OTE Pay Range $82,500—$104,500 USD. - Schedule: "This is a permanent position based in our Boston office, with 4 days on-site per week." So schedule: 4 days on-site per week, permanent, Boston. We also have location info; could be part of Schedule or a separate paragraph. We must not include filler like "commensurate with experience". Not present. We need to remove boilerplate: the "About Mirakl" company description maybe not needed as a heading? Could be included as a brief intro paragraph before sections? The instruction says output only HTML fragment; we can include a
for company overview if we want, but not as a heading. It's substantive. We'll keep it as a
before sections. Also "Mirakl in Numbers" etc maybe not needed; but it's substantive about company size. Could keep as
but maybe not needed. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep all substantive info, but we can format as paragraphs or lists. The "Mirakl in Numbers" includes founded year, employees, offices, values list. That's substantive. Could be included as a
or
- . But we need to avoid creating sections unless real content. We could include a brief paragraph summarizing that info. However the instruction says prefer a few substantive sections over many thin ones. So maybe we keep only the main sections (About the role, Responsibilities, Requirements, Benefits, Pay, Schedule) and embed other details like company overview within About the role paragraph or as a preceding
- list from "What You'll Do at Mirakl".
Requirements
with- list from Qualifications.
Maybe also include KPIs/Success Metrics as a subsection? Could be part of Responsibilities or Requirements? It's about success metrics; could be its own section but not in prescribed headings. Could embed within Responsibilities as a list? But better to add a section "Performance Metrics" not in list; but instruction says prefer few substantive sections; we could add a
Success Metrics
though not in the given examples but maybe allowed? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we can add other headings if needed. But to keep few sections, maybe incorporate KPIs into Responsibilities or Requirements? Might be okay to add a separate section for KPIs. Benefits: we have benefits. Pay: OTE Pay Range. Schedule: location and on-site days. We also have "This is a permanent position based in our Boston office, with 4 days on-site per week." That's schedule. We also have "Find out more about our benefits here." link; we can drop as boilerplate? It's a link to benefits; but we already have benefits summary; we can drop the link. We also have "Below you will find the reasonably estimated annual On-Target Earnings (OTE) range for this role." That's intro to Pay; we can incorporate. We also have "We welcome collaborators..." etc; that's fluff; maybe drop as boilerplate? It's somewhat generic; but it's substantive about culture. Could be included in About the role paragraph? Might be considered boilerplate; but it's about culture. Safer to keep as a
maybe under About the role? But we already have About the role paragraph; we could add another
after that about culture. However instruction: prefer few substantive sections; we could add a
after About the role. We also have "As part of our recruitment process..." etc; that's legal/privacy; drop. We also have AI guidelines; drop. Now craft HTML. We'll start with a
for company overview: include founding, mission, dual HQ, employees, offices, values list (maybe as
- ). Then
- each bullet from What You'll Do.
Then
Requirements
with- each bullet from Qualifications.
Then
Benefits
withlisting health, dental, 401(k) match, commuter, PTO. Then
Pay
withOTE Pay Range $82,500—$104,500 USD. Then
Schedule
withPermanent position based in Boston office; 4 days on-site per week. We might also include KPIs as a
Success Metrics
with- list. But that adds another section; still okay. We need to ensure we don't repeat content. Let's extract bullets. From "What You'll Do at Mirakl": - Partner with Account Executives throughout the sales cycle to qualify opportunities, understand customer needs, and define the appropriate solution approach. - Lead discovery sessions with prospects and customers to uncover business objectives, current processes, pain points, technical requirements, and success criteria. - Deliver compelling, tailored product demonstrations and presentations that connect Catalog Transformer and Mirakl Connect capabilities to customer business outcomes. - Collaborate with Sales on proposals, responses to RFPs and RFIs, proof-of-concept planning, security and technical questionnaires, and other strategic deal activities. - Work closely with Product, Engineering, Support, Partnerships, and Marketplace Operators to validate solution feasibility and ensure a smooth customer experience. - Support the transition from closed-won to onboarding, ensuring that customer goals, requirements, solution decisions, and success criteria are clearly documented and communicated. - Own or support the onboarding experience for Catalog Transformer customers, from kickoff through successful launch and early adoption. - Create and maintain sales and onboarding assets, including discovery guides, demo flows, solution templates, playbooks, case studies, and customer-facing documentation. - Capture customer and prospect feedback to influence product priorities, positioning, competitive insights, and go-to-market strategy. - Leverage AI and automation tools, such as Salesforce, Dust, Claude, and Make, to improve sales effectiveness, documentation quality, solution consistency, and operational efficiency. - Contribute to continuous improvement of the Solutions Consulting and onboarding motions by sharing best practices, analyzing performance, and reducing friction across the customer journey. That's many bullets; we keep all. Qualifications bullets: - 3+ years of experience in Solutions Consulting, Sales Engineering, Pre-Sales, Implementation, Professional Services, Customer Success, or a similar customer-facing SaaS role. - Strong presentation and product demonstration skills, with the ability to tailor a message to different audiences and levels of seniority. - Experience partnering closely with Account Executives and contributing to opportunity strategy, qualification, proposals, or RFP responses. - Ability to manage multiple opportunities and customer engagements while maintaining a high level of organization and follow-through. - Strong problem-solving skills and the ability to collaborate effectively across Sales, Product, Engineering, Support, and Partnerships. - Experience working with Shopify, APIs, integrations, data flows, or other technical concepts relevant to SaaS implementations. - Experience in marketplaces, ecommerce, retail, catalog management, product data, or digital transformation is a plus. - Experience leveraging AI tools to improve productivity, sales effectiveness, or customer outcomes is a plus. KPIs / Success Metrics bullets: - Discovery, demo, and proposal effectiveness - Successful handoff from Sales to Onboarding - Time-to-Launch - Customer Adoption and Activation - Time-to-First Value - Customer Satisfaction (CSAT) - Quality and reuse of sales and onboarding assets - Process improvement and operational efficiency Now company overview 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
- each bullet from Qualifications.
Then
About the role
with paragraph from Your Impact. ThenResponsibilities
with - each bullet from What You'll Do.
Then
- list from Qualifications.
Maybe also include KPIs/Success Metrics as a subsection? Could be part of Responsibilities or Requirements? It's about success metrics; could be its own section but not in prescribed headings. Could embed within Responsibilities as a list? But better to add a section "Performance Metrics" not in list; but instruction says prefer few substantive sections; we could add a
. But we must preserve all substantive info; we cannot drop details like employee count, offices, values, etc. So we need to include them somewhere. We could include a
before sections that contains the company overview: Founded 2012, mission, dual HQ, employees, offices, values list, etc. That preserves info. Then sections: