Software Engineer, Growth

We need to output HTML fragment with sections: About the role (maybe not needed? The posting includes "About Tin Can" then "The Role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need sections based on content. We have: - About Tin Can (company description) - could be "About the role"? Actually "About Tin Can" is company overview. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings if they exist. We have sections: - About Tin Can (company description) - maybe we treat as "About the role"? But that heading is for role description. However we have "The Role" heading in posting. Could map to "About the role". We'll include that. - What You'll Do (responsibilities) -> "Responsibilities" - What We're Looking For (requirements/qualifications/skills) -> could split into Requirements, Qualifications, Skills. But we need to avoid thin sections. Could combine into "Requirements" and "Skills"? The instruction: prefer a few substantive sections over many thin ones. So maybe we have "Responsibilities" and "Requirements" (including qualifications and skills). Also we have "Compensation Range" -> Pay section. We have no explicit Benefits or Schedule. So we omit those. We must not include boilerplate like EEO etc. Not present. We need to preserve all substantive information. So we need to include all details from About Tin Can, The Role, What You'll Do, What We're Looking For, Compensation Range. We must not repeat job title as heading (the page already shows it). The job title is likely "Software Engineer, Growth" or similar but not given explicitly. We'll not add. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

... company description and role overview ...

Responsibilities

• Own our Shopify storefront for acquisition — the launches and seasonal campaigns behind our biggest moments of the year
• Build our referral program end to end — invite moments, eligibility, reward fulfillment, and the identity and attribution data that makes us pay exactly once
...

Requirements

• 4+ years building and running customer-facing web applications, with real ownership of what you shipped
• Strong TypeScript across the stack — you’ve built and run APIs in production (AWS Lambda, Cloudflare Workers, etc.)
...

Maybe also include a subsection for Skills? But we can incorporate into Requirements. We also need to include Compensation Range as Pay section if present. The posting includes "Compensation Range: $145K - $175K". So we need a Pay section. Thus:

Pay

Compensation Range: $145K - $175K

We must not include schedule or benefits. We need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to extract the substantive content. Let's parse the posting: About Tin Can Tin Can is building a safer, simpler way for kids to connect — without smartphones. We’re creating screen-free, delightful devices and services that let families call the people who matter most, free from the noise of today’s digital world. We’re building a bold, authentic, nostalgic, and kinda quirky brand that resonates with folks who want something simpler & better for their kids than the tech-infused lives we’re currently living (and who have a sense of humor about it). The Role Families meet Tin Can long before they hold one — on a landing page, in a friend’s text with a referral code, in an ad that made them smile. All of it is software. When it works, a family who wanted something better for their kids finds us; when a page breaks mid-campaign or a promised referral credit never arrives, they don’t. We’re looking for a software engineer to own the systems behind how new families find Tin Can and decide to bring one home. You’ll run our Shopify storefront, build our referral program, and own the services and APIs underneath both. You’ll build the tooling that lets growth marketers launch their own landing pages, and turn the integrations behind our storefront into systems we can test, watch, and reverse. You’ll collaborate with our growth and brand teams, and work with the engineers who own our app, voice platform, and account portal. Real money and real trust run through these systems, so you’ll go as deep as that asks. What You’ll Do Own our Shopify storefront for acquisition — the launches and seasonal campaigns behind our biggest moments of the yearBuild our referral program end to end — invite moments, eligibility, reward fulfillment, and the identity and attribution data that makes us pay exactly onceOwn the integrations where an order becomes a customer, an activation, and a reward — the seams between platforms are where the money and the trust liveTurn the glue behind our campaigns into services with owners, tests, alarms, and a rollbackBuild the self-serve tooling that gets you out of the page-building business — components, templates, version control, and monitoring, so growth marketing can publish on their ownBuild the digital half of our brand campaigns with our creative team — the sites and sign-up flows behind the stories we want families to joinInstrument what you ship, with the team that owns our experimentation platform, so a launch’s numbers can be trusted What We’re Looking For 4+ years building and running customer-facing web applications, with real ownership of what you shippedStrong TypeScript across the stack — you’ve built and run APIs in production (AWS Lambda, Cloudflare Workers, etc.)You’ve built integrations across third-party platforms and think in idempotency and reconciliation, because events arrive twice, arrive late, and bring the same person back under two identitiesYou prioritize testability, observability, and reliabilityYou’ve built tools for non-engineers so the people closest to a campaign don’t wait on youPlatform judgment on commerce — what belongs inside Shopify, what belongs in a service you own, and what an integration’s credentials can reachFluency using AI as a multiplier across prototyping, build, and analysis; this is how we work, not a nice-to-haveYou’ve worked toward campaign deadlines and know how to ship something excellent when the launch date genuinely can’t move, and you can take brand and design direction and make it look rightA clear communicator who writes things down, and a collaborative, low-ego approach — everyone here sweeps the floorBonus: a referral, affiliate, or loyalty platform you integrated through its APIs, where the real work hid in identity, attribution, and reward fulfillment; Shopify theme, checkout, or app development; feature-flag or lifecycle-marketing tooling; an eye for craft; or growing a direct-to-consumer brand through real seasonal peaks Why Join Tin Can ... (we need to include? It's substantive but not under headings; maybe we can include under About the role? Actually "Why Join Tin Can" is about company benefits/culture. Could be considered as part of "About the role" or maybe we could create a "Benefits" section? But we only create Benefits if posting actually states them. The "Why Join Tin Can" includes benefits like mission, impact, small team, room to explore. That's substantive. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could create a section like "About the company" or "Why Join Tin Can". But the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join Tin Can" could map to Benefits? It's about culture and mission, not typical benefits like health insurance. But we could treat as Benefits? However the instruction says prefer a few substantive sections over many thin ones. We already have About the role, Responsibilities, Requirements, Pay. Adding Benefits may be okay if we have substantive content. The "Why Join Tin Can" includes: building tech that protects childhood, mission, rare opportunity, own the machine, small high-trust team, room to explore. That's substantive. So we could add a Benefits section with those points. But we need to check if we already covered some of that in About the role. The About the role currently includes company description and role overview. The "Why Join Tin Can" is separate motivational content. Could be included under About the role as well, but we might split. Given the instruction to prefer few sections, maybe we combine About the role and Why Join Tin Can into one About the role section (since it's about the role and company). That would be substantive. Thus About the role section will contain both the company description and the motivational points. Let's craft About the role paragraph(s) that include: - Tin Can building safer, simpler way for kids to connect without smartphones; screen-free devices; brand description. - Families meet Tin Can before holding one; software role; owning Shopify storefront, referral program, services/APIs; tooling for growth marketers; collaborate with growth/brand teams; work with engineers; real money/trust. - Why Join Tin Can: building tech that protects childhood; mission to give kids analog childhood; rare opportunity; own machine behind how families find us; small high-trust team; room to explore; challenge assumptions; solve hard problems; build systems reflecting trust, simplicity, care. We'll combine. Now Responsibilities: list each bullet from "What You’ll Do". Need to split into separate li items. The original text is a run-on sentence but we can parse. Original: "Own our Shopify storefront for acquisition — the launches and seasonal campaigns behind our biggest moments of the yearBuild our referral program end to end — invite moments, eligibility, reward fulfillment, and the identity and attribution data that makes us pay exactly onceOwn the integrations where an order becomes a customer, an activation, and a reward — the seams between platforms are where the money and the trust liveTurn the glue behind our campaigns into services with owners, tests, alarms, and a rollbackBuild the self-serve tooling that gets you out of the page-building business — components, templates, version control, and monitoring, so growth marketing can publish on their ownBuild the digital half of our brand campaigns with our creative team — the sites and sign-up flows behind the stories we want families to joinInstrument what you ship, with the team that owns our experimentation platform, so a launch’s numbers can be trusted" We need to split at each capitalized verb after a dash? Actually each begins with a verb: Own, Build, Own, Turn, Build, Build, Instrument. We'll separate. Thus li items: - Own our Shopify storefront for acquisition — the launches and seasonal campaigns behind our biggest moments of the year - Build our referral program end to end — invite moments, eligibility, reward fulfillment, and the identity and attribution data that makes us pay exactly once - Own the integrations where an order becomes a customer, an activation, and a reward — the seams between platforms are where the money and the trust live - Turn the glue behind our campaigns into services with owners, tests, alarms, and a rollback - Build the self-serve tooling that gets you out of the page‑building business — components, templates, version control, and monitoring, so growth marketing can publish on their own - Build the digital half of our brand campaigns with our creative team — the sites and sign‑up flows behind the stories we want families to join - Instrument what you ship, with the team that owns our experimentation platform, so a launch’s numbers can be trusted Now Requirements: we need to capture all bullet points from "What We’re Looking For". The text is also run-on. Let's parse. Original: "4+ years building and running customer-facing