Fullstack Developer
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can adapt headings to match content. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? It says e.g., meaning examples. Probably we should use those headings where appropriate. We need to include sections only when posting has real specific content. We have compensation: $140,000-$160,000, competitive startup comp, meaningful equity upside. Also benefits: health, dental, vision, 401(k), wellness stipend, monthly dogfooding budget. So we can have Pay section with salary range, Benefits section with benefits. No schedule info. So we omit Schedule.
We need to avoid repeating job title as heading. So no heading for Fullstack Developer.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove "How to Apply" and the equal opportunity employer line. Also remove "Location: Dallas, TX" maybe? It's metadata; we can fold minor metadata into a short
or drop it. Probably include location in a short paragraph.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
Location: Dallas, TX
maybe.
Then About the role
with description of role (maybe combine About Rare Candy and The Role). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
About the role: include company description and role overview.
Responsibilities: list of duties (What You'll Do, A Day in Your Life, etc.)
Requirements: maybe "What You'll Need to Thrive Here" and "You Might Be a Fit If" combined.
Qualifications: maybe "What Success Looks Like"? Not sure. But we can treat Qualifications as experience/education? Not given. Could skip if no specific qualifications. But we need to avoid empty headings. So only include sections with real content.
We have Pay: salary range.
Benefits: list.
We might also have Skills: list of technical skills (Go, React, GraphQL, etc.)
Let's extract:
Company description: Rare Candy is revolutionizing... etc.
Role description: The Role paragraph.
What Success Looks Like: timeline.
What You'll Do: bullet list.
A Day in Your Life: narrative.
You Might Be a Fit If: bullet list of fit criteria.
What You'll Need to Thrive Here: paragraph.
Why Join Us Now: bullet list of benefits? Actually includes compensation and benefits and dogfooding budget.
We need to avoid duplication.
Let's craft sections:
About the role
Rare Candy is revolutionizing the $25 billion trading-card industry as the “friendly local game shop” in the palm of your hands. Collectors use our AI-powered card scanner, open their favorite chase cards with Instapacks, and keep track of them with our data-rich collection tools which showcases Pokémon, MTG, Lorcana, One Piece, and more. We've hit 10x revenue growth over the last 6 months, the business is profitable, and we're building the team to take this from a great product to a category-defining one. We're a 10-person product team moving fast and looking for the next set of TCG-obsessed rock stars to join our team.
The Fullstack Developer will help build the operations toolchain used to manage warehouse, inventory, and Instapacks business. You'll work closely with the CTO and engineering team to ship new tools and features for the operations team, solving logistic problems, using Go and React, and growing quickly inside a fast‑moving startup.
Responsibilities
- Build and improve the Ops toolchain to support the Warehouse and Logistics team.
- Fix bugs, improve bottlenecks, and raise the quality bar for the Ops toolchain.
- Work closely with ops and engineering to increase efficiency on hard problems.
- Learn quickly, ask good questions, and communicate clearly when something is blocked, unclear, or ready for review.
- Start the day checking in with the warehouse team and reviewing feedback on shipped features.
- Pair with other engineers on backend service improvements.
- Tighten up dashboards, fix edge cases, and test flows against real‑time operations.
- Participate in operations discussions about launching new games for Instapacks and how the toolchain must support them.
- Open PRs with clear summaries and notes on what still needs review.
Requirements
- Around 3‑5 years of fullstack development experience with Go.
- Comfortable building with React or other React frameworks.
- Experience with GraphQL, or sufficient API experience to ramp quickly.
- Care about product quality and the little details that make tools easy to use and feel good.
- Experience building internal tools and understanding the importance of understanding the customer to build the right thing.
- Comfortable in a fast‑moving startup where priorities shift and the best answer is often “figure it out, then make it better.”
- Familiarity with the trading‑card or collector world (collecting, playing, ripping packs, following the market, or similar fluency).
Skills
- Go (backend)
- React (frontend)
- GraphQL / API design
- Internal tool development
- Problem‑solving and debugging
- Communication and collaboration
Pay
$140,000‑$160,000 base salary, plus competitive startup compensation and meaningful equity upside.
Benefits
- Health, dental, and vision coverage
- 401(k)
- Wellness stipend
- Monthly dogfooding budget to spend on cards
We should also include "What Success Looks Like" maybe as a subsection under About the role? But we already covered responsibilities. Could add a section "Qualifications" for success metrics? But we have no explicit qualifications besides experience. Could incorporate success timeline into About the role or Responsibilities. However we must preserve all substantive information; we cannot omit the success timeline. So we need to include it somewhere. Perhaps as a separate section "Qualifications" (though it's more about expectations). Or we could add a section "What Success Looks Like" as a heading, but the instruction says use headings like About the role, Responsibilities, etc. It didn't forbid other headings, but said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we could also add other headings if needed? Safer to stick to those. We can map success timeline to "Qualifications" maybe. But qualifications usually refer to required qualifications, not success metrics. However we can put success timeline under "Qualifications" as expected performance outcomes. Might be okay.
Alternatively we could add a section "About the role" that includes success timeline. Let's incorporate success timeline into About the role paragraph after role description.
Let's rewrite About the role to include success timeline.
We'll keep About the role as a prose
that includes company description, role description, and what success looks like (first 30 days, day 90, end of year one). That preserves info.
Thus we don't need separate Qualifications.
We still need Requirements (maybe from "What You'll Need to Thrive Here" and "You Might Be a Fit If"). We'll combine those into Requirements.
Skills we can list technical skills.
Now ensure we haven't missed any substantive info: The "Why Join Us Now" includes: Work on features collectors actually care about and are using everyday. Get real ownership early in your career while learning directly from experienced engineering leadership. Join a high-trust, low-ego team that ships fast, celebrates wins, and cares deeply about the hobby. Competitive startup comp, meaningful equity upside, and a salary range of $140,000-$160,000. Full benefits: health, dental, and vision coverage, 401(k), and a wellness stipend. A monthly dogfooding budget to spend on cards, because we hire people who love this hobby.
We already captured compensation and benefits. The other points (ownership, learning from leadership, high-trust team) are substantive; we should include them somewhere, maybe in About the role or a separate section like "Why Join Us". But we don't have a heading for that; we could add a section "About the role" again? Could add a paragraph under About the role about why join. Or we could add a section "Why Join Us" as a heading, but not in the list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g ...)". It might be interpreted that we should use those headings for sections, but we can also use other headings if needed? Safer to stick to those. We could incorporate those points into About the role or Benefits. For example, we can add a sentence in About the role: "You'll get real ownership early, learn from experienced engineering leadership, and join a high‑trust, low‑ego team that ships fast and celebrates wins." That covers.
Thus we have all.
Now ensure we removed boilerplate: "How to Apply", "Equal opportunity employer", "Location: Dallas, TX" we kept as a short p. Also we removed "Competitive startup comp, meaningful equity upside, and a salary range of $140,000-$160,000." Already in Pay.
We also removed "Full benefits: health, dental, and vision coverage, 401(k), and a wellness stipend." Already in Benefits.
We removed "A monthly dogfooding budget to spend on cards, because we hire people who love this hobby." Already in Benefits.
Now check for duplicate lines: We have not repeated.
Now output HTML fragment.
Let's craft final HTML:
Location: Dallas, TX
About the role
Rare Candy is revolutionizing the $25 billion trading‑card industry as the “friendly local game shop” in the palm of your hands. Collectors use our AI‑powered card scanner, open their favorite chase cards with Instapacks, and keep track of them with our data‑rich collection tools which showcases Pokémon, MTG, Lorcana, One Piece, and more. We've hit 10× revenue growth over the last
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove "How to Apply" and the equal opportunity employer line. Also remove "Location: Dallas, TX" maybe? It's metadata; we can fold minor metadata into a short
or drop it. Probably include location in a short paragraph. We need to output only HTML fragment, no /, no markdown fences. Let's structure:
Location: Dallas, TX
maybe. ThenAbout the role
with description of role (maybe combine About Rare Candy and The Role). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. About the role: include company description and role overview. Responsibilities: list of duties (What You'll Do, A Day in Your Life, etc.) Requirements: maybe "What You'll Need to Thrive Here" and "You Might Be a Fit If" combined. Qualifications: maybe "What Success Looks Like"? Not sure. But we can treat Qualifications as experience/education? Not given. Could skip if no specific qualifications. But we need to avoid empty headings. So only include sections with real content. We have Pay: salary range. Benefits: list. We might also have Skills: list of technical skills (Go, React, GraphQL, etc.) Let's extract: Company description: Rare Candy is revolutionizing... etc. Role description: The Role paragraph. What Success Looks Like: timeline. What You'll Do: bullet list. A Day in Your Life: narrative. You Might Be a Fit If: bullet list of fit criteria. What You'll Need to Thrive Here: paragraph. Why Join Us Now: bullet list of benefits? Actually includes compensation and benefits and dogfooding budget. We need to avoid duplication. Let's craft sections:About the role
Rare Candy is revolutionizing the $25 billion trading-card industry as the “friendly local game shop” in the palm of your hands. Collectors use our AI-powered card scanner, open their favorite chase cards with Instapacks, and keep track of them with our data-rich collection tools which showcases Pokémon, MTG, Lorcana, One Piece, and more. We've hit 10x revenue growth over the last 6 months, the business is profitable, and we're building the team to take this from a great product to a category-defining one. We're a 10-person product team moving fast and looking for the next set of TCG-obsessed rock stars to join our team.
The Fullstack Developer will help build the operations toolchain used to manage warehouse, inventory, and Instapacks business. You'll work closely with the CTO and engineering team to ship new tools and features for the operations team, solving logistic problems, using Go and React, and growing quickly inside a fast‑moving startup.
Responsibilities
- Build and improve the Ops toolchain to support the Warehouse and Logistics team.
- Fix bugs, improve bottlenecks, and raise the quality bar for the Ops toolchain.
- Work closely with ops and engineering to increase efficiency on hard problems.
- Learn quickly, ask good questions, and communicate clearly when something is blocked, unclear, or ready for review.
- Start the day checking in with the warehouse team and reviewing feedback on shipped features.
- Pair with other engineers on backend service improvements.
- Tighten up dashboards, fix edge cases, and test flows against real‑time operations.
- Participate in operations discussions about launching new games for Instapacks and how the toolchain must support them.
- Open PRs with clear summaries and notes on what still needs review.
Requirements
- Around 3‑5 years of fullstack development experience with Go.
- Comfortable building with React or other React frameworks.
- Experience with GraphQL, or sufficient API experience to ramp quickly.
- Care about product quality and the little details that make tools easy to use and feel good.
- Experience building internal tools and understanding the importance of understanding the customer to build the right thing.
- Comfortable in a fast‑moving startup where priorities shift and the best answer is often “figure it out, then make it better.”
- Familiarity with the trading‑card or collector world (collecting, playing, ripping packs, following the market, or similar fluency).
Skills
- Go (backend)
- React (frontend)
- GraphQL / API design
- Internal tool development
- Problem‑solving and debugging
- Communication and collaboration
Pay
$140,000‑$160,000 base salary, plus competitive startup compensation and meaningful equity upside.
Benefits
- Health, dental, and vision coverage
- 401(k)
- Wellness stipend
- Monthly dogfooding budget to spend on cards
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we could also add other headings if needed? Safer to stick to those. We can map success timeline to "Qualifications" maybe. But qualifications usually refer to required qualifications, not success metrics. However we can put success timeline under "Qualifications" as expected performance outcomes. Might be okay. Alternatively we could add a section "About the role" that includes success timeline. Let's incorporate success timeline into About the role paragraph after role description. Let's rewrite About the role to include success timeline. We'll keep About the role as a prose
that includes company description, role description, and what success looks like (first 30 days, day 90, end of year one). That preserves info. Thus we don't need separate Qualifications. We still need Requirements (maybe from "What You'll Need to Thrive Here" and "You Might Be a Fit If"). We'll combine those into Requirements. Skills we can list technical skills. Now ensure we haven't missed any substantive info: The "Why Join Us Now" includes: Work on features collectors actually care about and are using everyday. Get real ownership early in your career while learning directly from experienced engineering leadership. Join a high-trust, low-ego team that ships fast, celebrates wins, and cares deeply about the hobby. Competitive startup comp, meaningful equity upside, and a salary range of $140,000-$160,000. Full benefits: health, dental, and vision coverage, 401(k), and a wellness stipend. A monthly dogfooding budget to spend on cards, because we hire people who love this hobby. We already captured compensation and benefits. The other points (ownership, learning from leadership, high-trust team) are substantive; we should include them somewhere, maybe in About the role or a separate section like "Why Join Us". But we don't have a heading for that; we could add a section "About the role" again? Could add a paragraph under About the role about why join. Or we could add a section "Why Join Us" as a heading, but not in the list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use
for section headings (e.g ...)". It might be interpreted that we should use those headings for sections, but we can also use other headings if needed? Safer to stick to those. We could incorporate those points into About the role or Benefits. For example, we can add a sentence in About the role: "You'll get real ownership early, learn from experienced engineering leadership, and join a high‑trust, low‑ego team that ships fast and celebrates wins." That covers. Thus we have all. Now ensure we removed boilerplate: "How to Apply", "Equal opportunity employer", "Location: Dallas, TX" we kept as a short p. Also we removed "Competitive startup comp, meaningful equity upside, and a salary range of $140,000-$160,000." Already in Pay. We also removed "Full benefits: health, dental, and vision coverage, 401(k), and a wellness stipend." Already in Benefits. We removed "A monthly dogfooding budget to spend on cards, because we hire people who love this hobby." Already in Benefits. Now check for duplicate lines: We have not repeated. Now output HTML fragment. Let's craft final HTML:
Location: Dallas, TX
About the role
Rare Candy is revolutionizing the $25 billion trading‑card industry as the “friendly local game shop” in the palm of your hands. Collectors use our AI‑powered card scanner, open their favorite chase cards with Instapacks, and keep track of them with our data‑rich collection tools which showcases Pokémon, MTG, Lorcana, One Piece, and more. We've hit 10× revenue growth over the last