Staff Software Engineer, DTC

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must include Pay if posting states it: yes, base salary hiring range $170,000-$182,500. Also mention final compensation based on location etc. So Pay section should include that. Schedule: The posting mentions "The Mammoth Brands' working model is in-office Tuesday, Wednesday, and Thursday." Also mentions office details. That's schedule info. So we can include Schedule section with that. Benefits: There's a Benefits And Perks section with list: Medical, dental, and vision coverage; 401k match; Equity; Flexible time off and working hours; L&D stipend; sabbatical weeks; parental leave; fun events; free products; office details (bagels Wed, lunch Thu, stocked kitchens). Also mention "We can’t quantify all of the intangible things..." but that's fluff; we can keep substantive benefits. We need to avoid repeating job title. The role is Software Engineer (Senior) for Lume storefront team. We'll not repeat as heading. We need sections: About the role (maybe we can call it About the role). Responsibilities: from "What You Will Accomplish" bullet list. Requirements: from "Required" bullet list. Qualifications? Could combine with Requirements? The instruction says use headings for those categories if content exists. We have "Required" and "Preferred" and "Bonus". Could treat Required as Requirements, Preferred as Qualifications? Or Skills? Let's map: - About the role: description of role (the paragraph about role). Could be under About the role. - Responsibilities: the "What You Will Accomplish" list. - Requirements: the "Required" bullet list. - Qualifications: maybe the "Preferred" bullet list (or we could treat as Skills). But we also have Skills heading; we could put technical skills under Skills. However the instruction says prefer few substantive sections over many thin ones. We could combine Preferred and Skills into one section called Skills (or Qualifications). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. We have content for About the role (role description). Responsibilities (list). Requirements (list). Preferred (list) could go under Qualifications or Skills. We have also specific skills like "Headless Shopify on React Router", "Strong JavaScript/TypeScript", etc. Those are in Required. Preferred includes extra tech like Custom Shopify Apps, Recharge, LoyaltyLion, Cloudflare, GTM, Optimizely, AI tooling, DTC experience. Those could be Skills. Thus we can have: - About the role: paragraph describing role. - Responsibilities: list of accomplishments. - Requirements: list of required experience. - Skills: list of preferred/bonus skills (maybe also include some from required? but we already have required). We'll put preferred/bonus under Skills. - Benefits: list. - Pay: salary range. - Schedule: in-office days. We must not include sections with filler. All have content. Now we need to strip boilerplate: remove About Mammoth Brands intro, About The Team, etc? Actually we need to preserve ALL substantive information. The About Mammoth Brands and About The Team are substantive? They describe company and team. But the instruction says we should reformat a job posting into clean HTML. Likely we should include About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. The company overview might be considered not needed for the job posting? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Mammoth Brands and About The Team are substantive but maybe not required for the job posting? However they are part of the posting. The instruction about headings only includes certain headings; we could include a section like "About the company" but not in allowed headings list. Since only those headings are allowed, we must fit content into those headings or drop it? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings for sections. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples given are those. Safer to stick to those headings and put relevant content under them. Company overview could go under About the role? Not ideal but maybe we can include a brief paragraph about company under About the role? The About the role heading is for role description; we could incorporate company context there. However we must preserve all substantive information; we can include company info in a paragraph under About the role before responsibilities. That would be okay. Similarly About The Team could be included under About the role or maybe under Skills? Better to include under About the role as context. Thus we will produce:

About the role

[company overview + team description + role description]

Then responsibilities list. Then requirements list. Then skills list (preferred/bonus). Then benefits list. Then pay paragraph. Then schedule paragraph. We must not include any markdown fences. Now craft content. About the role paragraph: combine Mammoth Brands description, team description, role description. Mammoth Brands description: "Mammoth Brands (formerly Harry’s Inc.) is the modern CPG company behind brands Harry’s, Flamingo, Lume, Mando, and Coterie. We’re building a new model—and home—brands, founders, and talent looking to solve unmet needs, improve peoples’ lives, and ultimately challenge the status quo. Our mission is to “Create Things People Like More.” ... We got our start in 2013 when our co-founders created Harry's. ... Today, Mammoth Brands is a growing portfolio of brands and the largest CPG company built in the last 20 years. Even as we grow, we take extra care to maintain the small, scrappy, entrepreneurial culture that helped to get us where we are today: to create a company that people like more, that better serves its customers, employees, and community. As a company, we’re also committed to making a positive impact and have donated over $20 million through our network of nonprofit partners to date. We build brands that move fast and think big — and we hire people who are curious about AI, willing to experiment with it in their day-to-day work, and excited to accelerate what's possible. We prioritize giving our team the tools, training, and space to build real fluency, so you grow alongside the technology and help shape how we use it." Team description: "The Lume & Mando technology team builds and runs the digital commerce experience for two of the fastest-growing brands in the Mammoth portfolio. We own the headless Shopify storefronts end to end — the React Router/Hydrogen applications our customers shop on, the subscription and loyalty experiences that keep them coming back, and the edge infrastructure that serves it all. We are a small, high-leverage team operating in a long-tail SaaS ecosystem: rather than building everything ourselves, we integrate best-in-class platforms and write the code that makes them work as one coherent experience. That means the engineering here is genuinely full-stack and genuinely commercial — the work you ship shows up in conversion, retention, and revenue within days, not quarters." Role description: "We’re looking for a Software Engineer to join the Lume storefront team as a senior member. This is a hands-on, senior individual contributor role for an engineer who is sought out as a domain expert, structures and breaks down project work, and delivers end-to-end solutions on a small team. You’ll own moderately complex problem areas across our headless Shopify architecture — storefront performance, subscription flows, loyalty, experimentation, and the integrations that tie them together. You’ll set the technical direction in those areas, raise the quality bar for everyone working in them, and translate business needs into what we build. This role reports to the Lume Head of Technology and partners daily with Product, Growth, Retention, Creative, and Analytics." We can combine into a paragraph or multiple paragraphs. Use

for prose. Now responsibilities: list from "What You Will Accomplish". Each bullet as

. List: - Lead projects end to end. Structure and break down work on storefront initiatives, define the technical tasks needed to hit team objectives, and deliver solutions. - Own the quality bar. Deliver secure, testable, maintainable, low-defect, efficient work that is well designed and well documented. - Drive technical decisions in a complex domain. Weigh other engineers' points of view against business requirements and synthesize the best solution, not the loudest one. - Build consensus. Harmonize discordant technical views and lead the resolution of contentious issues — across engineering and with cross-functional partners. - Create the things that make others faster. Produce exemplars, frameworks, shared components, runbooks, and technical documentation that raise the ceiling for everyone working in the codebase. - Debug across the stack. Identify and correct defects—not just your own—across multiple technologies, from the Remix application and edge layer through third-party platform integrations. - Communicate to align. Structure technical communication and documentation that achieves alignment on decisions of broad scope across codebases, projects, and business functions. - Map business needs to technology. Influence the business processes and product decisions within the Lume domain, not just the code that implements them. - Grow the people around you. Actively share knowledge, create the structures and processes that make sharing routine, and coach less experienced engineers. Now requirements list from "Required": - Substantial professional experience building and operating production e-commerce applications, with a track record of independently delivering projects on time in a live, revenue-generating environment. - Headless Shopify on React Router. Deep, hands-on experience is a must — Storefront API, Remix data loading and routing patterns, caching strategy, and the realities of running a headless storefront at scale. Shopify Hydrogen experience is important. - Strong JavaScript/TypeScript, modern React, and front-end performance fundamentals (Core Web Vitals, rendering strategy, bundle discipline). - Experience integrating third-party SaaS platforms via APIs and webhooks — including the unglamorous parts: idempotency, retries, rate limits, data reconciliation, and graceful degradation when a vendor is down. - Fluency in the practices that keep a storefront stable: testing, code review, observability, incident response, and releasing to production without impacting performance or reliability. - The ability to communicate a clear technical point of view in a group, understand the views of others, and commit to the team’s decision. Now skills list from "Preferred" and maybe "Bonus". We'll combine. Preferred: - Custom Shopify Apps: Experience designing, building, and maintaining custom or private Shopify apps — Admin and Storefront GraphQL APIs, OAuth and webhook handling, app extensions, Shopify Functions and checkout extensibility — plus the operational side of keeping an app healthy as Shopify's API versions turn over. - Bonus if you've had to decide when a problem warrants a custom app versus an off-the-shelf one. - Recharge for subscriptions — subscription lifecycle, billing cadence, and customer portal experiences. - LoyaltyLion for loyalty programs. - Cloudflare for headless app hosting — Workers, caching and cache invalidation, edge configuration, and WAF. - Google Tag Manager and the broader client-side measurement stack, including consent and data-quality considerations. - Optimizely or comparable experimentation platforms, and comfort designing tests that produce trustworthy results. - Experience