Account Executive, Mid-Market | North America

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are Is What We Do." That's company description. Should we include as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have responsibilities (English and French). Requirements (English and French). Benefits (English and French). Also there is "Total Rewards" and "Rémunération Globale" which talk about compensation but not specific numbers. It says "Your offer will be localized...". No specific pay range given. So we should not create Pay section because no specific numbers. Benefits we have list. Also there is "Stock grant opportunities" under Total Rewards. That's a benefit? Could be part of Benefits. But we already have benefits list; we could add that as bullet. We must not repeat job title as heading. The job title appears: "Account Executive, Marché intermédiaire | Amérique du Nord". We should not put that as heading. We need to preserve all substantive information; remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines (the French and English duplicate content). We need to keep content but not duplicate? The posting includes both English and French sections. We should keep the substantive info; but we can combine? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to avoid repeating same info in both languages. We could keep one language version (maybe English) and drop the French duplicate. But we must preserve all substantive information; if we drop French, we lose that language info but it's duplicate of English. So it's okay to remove duplicate lines. We'll keep English version for responsibilities, requirements, benefits. Also we have "Total Rewards" section with stock grant opportunities etc. That's substantive and not duplicated elsewhere. We'll include that as maybe "Benefits" or separate? Since we already have Benefits section, we could add stock grant opportunities there. But the instruction: Prefer a few substantive sections over many thin ones. So we can have sections: Responsibilities, Requirements, Benefits (including stock grant opportunities). Also maybe "About the role" could be the company description at start. That's substantive. We'll include an "About the role" section with the company description (the first paragraphs). That is not duplicated. We'll not include "Who We Are Is What We Do." as heading; we use About the role. We must not include Pay or Schedule sections because no specific info. We must not include application instructions, EEO, legal, etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Deel is the all-in-one payroll and HR platform for global teams. Our vision is to unlock global opportunity for every person, team, and business. Built for the way the world works today, Deel combines HRIS, payroll, compliance, benefits, performance, and equipment management into one seamless platform. With AI-powered tools and a fully owned payroll infrastructure, Deel supports every worker type in 150+ countries—helping businesses scale smarter, faster, and more compliantly. Among the largest globally distributed companies in the world, our team of 7,000 spans more than 100 countries, speaks 74 languages, and brings a connected and dynamic culture that drives continuous learning and innovation for our customers. As the fastest-growing SaaS company in history, Deel is transforming how global talent connects with world-class companies – breaking down borders that have traditionally limited both hiring and career opportunities. We're not just building software; we're creating the infrastructure for the future of work, enabling a more diverse and inclusive global economy. In 2024 alone, we paid $11.2 billion to workers in nearly 100 currencies and provided healthcare and benefits to workers in 109 countries—ensuring people get paid and protected, no matter where they are. Our momentum is reflected in our achievements and customer satisfaction: CNBC Disruptor 50, Forbes Cloud 100, Deloitte Fast 500, and repeated recognition on Y Combinator's top companies list – all while maintaining a 4.83 average rating from 15,000 reviews across G2, Trustpilot, Capterra, Apple and Google. Your experience at Deel will be a career accelerator. At the forefront of the global work revolution, you'll tackle complex challenges that impact millions of people's working lives. With our momentum—backed by a $17.3 billion valuation and $1 B in Annual Recurring Revenue (ARR) in just over five years—you'll drive meaningful impact while building expertise that makes you a sought-after leader in the transformation of global work.

Responsibilities

• Develop and own a targeted account list and develop a territory plan for winning business with companies between 201-2,000 employees
• Manage the customer buying journey from start to finish, providing subject matter expertise and guidance to prospective customers
• Meet or exceed monthly and yearly revenue targets
• Continually develop a robust sales pipeline through individual outreach, collaborating with your sales development representative, and managing inbound prospects
• Keep CRM system up to date with customer information, forecasts, and pipeline data so we can learn more about our business and our sales process

Requirements

• Geographically based in the US or Canada
• 4+ years of full sales cycle experience, featuring a minimum of 2 years in SaaS and 1 year successfully selling into mid-market accounts
• A track record of developing a greenfield territory, executing across the full sales cycle, and adding net new logos
• Ability to work in cross-functional teams to ensure Customer Success and Satisfaction
• Desire to work for a fast-paced startup and take on increasing levels of responsibility

Benefits

• Health Insurance Effective from Day 1 (Medical, Dental, & Vision)
• 401k Retirement Plan
• Disability Insurance
• Life Insurance
• Employee Assistance Program (EAP)
• Flexible Savings Account (FSA)
• Flexible time off (PTO)
• 12 paid holidays per year
• Parental leave: 16 weeks for the birthing parent and 8 weeks for the non-birthing parent
• Stock grant opportunities

We should not include "Total Rewards" heading separately; we incorporated stock grant opportunities into Benefits. Check for any leftover boilerplate: we removed French duplicate, EEO, legal, application instructions, accessibility, AI usage, etc. We kept all substantive info: company description, responsibilities, requirements, benefits (including stock grant). Did we miss any other substantive info like "Rémunération Globale" about compensation? It mentions stock grant opportunities and flexible work, but we already captured stock grant. The flexible work mention: "La flexibilité du travail à distance, incluant un accès optionnel aux espaces WeWork." That's a benefit (remote work flexibility). Should we add that as benefit. It's not in the English benefits list. The English benefits list didn't mention remote work flexibility. So we should add that as a benefit bullet. Also "Des opportunités d'attribution d'actions (stock options)" we already have stock grant. Also "Des avantages et privilèges supplémentaires basés sur votre statut d'emploi et votre pays." That's vague; we can't invent specifics. So we ignore vague. Thus add benefit: "Flexible remote work with optional access to WeWork spaces." Also the English benefits list didn't mention remote work; we should add. Let's add bullet: "Flexible remote work with optional access to WeWork spaces." Now ensure we didn't miss any other substantive info: The "Total Rewards" also says "Our salary range reflects gross base salary. For commercial roles with commission eligibility, this figure represents On-Target Earnings (OTE), inclusive of base salary and target commission.Salary ranges are quoted in USD as a consistent global reference. Your offer will be localized to your country's currency using a market-aligned conversion.Final pay is based on objective, job-related criteria including experience, skills, and location.We don't ask about salary history. Offers are based on the role and what you bring to it." This is generic compensation description but no specific numbers or range. According to instruction, we should not create Pay section unless posting actually states them. It does not state specific pay range or numbers. So we should not create Pay section. However the info about compensation is substantive but it's generic; still we could include it under Benefits? But it's about pay. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (we have). It does not state specific pay. So we should not add a Pay section. The generic compensation description could be considered part of Benefits? But it's about pay; better to omit as it's not specific. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit that generic compensation description as it's not specific numbers. It's still substantive but maybe we could include as a paragraph under Benefits? However it's about pay, not benefits. The instruction says do not create Pay section unless posting actually states them. It does state some info about pay (salary range reflects gross base salary, OTE, etc). That is stating something about pay, albeit not numbers. But it's still stating pay info. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (some info). So we could create a Pay section with that info. However we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The posting says: "Your offer will be localized to your country's currency using a market-aligned conversion.Final pay is based on objective, job-related criteria including experience, skills, and location.We don't ask about salary history. Offers are based on the role and what you bring to it." That's not filler; it's substantive. So we could include a Pay section. But we must also consider that we already have Benefits section; adding Pay section is okay. We need to decide: The instruction says "Prefer a few substantive sections over many thin ones." Adding Pay section would make three sections (About, Responsibilities, Requirements, Benefits, Pay) = 5 sections. That's okay if each has substantive content. We have About role (substantive), Responsibilities (substantive), Requirements (substantive), Benefits (substantive), Pay (substantive). That's 5 sections. Could be okay. But we must ensure we don't create thin sections. Pay section would have a few paragraphs; that's fine. Let's include Pay section with the compensation description. We need to avoid repeating the job title as heading; fine. We must not include schedule section because no schedule info. Thus final HTML:

About the role

...

Responsibilities

...

Requirements

...

Benefits

...

Pay

Our salary range reflects gross base salary. For commercial roles with commission eligibility, this figure represents On-Target Earnings (OTE), inclusive of base salary and target commission. Salary ranges are quoted in USD as a consistent global reference. Your offer will be localized to your country's currency using a market-aligned conversion. Final pay is based on objective, job-related criteria including experience