Chief of Staff
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment.
Let's extract content.
Company description (About Way) maybe not needed as a section? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when the posting has real, specific content for it. The posting includes "ABOUT WAY" which is about the company, not the role. But we could treat that as "About the role"? Not exactly. The instruction says "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having an "About the company" section, but the list of headings given is limited to those. Probably we should stick to those headings. The "About Way" could be considered "About the role"? Not really. Might be better to omit it, as it's not requested. However we need to preserve ALL substantive information. If we omit the company description, we lose info. But maybe we can incorporate it into "About the role" as a brief description? 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 "include a section ONLY when the posting has real, specific content for it". It gives examples but not exhaustive. Could we add an "About Way" section? Possibly but safer to stick to given headings. However we need to preserve all substantive info; we could embed the company description within the "About the role" section as prose. That would preserve it.
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.
Then responsibilities: list each bullet.
We need to convert each line under KEY RESPONSIBILITIES into - . Let's list them:
- Work closely with the COO to support high-priority strategic and operational initiatives
- Own internal performance metrics and reporting infrastructure across departments
- Build and maintain internal databases to ensure high-quality, scalable business intelligence
- Lead deep-dive analyses to inform decision-making across product, ops, and customer success
- Identify process bottlenecks and recommend scalable, data-backed solutions
- Design frameworks to track key company KPIs and strategic objectives
- Partner cross-functionally to implement dashboards and streamline access to insights
- Take on high-impact projects with little guidance and see them through from idea to execution
We'll put inside
.
Next: WHAT WE'RE LOOKING FOR. Need to split into Requirements, Qualifications, Skills. The bullet list includes:
- 3-5 years of experience in consulting, data analytics, investment banking, high-growth startups, or similar
- Strong analytical foundation with experience using Excel, PowerPoint, and internal BI tools
- Ability to independently structure complex problems and communicate insights clearly
- Demonstrated self-starter with grit, adaptability, and a strong sense of ownership
- Comfortable operating with minimal direction in fast-paced, ambiguous environments
- Excellent written and verbal communication skills
- Experience with SQL, Tableau, Looker, or similar tools is a plus
- Hands-on experience with HubSpot or similar CRM tools preferred
- Prior experience in SaaS, B2B tech, or hospitality & travel is a plus, but not required
We need to categorize: Requirements (maybe years of experience, ability to structure problems, self-starter, comfortable operating, communication skills). Qualifications (maybe experience with SQL etc). Skills (maybe tools). But we need to follow instruction: Use sections only when posting has real specific content. We can create three sections: Requirements, Qualifications, Skills. We need to allocate bullets appropriately.
We could treat:
Requirements:
- 3-5 years of experience in consulting, data analytics, investment banking, high-growth startups, or similar
- Ability to independently structure complex problems and communicate insights clearly
- Demonstrated self-starter with grit, adaptability, and a strong sense of ownership
- Comfortable operating with minimal direction in fast-paced, ambiguous environments
- Excellent written and verbal communication skills
Qualifications:
- Strong analytical foundation with experience using Excel, PowerPoint, and internal BI tools
- Experience with SQL, Tableau, Looker, or similar tools is a plus
- Hands-on experience with HubSpot or similar CRM tools preferred
- Prior experience in SaaS, B2B tech, or hospitality & travel is a plus, but not required
Skills:
Maybe we could list tools as skills: Excel, PowerPoint, internal BI tools, SQL, Tableau, Looker, HubSpot. But that duplicates. Better to keep Qualifications as skills. But we need three sections; maybe we can combine Requirements and Qualifications and leave Skills empty? But we must not create empty sections. So we need to decide.
Alternative: Use only Requirements and Qualifications sections, and maybe Skills not needed. But the instruction says we can include sections only when posting has real specific content. It doesn't require us to include all example headings. So we can omit Skills if no specific content distinct. However we have content about tools etc. Could treat them as Qualifications. Let's do:
Requirements
- 3-5 years of experience in consulting, data analytics, investment banking, high-growth startups, or similar
- Ability to independently structure complex problems and communicate insights clearly
- Demonstrated self-starter with grit, adaptability, and a strong sense of ownership
- Comfortable operating with minimal direction in fast-paced, ambiguous environments
- Excellent written and verbal communication skills
Qualifications
- Strong analytical foundation with experience using Excel, PowerPoint, and internal BI tools
- Experience with SQL, Tableau, Looker, or similar tools is a plus
- Hands-on experience with HubSpot or similar CRM tools preferred
- Prior experience in SaaS, B2B tech, or hospitality & travel is a plus, but not required
We could also add a Skills section maybe for "Tools: Excel, PowerPoint, internal BI tools, SQL, Tableau, Looker, HubSpot". But that duplicates. Better to omit Skills.
Now Benefits and Pay.
From WHY JOIN WAY?:
- Compensation: competitive salary calibrated to experience, and meaningful equity in a sustainably growing company with real value creation already realized.
- 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.
We need Benefits section: health, dental, vision, stipend maybe. Also maybe "direct access to brands" etc is more about work, not benefit. But we can include as benefit? The instruction: Benefits section only if posting actually states them. It does state health, dental, vision, stipend. Also maybe "tools" etc not typical benefit. We'll include health, dental, vision, stipend.
Pay section: compensation statement.
We could also include "Where you’ll be" as maybe Schedule? Not schedule. Could be location but not requested. We'll omit.
Thus:
Benefits
- Full health, dental, and vision coverage
- Annual hotel and travel stipend at properties and partners in Way’s global ecosystem
Pay
Competitive salary calibrated to experience, and meaningful equity in a sustainably growing company with real value creation already realized.
We should not include "The work", "The tools", "Where you’ll be" as they are not requested headings. But we might lose substantive info. However the instruction says preserve ALL substantive information. If we omit those, we lose info. But maybe we can incorporate them into Benefits or About the role? The "work" and "tools" could be considered part of Benefits? Not really. Could be part of "About the role" as description of role. Could add a paragraph after responsibilities about the work environment. But the instruction says we should not invent sections; we can add paragraphs under existing sections. For example, after responsibilities we could add a about work, tools, location. But that might be mixing categories. However it's allowed to have prose under any section.
Thus we could add a paragraph under Benefits or maybe under About the role describing the work, tools, location. But the instruction says "Use
for prose." So we can add a
under any section
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's extract content. Company description (About Way) maybe not needed as a section? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when the posting has real, specific content for it. The posting includes "ABOUT WAY" which is about the company, not the role. But we could treat that as "About the role"? Not exactly. The instruction says "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having an "About the company" section, but the list of headings given is limited to those. Probably we should stick to those headings. The "About Way" could be considered "About the role"? Not really. Might be better to omit it, as it's not requested. However we need to preserve ALL substantive information. If we omit the company description, we lose info. But maybe we can incorporate it into "About the role" as a brief description? 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 "include a section ONLY when the posting has real, specific content for it". It gives examples but not exhaustive. Could we add an "About Way" section? Possibly but safer to stick to given headings. However we need to preserve all substantive info; we could embed the company description within the "About the role" section as prose. That would preserve it.
Thus:
About the role
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.
Then responsibilities: list each bullet. We need to convert each line under KEY RESPONSIBILITIES into- .
Next: WHAT WE'RE LOOKING FOR. Need to split into Requirements, Qualifications, Skills. The bullet list includes:
- 3-5 years of experience in consulting, data analytics, investment banking, high-growth startups, or similar
- Strong analytical foundation with experience using Excel, PowerPoint, and internal BI tools
- Ability to independently structure complex problems and communicate insights clearly
- Demonstrated self-starter with grit, adaptability, and a strong sense of ownership
- Comfortable operating with minimal direction in fast-paced, ambiguous environments
- Excellent written and verbal communication skills
- Experience with SQL, Tableau, Looker, or similar tools is a plus
- Hands-on experience with HubSpot or similar CRM tools preferred
- Prior experience in SaaS, B2B tech, or hospitality & travel is a plus, but not required
We need to categorize: Requirements (maybe years of experience, ability to structure problems, self-starter, comfortable operating, communication skills). Qualifications (maybe experience with SQL etc). Skills (maybe tools). But we need to follow instruction: Use sections only when posting has real specific content. We can create three sections: Requirements, Qualifications, Skills. We need to allocate bullets appropriately.
We could treat:
Requirements:
- 3-5 years of experience in consulting, data analytics, investment banking, high-growth startups, or similar
- Ability to independently structure complex problems and communicate insights clearly
- Demonstrated self-starter with grit, adaptability, and a strong sense of ownership
- Comfortable operating with minimal direction in fast-paced, ambiguous environments
- Excellent written and verbal communication skills
Qualifications:
- Strong analytical foundation with experience using Excel, PowerPoint, and internal BI tools
- Experience with SQL, Tableau, Looker, or similar tools is a plus
- Hands-on experience with HubSpot or similar CRM tools preferred
- Prior experience in SaaS, B2B tech, or hospitality & travel is a plus, but not required
Skills:
Maybe we could list tools as skills: Excel, PowerPoint, internal BI tools, SQL, Tableau, Looker, HubSpot. But that duplicates. Better to keep Qualifications as skills. But we need three sections; maybe we can combine Requirements and Qualifications and leave Skills empty? But we must not create empty sections. So we need to decide.
Alternative: Use only Requirements and Qualifications sections, and maybe Skills not needed. But the instruction says we can include sections only when posting has real specific content. It doesn't require us to include all example headings. So we can omit Skills if no specific content distinct. However we have content about tools etc. Could treat them as Qualifications. Let's do:
- 3-5 years of experience in consulting, data analytics, investment banking, high-growth startups, or similar
- Ability to independently structure complex problems and communicate insights clearly
- Demonstrated self-starter with grit, adaptability, and a strong sense of ownership
- Comfortable operating with minimal direction in fast-paced, ambiguous environments
- Excellent written and verbal communication skills
- Strong analytical foundation with experience using Excel, PowerPoint, and internal BI tools
- Experience with SQL, Tableau, Looker, or similar tools is a plus
- Hands-on experience with HubSpot or similar CRM tools preferred
- Prior experience in SaaS, B2B tech, or hospitality & travel is a plus, but not required
- Full health, dental, and vision coverage
- Annual hotel and travel stipend at properties and partners in Way’s global ecosystem
Requirements
Qualifications
Benefits
Pay
Competitive salary calibrated to experience, and meaningful equity in a sustainably growing company with real value creation already realized.
We should not include "The work", "The tools", "Where you’ll be" as they are not requested headings. But we might lose substantive info. However the instruction says preserve ALL substantive information. If we omit those, we lose info. But maybe we can incorporate them into Benefits or About the role? The "work" and "tools" could be considered part of Benefits? Not really. Could be part of "About the role" as description of role. Could add a paragraph after responsibilities about the work environment. But the instruction says we should not invent sections; we can add paragraphs under existing sections. For example, after responsibilities we could add aabout work, tools, location. But that might be mixing categories. However it's allowed to have prose under any section. Thus we could add a paragraph under Benefits or maybe under About the role describing the work, tools, location. But the instruction says "Use
for prose." So we can add a
under any section