Jobs · Business Development · New York

Enterprise Account Executive

REGAL · New York, NY · 3 wk ago
HybridBusiness Development$82/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications?), Benefits, maybe Pay/Schedule if present. The posting includes "ABOUT US" but we should not repeat job title as heading; we can include About Us? 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 posting has real, specific content for it. We have About the role content (under ABOUT THE ROLE). We have Responsibilities. We have ABOUT YOU which is qualifications/requirements. We have BENEFITS/PERKS. We have POSITION LOCATION & OFFICE DETAILS (maybe schedule? Not exactly schedule but location). There's no explicit Pay or Schedule details (they mention compensation but not specific numbers). So we should not create Pay or Schedule sections because no specific content. We could include a section for Location? Not in list but we could maybe put under "Schedule"? Not appropriate. Better to omit location if not requested. The instruction says use those headings as examples; we can also add other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they expect those. We could include "About Us" maybe not needed. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include About Us as a heading? Not in list but could be okay. However they said prefer a few substantive sections over many thin ones. So we could combine About Us into About the role? Probably better to include About Us as a separate section? But they didn't list About Us as example; but we could still use

for About Us. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive. So we can add About Us. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some AI hiring process note; that's not boilerplate? It's about hiring process; maybe we should keep? It's not EEO etc. It's about AI tools usage. Might be considered boilerplate? It's not typical legal; but it's about hiring process. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools note is not exactly those; but could be considered part of hiring process description; maybe keep? It's not application instructions (like how to apply). It's a statement about AI usage. I'd keep it as part of the description maybe under About Us or a separate note. But to be safe, we could keep it as a paragraph under About Us. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from About Us, About the role, Responsibilities, About You, Benefits/Perks, Position location & office details, and the AI tools note. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have, so include Benefits section. Pay: they mention compensation but not specific numbers; they say "The reasonably estimated on-target earnings for this role is provided as a range within this job description." Actually they didn't provide a range; they just say it's provided as a range within this job description, but no range given. So we should not create Pay section because no specific content. Schedule: they mention hybrid roles required in office T/W/TH and office optional M/F. That is schedule info. So we could create a Schedule section with that detail. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state schedule (hybrid). So we can include Schedule section. Thus sections: About Us, About the role, Responsibilities, Requirements (or Qualifications), Benefits, Schedule. We need to use
  • for any list of duties/requirements/benefits. So for Responsibilities list, About You list (requirements), Benefits list. We need to use

    for prose. We must not include markdown code fences. Output only HTML fragment. Let's extract content. About Us: "Founded in 2020, Regal is the AI Agent Platform. Regal gives every company the tools to transform customer communications with delightful AI Agents that are connected to your data, easy to customize and monitor, always available, and ready to take action. Power better support, sales, and operations – with way less effort. Our founders, Alex Levin and Rebecca Greene, helped build Angi (Angie’s List, HomeAdvisor, and Handy) to over $1.5B in revenue. Based in Manhattan, we’re building an in-person culture of entrepreneurs who want to win and build something meaningful. We’re backed by top investors including Founder Collective, Homebrew, and Emergence Capital. Come join us as we create a category-defining company, and follow Regal's company page on LinkedIn to stay up-to-date on our journey and current job openings! We’re moving fast, and the numbers speak for themselves: Partnered with enterprise brands like Google, AAA, Ro, Coursera Raised $82M (top tier investors including Emergence & Homebrew) Completed 500M+ calls Driven $7B revenue for customers Scaled to $##M ARR Built amazing NYC (Midtown) in office culture" Note: there is "$##M ARR" placeholder; we should keep as is? It's placeholder but it's in the posting. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. This is about headings with filler text. The placeholder "$##M ARR" is inside a paragraph, not a heading. It's okay to keep. We should not include the "Come join us as we create a category-defining company, and follow Regal's company page on LinkedIn to stay up-to-date on our journey and current job openings!" That's somewhat promotional but still substantive. Keep. About the role: "At Regal, we’re transforming how businesses engage customers with powerful, customizable AI Agents. As an Enterprise Account Executive, you’ll play a critical role in driving new business by sourcing and generating pipeline, navigating complex sales cycles, and closing new business with large, strategic organizations. You’ll engage senior executives across marketing, sales, and technology, craft compelling pitches, and partner closely with leadership, marketing, and BDRs to execute account strategies. This role is ideal for a driven seller who thrives on building new relationships at the executive level, guiding organizations through Regal’s value proposition, and crafting business cases that demonstrate clear ROI. You’ll make a lasting impact by helping us define the category and transform customer engagement for enterprise-scale businesses. Our team is looking for a driven and passionate seller who can speak with conviction, craft compelling pitches, and is eager to make a lasting impact at their next AI company!" Responsibilities list: - Drive revenue for Regal’s AI Agent platform by closing complex, enterprise-scale deals that demonstrate clear ROI and transformation potential - Consistently meet and exceed quarterly and annual sales targets - Build and maintain a high-quality pipeline through outbound prospecting, AI-assisted tools, and strategic outreach - Engage senior stakeholders (CMO, CRO, CTO, CIO) and guide them through Regal’s value proposition with a consultative, outcomes-focused approach - Craft and evaluate business cases that quantify ROI and align Regal’s solutions with customer objectives - Collaborate with leadership, marketing, and BDRs to create and execute multi-threaded account strategies - Stay current on AI trends, buyer needs, and the competitive landscape to drive informed, strategic conversations About You (requirements): - 5-7+ years of full-cycle SaaS sales experience with a proven track record of exceeding quota in enterprise sales - Success selling into executive buyers across marketing, sales, and technology functions - Skilled at managing complex sales cycles and engaging multiple stakeholders in consultative, strategic conversations - Experience with AI, automation, or conversational platforms strongly preferred - Demonstrated ability to build and analyze business cases that highlight ROI for customers - Strong ownership mindset with examples of delivering exceptional results - Excited to shape the future of customer engagement in a dynamic, category-defining environment Benefits/Perks: - We care about your health! Medical, Dental, and Vision plans - 80% covered by the company - Flexible PTO & 11 paid holidays/year - We care about future you! 401k Plan, Paid parental leave, Pre-tax commuter benefits - We care about connection! In-office breakfast and snacks daily, Happy hours, team outings, & annual off-sites, Complete laptop workstation & more to come! Position Location & Office Details: "This position is only available in New York City (HQ- Midtown). Hybrid roles are required in office T/W/TH and office optional M/F. If you think you’re missing relevant experience but you’re hungry and a fast learner (and can prove it), we want to hear from you! We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us." We need to exclude application instructions like "If you think you’re missing relevant experience but you’re hungry and a fast learner (and can prove it), we want to hear from you!" That's somewhat encouraging to apply but not explicit instruction. Might be considered application encouragement; but it's not a direct instruction like "apply here". Might keep? The instruction: remove application instructions. This line is encouraging to apply; could be considered application instruction. Safer to remove that sentence. Also the AI tools note is not application instruction; it's about hiring process. Keep. Thus location/hybrid schedule: we can put in Schedule section: "This position is only available in New York City (HQ- Midtown). Hybrid roles are required in office T/W/TH and office optional M/F." plus maybe the AI tools note? That note is not schedule; maybe we can put under About Us or a separate note. But we could include a separate section "Hiring Process" but not in list. Better to incorporate AI tools note into a paragraph under About Us or a separate

    after Benefits. Since it's substantive, we should keep it somewhere. Perhaps add a section "Hiring Process" but not required. Could just add a

    after Benefits. We must not repeat job title as heading. We'll not. Now construct HTML. We'll have:

    About Us

    Founded in 2020, Regal is the AI Agent Platform. Regal gives every company the tools to transform customer communications with delightful AI Agents that are connected to your data, easy to customize and monitor, always available, and ready to take action. Power better support, sales, and operations – with way less effort. Our founders, Alex Levin and Rebecca Greene, helped build Angi (Angie’s List, HomeAdvisor, and Handy) to over $1.5B in revenue. Based in Manhattan, we’re building an in-person culture of entrepreneurs who want to win and build something meaningful. We’re backed by top investors including Founder Collective, Homebrew, and Emergence Capital. Come join us as we create a category-defining company, and follow Regal

Similar jobs