Full Stack Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Content: - Intro: "Do you love to build? Are you one of the most ambitious people you know? If so, you'll be right at home at Unwrap. We are seeking a full stack software engineer who has a specific interest in working across the tech stack on both frontend, backend, and data pipelines. Our tech stack is built in TypeScript, our backend is a GraphQl / node based service, and our frontend runs on React. You’ll own and deliver major customer-facing components end-to-end. This includes understanding customer needs, helping compile sprint requirements, and ultimately shipping core product features. You’ll get exposure to all aspects of the company, from sales to marketing to customer success, but you’d focus primarily on designing and building user-facing tools. Our strong preference is for this person to be in-person, as most of the team is in beautiful Santa Barbara, CA. Our office is downtown, walking distance to great restaurants, coffee shops, and the beach." - "Who We Are" paragraph about Unwrap.ai mission, customers, tech, team size, funding, founders, NLP. - "What You Bring": bullet list? Actually lines: "Bachelors degree or equivalent in Computer Science or similar fieldYou have 2+ years experience as a software engineerYou are first and foremost a builder and are excited about the idea of spending 80%+ of your time actively developing software. You have hands-on experience working on frontend and backend software systems. You pride yourself on developing high quality products that solve real customer problems. You own what you build and take pride in shipping robust high quality software. You're not afraid of ambiguous product requirements. You're comfortable meeting with customers." - "What You Get": bullet list: "Ground floor impact at a Series A startup with tremendous latitude over technical strategy and approachSignificant, potentially life-changing equityAbility to rapidly advance your career alongside company growthCollaborate with experienced teammates, entrepreneurs, and advisorsWork directly with enterprise customers to ideate and develop solutions" - "Compensation Range: $110K - $160K" No explicit Benefits, Schedule, etc. So we should include sections that have content: About the role (intro), Responsibilities (maybe from "You’ll own and deliver..."), Requirements (maybe from "What You Bring"?), Qualifications (maybe degree and experience), Skills (maybe tech stack), Benefits (maybe "What You Get"?), Pay (Compensation Range). Schedule not present, so omit. We must not repeat job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to decide how to split content into sections. Potential sections: - About the role: could be the introductory paragraph describing role and company context? But "About the role" maybe includes description of role and team location preference. - Responsibilities: list of duties: own and deliver major customer-facing components end-to-end, understanding customer needs, helping compile sprint requirements, shipping core product features, exposure to all aspects of company (sales, marketing, customer success), focus on designing and building user-facing tools. - Requirements: maybe the "What You Bring" items: Bachelors degree or equivalent in CS, 2+ years experience as software engineer, builder mindset, 80%+ time developing software, hands-on experience frontend/backend, pride in high quality products, ownership, not afraid of ambiguous requirements, comfortable meeting customers. - Qualifications: maybe overlapping with requirements; but we could treat "What You Bring" as Qualifications. However we need to avoid duplication. Could split: Requirements = technical stack experience (TypeScript, GraphQL/Node, React). Qualifications = education/experience/builder mindset. But the posting doesn't explicitly separate; we need to infer but not invent. Safer to have one section for "What You Bring" as Qualifications or Requirements. The instruction: Use sections only when posting has real specific content for it. We can decide to have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Let's map: About the role: Intro paragraph about seeking full stack engineer, tech stack, location preference. Responsibilities: bullet list of duties (own and deliver..., understanding customer needs..., helping compile sprint..., shipping core product..., exposure to..., focus on designing and building user-facing tools). Qualifications: bullet list of education/experience/builder mindset etc. Skills: bullet list of tech stack: TypeScript, GraphQL/Node backend, React frontend, maybe also mention working across frontend/backend/data pipelines. Benefits: bullet list from "What You Get": ground floor impact, significant equity, rapid career advancement, collaborate with experienced teammates, work directly with enterprise customers. Pay: Compensation Range: $110K - $160K. Schedule: not present, omit. We must not include filler like "commensurate with experience". Not present. We need to ensure we don't repeat content. Let's extract exact sentences. Intro: "Do you love to build? Are you one of the most ambitious people you know? If so, you'll be right at home at Unwrap. We are seeking a full stack software engineer who has a specific interest in working across the tech stack on both frontend, backend, and data pipelines. Our tech stack is built in TypeScript, our backend is a GraphQl / node based service, and our frontend runs on React. You’ll own and deliver major customer-facing components end-to-end. This includes understanding customer needs, helping compile sprint requirements, and ultimately shipping core product features. You’ll get exposure to all aspects of the company, from sales to marketing to customer success, but you’d focus primarily on designing and building user-facing tools. Our strong preference is for this person to be in-person, as most of the team is in beautiful Santa Barbara, CA. Our office is downtown, walking distance to great restaurants, coffee shops, and the beach." We could split: first sentence maybe part of About the role. The rest about responsibilities etc. But we need to avoid duplication: The sentence "You’ll own and deliver major customer-facing components end-to-end..." could be responsibility. Let's craft sections:

  About the role

  Do you love to build? Are you one of the most ambitious people you know? If so, you'll be right at home at Unwrap. We are seeking a full stack software engineer who has a specific interest in working across the tech stack on both frontend, backend, and data pipelines. Our tech stack is built in TypeScript, our backend is a GraphQL/node based service, and our frontend runs on React. Our strong preference is for this person to be in-person, as most of the team is in beautiful Santa Barbara, CA. Our office is downtown, walking distance to great restaurants, coffee shops, and the beach.

  That covers intro and location preference.

  Responsibilities

  • Own and deliver major customer-facing components end-to-end.
  • Understand customer needs.
  • Help compile sprint requirements.
  • Ship core product features.
  • Get exposure to all aspects of the company, from sales to marketing to customer success.
  • Focus primarily on designing and building user-facing tools.
  Note: The bullet list should preserve all info. The phrase "You’ll get exposure to all aspects of the company, from sales to marketing to customer success, but you’d focus primarily on designing and building user-facing tools." We split into two bullets: exposure and focus.

  Qualifications

  • Bachelor’s degree or equivalent in Computer Science or similar field.
  • 2+ years experience as a software engineer.
  • First and foremost a builder, excited about spending 80%+ of time actively developing software.
  • Hands‑on experience working on frontend and backend software systems.
  • Pride in developing high quality products that solve real customer problems.
  • Own what you build and take pride in shipping robust, high‑quality software.
  • Not afraid of ambiguous product requirements.
  • Comfortable meeting with customers.
  We need to keep the exact phrasing? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the exact wording as much as possible, but we can adjust punctuation for HTML. We'll keep the meaning. Potentially we could combine some bullets but it's okay.

  Skills

  • TypeScript
  • GraphQL/Node.js backend
  • React frontend
  • Experience working across frontend, backend, and data pipelines
  But the phrase "working across the tech stack on both frontend, backend, and data pipelines" is from intro; we could include as skill.

  Benefits

  • Ground floor impact at a Series A startup with tremendous latitude over technical strategy and approach
  • Significant, potentially life‑changing equity
  • Ability to rapidly advance your career alongside company growth
  • Collaborate with experienced teammates, entrepreneurs, and advisors
  • Work directly with enterprise customers to ideate and develop solutions

  Pay

  Compensation Range: $110K - $160K

  We should not include Schedule. Check for any duplicated lines: We used "You’ll own and deliver major customer-facing components end-to-end." in responsibilities; we also had that phrase in intro but we removed from intro to avoid duplication. Good. Check that we didn't miss any substantive info: The mission description about Unwrap.ai, customers, NLP, team size, funding, founders. That is substantive but not clearly fitting into any of the allowed sections. Where to put? Possibly "About the role" could include company description. The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include company description under About the role. It's substantive. Let's incorporate that. Thus About the role paragraph should include: mission, customers, NLP, team size, funding, founders. Let's rewrite About the role to include both role description and company info. We need to avoid repeating the role description sentences we used elsewhere. We can keep some generic description but not duplicate the responsibility bullets. Let's craft About the role:

  Do you love to build? Are you one of the most ambitious people you know? If so, you'll be right at home at Unwrap. We are seeking a full stack software engineer who has a specific interest in working across the tech stack on both frontend, backend, and data pipelines. Our tech stack is built in TypeScript, our backend is a GraphQL/node based service, and our frontend runs on React. Unwrap.ai is on a mission to fill the world with products people love, helping companies like Lyft, Stripe, Oura, Microsoft, Perplexity, and Github collect and process feedback more effectively. We ingest feedback from thousands of sources (support channels, surveys, social) and use state‑of‑the‑art NLP technology to extract actionable insights for customers across software, hardware, and retail sectors. We’re currently a team of 40, based in Santa Barbara, and growing quickly. We are venture‑backed, and just raised our $12M Series A from world‑leading VCs. Our founders, two ex‑Amazon Alexa Product Managers, were tired of manually sifting through customer reviews, support tickets, and bugs while working on Alexa. They understood the importance of listening to customers and prioritizing their requests effectively, but simply had too much feedback to parse through. So, Unwrap.ai was born to solve this problem. Specifically