Head of E-Commerce

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, no invented details. Remove boilerplate like EEO, equal opportunity, etc. Also remove application instructions, navigation, cookie, legal, etc. Also remove duplicated lines. We need to parse the job posting. Let's extract sections: - About the role: The first paragraph describing Javvy mission and the opportunity. Likely we can put under "About the role". Should be prose. - Responsibilities: The bullet list under "What You’ll Own" and subsequent paragraphs about leading web team, owning ecommerce launches, etc. So we can list responsibilities. - Requirements/Qualifications/Skills: The "You’re a Fit If…" list includes experience, etc. Also "Strongly Preferred:" list. Also "What Success Looks Like:" maybe more expectations but could be part of responsibilities? Might be considered qualifications? The instruction: Use headings for Requirements, Qualifications, Skills. We need to decide where to put content. Likely combine experience and skills under Requirements or Qualifications. But we need to avoid thin sections. Perhaps we can have one "Requirements" section that includes both required and preferred qualifications, and maybe a "Skills" section for specific skills? However we must not create sections with filler. We need to see if we have enough content for each. We have: - About the role: description. - Responsibilities: many bullet points. - Requirements: "You’re a Fit If…" list (5+ years experience, etc.) plus "Strongly Preferred:" list. - Skills: maybe we can extract specific skills like CRO, web design, UI/UX judgment, Shopify experience, managing team, project management, analytics, technical fluency, written communication, etc. But those are already in requirements. We could combine Requirements and Qualifications into one section, but the instruction says use headings for each if content exists. We could have "Requirements" and "Qualifications" both with content, but we need to avoid duplication. Perhaps we treat "Requirements" as mandatory experience, and "Qualifications" as preferred/experience. Or "Skills" as specific abilities. Let's extract: Mandatory (You’re a Fit If…): - 5+ years of relevant experience in ecommerce, CRO, digital product, ecommerce operations, or related field. - Meaningful experience at a high-growth DTC or ecommerce company. - Demonstrated record of improving ecommerce conversion rates and customer experiences. - Strong visual, web-design, and UI/UX judgment. - Experience identifying conversion opportunities and managing A/B tests from hypothesis through implementation and analysis. - Strong Shopify experience and understanding of products, variants, offers, discounts, collections, checkout and third-party integrations. - Experience directly managing or leading developers, designers, CRO specialists, and QA contributors. - Strong project-management skills, including scoping, prioritization, dependency management, risk management, and follow-through. - Ability to use ecommerce and product analytics to investigate questions and make recommendations. - Enough technical fluency to work effectively with engineers and understand how ecommerce systems interact. - Excellent written communication, sound judgment, and ability to turn ambiguity into clear plans. - Based in the United States and able to work Eastern Time hours. Strongly Preferred: - Experience with subscription commerce and platforms such as Recharge, Skio, Stay.ai, Loop, or Smartrr. - Experience with Webflow or another high-volume ecommerce CMS. - Experience with Amplitude, PostHog, Mixpanel, or similar product-analytics tools. - Familiarity with ecommerce tracking, pixels, event properties, and order-level validation. What Success Looks Like (first 90 days) could be considered expectations but could be placed under Responsibilities or maybe a separate section "Expectations". But we only have headings list; we could put under Responsibilities as part of what you'll achieve. Benefits: The posting includes "Why This Role Rocks:" with bullet list: Competitive Salary, 100% Company-Paid Health, Dental, Vision & Life Insurance for employees (Family coverage available at employee cost), 401(k) Retirement Plan, Parental Leave, Free Access to Javvy Products, Career Growth Opportunities, Collaborative, Fast-Paced Start-Up Environment. Also maybe other benefits. Pay: Not explicitly stated; only "Competitive Salary" but no numbers. The instruction says do NOT create Pay section unless posting actually states them. It says "Competitive Salary" is a statement but not a specific figure. Is that enough? It says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive Salary" is vague but not exactly placeholder like those. However it's still not a specific number. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "states them" meaning actual content. Does "Competitive Salary" count as stating pay? It's a statement but not a specific amount. Might be considered stating that there is a competitive salary, which is a benefit. But the instruction about placeholder text includes "commensurate with experience", "not specified", etc. "Competitive Salary" is similar to vague but not exactly those. Safer to not create Pay section because it's not a specific figure. We'll omit Pay. Schedule: Not mentioned; no schedule details. So omit Schedule. Benefits: We have concrete benefits: Health, Dental, Vision & Life Insurance (100% company-paid), 401(k), Parental Leave, Free Access to Javvy Products, Career Growth Opportunities, Collaborative Fast-Paced Start-Up Environment. Also maybe "Competitive Salary" could be considered benefit but we omitted Pay. We'll include Benefits section. Now we need to format. We'll output:

About the role

... prose ...

Responsibilities

• ... each bullet ...

Requirements

• ... mandatory ...

Qualifications

• ... preferred ...

Skills

Maybe we can combine some skills not covered? But we already covered many in requirements. Could we create Skills section for specific abilities like CRO, web design, UI/UX judgment, Shopify, project management, analytics, technical fluency, written communication? However those are already in requirements. To avoid duplication, maybe we skip Skills section. But we need to ensure we include all substantive info. If we put all mandatory and preferred under Requirements and Qualifications, we cover them. The skills are included there. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Check if any other sections like "What Success Looks Like" could be part of Responsibilities or maybe a separate section "Expectations". But we don't have a heading for Expectations; we could incorporate into Responsibilities as bullet points about first 90 days achievements. However the instruction: "Prefer a few substantive sections over many thin ones." So we can incorporate that into Responsibilities. Now we need to write prose for About the role: combine first paragraphs. Let's extract About the role text: "Javvy is on a mission to set a new standard for café favorites with better-for-you beverages that are craveable, convenient, and without compromise. Positioned at the intersection of café culture, convenience, and functional nutrition, we’re reimagining the drinks people buy every day — proving you don’t have to compromise between great taste and quality ingredients. What began as a cult-favorite DTC brand has rapidly scaled into an omnichannel business, now expanding into major retail while building a loyal community around better-for-you café favorites. The Opportunity: Javvy is looking for a highly capable Head of E-Commerce to own and continuously improve our direct-to-consumer ecommerce experience. Your primary mandate will be improving conversion (CRO), web design, and UI/UX across Javvy's Website, Landing Pages, Funnels, And Other Digital Touchpoints. This is an ecommerce product, CRO, operations, and execution leadership role - not primarily a paid media or brand marketing position. You will directly manage Javvy's web team across development, design, CRO, and QA. You will own the ecommerce roadmap, turn company priorities and customer insights into well-executed initiatives, and ensure projects are properly designed, launched, measured, and improved. You will also partner closely with Marketing, Retention, Retail, Analytics, and other teams that own their respective channels. Initially, you will work closely with our CTO to learn Javvy's customers, products, systems, and decision-making principles. As you build context and demonstrate sound judgment, you will take ownership of an increasing number of day-to-day ecommerce decisions." We can put that as prose. Now Responsibilities: list from "What You’ll Own:" and subsequent paragraphs. Let's extract bullet points: From "What You’ll Own: CRO, Web Design, and UI/UX": - Your first priority will be improving the performance and quality of Javvy's ecommerce experience. - Own the CRO roadmap across landing pages, product pages, offers, funnels, navigation, cart, checkout, upsells, and other key customer touchpoints. - Identify conversion opportunities using customer behavior, funnel data, analytics, user feedback, and qualitative insights. - Turn opportunities into clear hypotheses, designs, tests, and implementation plans. - Lead the continuous improvement of intuitive, persuasive, mobile-first ecommerce experiences. - Establish a high standard for web design, UI consistency, usability, messaging hierarchy, and customer clarity. - Manage A/B tests from prioritization and implementation through QA, analysis, and decision-making. - Bring recommendations and proposed decisions - not just dashboards or raw data - to leadership. - You do not need to personally design every page, but you must have strong visual and UX judgment. - You should be able to recognize weak design, unclear messaging, unnecessary friction, and missed conversion opportunities - and lead the team toward a better solution. Then "Lead the Web Team and Own Execution": - You will be responsible for turning business priorities and CRO opportunities into organized, high-quality execution. - Directly manage the web team's priorities, workload, performance, and operating cadence. - Translate ideas, data, and cross-functional requests into well-scoped projects with clear requirements, owners, dependencies, timelines, and acceptance criteria. - Determine what should be prioritized, what should wait, and what additional information is needed. - Identify missing requirements and downstream implications before work is already underway. - Remove blockers, adapt plans as priorities change, and hold the team accountable for communication, quality, and follow-through. - Ensure projects move from idea through design, development, QA, launch, and post-launch validation. - Improve the team's processes, documentation, templates, and quality standards over time. Then "Own E-Commerce Launches, Systems, and Operations": - You will own the operational complexity behind ecommerce launches and the systems supporting them. - Coordinate new products, flavors, offers, formula changes, and product-version transitions from planning through post-launch monitoring. - Maintain launch playbooks covering Shopify, landing pages, product assets, pricing, subscriptions, shipping, international experiences, upsells, tracking, and other dependencies. - Ensure product IDs, SKUs, UPCs, GTINs, product mappings, audiences, and versions are accurate across relevant systems. - Coordinate QA, test orders, launch readiness, go-live sequencing, and post-launch verification. - Own routine configuration, audits, data hygiene, and vendor follow-up across platforms such as Shopify, Recharge, Webflow, KnoCommerce, Bazaarvoice, Amplitude, and PostHog. - Become independently proficient in unfamiliar systems and take operational ownership of them. -