NetSuite - Regional Sales Director - Software vertical - East

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, duplicate lines, etc. We need to parse the job description. Key sections: - About the role: The first paragraph: "With a focus on SMB businesses, our Direct Sales team is seeking a Sales Manager with a successful background managing inside and outside sales representatives." Also "More about the Opportunity: Working in a fast-paced, innovative environment, you are responsible for managing a team of outside Sales Representatives that serve our Mid-Market and Corporate spaces. You are responsible for developing and managing the team to generate revenue and achieve individual team and organizational quotas. Teach, coach and mentor successful sales professionals to develop in their careers. Recruit, train, and coach the team in both sales strategy and NetSuite product knowledge. Monitoring demand generation and sales activity and tracking the results. Develop solution proposals encompassing all aspects of the business applications." That's about the role. - Responsibilities: The same as above repeated later. We need to list responsibilities as bullet list. - Qualifications: The "About You" section: list qualifications. - Skills: Might be derived from qualifications? The posting mentions "strong understanding of accounting solutions, business solutions, ecommerce, ERP or CRM", "ability to negotiate pricing and contractual terms", "strong leadership capabilities and experience in sales coaching and mentoring", "tremendous work ethic, laser focus, passion, dedication", "enjoy learning technology and can translate that into value for prospects", "curious, insightful, perceptive". Could be considered skills. - Benefits: The benefits list after "Oracle US offers a comprehensive benefits package which includes the following:" then list many items. - Pay: The range: "US: Hiring Range in USD from: $118,700 - $194,400 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 45 / 55." - Schedule: Not explicitly mentioned. No schedule info. So we should not include Schedule section. - Requirements: Might be similar to qualifications? The posting has "Qualifications" heading later with disclaimer and range etc. But we already have Qualifications section. Could treat "Qualifications" as the formal qualifications (experience, etc.) and "Requirements" maybe not needed. However we need to follow instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. If a section lacks real specific content, we should not emit it. So we need to decide which sections have content. We have content for About the role, Responsibilities, Qualifications (About You), Skills (maybe derived), Benefits, Pay. Requirements maybe not distinct; but we could treat "About You" as Qualifications, and maybe "Requirements" could be the same as qualifications? But we should not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Requirements into one Qualifications section. But we have to use headings exactly as given if we include them. If we include Requirements heading, we need content under it. Could we put the "About You" bullet list under Requirements? But then we would also need Qualifications heading maybe for something else like "Range and benefit information"? Actually the Qualifications heading in the posting includes disclaimer and pay range etc. But we already have Pay separate. So maybe we treat the "Qualifications" heading (the one with disclaimer and pay) as Qualifications section, and the "About You" as Skills/Requirements? However the instruction says to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. Let's extract: About the role: initial paragraph. Responsibilities: bullet list of duties. Requirements: maybe the "About You" list of experience/skills needed (3 years closing experience, SaaS/Technology sales, understanding of accounting solutions, etc.) That seems like requirements. Qualifications: maybe the "About You" also includes leadership capabilities etc. But we could treat Requirements as the hard requirements (experience, knowledge) and Qualifications as the preferred/leadership traits. However the posting lumps them together. To avoid thin sections, we could combine Requirements and Qualifications into one Qualifications section. But then we would not have a Requirements heading. That's okay if we don't have real specific content for Requirements separate. The instruction: "include a section ONLY when the posting has real, specific content for it". So if we don't have distinct content for Requirements, we omit it. Similarly Skills: we could extract skills from About You: leadership capabilities, coaching, negotiation, technology learning, communication, etc. Could be a Skills section. Benefits: we have. Pay: we have. Schedule: none. Thus we will output sections: About the role, Responsibilities, Requirements (maybe we treat as Requirements), Skills, Benefits, Pay. But we need to avoid duplication. Let's craft content. About the role: combine first paragraph and maybe the "More about the Opportunity" paragraph (but that is essentially responsibilities). To avoid duplication, we can keep About the role as the introductory sentence: "With a focus on SMB businesses, our Direct Sales team is seeking a Sales Manager with a successful background managing inside and outside sales representatives." Could also include "Click here to learn more about Oracle NetSuite!" but that's a link, maybe we drop as it's navigation? Probably drop. Responsibilities: bullet list of duties from the responsibilities paragraph (not repeating the intro). List: - Managing a team of outside Sales Representatives that serve Mid-Market and Corporate spaces. - Developing and managing the team to generate revenue and achieve individual team and organizational quotas. - Teaching, coaching, and mentoring successful sales professionals to develop in their careers. - Recruiting, training, and coaching the team in both sales strategy and NetSuite product knowledge. - Monitoring demand generation and sales activity and tracking the results. - Developing solution proposals encompassing all aspects of the business applications. Requirements: from "About You": list of required experience/knowledge: - At least 3 years of closing experience and/or sales management experience within SaaS/Technology sales. - Strong understanding of accounting solutions, business solutions, ecommerce, ERP or CRM in a sales capacity. - Ability to negotiate pricing and contractual terms to close a sale. - Proven track record as a regular on your company’s top producer’s list with stats to back it up. - Strong leadership capabilities and experience in sales coaching and mentoring. - Tremendous work ethic, laser focus, passion, and dedication. - Enjoy learning technology and can translate that into value for prospects. - Curious, insightful, and perceptive. But some of those are more like skills/qualities. However we can keep them as Requirements. Skills: maybe we can extract specific skills: leadership, coaching/mentoring, negotiation, technology learning, communication, writing skills, attention to detail, emotional intelligence, quick turnaround. However many overlap with Requirements. To avoid thin sections, maybe we skip Skills and put those under Requirements. But the instruction says we can have Skills section if there is real specific content. There is some: "We value outstanding writing skills and a friendly, thoughtful, and effective communication style." "We strive for attention to detail, emotional intelligence, and quick turnaround times." That's from About the Team. Could be Skills. Thus we can have Skills section containing: - Outstanding writing skills. - Friendly, thoughtful, and effective communication style. - Attention to detail. - Emotional intelligence. - Quick turnaround times. Also maybe "strong leadership capabilities" etc but that's already in Requirements. We'll keep Skills separate. Benefits: list all benefits items. Pay: include range, equity eligibility, commission mix. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include boilerplate like EEO, disclaimer about immunization, etc. Also remove duplicated lines. We need to ensure we preserve all substantive information. Let's capture all substantive info from the posting: - About the role: "With a focus on SMB businesses, our Direct Sales team is seeking a Sales Manager with a successful background managing inside and outside sales representatives." - More about the Opportunity: (we used for responsibilities). Also maybe "Working in a fast-paced, innovative environment" is part of responsibilities. - About the Team: "We are responsible for driving interest to our prospective customers and to execute in tandem with our marketing and sales teams vision. We value outstanding writing skills and a friendly, thoughtful, and effective communication style. We strive for attention to detail, emotional intelligence, and quick turnaround times. We get stuff done. And fast." That's substantive; we could incorporate into Skills or maybe a separate "About the Team" but not a heading we have. Could add to Skills or maybe to About the role? But we already have About the role. Could add a paragraph about team under About the role? But the instruction says use headings for specific sections; we could incorporate team description into About the role as extra prose. However we already used About the role for a short sentence; we could expand it. Better: About the role section could include both the initial sentence and the team description? But the team description is about the team, not the role. However we could treat it as part of About the role (the environment). It's okay. Let's craft About the role paragraph: "With a focus on SMB businesses, our Direct Sales team is seeking a Sales Manager with a successful background managing inside and outside sales representatives. Working in a fast-paced, innovative environment, you will be part of a team responsible for driving interest to prospective customers and executing in tandem with marketing and sales teams. The team values outstanding writing skills, a friendly/thoughtful/effective communication style, attention to detail, emotional intelligence, and quick turnaround times." That captures team description. Now Responsibilities: as bullet list. Requirements: bullet list of required experience/knowledge. Skills: bullet list of skills from About the Team and maybe other skill mentions: leadership, coaching, negotiation, technology learning, etc. But we already have leadership in Requirements; maybe we keep Skills as the team-valued skills: writing, communication, attention to detail, emotional intelligence, quick turnaround. Also maybe "strong understanding of accounting solutions..." is more knowledge than skill. We'll keep Skills as those. Benefits: list. Pay: paragraph. Now ensure we don't include boilerplate: disclaimer about immunization, Range and benefit information provided in this posting are specific to the stated locations only US: ... we kept pay range but we need to include that sentence? The pay range is part of Pay section. The disclaimer about immunization etc is boilerplate; we should drop. Also drop "Range and benefit information provided in this posting are specific to the stated locations only US:" maybe we keep as part of Pay? It's metadata about range; we can incorporate: "US: Hiring Range in USD from: $118,700 - $194,400 per year." That's fine. Also drop "May be eligible for equity." keep. "Eligible for commission with an estimated pay mix of 45 / 55." keep. Drop "Oracle maintains broad salary ranges..." etc as boilerplate? It's somewhat generic but still substantive about pay philosophy. Might be considered boilerplate; but it's not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The sentence about broad salary ranges is somewhat generic but still part of the posting. However it's not specific to the role; it's a general statement. Might be considered boilerplate. Safer to drop it. Also drop "Candidates are typically placed into the range based on the preceding factors as well as internal peer equity." That's also generic. Drop "Oracle US offers a comprehensive benefits package which includes the following:" we can keep as intro to benefits but maybe we can just start list. We need to avoid duplication: responsibilities appear twice; we only list once. Now produce HTML. Structure: