Account Executive - Midmarket
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the job posting content: It's a bit messy: starts with Allegion description, then Waitwhile description, then job summary, responsibilities, what you need to succeed, why you'll love Waitwhile, why work for us (Allegion benefits), compensation, etc.
We need to extract substantive content: About the role? Could be the job summary. Responsibilities: "What You Will Do" bullet list. Requirements/Qualifications: "What You Need To Succeed". Skills: maybe "Familiarity with tools...". Benefits: "Why You’ll Love Waitwhile" and "Why Work for Us?" includes benefits like unlimited PTO, health insurance, 401k match, etc. Pay: "Compensation: ... expected Base Salary Range: $80,000 to $100,000. Bonus Eligible: Yes". Schedule: maybe hybrid details: "This role offers the benefits of our dynamic hybrid work model—combining in-person collaboration for meaningful moments with the flexibility of remote work." Also "Since hybrid arrangements can vary... your talent acquisition partner will provide specific hybrid details". Also "While this is the current structure and we currently have no plans to change, we reserve the right to make changes to the hybrid schedule as needed". So schedule info exists.
We must not include filler like "commensurate with experience". The compensation section is specific: base salary range $80k-$100k, bonus eligible yes. That's substantive.
We must not repeat job title as heading. So no
Account Executive-Midmarket-Chicago, IL (Hybrid). We'll not include that.
We need to output only HTML fragment, no /, no markdown fences.
We need to decide sections: maybe About the role (job summary), Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We must ensure each section has real content.
Let's extract content:
About the role (Job Summary): "As a Mid-Market Account Executive, you’ll own the full sales cycle — from prospecting and discovery to negotiation and close — with a focus on mid-market customers across key industries like retail, finance, government, education and healthcare. You’ll work closely with marketing and customer success teams to build pipeline, run tailored demos, and help shape the next stage of Waitwhile’s growth story."
We could also include the Waitwhile company description? Might be considered about the role? Probably not needed; but we can include a brief about Waitwhile as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include the Waitwhile description as part of About the role? It's about the company, not the role. Might be considered "About the company". But we only have headings for About the role, Responsibilities, etc. Could we add an "About the company" section? Not in allowed headings list. The allowed headings are those listed; we should stick to them. So we can incorporate company description into About the role? Might be okay but could be considered not exactly role. However we need to preserve all substantive info; we could put it in a
under About the role. It's not violating any rule.
Responsibilities: list from "What You Will Do". Items:
- Own the full sales cycle
- Manage opportunities from first conversation to close.
- Focus on deals in the $30K–$150K ARR range.
- Build pipeline strategically
- Partner with BDRs and Marketing to target the right accounts and industries.
- You will be expected to drive pipeline through inbound and self-sourced outbound opportunities.
- Run world-class demos and presentations
- Partner with sales engineers to build custom tailored demos
- Tailor messaging and ROI storytelling to each buyer persona
- Be an expert on Waitwhile and the value that it brings each buyer persona
- Negotiate and close deals
- Deliver deals that create value for our customers and Waitwhile
- Ensure that a deal is a good fit for Waitwhile and that we will continue to drive value over time
- Collaborate cross-functionally
- Partner with Sales, Marketing, and RevOps to ensure alignment across campaigns, handoffs, and messaging.
- Provide feedback from frontline prospecting to inform content, targeting, and product positioning with Marketing, Product, and CS to ensure smooth handoffs and impactful onboarding.
- Track and forecast
- Track all leads from top of funnel to close accurately in CRM (Hubspot) and contribute to data-driven pipeline reviews.
- Own timelines and estimated closes for all deals.
We can condense but must preserve all substantive info; we can keep each as
- .
Requirements/Qualifications: "What You Need To Succeed":
- 4–6+ years of B2B SaaS sales experience, with proven success in closing mid-market or upper-SMB deals.
- Consistent track record of meeting or exceeding quota.
- Excellent communication, negotiation, and storytelling skills.
- Strong understanding of consultative and value-based selling.
- Ability to navigate complex buying committees and multithread deals.
- Experience selling to retail, education, or enterprise services is a plus.
- Familiarity with tools like ZoomInfo, HubSpot, Chorus, and Notion.
We could treat this as Requirements.
Skills: maybe the tools familiarity could be Skills, but we already have them in Requirements. Could separate Skills: "Familiarity with tools like ZoomInfo, HubSpot, Chorus, and Notion." Also maybe "Excellent communication, negotiation, and storytelling skills." But we can keep them under Requirements.
Benefits: from "Why You’ll Love Waitwhile" and "Why Work for Us?" plus Allegion benefits.
Why You’ll Love Waitwhile:
- Opportunity to design and own a brand-new outbound motion at a fast-growing SaaS company.
- Fully remote team with flexible hours and an inclusive culture.
- Collaborative, low-ego environment where new ideas are welcomed and tested.
- Chance to work with globally recognized brands and make a visible impact on growth.
- Backed by Allegion (NYSE:ALLE), a $3B global leader in access management, we have financial stability, extremely good benefits and resources to grow.
- Waitwhile has a positive, diverse, and supportive culture—we look for people who are curious, inventive, and work to be a little better every single day.
- We aim to be smart, humble, hardworking and, above all, collaborative.
Why Work for Us? (Allegion benefits):
- Health, dental and vision insurance coverage, helping you “be safe, be healthy”
- Unlimited Paid Time Off
- A commitment to your future with a 401K plan, which currently offers a 6% company match and no vesting period
- Health Savings Accounts – Tax-advantaged savings account used for healthcare expenses
- Flexible Spending Accounts – Tax-advantaged spending accounts for healthcare and/or dependent daycare expenses
- Disability Insurance – Short-Term and Long-Term coverage, paid for by Allegion, provides income replacement for illness or injury
- Life Insurance – Term life coverage with the option to purchase supplemental coverage
- Tuition Reimbursement
- Voluntary Wellness Program – Simply complete wellness activities and earn monetary rewards
- Employee Discounts through Perks at Work
- Community involvement and opportunities to give back so you can “serve others, not yourself”
- Opportunities to leverage your unique strengths through CliftonStrengths assessment & coaching
We should combine these into Benefits section.
Pay: "Compensation: This range is provided by Allegion. Your actual pay will be based on your skills and experience. The expected Base Salary Range: $80,000 to $100,000. The actual compensation will be determined based on experience and other factors permitted by law. Bonus Eligible: Yes"
Schedule: hybrid details: "This role offers the benefits of our dynamic hybrid work model—combining in-person collaboration for meaningful moments with the flexibility of remote work. Since hybrid arrangements can vary based on the needs of the individual, team and business, your talent acquisition partner will provide specific hybrid details about this role. We are committed to fostering a healthy work-life balance and building meaningful connections, ensuring you have the tools, resources, and support needed to excel in any environment. Together, we’ll unlock your potential and create a lasting impact. While this is the current structure and we currently have no plans to change, we reserve the right to make changes to the hybrid schedule as needed at the Company’s discretion."
We need to ensure we don't include filler like "commensurate with experience". Not present.
We must not include duplicated lines. There's duplicated "Why You’ll Love Waitwhile" paragraph repeated twice; we should include only once.
Also duplicated "We aim to be smart, humble, hardworking and, above all, collaborative." appears twice; include once.
Also duplicated "Waitwhile has a positive, diverse, and supportive culture—we look for people who are curious, inventive, and work to be a little better every single day." appears twice; include once.
Also duplicated "If this sounds like a good fit for you, why not say hello?" appears twice; include once.
We should remove application instructions like "Apply Today! Join our team of experts today and help us make tomorrow’s world a safer place!" and the EEO boilerplate etc. Also remove "Not sure if your experience perfectly aligns..." etc. Also remove "We Celebrate Who We Are!" etc. Also remove legal/footer.
Now craft HTML.
We'll have sections:
About the role
... (including Waitwhile description and job summary)
Responsibilities
- ... each bullet
Requirements
- ... each bullet
Skills
- Familiarity with tools like ZoomInfo, HubSpot, Chorus, and Notion.
But we might also include communication etc under Skills; but we already have them under Requirements. Could move communication etc to Skills. However we need to avoid thin sections. Perhaps combine Requirements and Skills into one section "Requirements and Skills". But allowed headings include Requirements, Skills separately. We could have both but ensure each has substantive content.
Let's assign:
Requirements: experience, quota, communication, negotiation, storytelling, consultative selling, navigating committees, experience selling to retail/education/enterprise (plus). That's substantive.
Skills: familiarity with tools.
Alternatively, we could put communication etc under Skills and keep Requirements for experience and quota. But we need to avoid thin sections; both will have multiple items.
Let's do:
Requirements
- 4–6+ years of B2B SaaS sales experience, with proven success in closing mid-market or upper‑SMB deals.
- Consistent track record of meeting or exceeding quota.
- Experience selling to retail, education, or enterprise services is a plus.
Skills
- Excellent communication, negotiation, and storytelling skills.
- Strong understanding of consultative and value‑based selling.
- Ability to navigate complex buying committees and multith
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the job posting content: It's a bit messy: starts with Allegion description, then Waitwhile description, then job summary, responsibilities, what you need to succeed, why you'll love Waitwhile, why work for us (Allegion benefits), compensation, etc. We need to extract substantive content: About the role? Could be the job summary. Responsibilities: "What You Will Do" bullet list. Requirements/Qualifications: "What You Need To Succeed". Skills: maybe "Familiarity with tools...". Benefits: "Why You’ll Love Waitwhile" and "Why Work for Us?" includes benefits like unlimited PTO, health insurance, 401k match, etc. Pay: "Compensation: ... expected Base Salary Range: $80,000 to $100,000. Bonus Eligible: Yes". Schedule: maybe hybrid details: "This role offers the benefits of our dynamic hybrid work model—combining in-person collaboration for meaningful moments with the flexibility of remote work." Also "Since hybrid arrangements can vary... your talent acquisition partner will provide specific hybrid details". Also "While this is the current structure and we currently have no plans to change, we reserve the right to make changes to the hybrid schedule as needed". So schedule info exists. We must not include filler like "commensurate with experience". The compensation section is specific: base salary range $80k-$100k, bonus eligible yes. That's substantive. We must not repeat job title as heading. So no
Account Executive-Midmarket-Chicago, IL (Hybrid). We'll not include that. We need to output only HTML fragment, no /, no markdown fences. We need to decide sections: maybe About the role (job summary), Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must ensure each section has real content. Let's extract content: About the role (Job Summary): "As a Mid-Market Account Executive, you’ll own the full sales cycle — from prospecting and discovery to negotiation and close — with a focus on mid-market customers across key industries like retail, finance, government, education and healthcare. You’ll work closely with marketing and customer success teams to build pipeline, run tailored demos, and help shape the next stage of Waitwhile’s growth story." We could also include the Waitwhile company description? Might be considered about the role? Probably not needed; but we can include a brief about Waitwhile as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include the Waitwhile description as part of About the role? It's about the company, not the role. Might be considered "About the company". But we only have headings for About the role, Responsibilities, etc. Could we add an "About the company" section? Not in allowed headings list. The allowed headings are those listed; we should stick to them. So we can incorporate company description into About the role? Might be okay but could be considered not exactly role. However we need to preserve all substantive info; we could put it in a
under About the role. It's not violating any rule. Responsibilities: list from "What You Will Do". Items: - Own the full sales cycle - Manage opportunities from first conversation to close. - Focus on deals in the $30K–$150K ARR range. - Build pipeline strategically - Partner with BDRs and Marketing to target the right accounts and industries. - You will be expected to drive pipeline through inbound and self-sourced outbound opportunities. - Run world-class demos and presentations - Partner with sales engineers to build custom tailored demos - Tailor messaging and ROI storytelling to each buyer persona - Be an expert on Waitwhile and the value that it brings each buyer persona - Negotiate and close deals - Deliver deals that create value for our customers and Waitwhile - Ensure that a deal is a good fit for Waitwhile and that we will continue to drive value over time - Collaborate cross-functionally - Partner with Sales, Marketing, and RevOps to ensure alignment across campaigns, handoffs, and messaging. - Provide feedback from frontline prospecting to inform content, targeting, and product positioning with Marketing, Product, and CS to ensure smooth handoffs and impactful onboarding. - Track and forecast - Track all leads from top of funnel to close accurately in CRM (Hubspot) and contribute to data-driven pipeline reviews. - Own timelines and estimated closes for all deals. We can condense but must preserve all substantive info; we can keep each as
About the role
... (including Waitwhile description and job summary)
Responsibilities
- ... each bullet
Requirements
- ... each bullet
Skills
- Familiarity with tools like ZoomInfo, HubSpot, Chorus, and Notion.
Requirements
- 4–6+ years of B2B SaaS sales experience, with proven success in closing mid-market or upper‑SMB deals.
- Consistent track record of meeting or exceeding quota.
- Experience selling to retail, education, or enterprise services is a plus.
Skills
- Excellent communication, negotiation, and storytelling skills.
- Strong understanding of consultative and value‑based selling.
- Ability to navigate complex buying committees and multith