Software Engineer, Communities

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Tin Can" description, then "The Role", then "What You’ll Do", "What We’re Looking For", "Why Join Tin Can", and "Compensation Range". According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map sections accordingly. The posting includes "About Tin Can" (company description). That could be considered "About the role"? Actually "About the role" is typical heading for role description. But we have "About Tin Can" describing company. Could map to "About the role"? Might be better to use "About the role" for the description of the role/tin can? However we have "The Role" heading. Could treat that as "About the role". The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. We need to include a section only when posting has real, specific content for it. So we need to decide which sections we have content for. We have: - About Tin Can (company overview) -> could be "About the role"? Not exactly. Maybe we can treat as "About the role" (description of role and company). Or we could skip "About the role" and instead use "Responsibilities" for "What You’ll Do". "Requirements" for "What We’re Looking For". "Benefits" for "Why Join Tin Can"? Actually "Why Join Tin Can" is more about mission/benefits. Could map to "Benefits". Pay: we have compensation range. So we can have Pay section. Schedule: not mentioned, so omit. We also have "Qualifications" maybe same as Requirements. We'll just have Requirements. We need to avoid repeating job title as heading. The job title is "Software Engineer, Communities". Not to be used as heading. We need to use

• for any list of duties/requirements/benefits. So we need to convert bullet points into lists. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. The posting contains duplicated sections (the "What You’ll Do", etc repeated twice). We need to deduplicate. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First part: About Tin Can paragraph: "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)." Then "The Role" paragraph: "A Tin Can is only as good as the list of people a kid can call. When a whole class or block gets Tin Cans together, the phone arrives with friends already on it. That’s Communities: hundreds of schools, neighborhoods, and groups have already bought Tin Cans together, and it’s one of the fastest-growing parts of the company. We’re looking for a Software Engineer to own the product side of it end to end. Today a community directory is set up by hand: an organizer collects families in a form, our team turns it into a roster, and every kid in it can call every other kid. You’ll make that something organizers and parents do themselves, down to the rule in our call-routing service that decides whether a community call goes through. You’ll sit with the Head of Communities and the community ops team, alongside the engineers who own our app, voice platform, and account portal. Every contact you make callable is a child a parent trusted us with, and you’ll go as deep as that responsibility requires." Then "What You’ll Do" bullet list (multiple lines). Let's capture: - Own the community portal, API, and ops tooling (Next.js, TypeScript on Lambda, Postgres) — what organizers use to run a directory and what our team uses behind community orders - Make directories self-serve — join requests parents can send, approvals that take effect immediately, and creation that doesn’t need a ticket to our team - Own the rule that decides whether a community call connects — who can call whom, opt-in versus opt-out, and what happens the second a parent removes their family - Capture each family’s school and neighborhood: pick the datasets worth acquiring, build the pipeline that ingests them, and let a parent choose from the result, so we can see which communities are a few families from critical mass and show parents what’s nearby - Build what comes after directories — the features that unlock once a community reaches real density, what a kid can do on a Tin Can only because the other kids on the block have one too - Handle children’s data the way parents assume we do — what we store, who can see it, and what happens when a family leaves - Instrument what you ship — alarms, tests, and the data that shows whether kids in dense communities call more Then "What We’re Looking For" bullet list: - 4+ years building and running web services, with real ownership of what you shipped - Strong TypeScript across the stack — you’ve built and run an API in production (ours run on AWS Lambda with Postgres) and can ship a Next.js front end a PTA volunteer can use - You can design a relational model for membership, permissions, and audit history, and you think about who leaves before who joins - You treat authorization as a product feature, not a checkbox — who can reach a child, how fast “no” takes effect, and how you’d prove it - Fluency using AI as a multiplier across prototyping, build, and analysis; this is how we work, not a nice-to-have - A reliability mindset — you instrument what you ship, and you’d rather catch a broken directory with an alert than an email from a PTA president - A clear communicator who writes things down, because you want the whole team to understand the systems you build - A collaborative, low-ego approach — everyone here sweeps the floor - Bonus: trust-and-safety or permissions systems; a kids’ product where you learned what COPPA asks; Flutter, Shopify, or Retool; or curiosity about telephony Then "Why Join Tin Can" paragraph(s): - "We’re building tech that protects childhood: We’re on a quest to give kids a more analog childhood — one with real conversations, real connection, and way less screen time. No doomscrolling, data mining, or dopamine traps — just a simpler, better way for kids to stay in touch. This is a rare opportunity to build something that truly matters." - "You’ll own what only works because there are other Tin Cans: Communities is how a phone arrives with friends already on it, and this is the first engineering role dedicated to it. Directories are the start; you’ll have a seat at the table for what unlocks once a community reaches real density." - "Small, high-trust team: Every company says “team,” but at Tin Can it means something different. We’re a small, mission-driven group that genuinely has each other’s backs — professionally and personally. You’ll be joining a tight-knit crew where your ideas and instincts matter from day one." - "Room to explore, not just execute: You’ll have the space to challenge assumptions, solve hard problems, and build systems that reflect our values of trust, simplicity, and care. If you’re excited by the idea of making sure every kid who picks up a Tin Can has friends on the other end — and building what gets better every time a neighbor gets one too — we’d love to meet you." Then "Compensation Range: $145K - $175K Software Engineer, Communities". Actually the line: "Compensation Range: $145K - $175K Software Engineer, Communities". Probably compensation range is $145K - $175K. The job title repeated but we should not repeat as heading. We'll just include compensation in Pay section. We need to avoid duplication: The posting repeats the "What You’ll Do", "What We’re Looking For", "Why Join Tin Can", "Compensation Range". We'll keep only one copy. Now map to headings: - About the role: Could combine About Tin Can + The Role? Or we could have two sections: About the role (company description) and Responsibilities (What You’ll Do). But instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have content for: - About the role: maybe we can put the company description and role overview under "About the role". That seems appropriate. - Responsibilities: "What You’ll Do" list. - Requirements: "What We’reLooking For" list (core requirements). Could also separate Qualifications but we can just use Requirements. - Benefits: "Why Join Tin Can" (mission, team, exploration). Could be Benefits. - Pay: compensation range. We should not include Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". Not applicable. Now format: Use

  for each section heading. Then content: For prose, use

  . For lists, use

  • . We need to avoid repeating job title as heading. Not using. Now produce HTML. Let's craft:

    About the role

    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).

    A Tin Can is only as good as the list of people a kid can call. When a whole class or block gets Tin Cans together, the phone arrives with friends already on it. That’s Communities: hundreds of schools, neighborhoods, and groups have already bought Tin Cans together, and it’s one of the fastest-growing parts of the company. We’re looking for a Software Engineer to own the product side of it end to end. Today a community directory is set up by hand: an organizer collects families in a form, our team turns it into a roster, and every kid in it can call every other kid. You’ll make that something organizers and parents do themselves, down to the rule in our call-routing service that decides whether a community call goes through. You’ll sit with the Head of Communities and the community ops team, alongside the engineers who own our app, voice platform, and account portal. Every contact you make callable is a child a parent trusted us with, and you’ll go as deep as that responsibility requires.

    Then Responsibilities:

    Responsibilities

    • Own the community portal, API, and ops tooling (Next.js, TypeScript on Lambda, Postgres) — what organizers use to run a directory and what our team uses behind community orders
    • Make directories self-serve — join requests parents can send, approvals that take effect immediately, and creation that doesn’t need a ticket to our team
    • Own the rule that decides whether a community call connects — who can call whom, opt-in versus opt-out, and what happens the second a parent removes their family
    • Capture each family’s school and neighborhood: pick the datasets worth acquiring, build the pipeline that ingests them, and let a parent choose from the result, so we can see which communities are a few