Senior Shopify Developer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The headings we can use: About the role (maybe "About garden3d" etc). Responsibilities (we have). Requirements/Qualifications/Skills: we have Must-Have Competencies and Nice-to-Have Competencies. Could combine as Requirements? But we need to follow instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to those headings. We should not repeat job title. We should not include Job ID. We should drop boilerplate like application instructions, cookie/navigation/legal/EEO etc. Also remove duplicated lines. We need to preserve all substantive information.
We need to decide which sections to include: About the role (we have description about company and role). Responsibilities (we have). Requirements (maybe Must-Have Competencies). Qualifications (maybe Nice-to-Have Competencies). Skills (maybe combine? but we can keep both). Benefits (maybe not explicit; we have "How We Work" includes transparency, carbon negative, remote friendly etc. Could be considered Benefits. Pay (we have compensation). Schedule (we have contract-based remote opportunity; projects at least eight full-time weeks at 40 hours per week). So we can include Schedule.
We must not include sections with filler like "commensurate with experience". We have actual content.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
About the role
... description ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
... maybe combine? but we can leave empty? Better to include if we have content. Could put "Technical competencies" but we already have Requirements and Qualifications. Maybe Skills can be omitted if no specific. But we can include a brief summary of technical skills from Must-Have and Nice-to-Have. However we must not invent. We could put a paragraph summarizing that the role requires expertise in TypeScript, Shopify, etc. That's already in Must-Have. Might be redundant. Safer to omit Skills section if no distinct content beyond what's already covered. But instruction: Prefer a few substantive sections over many thin ones. So we could combine Must-Have and Nice-to-Have into Requirements and Qualifications. Let's do: - About the role: includes company description, role overview. - Responsibilities: list. - Requirements: Must-Have Competencies. - Qualifications: Nice-to-Have Competencies. - Benefits: How We Work (transparency, carbon negative, remote friendly, etc.) - Pay: Compensation. - Schedule: Contract-based remote opportunity; projects at least eight full-time weeks at 40 hours per week. We need to ensure we preserve all substantive information. Let's extract. About garden3d description: "We are worker owned creative collective, innovating on everything from brands and IRL communities to IoT devices and cross platform apps. We share profit, open source everything, spin out new businesses, and invest in exciting ideas through financial and/or in-kind contributions. Our client roster includes Google, Stripe, Figma, Hinge, Black Socialists in America, ACLU, Pratt, Parsons, Mozilla, The Nobel Prize, MIT, Gnosis, Etsy & Gagosian. We’re the software team behind innovative products like The Light Phone & Mill, and we operate a global, decentralized community space collective called Index Space. We think of our garden3d as collective for creative people, prioritizing a happy, talented, and diverse studio culture. We work on projects that bring value to our world, and we balance deep care for the work we do with a genuine curiosity about life outside of our jobs." Also there is "Sanctuary Computer — Development" and "XXIX — Design" sections describing sub-teams. Should we include? They are part of About the role? Could be included in About the role paragraph. We'll combine. Responsibilities list: we have bullet points after "Responsibilities will include:" with many items. Need to capture each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could use others but likely they want only those. Safer to stick to those.
How We Work: includes transparency, carbon negative, remote friendly, etc. That could be Benefits.
Important Reminders: about submitting application; that's application instructions, should be removed.
Thus we will produce sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now craft HTML.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
About the role
... combined description ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- Transparency & Ownership: profit sharing, open source, profit & loss statements shared.
- 150% Carbon Negative: studio offsets 150% of carbon used each year since 2015, certified climate neutral since 2021.
- Strong Morals: turned down $1mm–$2mm of work not meeting moral standards.
- Async & Decentralized: tools for calm communication, opt for async, maintain focus time.
- Remote Friendly: fluent in remote work, decentralized and