Project Coordinator, Market Execution
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Brief Description / ROLE SUMMARY: description of role.
- What You’ll Do: bullet list of duties (Project Execution & Tracking, Cross-Functional Coordination, Communication & Visibility, Market Execution Support, Systems & Process, Working with the Expansion Team). Could be grouped under "Responsibilities".
- What You Bring: bullet list of qualifications/experience.
- The Environment: description of environment.
- What You Get In Return: benefits list (Medical insurance options, 401(k) matching, Employee Assistance Program (EAP), Phone stipends for qualified roles, Paid company holidays, PTO, and sick leave, Company events including holiday parties and summer events). Also note "Benefits may vary by role, location, and employment status."
- WORK ENVIRONMENT: details about onsite, schedule, etc.
- About Mfused: company description.
- COMPLIANCE & LEGAL: age requirement, background check, compensation determined based on experience, location, other factors, visa sponsorship not available, equal opportunity employer.
- INTERNAL CANDIDATES: internal applicants.
We need to decide which sections to output.
We have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content.
- About the role: could be ROLE SUMMARY + brief description.
- Responsibilities: What You’ll Do (list of duties). Could also include Working with the Expansion Team as part of responsibilities.
- Requirements / Qualifications / Skills: What You Bring (experience, skills). Could split into Requirements (experience) and Qualifications/Skills (tools). But we can combine into one section maybe "Requirements". However we have multiple allowed headings; we should avoid thin sections. Perhaps combine into "Requirements" covering experience, skills, tools.
- Benefits: What You Get In Return (benefits list). Also note "Benefits may vary..." but that's okay.
- Schedule: WORK ENVIRONMENT includes schedule (Onsite Monday-Friday, occasional evening/weekend). Could create Schedule section.
- Pay: Not explicitly stated; compensation determined based on experience, location, other factors. That's vague; we should not create Pay section unless posting actually states them. It says "Compensation is determined based on experience, location, and other factors". That's not a specific number or range; it's vague. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, we have only vague statement; maybe we should not create Pay section because it's not specific. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we need specific numbers; just states them. The posting does state compensation is determined based on experience, location, and other factors. That is a statement about pay. So we could include a Pay section with that statement. However the rule also says "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "Compensation is determined based on experience, location, and other factors" is similar to "commensurate with experience". That might be considered filler/placeholder. The rule says never emit a heading followed by filler/placeholder text. So we should avoid Pay section if it's just that vague statement. So we omit Pay.
- Schedule: we have specific schedule info: Onsite at our Scottsdale, AZ office, Monday through Friday, with occasional evening or weekend work to meet business needs. That's specific enough. So we can create Schedule section.
- Benefits: we have specific list; we can create Benefits section.
- About the role: we have ROLE SUMMARY.
- Responsibilities: we have What You’ll Do.
- Requirements/Qualifications/Skills: we have What You Bring (experience, skills). Could also include "Experience in cannabis, regulated industries, manufacturing, or multi-state operations is a plus". That's a qualification.
We need to avoid duplication. Also need to remove boilerplate: EEO, equal opportunity, compliance & legal (age requirement, background check, visa sponsorship, equal opportunity). Those are legal boilerplate; we should remove them. Also internal candidates section maybe not needed? It's not boilerplate but could be considered internal hiring info; but it's not a standard heading; we could maybe include under About the role? But it's not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove COMPLIANCE & LEGAL and INTERNAL CANDIDATES sections. Also remove "About Mfused" maybe? That's company description; not boilerplate; could be part of About the role? But we already have About the role heading; we could include company description there. However the About Mfused section is separate; we could incorporate into About the role or maybe we could create a separate "About the company" but not allowed headings. So we can merge into About the role.
Thus final HTML:
About the role
[role summary + company description]
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Schedule
Onsite at our Scottsdale, AZ office, Monday through Friday, with occasional evening or weekend work to meet business needs.
We should not include Pay.
Check for duplication: Ensure we don't repeat same content.
Now extract role summary: "The Project Coordinator, Market Execution works under the direction of the Project Manager to support execution across market and business priorities spanning product, operations, supply chain, compliance, marketing, sales, and external partners. This role supports work after a market or product decision has been made. Market evaluation, licensing, and partner agreements before that decision are supported by the Project Coordinator, Expansion. This role keeps internal work moving by maintaining project plans and timelines, tracking deliverables, following up with owners, keeping documentation current, and surfacing risks or blockers early. The goal is to keep projects organized, visible, and moving without dropped handoffs or unclear next steps."
Add company description: "MFUSED is a minority-owned and operated cannabis company headquartered in Scottsdale, Arizona, with operations across multiple U.S. markets and internationally. We operate in one of the most regulated and competitive industries in the country. The expectation is simple: build high-quality products, execute at a high level, and continue raising the standard."
Combine into About the role paragraph(s). Could be two but we can combine into one
with sentences.
Now Responsibilities: list from What You’ll Do sections:
- Project Execution & Tracking:
* Maintain project plans, timelines, milestones, owners, dependencies, and deliverables
* Track work from kickoff through completion and keep project information current
* Follow up with internal owners on outstanding deliverables and action items
* Identify missed deadlines, bottlenecks, dependencies, and risks early
* Escalate blockers or decisions needed to the Project Manager
* Support multiple projects and market workstreams simultaneously as assigned by the Project Manager
- Cross-Functional Coordination:
* Track work across the internal teams the Project Manager runs projects with: product, operations, marketing, sales, compliance, and external partners
* Track cross-functional dependencies and ensure required inputs and deliverables stay moving
* Capture decisions, owners, and next steps and follow through until actions are closed
* Flag gaps between teams before they impact timelines or execution
- Communication & Visibility:
* Maintain accurate project boards, trackers, and documentation
* Prepare clear status updates covering progress, milestones, risks, and outstanding actions
* Keep boards and status current so the Project Manager can keep stakeholders and leadership informed; communicate day-to-day changes directly to task owners
* Surface risks and delays early so they can be addressed before they escalate
- Market Execution Support:
* Support execution across product launches, commercialization, and in-market initiatives assigned by the Project Manager
* Maintain project documentation, approvals, trackers, and version history as needed
* Coordinate internal meetings, reviews, samples, approvals, and other activities required to move projects forward (schedules and tracks approvals; does not grant them)
* Support launch-readiness and execution checklists across relevant functions
* Receive the handoff from the Expansion team once a market decision is made, and build the launch tracker from the Expansion team’s plan and open items
- Systems & Process:
* Maintain project boards in Asana or other project management systems
* Build out and maintain the trackers, templates, and workflows defined by the Project Manager
* Keep project structures organized, current, and easy for teams to use
* Identify recurring execution gaps and surface opportunities for process improvement
* Document the repeatable ways of working the Project Manager defines as the function grows
- Working with the Expansion Team:
* (description about two coordinators, Asana, go decision, etc.) This is more procedural; could be included as responsibility. We'll summarize: "Coordinate with the Expansion team to ensure a single Asana portfolio per market, with a handoff at the 'Go decision' milestone; Expansion owns work up to that point, Market Execution owns after; maintain cross-lane visibility without duplicating tracking."
We need to preserve all substantive information; we should not omit details. So include that description.
Now Requirements/Qualifications/Skills: from What You Bring:
- 1+ years supporting projects in a fast-moving environment (coordinator, analyst, operations, or similar)
- Experience maintaining project plans, timelines, and trackers for multiple projects at once
- Hands-on use of Asana or a similar project management tool, and strong Microsoft Office skills, especially Excel
- Comfortable following up with people at every level until an action is closed
- Clear, direct written communication; status updates that are short and useful
- High attention to detail and follow-through; nothing falls through the cracks
- Experience in cannabis, regulated industries, manufacturing, or multi-state operations is a plus
We could split into Requirements (experience) and Skills (tools). But we have only one heading allowed for Requirements, Qualifications, Skills. We could make one section "Requirements" and include all. Or we could make two sections: Requirements and Skills. But we should prefer few substantive sections over many thin ones. Having two sections might be okay if each has substantive content. However we have only one "What You Bring" block; splitting may be artificial. I'd combine into one section "Requirements". Or we could use "Qualifications" for experience and "Skills" for tools. But we need to avoid thin sections. The experience and skills are both substantive; we could have two sections: Requirements (experience) and Skills (tools). Let's see: Requirements: 1+ years supporting projects, experience maintaining project plans..., comfortable following up...,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Brief Description / ROLE SUMMARY: description of role. - What You’ll Do: bullet list of duties (Project Execution & Tracking, Cross-Functional Coordination, Communication & Visibility, Market Execution Support, Systems & Process, Working with the Expansion Team). Could be grouped under "Responsibilities". - What You Bring: bullet list of qualifications/experience. - The Environment: description of environment. - What You Get In Return: benefits list (Medical insurance options, 401(k) matching, Employee Assistance Program (EAP), Phone stipends for qualified roles, Paid company holidays, PTO, and sick leave, Company events including holiday parties and summer events). Also note "Benefits may vary by role, location, and employment status." - WORK ENVIRONMENT: details about onsite, schedule, etc. - About Mfused: company description. - COMPLIANCE & LEGAL: age requirement, background check, compensation determined based on experience, location, other factors, visa sponsorship not available, equal opportunity employer. - INTERNAL CANDIDATES: internal applicants. We need to decide which sections to output. We have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. - About the role: could be ROLE SUMMARY + brief description. - Responsibilities: What You’ll Do (list of duties). Could also include Working with the Expansion Team as part of responsibilities. - Requirements / Qualifications / Skills: What You Bring (experience, skills). Could split into Requirements (experience) and Qualifications/Skills (tools). But we can combine into one section maybe "Requirements". However we have multiple allowed headings; we should avoid thin sections. Perhaps combine into "Requirements" covering experience, skills, tools. - Benefits: What You Get In Return (benefits list). Also note "Benefits may vary..." but that's okay. - Schedule: WORK ENVIRONMENT includes schedule (Onsite Monday-Friday, occasional evening/weekend). Could create Schedule section. - Pay: Not explicitly stated; compensation determined based on experience, location, other factors. That's vague; we should not create Pay section unless posting actually states them. It says "Compensation is determined based on experience, location, and other factors". That's not a specific number or range; it's vague. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, we have only vague statement; maybe we should not create Pay section because it's not specific. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we need specific numbers; just states them. The posting does state compensation is determined based on experience, location, and other factors. That is a statement about pay. So we could include a Pay section with that statement. However the rule also says "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "Compensation is determined based on experience, location, and other factors" is similar to "commensurate with experience". That might be considered filler/placeholder. The rule says never emit a heading followed by filler/placeholder text. So we should avoid Pay section if it's just that vague statement. So we omit Pay. - Schedule: we have specific schedule info: Onsite at our Scottsdale, AZ office, Monday through Friday, with occasional evening or weekend work to meet business needs. That's specific enough. So we can create Schedule section. - Benefits: we have specific list; we can create Benefits section. - About the role: we have ROLE SUMMARY. - Responsibilities: we have What You’ll Do. - Requirements/Qualifications/Skills: we have What You Bring (experience, skills). Could also include "Experience in cannabis, regulated industries, manufacturing, or multi-state operations is a plus". That's a qualification. We need to avoid duplication. Also need to remove boilerplate: EEO, equal opportunity, compliance & legal (age requirement, background check, visa sponsorship, equal opportunity). Those are legal boilerplate; we should remove them. Also internal candidates section maybe not needed? It's not boilerplate but could be considered internal hiring info; but it's not a standard heading; we could maybe include under About the role? But it's not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove COMPLIANCE & LEGAL and INTERNAL CANDIDATES sections. Also remove "About Mfused" maybe? That's company description; not boilerplate; could be part of About the role? But we already have About the role heading; we could include company description there. However the About Mfused section is separate; we could incorporate into About the role or maybe we could create a separate "About the company" but not allowed headings. So we can merge into About the role. Thus final HTML:
About the role
[role summary + company description]
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Schedule
Onsite at our Scottsdale, AZ office, Monday through Friday, with occasional evening or weekend work to meet business needs.
We should not include Pay. Check for duplication: Ensure we don't repeat same content. Now extract role summary: "The Project Coordinator, Market Execution works under the direction of the Project Manager to support execution across market and business priorities spanning product, operations, supply chain, compliance, marketing, sales, and external partners. This role supports work after a market or product decision has been made. Market evaluation, licensing, and partner agreements before that decision are supported by the Project Coordinator, Expansion. This role keeps internal work moving by maintaining project plans and timelines, tracking deliverables, following up with owners, keeping documentation current, and surfacing risks or blockers early. The goal is to keep projects organized, visible, and moving without dropped handoffs or unclear next steps." Add company description: "MFUSED is a minority-owned and operated cannabis company headquartered in Scottsdale, Arizona, with operations across multiple U.S. markets and internationally. We operate in one of the most regulated and competitive industries in the country. The expectation is simple: build high-quality products, execute at a high level, and continue raising the standard." Combine into About the role paragraph(s). Could be twobut we can combine into one
with sentences. Now Responsibilities: list from What You’ll Do sections: - Project Execution & Tracking: * Maintain project plans, timelines, milestones, owners, dependencies, and deliverables * Track work from kickoff through completion and keep project information current * Follow up with internal owners on outstanding deliverables and action items * Identify missed deadlines, bottlenecks, dependencies, and risks early * Escalate blockers or decisions needed to the Project Manager * Support multiple projects and market workstreams simultaneously as assigned by the Project Manager - Cross-Functional Coordination: * Track work across the internal teams the Project Manager runs projects with: product, operations, marketing, sales, compliance, and external partners * Track cross-functional dependencies and ensure required inputs and deliverables stay moving * Capture decisions, owners, and next steps and follow through until actions are closed * Flag gaps between teams before they impact timelines or execution - Communication & Visibility: * Maintain accurate project boards, trackers, and documentation * Prepare clear status updates covering progress, milestones, risks, and outstanding actions * Keep boards and status current so the Project Manager can keep stakeholders and leadership informed; communicate day-to-day changes directly to task owners * Surface risks and delays early so they can be addressed before they escalate - Market Execution Support: * Support execution across product launches, commercialization, and in-market initiatives assigned by the Project Manager * Maintain project documentation, approvals, trackers, and version history as needed * Coordinate internal meetings, reviews, samples, approvals, and other activities required to move projects forward (schedules and tracks approvals; does not grant them) * Support launch-readiness and execution checklists across relevant functions * Receive the handoff from the Expansion team once a market decision is made, and build the launch tracker from the Expansion team’s plan and open items - Systems & Process: * Maintain project boards in Asana or other project management systems * Build out and maintain the trackers, templates, and workflows defined by the Project Manager * Keep project structures organized, current, and easy for teams to use * Identify recurring execution gaps and surface opportunities for process improvement * Document the repeatable ways of working the Project Manager defines as the function grows - Working with the Expansion Team: * (description about two coordinators, Asana, go decision, etc.) This is more procedural; could be included as responsibility. We'll summarize: "Coordinate with the Expansion team to ensure a single Asana portfolio per market, with a handoff at the 'Go decision' milestone; Expansion owns work up to that point, Market Execution owns after; maintain cross-lane visibility without duplicating tracking." We need to preserve all substantive information; we should not omit details. So include that description. Now Requirements/Qualifications/Skills: from What You Bring: - 1+ years supporting projects in a fast-moving environment (coordinator, analyst, operations, or similar) - Experience maintaining project plans, timelines, and trackers for multiple projects at once - Hands-on use of Asana or a similar project management tool, and strong Microsoft Office skills, especially Excel - Comfortable following up with people at every level until an action is closed - Clear, direct written communication; status updates that are short and useful - High attention to detail and follow-through; nothing falls through the cracks - Experience in cannabis, regulated industries, manufacturing, or multi-state operations is a plus We could split into Requirements (experience) and Skills (tools). But we have only one heading allowed for Requirements, Qualifications, Skills. We could make one section "Requirements" and include all. Or we could make two sections: Requirements and Skills. But we should prefer few substantive sections over many thin ones. Having two sections might be okay if each has substantive content. However we have only one "What You Bring" block; splitting may be artificial. I'd combine into one section "Requirements". Or we could use "Qualifications" for experience and "Skills" for tools. But we need to avoid thin sections. The experience and skills are both substantive; we could have two sections: Requirements (experience) and Skills (tools). Let's see: Requirements: 1+ years supporting projects, experience maintaining project plans..., comfortable following up...,