Senior Product 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. The posting includes "About the role" (the description after The RoleWe’re looking...). Responsibilities: "What You’ll Do" bullet list. Requirements/Qualifications: "What We’re Looking For". Skills: maybe combine with requirements? The posting mentions specific tech stack: React, TypeScript, etc. Benefits: "Coverage: full health, dental, and vision." Also "annual hotel and travel stipend". Also "direct access to the world’s most recognized consumer brands". Also "the best available tools". Also "experience firsthand: an annual hotel and travel stipend". Also "Where you’ll be: in a beautiful office in Austin, San Francisco, or Paris." That's location, maybe schedule? Not schedule. Pay: "Compensation: competitive salary calibrated to experience, and meaningful equity". That's pay. Schedule: not mentioned. So we should not include Schedule section. We need headings

for each section. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive information. So we need to include the About Way description? The "ABOUT WAY" section is company overview. Should we include that? Possibly under "About the role"? Actually "About the role" is separate. The posting includes "ABOUT WAY" then "The Role". The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections: About the role, Responsibilities? Actually "About the role" is a heading. We might also include "About Way" as maybe not required; but they said prefer a few substantive sections over many thin ones. Could combine company overview into About the role? But they said use headings as given; we can include "About the role" and maybe "About Way" is not in list, so we should not create a heading for it. However we need to preserve all substantive information; we could embed the company overview within the About the role paragraph? Might be okay. But better to include a short paragraph under About the role that includes both role description and company overview? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Probably we should stick to those headings only if content exists. So we need to map content: - About the role: description of role (The RoleWe’re looking...). Could also include company overview? Might be okay to include a brief note about Way within About the role. - Responsibilities: What You’ll Do bullet list. - Requirements: What We’re Looking For bullet list (experience, etc.) - Qualifications: maybe same as Requirements? Could combine? But we have both headings; we could put qualifications under Requirements? Might be redundant. Better to have Requirements for experience, Qualifications for specific technical stack? The posting: "What We’re Looking For" includes experience, React/TypeScript, track record, product sensibility, comfort without PM, high-ownership mindset. That's more like qualifications. Could treat that as Qualifications. Then Skills could be the specific tech stack: React, TypeScript, Node.js, APIs, PostgreSQL, GCP, etc. But the posting also mentions those under "What We’re Looking For". Might be overlapping. To avoid thin sections, we could combine Requirements and Qualifications into one section? But they said prefer a few substantive sections over many thin ones. So maybe we have: About the role, Responsibilities, Qualifications (covering experience and skills), Benefits, Pay. That's four sections. But they gave examples of headings; we can omit some if no content. Let's decide: - About the role: include role description and maybe company overview. - Responsibilities: bullet list from What You’ll Do. - Qualifications: bullet list from What We’re Looking For (including experience, technical, product sensibility, ownership). - Benefits: bullet list from Coverage: full health, dental, vision; annual hotel and travel stipend; direct access to brands; best tools; office locations. - Pay: bullet list from Compensation: competitive salary calibrated to experience, meaningful equity. We should not include Schedule. Now format:

  About the role

  then

  ...

  . For bullet lists:
  • ...
  . We need to preserve all substantive information: ensure we don't lose any details. Let's extract details: About Way paragraph: "ABOUT WAY Way is building the AI, data, and infrastructure layer for the experience economy. As artificial intelligence automates labor and people reclaim time, the shift toward spending on experiences over things only accelerates. Way sits at the center of that shift as the platform, intelligence layer, and curated marketplace on which experiences are created, distributed, and sold. Founded in 2020 and headquartered in Austin with offices in Paris and San Francisco, Way built the category of experiences in hospitality from the ground up, during a pandemic that had shut the industry down. Leading global travel, retail, lifestyle, and hospitality brands leverage Way, including Hyatt, Hilton, Alaska Airlines, Aspen, Piaget, and countless others. Way’s position is layered by design: a proprietary data network built on millions of experiential data points, the system of record for experiential operations, an e-commerce layer embedded directly into partners’ customer journeys, and a marketplace through Partner Exchange, where brands across hospitality, travel, lifestyle, and retail co-create and co-sell experiences with one another. Every brand that joins makes the network more valuable to every brand already on it. That combination of data, workflow, distribution, and network effects is not something that can be vibe-coded into existence. It compounds. It is what positions Way as the durable infrastructure for the experience economy regardless of how the technology landscape evolves. Way is backed with $22m in capital from Tiger Global and strategic family offices and angel investors. The company has mid-8 figures of ARR from a global enterprise customer set, with outstanding growth and efficiency metrics." The Role paragraph: "The RoleWe’re looking for a Senior Product Engineer to help build the next generation of Way. You’ll work across the stack to turn ambitious product ideas into fast, polished, and reliable experiences for the brands, operators, and guests who use Way. You’ll work closely with Product and Design to shape the problem, prototype solutions, make pragmatic technical decisions, and own features from idea through production. The work spans new product capabilities and the existing platform that serves enterprise customers every day. This is a role for an experienced, hands-on builder who cares equally about product quality and software craftsmanship. You should be comfortable moving from React interaction details to TypeScript services, PostgreSQL models, integrations, observability, and production operations. We use AI and coding agents as everyday development tools, with the expectation that you verify and own what ships." What You’ll Do bullet list (need to capture each line): - Build customer-facing product capabilities across Way—from discovery and merchandising to booking, payments, the guest journey after a room is booked, reporting, and third-party integrations. - Build AI-powered functionality into the core of Way. - Work closely with Product and Design to shape ambiguous problems, prototype quickly, and iterate toward experiences that feel intuitive, responsive, and distinctly Way. - Drive complex, end-to-end features across React and Next.js frontends, TypeScript and NestJS services, PostgreSQL, and event-driven workflows. - Own a product domain or platform capability through design, implementation, testing, production release, runbook, and operational follow-through. - Develop a deep understanding of the critical workflows and operational risks, improving the existing platform while helping establish clearer boundaries, contracts, and independently deployable capabilities. What We’re Looking For bullet list: - 5+ years of experience building and operating customer-facing products in a high-quality software environment, with the depth and scope expected of a senior or staff-level engineer. - Strong React and TypeScript fundamentals, with production experience across browser technologies, Node.js, APIs, PostgreSQL, and serverless or managed cloud services, especially on GCP. - A track record of driving complex, end-to-end features with visible customer or business impact—not only incremental improvements and refactors. - Product sensibility: you care about UX, speed, and polish, and you speak up when something does not feel right. - Comfort working without heavy PM overhead: you help shape the problem, make tradeoffs explicit, create clarity across teams, and reduce large goals to safe, valuable increments. - A high-ownership mindset: you are a self-directed, full-lifecycle builder who takes responsibility for testing, reliability, security, observability, and what happens after launch, while raising the engineering bar for the people around you. Benefits/Coverage etc: - Coverage: full health, dental, and vision. - The work: direct access to the world’s most recognized consumer brands and the mandate to move quickly on their behalf. - The tools: the best available, and the expectation that you use them to raise your own ceiling. - Experience firsthand: an annual hotel and travel stipend at the properties and partners in Way’s global ecosystem. - Where you’ll be: in a beautiful office in Austin, San Francisco, or Paris. Pay: - Compensation: competitive salary calibrated to experience, and meaningful equity in a sustainably growing company with real value creation already realized. We should not include fluff like "competitive salary calibrated to experience" is okay. Now produce HTML. We need to ensure no extra text outside HTML. No markdown fences. Let's craft:

  About the role

  [combined About Way + The Role]

  But we need to avoid duplication; we can include both paragraphs. Let's write About the role paragraph: combine company overview and role description. We'll put two

  maybe? But they said use

  for prose. Could have multiple

  under same heading. That's fine. Thus:

  About the role

  Way is building the AI, data, and infrastructure layer for the experience economy. As artificial intelligence automates labor and people reclaim time, the shift toward spending on experiences over things only accelerates. Way sits at the center of that shift as the platform, intelligence layer, and curated marketplace on which experiences are created, distributed, and sold. Founded in 2020 and headquartered in Austin with offices in Paris and San Francisco, Way built the category of experiences in hospitality from the ground up, during a pandemic that had shut the industry down. Leading global travel, retail, lifestyle, and hospitality brands leverage Way, including Hyatt, Hilton, Alaska Airlines, Aspen, Piaget, and countless others. Way’s position is layered by design: a proprietary data network built on millions of experiential data points, the system of record for experiential operations, an e-commerce layer embedded directly into partners’ customer journeys, and a marketplace through Partner Exchange, where brands across hospitality, travel, lifestyle, and retail co-create and co-sell experiences with one another. Every brand that joins makes the network more valuable to every brand already on it. That combination of data, workflow, distribution, and network effects is not something that can be vibe-coded into existence. It compounds. It is what positions Way as the durable infrastructure for the experience economy regardless of how the technology landscape evolves. Way is backed with $22m in capital from Tiger Global and strategic family offices and angel investors. The company has mid-8 figures of ARR from a global enterprise customer set, with outstanding growth and efficiency metrics.

  We’re looking for a Senior Product Engineer to help build the next generation of Way. You’ll work across the stack to turn ambitious product ideas into fast, polished, and reliable experiences for the brands, operators, and guests who use Way