Senior Director, Sales – North America Verticals

We need to output HTML fragment with sections: About the role? The posting includes a description before "Job Description". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings. Preserve all substantive info. 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. Prefer few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: description (intro), Job Description (What You'll Do), Qualifications, What Success Looks Like, Additional Information (includes salary, diversity statement). Also maybe "Benefits"? Not mentioned. Pay: salary range given. Schedule: not mentioned. Benefits: not mentioned. Skills: not explicit separate but could be part of qualifications. We could combine Qualifications and Skills into one section? But instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections with real content. We have content for: About the role (maybe the intro paragraph before Job Description). Could use "About the role" heading for the introductory paragraphs describing Freshworks and the role overview. Then "Responsibilities" for What You'll Do. Then "Qualifications" for the qualifications list. Then "Pay" for salary range. Possibly "Additional Information" could be split into "Benefits" (none) and "Other" but we shouldn't create empty sections. Could include "Additional Information" as a section? Not in the list of allowed headings but we could use a generic heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Probably we should stick to those headings. So we can have About the role, Responsibilities, Qualifications, Pay. Possibly also "What Success Looks Like" could be part of Responsibilities or About the role? Might be better as a separate section like "Expectations" but not in list. Could incorporate into Responsibilities or About the role. Since we prefer few substantive sections, we could merge What Success Looks Like into Responsibilities or About the role. But it's distinct. However we could add a section "Expectations" but not in examples; risk of being considered not allowed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add other headings if needed. But better to follow examples. We have content for: About the role (intro). Responsibilities (What You'll Do). Qualifications (list). Pay (salary). Possibly also "Benefits" not present. Schedule not present. Requirements maybe same as Qualifications; we could use Requirements heading instead of Qualifications. But we have qualifications list; we could use Requirements heading. However we also have "What Success Looks Like" which could be considered part of Responsibilities or maybe a separate "Expectations". I'd include a section "Expectations" maybe but not in examples. Safer to include as part of Responsibilities. Thus final HTML:

About the role

... intro paragraphs ...

Responsibilities

• ... each responsibility ...

Qualifications

• ... each qualification ...

Pay

The annual base salary range for this position is $288,320 - $356,160 Base Salary. This role is also eligible for variable compensation + Equity Compensation is based on a variety of factors including but not limited to location, experience, job-related skills, and level.

We need to preserve all substantive information. Must not lose details like the description of Freshworks, the mission, etc. Also the "Additional Information" includes diversity statement. Should we include that? It's substantive but not covered by headings. Could add a section "Additional Information" or incorporate into About the role or Pay? Probably better to add a section "Additional Information" as a heading (though not in examples). But we could also put under About the role? Might be okay to add a section "Additional Information". The instruction says use h3 for section headings (e.g. ...). It doesn't forbid other headings. So we can add Additional Information. Thus sections: About the role, Responsibilities, Qualifications, Pay, Additional Information. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The diversity statement is not boilerplate? It's EEO statement. Actually it's an equal opportunity statement. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove the diversity statement. Also remove "Fresh vision. Real impact. Come build it with us." repeated at end? That's maybe tagline but could be considered boilerplate. Might remove duplicates. The intro includes "Fresh vision. Real impact. Come build it with us." at start and end. Might keep one? But it's repetitive. Probably remove duplicate lines. We'll keep the introductory description but remove the repeated tagline at the end. Also remove "We're committed to building a workplace that reflects the diverse world we serve..." etc. That's EEO boilerplate, remove. Also remove "At Freshworks, we have fostered an environment that enables everyone to find their true potential..." etc. That's also EEO. Remove. Thus Additional Information section will contain only the salary info? Actually salary is already in Pay. Additional Information may be empty then. Better to not have Additional Information if only salary. So we will put salary in Pay section and omit Additional Information. Thus final sections: About the role, Responsibilities, Qualifications, Pay. Now we need to extract the substantive content for each. About the role: Should include the introductory paragraphs before "Job Description". Let's capture: "Organizations everywhere struggle under the crushing costs and complexities of “solutions” that promise to simplify their lives. To create a better experience for their customers and employees. To help them grow. Software is a choice that can make or break a business. Create better or worse experiences. Propel or throttle growth. Business software has become a blocker instead of ways to get work done. There’s another option. Freshworks. With a fresh vision for how the world works. At Freshworks, we build uncomplicated service software that delivers exceptional customer and employee experiences. Our enterprise-grade solutions are powerful, yet easy to use, and quick to deliver results. Our people-first approach to AI eliminates friction, making employees more effective and organizations more productive. Over 72,000 companies, including Bridgestone, New Balance, Nucor, S&P Global, and Sony Music, trust Freshworks’ customer experience (CX) and employee experience (EX) software to fuel customer loyalty and service efficiency. And, over 4,500 Freshworks employees make this possible, all around the world. Fresh vision. Real impact. Come build it with us." Then after that there is "Job Description Freshworks is seeking an experienced Senior Director of Sales, North America (US and Canada) Verticals to lead our go-to-market execution across three strategic vertical markets: Manufacturing, State, Local & Education (SLED), and Federal/Government as well as Canada. Reporting directly to the SVP & GM of America’s Sales, this leader will oversee three sales teams and their respective leaders, with responsibility for building and executing the strategy required to accelerate Freshworks' growth within these highly specialized markets. This is a senior, second- or third-line sales leadership position requiring someone who has successfully led leaders, scaled enterprise SaaS sales organizations, and brings deep experience navigating the unique buying environments, procurement processes, and customer needs within the public sector and other complex vertical markets. The ideal candidate combines strategic leadership with strong operating discipline. They can set the direction for the business, develop high-performing sales leaders, navigate complex enterprise opportunities, and partner across the organization to turn vertical specialization into a competitive advantage for Freshworks." That could be part of About the role or Responsibilities? It's more about the role overview. Could be included in About the role. But we already have About the role with the company description. Might combine role overview there. However the instruction says do NOT repeat the job title as a heading. It's okay to include job title in paragraph. Thus About the role will contain both company intro and role overview. Responsibilities: The "What You'll Do" bullet list (though not bullet but sentences). We need to convert each responsibility into

. Let's list them: - Lead Freshworks' North America vertical sales organization, with responsibility for teams focused on Manufacturing, SLED, and Federal/Government markets. - Lead, coach, and develop the sales leaders responsible for each vertical, establishing a high bar for performance, accountability, talent development, and execution. - Develop and execute a comprehensive vertical sales strategy aligned with Freshworks' broader North America and enterprise growth objectives. - Own revenue performance across the verticals organization, including pipeline generation, forecasting, deal execution, productivity, and attainment. - Build a scalable operating model across the three vertical teams while recognizing the distinct customer, regulatory, procurement, and go-to-market requirements of each market. - Drive Freshworks' continued expansion into larger, more complex enterprise SaaS opportunities and help teams navigate sophisticated, multi-stakeholder sales cycles. - Serve as an executive sponsor on strategic opportunities, helping teams engage senior customer stakeholders, overcome obstacles, and successfully close transformational deals. - Establish strong inspection and forecasting discipline across the organization, providing clear visibility into pipeline health, risks, opportunities, and business performance. - Recruit, retain, and develop exceptional sales leadership and sales talent as the vertical organization scales. - Partner closely with Marketing, Solution Engineering, Customer Success, Professional Services, Channels & Alliances, Revenue Operations, Finance, Product, and other functions to develop integrated vertical go-to-market strategies. - Build strong relationships with channel, technology, and ecosystem partners that can accelerate Freshworks' presence within strategic vertical markets. - Bring market intelligence back into Freshworks, helping Product and GTM leadership understand the evolving needs of Manufacturing, SLED, and Federal/Government customers. - Represent the verticals organization within the North America sales leadership team and contribute to broader GTM strategy, planning, and execution. We need to ensure we preserve all. Qualifications: list each qualification bullet. Let's extract qualifications list: - 15+ years of progressive sales experience, ideally within enterprise software or SaaS organizations. - 8+ years of sales leadership experience, including 5+ years leading managers and operating at a second- or third-line leadership level. - Demonstrated success building, scaling, and leading high-performing enterprise sales organizations through multiple layers of leadership. - Significant experience selling into and leading sales organizations focused on SLED and/or Federal/Government markets is required, with a strong understanding of public-sector buying cycles, procurement processes, contracting requirements, and go-to-market dynamics. - Experience within Manufacturing or other complex enterprise vertical markets is strongly preferred. - Deep understanding of complex enterprise SaaS sales cycles, including executive engagement, multi-threaded decision processes, procurement, security, legal, implementation, and commercial negotiations. - Proven track record of consistently delivering against ambitious revenue targets and driving predictable, sustainable growth. - Experience developing and executing vertical-specific GTM strategies rather than relying solely on traditional geographic or territory-based sales models. - Strong command of pipeline management, forecasting, territory planning, account strategy, and sales productivity. - Demonstrated ability to coach and develop experienced sales leaders while creating a culture of accountability, collaboration, and high performance. - Strong executive presence with the ability to engage credibly with C-suite customers, senior government and public-sector stakeholders, internal executives, partners, and other senior decision-makers.