Strategic Account Executive

We need to output HTML fragment with sections for headings present: About the role? Actually the posting includes "About HappyRobot" then "Role Overview" then bullet list of responsibilities, then "Must have" (requirements), then "Why join us?" (benefits?), then "Our Operating Principles" (maybe not needed). We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections where there is real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate like privacy policy etc. We need to preserve all substantive information. So we need to extract: - About HappyRobot: description of company. Could be placed under a heading? Possibly "About the role" is not present; we have "About HappyRobot". 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? It says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect those standard headings. But we have "About HappyRobot" which is about company, not role. Could we treat as "About the role"? Not exactly. Maybe we can omit that section because it's not one of the prescribed headings? However we need to preserve ALL substantive information. If we omit it, we lose info. But we could incorporate it into a

without heading? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but suggests using those for sections. Safer to include a heading like "About HappyRobot" as

maybe? It's not in the list but still a section heading. The instruction says use

for section headings (e.g. About the role, Responsibilities...). It implies those are examples; we can use

for any section heading. So we can use

About HappyRobot

. Then after that we have "Role Overview" which could be a heading. Could be

Role Overview

. Then responsibilities list under that. Then "Must have" which is requirements/qualifications. Could be

Requirements

or

Qualifications

. We'll choose Requirements. Then "Why join us?" includes benefits and competitive salary + equity. So we can make a Benefits section. Also there is "Our Operating Principles" which is not requested but could be omitted? It's substantive but not a standard heading. Could we include as a section? The instruction says prefer a few substantive sections over many thin ones. Could include Operating Principles as a section maybe under

Operating Principles

. But not in the list; still okay. We must not include Pay/Schedule/Benefits unless posting actually states them. Benefits: "Comprehensive Benefits including healthcare, dental, vision coverage. Competitive salary + equity in a high-growth startup." That's benefits and pay (salary+equity). So we can include Benefits section with that info. Pay: we have competitive salary + equity; we could include Pay section but maybe combine with Benefits. Since they said only create Pay/Schedule/Benefits sections if posting actually states them. It does state benefits and compensation. Could make Benefits section with that info; Pay maybe redundant. We'll just include Benefits. Schedule: not mentioned, so omit. Now we need to remove boilerplate: privacy policy, data processing, etc. Also remove "Learn more about our vision in our manifesto." maybe keep? It's part of About HappyRobot? It's a line: "Learn more about our vision in our manifesto." That's substantive? It's a reference; we can keep. Also remove duplicated lines, application instructions. Now produce HTML:

About HappyRobot

HappyRobot is the infrastructure for enterprises to build and orchestrate AI workforces. Our AI workers don't just communicate through voice and email - they make decisions, take action, and run operations autonomously across entire enterprise systems. Born in Y Combinator (S23) and backed by a16z, Base10, Prysm Capital and Eurazeo with over $150M raised, we power critical operations for global enterprises worldwide. Our platform is battle-tested in the most demanding environments, where AI has real consequences. We started in logistics, built our own voice stack, models, and orchestration layer from the ground up, and are now bringing that infrastructure to every enterprise that runs the real economy. Learn more about our vision in our manifesto.

Role Overview

We are looking for a highly driven Strategic Account Executive to join our growing sales team. In this role, you will be responsible for managing the full sales cycle, building strong relationships with enterprise clients, and driving revenue growth.

Responsibilities

• Enterprise Sales Execution - Own the full sales cycle from prospecting to closing enterprise-level deals.
• Pipeline Management - Develop and maintain a robust pipeline of enterprise accounts, ensuring consistent deal flow.
• Consultative Selling - Understand client challenges, industry trends, and business goals to position our SaaS solution effectively.
• Relationship Building - Establish and nurture long-term relationships with key stakeholders and decision-makers.
• Strategic Negotiations - Lead complex negotiations, ensuring a win-win outcome for both the client and the company.
• Cross-functional Collaboration - Work closely with Sales Engineering, Customer Success, and Product teams to deliver tailored solutions.
• Revenue Growth - Meet and exceed sales targets, contributing to the company's overall revenue goals.
• Market Insights - Stay informed about industry trends, competitor activity, and market shifts to refine sales strategies.

Requirements

• Experience in enterprise sales, preferably in the SaaS industry.
• Proven track record of consistently meeting or exceeding sales quotas in a B2B environment.
• Large ACV track record
• Strong experience managing complex sales cycles and working with multiple stakeholders.
• Excellent communication, negotiation, and presentation skills.
• Ability to analyze customer needs and align them with the right solutions.
• Experience with CRM tools such as Salesforce, HubSpot, or similar platforms.
• Ability to thrive in a fast-paced, high-growth environment.

Benefits

• Comprehensive Benefits including healthcare, dental, vision coverage.
• Competitive salary + equity in a high-growth startup.

Optionally include Operating Principles but might be too many sections. The instruction: "Prefer a few substantive sections over many thin ones." Operating Principles is a substantive block but could be considered thin? It's a list of principles. Might be okay to include as a section. However we already have About HappyRobot, Role Overview, Responsibilities, Requirements, Benefits. That's 5 sections. Adding Operating Principles makes 6. Still okay. But we need to see if it's required to preserve all substantive information. The Operating Principles section contains details about company culture. If we omit, we lose that info. So better to include. Let's add:

Operating Principles

• Extreme Ownership – We take full responsibility for our work, outcomes, and team success. No excuses, no blame-shifting — if something needs fixing, we own it and make it better.
• Craftsmanship – Putting care and intention into every task, striving for excellence, and taking deep ownership of the quality and outcome of your work.
• We are “majos” – Be friendly & have fun with your coworkers. Always be genuine & honest, but kind.
• Urgency with Focus – Create the highest impact in the shortest amount of time. Move fast, but in the right direction.
• Talent Density and Meritocracy – Hire only people who can raise the average; ‘exceptional performance is the passing grade.’
• First-Principles Thinking – Strip a problem to physics-level facts, ignore industry dogma, rebuild the solution from scratch.

We need to ensure we preserve the text exactly as given, not invent or summarize away detail. We have paraphrased some bullet points (like adding dash). The original text for each principle is a paragraph. We could keep as

but they said use

• for any list of duties/requirements/benefits. Operating Principles is a list; we can use
  • . Ensure we keep the substance. Let's extract each principle text exactly: From posting: "Extreme Ownership We take full responsibility for our work, outcomes, and team success. No excuses, no blame-shifting — if something needs fixing, we own it and make it better. This means stepping up, even when it’s not “your job.” If a ball is dropped, we pick it up. If a customer is unhappy, we fix it. If a process is broken, we redesign it. We don’t wait for someone else to solve it — we lead with accountability and expect the same from those around us." "Craftsmanship Putting care and intention into every task, striving for excellence, and taking deep ownership of the quality and outcome of your work. Craftsmanship means never settling for “just fine.” We sweat the details because details compound. Whether it’s a product feature, an internal doc, or a sales call — we treat it as a reflection of our standards. We aim to deliver jaw-dropping customer experiences by being curious, meticulous, and proud of what we build — even when nobody’s watching. We are “majos” Be friendly & have fun with your coworkers. Always be genuine & honest, but kind. “Majo” is our way of saying: be a good human. Be approachable, helpful, and warm. We’re building something ambitious, and it’s easier (and more fun) when we enjoy the ride together. We give feedback with kindness, challenge each other with respect, and celebrate wins together without ego." "Urgency with Focus Create the highest impact in the shortest amount of time. Move fast, but in the right direction. We operate with speed because time is our most limited resource. But speed without focus is chaos. We prioritize ruthlessly, act decisively, and stay aligned. We aim for high leverage: the biggest results from the simplest, smartest actions. We’re running a high-speed marathon — not a sprint with no strategy." "Talent Density and Meritocracy Hire only people who can raise the average; ‘exceptional performance is the passing grade.’ Ability trumps seniority. We believe the best teams are built on talent density — every hire should raise the bar. We reward contribution, not titles or tenure. We give ownership to those who earn it, and we all hold each other to a high standard. A-players want to work with other A-players — that’s how we win." "First-Principles Thinking Strip a problem to physics-level facts, ignore industry dogma, rebuild the solution from scratch. We don’t copy-paste solutions. We go back to basics, ask why things are the way they are, and rebuild from the ground up if needed. This mindset pushes us to innovate, challenge stale assumptions, and move faster than incumbents. It’s how we build what others think is impossible." We also have "We are “majos”" appears inside Craftsmanship paragraph; but we already captured. We'll put each principle as
  • with the full paragraph. Now ensure we didn't include any boilerplate like privacy policy etc. Now produce final HTML fragment. Check that we didn't repeat