Go Backend Developer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, application instructions, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Location: Fully Remote (maybe part of metadata; could be a short p)
- Compensation: $160,000 - 180,000, competitive startup comp, and meaningful equity upside
- Department: Engineering
- Reports to: CTO
- About Rare Candy (description)
- The Role (description)
- What Success Looks Like (maybe part of responsibilities? Could be its own section? Not in list but could be part of Responsibilities or Qualifications. We can embed under Responsibilities or maybe a separate "Expectations". But we only allowed headings from list. We could put under Responsibilities or Qualifications. Probably Responsibilities includes what you'll do and success metrics. We'll include Responsibilities section with bullet list of duties.
- What You'll Do (list of duties) -> Responsibilities.
- A Day in Your Life (maybe also responsibilities but could be omitted as it's narrative; we could include as prose under Responsibilities.
- You Might Be a Fit If (list of qualifications) -> Requirements or Qualifications.
- What You'll Need to Thrive Here (more qualifications) -> could be Qualifications.
- Why Join Us Now (benefits) -> Benefits section.
- Pay: we have compensation details; we can make a Pay section with salary range and equity.
- Benefits: list health, dental, vision, 401(k), wellness stipend, monthly dogfooding budget.
- Schedule: not specified; we should not create Schedule section unless posting states it. It doesn't, so omit.
- About the role: we have About Rare Candy and The Role; could combine as About the role section.
We need to avoid filler like "commensurate with experience". Not present.
We must not include application instructions (How to Apply) etc. Also remove EEO line.
We must preserve all substantive info: location, compensation, department, reports to, about rare candy, role description, success looks like, what you'll do, day in life, you might be a fit if, what you'll need to thrive here, why join us now (benefits). Also maybe mention "Full benefits: health, dental, and vision coverage, 401(k), and a wellness stipend. A monthly dogfooding budget to spend on cards". Also "Competitive startup comp, meaningful equity upside, and a salary range of $160,000-$180,000."
We need to format as HTML fragment: use for section headings, - for lists,
for prose.
We need to decide which sections to include:
- About the role: combine About Rare Candy and The Role description (maybe also success looks like?). Could be separate but we have limited headings. We'll put About the role as
About the role
with paragraphs.
- Responsibilities: Responsibilities
with of duties from What You'll Do and maybe A Day in Your Life (but we can embed as prose). We'll list bullet points.
- Requirements: maybe combine You Might Be a Fit If and What You'll Need to Thrive Here. Could be Requirements
with bullet list.
- Qualifications: maybe not needed if we combine. But we have both Requirements and Qualifications headings allowed. Could split: Requirements = technical experience (5-7 years, Go, APIs, relational DB). Qualifications = softer skills (ownership, curiosity, collector fluency). But we can also just have one Requirements section and omit Qualifications if not enough distinct content. However we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe just Requirements.
- Benefits: Benefits
with list.
- Pay: Pay
with paragraph about salary range and equity.
- Schedule: omit.
We also need to include location, department, reports to maybe as a short p before sections.
We must not repeat job title (Go Backend Developer). Not include as heading.
We must not include Job ID etc.
We must not include application instructions, EEO, etc.
Let's craft.
First, a short p for metadata: maybe "Location: Fully Remote • Department: Engineering • Reports to: CTO". Could be one p.
Then About the role section: combine About Rare Candy and The Role description.
We need to preserve all substantive info: The description about Rare Candy: "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 Role description: "We’re hiring a Go Backend Developer to help build the services and APIs that power Rare Candy, from managing collections and marketplace transactions to opening Instapacks. You’ll work closely with the CTO and engineering team to ship backend features that collectors rely on every day. This is a hands-on product engineering role for someone who already knows how to build in Go, has experience with APIs and relational databases, and wants to grow quickly inside a fast-moving startup. You won’t be handed endless tickets in a giant backlog. You’ll work on real product problems, learn from experienced engineers, and see your work directly improve the experience of passionate collectors. If you love trading cards or collector communities and want to level up fast, this is a role for you."
We could also include What Success Looks Like as part of About the role or Responsibilities. Might be better to include under Responsibilities as expectations.
But we have Responsibilities section for duties; we could also include success metrics there.
Let's decide: Responsibilities will include bullet list of What You'll Do and maybe A Day in Your Life as prose.
Now Requirements: bullet list from You Might Be a Fit If and What You'll Need to Thrive Here.
We need to capture:
You Might Be a Fit If:
- around 5-7 years of backend development experience and have shipped real features in a production system or serious side project.
- comfortable building in Go and understand error handling, interfaces, concurrency basics, and testing.
- built or maintained APIs. GraphQL experience is a plus, and you’re comfortable learning it if your background is primarily REST.
- worked with relational databases and SQL, including schema design, joins, indexes, and transactions.
- care about correctness, reliability, and maintainable code. You think through what happens when a request fails, runs twice, or encounters unexpected data.
- comfortable using logs and debugging tools to trace a problem through an API, service, or database.
- comfortable in a fast-moving startup where priorities can shift and the best answer is often “figure it out, then make it better.”
- know the trading-card or collector world. You collect, play, rip packs, follow the market, or have real fluency in a similar collectible space.
What You'll Need to Thrive Here:
- expected to take ownership of your role and drive your own growth. You’ll have support, context, and mentorship.
- systems are still evolving, team is small, work will matter immediately.
- need to be curious, detail-oriented, and comfortable learning by doing.
- If you like to build internal tools, solve operational issues, and the idea of building tools you would actually want to use yourself, you'll do great here.
We can combine.
Benefits: Full benefits: health, dental, and vision coverage, 401(k), and a wellness stipend. A monthly dogfooding budget to spend on cards.
Also mention Competitive startup comp, meaningful equity upside, and a salary range of $160,000-$180,000. That's Pay.
Pay section: include salary range and equity.
Now we need to ensure we don't include any boilerplate like "Rare Candy is an equal opportunity employer." etc.
Let's construct HTML.
We'll start with a p for metadata.
Then About the role
with two paragraphs: one about Rare Candy, one about the role.
Then Responsibilities
with list of duties from What You'll Do (maybe 7 items). Also we could include A Day in Your Life as a after list.
Then
Requirements
with list of qualifications.
Then Benefits
with list.
Then Pay
with about salary range and equity.
We should not include Schedule.
Check that we haven't missed any substantive info: The success looks like (first 30 days, day 90, end of year one) - we haven't included that. Should we include? It's substantive. Could be part of Responsibilities or maybe a separate section like Expectations but not in allowed headings. Could incorporate into Responsibilities as prose or bullet list. Let's add a
under Responsibilities after the list describing success timeline.
Also we missed mention of "You’ll work closely with the CTO and engineering team to ship backend features that collectors rely on every day." Already in role description.
We also missed "You won’t be handed endless tickets in a giant backlog." Already in role description.
We also missed "Learn quickly, ask good questions, and communicate clearly when something is blocked, unclear, or ready for review." That's in What You'll Do list? Actually it's under What You'll Do? It appears after "Work closely with product, design, and engineering to turn ideas into shipped experiences." then "Learn quickly, ask good questions, and communicate clearly when something is blocked, unclear, or ready for review." That's a duty; include in responsibilities.
Also "You Might Be a Fit If" includes "You’re comfortable in a fast-moving startup where priorities can shift and the best answer is often “figure it out, then make it better.”" Already captured.
Now ensure we don't repeat info unnecessarily.
Let's draft.
HTML:
Location: Fully Remote • Department: Engineering • Reports to: CTO
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.
We’re hiring a Go Backend Developer to help build the services and APIs that power Rare Candy, from managing collections and marketplace transactions to opening Instapacks. You’ll work closely with the CTO and engineering team to ship backend features that collectors rely on every day. This is a hands-on product engineering role for someone who already knows how to build in Go, has experience with APIs and relational databases, and wants to grow quickly inside a fast-moving startup. You won
- for lists,
for prose. We need to decide which sections to include: - About the role: combine About Rare Candy and The Role description (maybe also success looks like?). Could be separate but we have limited headings. We'll put About the role as
About the role
with paragraphs. - Responsibilities:Responsibilities
with- of duties from What You'll Do and maybe A Day in Your Life (but we can embed as prose). We'll list bullet points.
- Requirements: maybe combine You Might Be a Fit If and What You'll Need to Thrive Here. Could be
Requirements
with bullet list. - Qualifications: maybe not needed if we combine. But we have both Requirements and Qualifications headings allowed. Could split: Requirements = technical experience (5-7 years, Go, APIs, relational DB). Qualifications = softer skills (ownership, curiosity, collector fluency). But we can also just have one Requirements section and omit Qualifications if not enough distinct content. However we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe just Requirements. - Benefits:Benefits
with list. - Pay:Pay
with paragraph about salary range and equity. - Schedule: omit. We also need to include location, department, reports to maybe as a short p before sections. We must not repeat job title (Go Backend Developer). Not include as heading. We must not include Job ID etc. We must not include application instructions, EEO, etc. Let's craft. First, a short p for metadata: maybe "Location: Fully Remote • Department: Engineering • Reports to: CTO". Could be one p. Then About the role section: combine About Rare Candy and The Role description. We need to preserve all substantive info: The description about Rare Candy: "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 Role description: "We’re hiring a Go Backend Developer to help build the services and APIs that power Rare Candy, from managing collections and marketplace transactions to opening Instapacks. You’ll work closely with the CTO and engineering team to ship backend features that collectors rely on every day. This is a hands-on product engineering role for someone who already knows how to build in Go, has experience with APIs and relational databases, and wants to grow quickly inside a fast-moving startup. You won’t be handed endless tickets in a giant backlog. You’ll work on real product problems, learn from experienced engineers, and see your work directly improve the experience of passionate collectors. If you love trading cards or collector communities and want to level up fast, this is a role for you." We could also include What Success Looks Like as part of About the role or Responsibilities. Might be better to include under Responsibilities as expectations. But we have Responsibilities section for duties; we could also include success metrics there. Let's decide: Responsibilities will include bullet list of What You'll Do and maybe A Day in Your Life as prose. Now Requirements: bullet list from You Might Be a Fit If and What You'll Need to Thrive Here. We need to capture: You Might Be a Fit If: - around 5-7 years of backend development experience and have shipped real features in a production system or serious side project. - comfortable building in Go and understand error handling, interfaces, concurrency basics, and testing. - built or maintained APIs. GraphQL experience is a plus, and you’re comfortable learning it if your background is primarily REST. - worked with relational databases and SQL, including schema design, joins, indexes, and transactions. - care about correctness, reliability, and maintainable code. You think through what happens when a request fails, runs twice, or encounters unexpected data. - comfortable using logs and debugging tools to trace a problem through an API, service, or database. - comfortable in a fast-moving startup where priorities can shift and the best answer is often “figure it out, then make it better.” - know the trading-card or collector world. You collect, play, rip packs, follow the market, or have real fluency in a similar collectible space. What You'll Need to Thrive Here: - expected to take ownership of your role and drive your own growth. You’ll have support, context, and mentorship. - systems are still evolving, team is small, work will matter immediately. - need to be curious, detail-oriented, and comfortable learning by doing. - If you like to build internal tools, solve operational issues, and the idea of building tools you would actually want to use yourself, you'll do great here. We can combine. Benefits: Full benefits: health, dental, and vision coverage, 401(k), and a wellness stipend. A monthly dogfooding budget to spend on cards. Also mention Competitive startup comp, meaningful equity upside, and a salary range of $160,000-$180,000. That's Pay. Pay section: include salary range and equity. Now we need to ensure we don't include any boilerplate like "Rare Candy is an equal opportunity employer." etc. Let's construct HTML. We'll start with a p for metadata. ThenAbout the role
with two paragraphs: one about Rare Candy, one about the role. ThenResponsibilities
with- list of duties from What You'll Do (maybe 7 items). Also we could include A Day in Your Life as a
after list. Then
Requirements
with- list of qualifications.
Then
Benefits
with- list.
Then
Pay
withabout salary range and equity. We should not include Schedule. Check that we haven't missed any substantive info: The success looks like (first 30 days, day 90, end of year one) - we haven't included that. Should we include? It's substantive. Could be part of Responsibilities or maybe a separate section like Expectations but not in allowed headings. Could incorporate into Responsibilities as prose or bullet list. Let's add a
under Responsibilities after the list describing success timeline. Also we missed mention of "You’ll work closely with the CTO and engineering team to ship backend features that collectors rely on every day." Already in role description. We also missed "You won’t be handed endless tickets in a giant backlog." Already in role description. We also missed "Learn quickly, ask good questions, and communicate clearly when something is blocked, unclear, or ready for review." That's in What You'll Do list? Actually it's under What You'll Do? It appears after "Work closely with product, design, and engineering to turn ideas into shipped experiences." then "Learn quickly, ask good questions, and communicate clearly when something is blocked, unclear, or ready for review." That's a duty; include in responsibilities. Also "You Might Be a Fit If" includes "You’re comfortable in a fast-moving startup where priorities can shift and the best answer is often “figure it out, then make it better.”" Already captured. Now ensure we don't repeat info unnecessarily. Let's draft. HTML:
Location: Fully Remote • Department: Engineering • Reports to: CTO
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.
We’re hiring a Go Backend Developer to help build the services and APIs that power Rare Candy, from managing collections and marketplace transactions to opening Instapacks. You’ll work closely with the CTO and engineering team to ship backend features that collectors rely on every day. This is a hands-on product engineering role for someone who already knows how to build in Go, has experience with APIs and relational databases, and wants to grow quickly inside a fast-moving startup. You won