Mobile Product Engineer Intern (React Native)

We need to output HTML fragment with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. Content: - About Ticket Tree (company description). Could be "About the role"? Actually "About Ticket Tree" is company description. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading for description of role? But we have "About Ticket Tree" which is about company. Might map to "About the role"? Probably we should use "About the role" heading and put the company description there? Or we could treat "About Ticket Tree" as "About the role"? The instruction says use those headings as examples; we can use them if appropriate. We have content about the role: "You'll build the fan side of Ticket Tree in our React Native (Expo) app: claiming, reveals, set progress, and trading." Also "Instrumentation and data" and "Product and UI/UX". So we can have sections: About the role (company + role overview), Responsibilities (what you'll do), Requirements (what we're looking for), Qualifications (maybe same as requirements?), Skills (maybe helpful but not required), Benefits (maybe none explicit), Pay (they have Paid, $20/hr), Schedule (Boston area · hybrid · 15–20 hrs/week · Mid-October through December, with extension likely). Also location/hours. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive info. We must not create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract: Company description: "Ticket Tree is the first ticketing platform built for fun. We're building the infrastructure underneath live events: ticketing, fan identity, and everything a fan does after the game, all in one system that teams own. It starts with the stub. Every ticket becomes an evergreen digital stub that the fan keeps and trades. Stubs are issued off the scan, so nobody gets one for a night they skipped, and every claim is a named fan the operator keeps. Fans reveal their stub's tier and chase sets that bring them back for the next event. We're live with college athletics programs, combat sports promotions, and live events across the Northeast. Our engineering team is one person. You'd be the second and third." Role overview: "The role Boston area · hybrid · 15–20 hrs/week · Paid, $20/hr · Mid-October through December, with extension likely You'll build the fan side of Ticket Tree in our React Native (Expo) app: claiming, reveals, set progress, and trading. These are the screens fans spend the most time in, and right now we can't see what they do there. We're hiring for two seats, split by what you'd own: Instrumentation and data. You own the event taxonomy and the client data layer. You decide what we measure, what a well-formed event looks like, and how a fan is identified across web and mobile. By December, we should be able to answer questions about fan behavior that we currently guess at. Product and UI/UX. You own the fan-facing surfaces. Once the funnels exist, the drop-off tells you where to work, and you design and ship against real data. You'll work closely with each other and directly with the founding team. Nobody sits between you and the decisions." What we're looking for: "You've shipped something in React Native that people other than you have used. A TestFlight link counts. You think about product as much as implementation. You have opinions about why a screen is wrong. You already work with agentic tooling like Claude Code or Cursor. We route work through Linear and expect you to move fast with a model in the loop. We hire for slope. If you need to learn something to finish the work, you go learn it. Helpful but not required: PostHog or similar analytics; an interest in sports, live events, or social products; experience on a small team where you owned an outcome end to end." How we work: "We're async by default. Work is scoped in Linear, discussed in writing, and reviewed in PRs. There's one scheduled sync block per day, and the rest of your time is yours to focus. Your work will be in front of fans this season. Reliability comes first. A ticket that won't scan means somebody is stuck outside a stadium, so anything that touches event night gets tested before event night. Everywhere else, we move fast and measure everything. Part of the job is learning which is which." Process: "Apply here: https://forms.gle/N57US1KkATgpnLAL6 An interview over zoom to align you on the position and our goals as a company A 45-minute coffee chat & work session on a real issue in our codebase, either async or in-person." We need to remove application instructions (the Process section). So we drop that. We also need to drop duplicated lines? Not seeing duplicates. Now decide sections: - About the role: could include company description + role overview? Might be okay. - Responsibilities: what you'll do: building fan side, instrumentation/data, product/UI/UX, working closely, etc. - Requirements: what we're looking for (must-haves): shipped RN app used by others, think about product, opinions, work with agentic tooling, hire for slope, learn quickly. - Qualifications: maybe same as requirements? Could combine but we need to avoid thin sections. Could have Requirements and Qualifications separate if distinct. But we have "Helpful but not required:" which could be Skills or Qualifications. So we can have Requirements (must-haves) and Skills (nice-to-haves). Qualifications maybe not needed. - Benefits: none explicit besides pay? Pay is separate. - Pay: "$20/hr" - Schedule: "Boston area · hybrid · 15–20 hrs/week · Mid-October through December, with extension likely" We should not create sections with filler like "not specified". So only include if we have content. Thus sections:

About the role

with company description and maybe role overview? But role overview also includes responsibilities. Might split. Better: About the role: company description. Responsibilities: bullet list of duties: building fan side in React Native (Expo) app: claiming, reveals, set progress, trading; own event taxonomy and client data layer; decide what we measure, well-formed event, fan identification across web and mobile; answer questions about fan behavior; own fan-facing surfaces; design and ship against real data; work closely with each other and founding team. Requirements: bullet list: shipped something in React Native used by others; think about product as much as implementation; have opinions about why a screen is wrong; already work with agentic tooling like Claude Code or Cursor; hire for slope (learn quickly to finish work). Skills (Helpful but not required): bullet list: PostHog or similar analytics; interest in sports, live events, or social products; experience on a small team where you owned an outcome end to end. Pay:

$20/hr

Schedule:

Boston area · hybrid · 15–20 hrs/week · Mid-October through December, with extension likely

We should not include any extra fluff. Make sure to use

• for lists. Let's craft HTML. Check for any repeated content: we must preserve all substantive info. Did we miss any? The description about "We're live with college athletics programs, combat sports promotions, and live events across the Northeast." included in company description. Good. Also "Our engineering team is one person. You'd be the second and third." included. Also "You'll build the fan side of Ticket Tree in our React Native (Expo) app: claiming, reveals, set progress, and trading." included in responsibilities. Also "These are the screens fans spend the most time in, and right now we can't see what they do there." maybe part of responsibilities. Also "We're hiring for two seats, split by what you'd own: Instrumentation and data." included. Also "You own the event taxonomy and the client data layer. You decide what we measure, what a well-formed event looks like, and how a fan is identified across web and mobile. By December, we should be able to answer questions about fan behavior that we currently guess at." included. Also "Product and UI/UX. You own the fan-facing surfaces. Once the funnels exist, the drop-off tells you where to work, and you design and ship against real data." included. Also "You'll work closely with each other and directly with the founding team. Nobody sits between you and the decisions." included. Also "We're async by default. Work is scoped in Linear, discussed in writing, and reviewed in PRs. There's one scheduled sync block per day, and the rest of your time is yours to focus. Your work will be in front of fans this season. Reliability comes first. A ticket that won't scan means somebody is stuck outside a stadium, so anything that touches event night gets tested before event night. Everywhere else, we move fast and measure everything. Part of the job is learning which is which." This is about how we work; could be a section "How we work" but not in allowed headings. Could we include as part of Responsibilities or maybe as a separate section? The instruction only gave examples but didn't forbid other headings? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add other headings if needed? Safer to stick to those. The "How we work" content could be placed under Responsibilities or maybe under About the role? It's about work process; maybe we can include under Responsibilities as part of what you'll do (how you work). Could add a bullet about async work, Linear, PRs, sync block, reliability, testing, etc. Thus responsibilities list can include those. Now ensure we don't include any boilerplate like "Apply here", interview process. We removed. Now produce HTML. Let's construct:

  About the role

  Ticket Tree is the first ticketing platform built for fun. We're building the infrastructure underneath live events: ticketing, fan identity, and everything a fan does after the game, all in one system that teams own. It starts with the stub. Every ticket becomes an evergreen digital stub that the fan keeps and trades. Stubs are issued off the scan, so nobody gets one for a night they skipped, and every claim is a named fan the operator keeps. Fans reveal their stub's tier and chase sets that bring them back for the next event. We're live with college athletics programs, combat sports promotions, and live events across the Northeast. Our engineering team is one person. You'd be the second and third.

  Responsibilities

  • Build the fan side of Ticket Tree in our React Native (Expo) app: claiming, reveals, set progress, and trading.
  • Own the event taxonomy and the client data layer; decide what we measure, what a well‑formed event looks like, and how a fan is identified across web and mobile.
  • By December, be able to answer questions about fan behavior that we currently guess at.
  • Own the fan‑facing surfaces; use funnel drop‑off data to design and ship improvements against real data.
  • Work closely with the other hire and directly with the founding team; no intermediaries.
  • Follow an async