MAWM Solution Design Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must include sections only when posting has real specific content. We have:
- About Fulfillment IQ (company description) could be "About the role"? Actually "About the role" is typical but we have "Role Overview". Could map to "About the role". We'll include that.
- Responsibilities: we have "Key Responsibilities" list.
- Requirements: we have "Must Have" list.
- Qualifications: maybe "Nice to Have" could be qualifications? But they said use Qualifications heading if content. We could treat "Nice to Have" as Qualifications or Skills? Might be better to have "Qualifications" for Must Have? Actually Must Have are requirements. Qualifications could be Nice to Have. We'll decide.
- Skills: maybe not separate; we could combine.
- Benefits: we have perks list.
- Pay: Salary Range given.
- Schedule: not given (no schedule specifics). So omit Schedule.
Also include maybe "Location" info? Not a heading; could be in a short p.
We must not repeat job title as heading. Do not put Job ID etc.
We must preserve all substantive info; remove boilerplate like AI use, accommodations, privacy, EEO, etc. Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content:
Job Title: MAWM Solution Design Lead (not heading)
Job Location: San Antonio, TX / Atlanta, GA, United States (Onsite/Hybrid) OR fully remote across the United States for exceptional candidates.
Job Type: Full-time, Permanent
Hiring Timeline: Immediate
Reporting Line: Co-Founder, COO & SVP Enterprise Systems
Travel Expectations: Up to 25-35% travel, based on customer requirements.
Existing Vacancy: Yes
Application Deadline: Open until Filled
Salary Range: 125K - 150K USD per year (negotiable)
About Fulfillment IQ (FIQ): description paragraph.
Role Overview: paragraph.
Mandate: bullet list? Actually it's a paragraph with multiple sentences each starting with a verb. Could treat as list? Might be better as - each mandate item.
Must Have: list of bullet points.
Nice to Have: list.
Key Responsibilities: list.
What Success Looks Like in the First 90 Days: subpoints 30,60,90 days.
Key Performance Indicators (KPIs): list.
Why You'll Love Working Here: paragraphs with subheadings? Actually they have bullet points: Work That Matters, Career Growth That Matters, Flexibility to Thrive, We Celebrate Impact, A Collaborative Culture. Then "Perks you'll appreciate:" list.
Additional Perks: list.
We need to include Benefits section: we have perks list (health, dental, PTO, retirement, professional growth, flexible work, equipment allowances, internet reimbursements, business travel coverage, ESOP, team events, meetups, company offsites). We'll combine.
We must not include boilerplate: AI use, accommodations, privacy, EEO, Learn More About Us (website, LinkedIn, Spotify, YouTube). Remove those.
Now craft HTML.
We'll start with a
for location and job type etc? Could combine metadata into a short
. Eg:
Location: San Antonio, TX / Atlanta, GA (Onsite/Hybrid) or fully remote US. Full‑time, Permanent. Reports to Co‑Founder, COO & SVP Enterprise Systems. Travel up to 25‑35%. Salary: $125K‑$150K USD per year (negotiable).
Then sections:
About the role
Role Overview: ... plus About Fulfillment IQ? Actually About the role could include Role Overview and company description. We'll put both.
Better:
About the role
Fulfillment IQ is a supply chain engineering and transformation company ... (the About Fulfillment IQ paragraph).
Role Overview: Many of our enterprise clients ... (the Role Overview paragraph).
Then Responsibilities
- ... each responsibility from Key Responsibilities list.
Then Requirements
- ... Must Have items.
Then Qualifications
- ... Nice to Have items.
Then Benefits
- ... perks list.
Then Pay
Salary Range: $125K‑$150K USD per year (negotiable).
We could also include Success and KPIs maybe as separate sections? But they said prefer few substantive sections over many thin ones. Could incorporate Success and KPIs into Responsibilities or maybe as separate sections if they have substantive content. But we already have many sections; maybe we can add a section "Performance Expectations" but not in list of allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. So we need to fit Success and KPIs somewhere else, maybe within Responsibilities or Requirements? Could add a under Responsibilities about success metrics? But better to incorporate into Responsibilities as additional bullet points? However they are not responsibilities but success metrics. Could put them under Responsibilities as part of what success looks like? Might be okay.
Alternatively we could create a section "Skills" for success metrics? Not ideal.
Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Success and KPIs into Responsibilities as additional bullet points under a subheading? But we cannot add extra headings. We could just add a
after Responsibilities describing success and KPIs. That would preserve info without extra heading.
Similarly, we could put "What Success Looks Like..." and KPIs as a paragraph under Responsibilities.
Thus final HTML:
Location: San Antonio, TX / Atlanta, GA (Onsite/Hybrid) or fully remote US. Full‑time, Permanent. Reports to Co‑Founder, COO & SVP Enterprise Systems. Travel up to 25‑35%. Salary: $125K‑$150K USD per year (negotiable).
About the role
Fulfillment IQ is a supply chain engineering and transformation company that helps brands, retailers, and 3PLs design, build, and scale high‑performance logistics operations. We work at the intersection of strategy, operations, and technology where we solve complex, real‑world problems across warehouse design, automation, order management, transportation, and end‑to‑end supply chain execution. Our teams combine deep domain expertise with strong technical capability, delivering outcomes through consulting, systems implementation, and proprietary platforms that accelerate time‑to‑value and reduce delivery risk. If you enjoy working in complex environments, partnering closely with clients, and seeing your work make a tangible impact on how global commerce moves, this is the place where your skills and judgment truly come to life.
Role Overview: Many of our enterprise clients have already made the move to Manhattan Active WM. They have a template, a few sites live, and an internal IT team that knows the system. What they need next is a senior design leader who has been through multi‑site rollouts before, who can see the operational roadblocks coming before they hit, and who can make the client's own team stronger along the way. As a Manhattan WMS Solution Design Lead, you are that person. You own solution design for Manhattan Active WM programs, drive operational conversations with warehouse and business leaders, and translate what you hear into sound, scalable designs. You bring options with clear tradeoffs rather than a single prescribed fix, and you coach the client's IT team so the capability stays with them after you leave.
Responsibilities
- Lead solution design for new site rollouts, scale‑ups, and enhancements on Manhattan Active WM programs
- Assess each facility's current‑state processes against the client's system template and identify gaps, risks, and required changes
- Facilitate business process workshops and requirement‑gathering sessions with DC operations and business teams
- Translate client requirements into multiple solution options with pros, cons, and effort estimates
- Build and present demos or proofs of concept to support client decision‑making
- Create and maintain functional specifications and solution design documentation
- Act as a primary techno‑functional point of contact for operations and IT stakeholders on assigned initiatives
- Train and mentor client IT team members, building their long‑term self‑sufficiency on the platform
- Partner with configuration specialists, technical teams, and testers to ensure designs are delivered as intended
- Present proposed solutions and recommendations to operational and executive stakeholders
Success in the first 90 days: 30 days – ramp up on the client's Manhattan Active WM template, live sites, rollout roadmap, and key stakeholders; build working relationships with the client's IT team and DC operations leaders. 60 days – lead design for your first site rollout or enhancement workstream; deliver the first options‑based solution proposal, with clear tradeoffs, to the client; begin structured knowledge transfer with the client's IT team. 90 days – fully own solution design for assigned sites and initiatives; be recognized by the client as a trusted operational and design advisor; demonstrate a repeatable approach for surfacing process risks early in each rollout. Key performance indicators include site rollout and design milestone adherence, number of options‑based solution proposals delivered (vs. single‑fix recommendations), client satisfaction with design quality, workshops, and presentations, process risks identified and resolved before go‑live, growth in client team self‑sufficiency on Manhattan Active WM, and quality and completeness of functional specifications and design documentation.
Requirements
- 5‑10 years of recent, hands‑on experience on Manhattan WMS products, including Manhattan Active WM and prior experience on an earlier Manhattan platform (WMOS or SCALE)
- Solution design or design lead experience on Manhattan WMS programs (design role; background focused only on testing or support not a fit)
- Experience across multiple DCs or sites, ideally supporting a phased, multi‑site rollout rather than a single‑site implementation
- Strong operational understanding of warehouse processes: receiving, put‑away, replenishment, waving and allocation, picking, packing, and shipping
- Proven ability to lead business process workshops, stakeholder interviews, and requirement‑gathering sessions with operations and IT audiences
- Track record of anticipating and resolving business process transformation challenges, not just configuring a system
- Ability to create functional specifications, solution design documents, and fit‑gap analyses
- Ability to provide effort estimates and implementation recommendations, and to present options and tradeoffs to operational and executive stakeholders
- Experience coaching or training client team members on Manhattan design and configuration
- Excellent client‑facing communication and presentation skills
- Based in the United States and able to travel 25‑35%
Qualifications
- Prior experience at Manhattan Associates or a leading Manhattan implementation partner
- CPG, Grocery, or other high‑volume Retail DC experience
for location and job type etc? Could combine metadata into a short
. Eg:
Location: San Antonio, TX / Atlanta, GA (Onsite/Hybrid) or fully remote US. Full‑time, Permanent. Reports to Co‑Founder, COO & SVP Enterprise Systems. Travel up to 25‑35%. Salary: $125K‑$150K USD per year (negotiable).
Then sections:About the role
Role Overview: ... plus About Fulfillment IQ? Actually About the role could include Role Overview and company description. We'll put both. Better:
About the role
Fulfillment IQ is a supply chain engineering and transformation company ... (the About Fulfillment IQ paragraph).
Role Overview: Many of our enterprise clients ... (the Role Overview paragraph).
ThenResponsibilities
- ... each responsibility from Key Responsibilities list.
Requirements
- ... Must Have items.
Qualifications
- ... Nice to Have items.
Benefits
- ... perks list.
Pay
Salary Range: $125K‑$150K USD per year (negotiable).
We could also include Success and KPIs maybe as separate sections? But they said prefer few substantive sections over many thin ones. Could incorporate Success and KPIs into Responsibilities or maybe as separate sections if they have substantive content. But we already have many sections; maybe we can add a section "Performance Expectations" but not in list of allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. So we need to fit Success and KPIs somewhere else, maybe within Responsibilities or Requirements? Could add aunder Responsibilities about success metrics? But better to incorporate into Responsibilities as additional bullet points? However they are not responsibilities but success metrics. Could put them under Responsibilities as part of what success looks like? Might be okay. Alternatively we could create a section "Skills" for success metrics? Not ideal. Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Success and KPIs into Responsibilities as additional bullet points under a subheading? But we cannot add extra headings. We could just add a
after Responsibilities describing success and KPIs. That would preserve info without extra heading. Similarly, we could put "What Success Looks Like..." and KPIs as a paragraph under Responsibilities. Thus final HTML:
Location: San Antonio, TX / Atlanta, GA (Onsite/Hybrid) or fully remote US. Full‑time, Permanent. Reports to Co‑Founder, COO & SVP Enterprise Systems. Travel up to 25‑35%. Salary: $125K‑$150K USD per year (negotiable).
About the role
Fulfillment IQ is a supply chain engineering and transformation company that helps brands, retailers, and 3PLs design, build, and scale high‑performance logistics operations. We work at the intersection of strategy, operations, and technology where we solve complex, real‑world problems across warehouse design, automation, order management, transportation, and end‑to‑end supply chain execution. Our teams combine deep domain expertise with strong technical capability, delivering outcomes through consulting, systems implementation, and proprietary platforms that accelerate time‑to‑value and reduce delivery risk. If you enjoy working in complex environments, partnering closely with clients, and seeing your work make a tangible impact on how global commerce moves, this is the place where your skills and judgment truly come to life.
Role Overview: Many of our enterprise clients have already made the move to Manhattan Active WM. They have a template, a few sites live, and an internal IT team that knows the system. What they need next is a senior design leader who has been through multi‑site rollouts before, who can see the operational roadblocks coming before they hit, and who can make the client's own team stronger along the way. As a Manhattan WMS Solution Design Lead, you are that person. You own solution design for Manhattan Active WM programs, drive operational conversations with warehouse and business leaders, and translate what you hear into sound, scalable designs. You bring options with clear tradeoffs rather than a single prescribed fix, and you coach the client's IT team so the capability stays with them after you leave.
Responsibilities
- Lead solution design for new site rollouts, scale‑ups, and enhancements on Manhattan Active WM programs
- Assess each facility's current‑state processes against the client's system template and identify gaps, risks, and required changes
- Facilitate business process workshops and requirement‑gathering sessions with DC operations and business teams
- Translate client requirements into multiple solution options with pros, cons, and effort estimates
- Build and present demos or proofs of concept to support client decision‑making
- Create and maintain functional specifications and solution design documentation
- Act as a primary techno‑functional point of contact for operations and IT stakeholders on assigned initiatives
- Train and mentor client IT team members, building their long‑term self‑sufficiency on the platform
- Partner with configuration specialists, technical teams, and testers to ensure designs are delivered as intended
- Present proposed solutions and recommendations to operational and executive stakeholders
Success in the first 90 days: 30 days – ramp up on the client's Manhattan Active WM template, live sites, rollout roadmap, and key stakeholders; build working relationships with the client's IT team and DC operations leaders. 60 days – lead design for your first site rollout or enhancement workstream; deliver the first options‑based solution proposal, with clear tradeoffs, to the client; begin structured knowledge transfer with the client's IT team. 90 days – fully own solution design for assigned sites and initiatives; be recognized by the client as a trusted operational and design advisor; demonstrate a repeatable approach for surfacing process risks early in each rollout. Key performance indicators include site rollout and design milestone adherence, number of options‑based solution proposals delivered (vs. single‑fix recommendations), client satisfaction with design quality, workshops, and presentations, process risks identified and resolved before go‑live, growth in client team self‑sufficiency on Manhattan Active WM, and quality and completeness of functional specifications and design documentation.
Requirements
- 5‑10 years of recent, hands‑on experience on Manhattan WMS products, including Manhattan Active WM and prior experience on an earlier Manhattan platform (WMOS or SCALE)
- Solution design or design lead experience on Manhattan WMS programs (design role; background focused only on testing or support not a fit)
- Experience across multiple DCs or sites, ideally supporting a phased, multi‑site rollout rather than a single‑site implementation
- Strong operational understanding of warehouse processes: receiving, put‑away, replenishment, waving and allocation, picking, packing, and shipping
- Proven ability to lead business process workshops, stakeholder interviews, and requirement‑gathering sessions with operations and IT audiences
- Track record of anticipating and resolving business process transformation challenges, not just configuring a system
- Ability to create functional specifications, solution design documents, and fit‑gap analyses
- Ability to provide effort estimates and implementation recommendations, and to present options and tradeoffs to operational and executive stakeholders
- Experience coaching or training client team members on Manhattan design and configuration
- Excellent client‑facing communication and presentation skills
- Based in the United States and able to travel 25‑35%
Qualifications
- Prior experience at Manhattan Associates or a leading Manhattan implementation partner
- CPG, Grocery, or other high‑volume Retail DC experience