Solution Principal – Healthcare & NPO

We need to output HTML fragment with sections: h3 headings for sections present. No job title heading. No Job ID. Remove boilerplate. Include only sections with real content. We need to parse the job posting. Key sections: Job Summary (but we shouldn't repeat job title; we can have a heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have "Job Summary" which is like About the role. So we can use

About the role

and put the summary paragraphs. Then "Role & Responsibilities" =>

Responsibilities

with list. Then "Job Requirements" => maybe

Requirements

or Qualifications. The instruction includes Requirements, Qualifications, Skills. We have "What you offer" under Job Requirements. Could treat as Requirements. We'll output

Requirements

with list. Then "Success Criteria" maybe part of Requirements? Could be separate but not a standard heading; maybe we incorporate into Requirements or Qualifications. But we can create a section "Qualifications" for success criteria? However success criteria are more like performance metrics; could be part of Requirements. Safer to include under Requirements as additional bullet points. Then "Organizational Alignment" maybe not needed; could be omitted as not a standard heading. Could be omitted or placed under About the role? Probably omit. Then "What we offer" => Benefits (and Pay). We have benefits list and also target compensation. So we need Benefits section and Pay section. Benefits: list of benefits. Pay: "Target compensation for this role will be $230k - $250K USD (mix of base salary and bonus)." Also mention "Generous pay with bonus structure (quarterly or bi-annual depending on the role)". So we can put Pay section with that info. Schedule: not mentioned; omit. We must not include sections with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. Good. We must not include cookie/navigation/legal/EEO etc. Remove lines like "The preceding job profile has been designed..." maybe that's boilerplate; we should remove that. Also "Additional duties may be assigned..." maybe boilerplate; remove. Also "Success Criteria" we keep as content but maybe it's not boilerplate; it's specific. Keep. "Organizational Alignment" maybe not needed; but we can include as a short paragraph under About the role? Might be considered metadata; but we can drop. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all substantive info from sections we keep. We need to decide what is substantive vs boilerplate. The lines: "The preceding job profile has been designed to indicate the general nature and level of work performed by associates within this role. It is not designed to contain or be interpreted as a comprehensive inventory of all duties, responsibilities, and qualifications required. Additional duties may be assigned and may be subject to change at any time due to reasonable accommodation or other reasons." This is generic boilerplate; we should remove. Also "Organizational Alignment Reports to: Vice President, Solution Sales & Solution Principals Collaborates with: Account Managers, Solution Sales Consultants, Solution Architects, Product Development team, and other Solution Principals Shares a com" seems cut off; but it's metadata; we could drop. Also "What we offer" includes many benefits; we keep. Also "Target compensation for this role will be $230k - $250K USD (mix of base salary and bonus). Actual offers may be higher or lower than this range and will be determined based on a variety of factors, including (but not limited to) candidates’ qualifications, experience, education, and work location. We are not able to consider candidates residing in the state of Hawaii currently." This is pay info; keep. Also "Company description" maybe boilerplate? It's generic description of company; could be considered boilerplate but it's substantive about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed; but it's likely considered boilerplate? However it's substantive about the company; but typical job postings include it; but instruction didn't forbid it. It says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description is not those. So we could keep it as a section maybe "About the company"? But not in allowed headings. Could incorporate into About the role? Might be okay to add a

after About the role? But we should not create new headings not in list unless needed. Could add a

under About the role summarizing company description. But we must preserve ALL substantive information; we can't drop it. So we need to include it somewhere. Perhaps we can add a

About the company

but not in allowed list. 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? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. We could put company description as a

under About the role or maybe under a generic

without heading? But we need to output only HTML fragment; we can have multiple

and

etc. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose." So we can have prose paragraphs without heading? Probably they expect each section preceded by heading. But we could have a heading "About the role" and then include both role summary and company description under that heading as prose. That seems acceptable. Thus structure:

  About the role

  Job Summary paragraph(s) + maybe organizational alignment + company description.

  But we need to preserve all details: The Job Summary paragraph includes multiple sentences. We'll combine them. Then

  Responsibilities

  with
  list of duties. Then

  Requirements

  with
  list of requirements (including success criteria maybe). We'll include bullet points from "What you offer" and also success criteria. Then

  Benefits

  with
  list of benefits. Then

  Pay

  with

  containing compensation details. We must not include Schedule. Check for duplicates: Ensure we don't repeat same info. Now extract details. Job Summary text: "This consultative role leverages broad solution knowledge, industry awareness, and business-outcome selling skills to identify opportunities aligned to customers' missions, operational priorities, compliance needs, and technology objectives while maximizing services revenue across healthcare, government/public sector, nonprofit, and other mission-driven organizations. The Solution Principal leads Solution Sales deal execution, assembles and guides teams pursuing opportunities, and contributes to territory and account strategy with a strong understanding of regulated, budget-sensitive, and stakeholder-complex environments. This is a sales quota-based position, critical in qualifying deals, supporting territory planning, shaping compelling value narratives, and collaborating across teams to drive increased services revenue and measurable customer impact. The Solution Principal serves as the single point of contact for regional sales leaders and their team of Account Managers, helping translate customer mission needs into actionable SoftwareOne services opportunities." We can keep that as prose. Organizational Alignment: "Reports to: Vice President, Solution Sales & Solution Principals Collaborates with: Account Managers, Solution Sales Consultants, Solution Architects, Product Development team, and other Solution Principals Shares a com" (cut off). Might be incomplete; we could drop as it's incomplete and maybe boilerplate. Safer to drop. Company description paragraph: "SoftwareOne is a global provider of software and cloud solutions. With a presence in over 70 countries and more than 12,000 professionals, we help organizations optimize software investments, modernize applications, and unlock the value of cloud, data, and AI. Our people are at the core of everything we do. We enable collaboration across borders, continuous learning, and opportunities to grow in a fast-evolving technology landscape. Whether your focus is on technology, customer success, or business operations, your ideas matter, and your contributions make a difference. Join a global team where you can build your skills, work with leading technologies, and make a real impact for our customers." We'll include that as prose under About the role. Now Responsibilities bullet points from "Role & Responsibilities". Let's list them: - Ability to travel up to 40% - Serve as the consultative sales principal for the Regional Sales Leaders and their team of account managers, heavily involved in Services deal identification, qualification and territory planning. - As the lead regional resource, identify, develop, and prioritize services opportunities to maximize revenue, deliver customer impact, and overachieve Regional services sales quota – avoiding costly or unreasonable pursuits. - Develop industry-informed account and pursuit strategies for healthcare, government/public sector, education, and nonprofit organizations, including sensitivity to mission outcomes, funding cycles, procurement requirements, compliance considerations, and multi-stakeholder decision processes. - Shape value narratives that connect SoftwareOne services to customer priorities such as cost optimization, citizen or patient experience, operational resiliency, data protection, workforce productivity, grant or budget stewardship, modernization, and measurable community impact. - Support RFx, bid, and go/no-go strategy for public sector, healthcare, and nonprofit pursuits by helping assess right-to-win, delivery feasibility, compliance constraints, required references, onshore or security requirements, and differentiated executive messaging. - Ensure deals are qualified for Solution Sales to deliver sales best practices, including: discovery processes, consultative value propositions, execution of pre call plans, run key deal events, and post-demo debriefs. - Collaborate with Account Executives and Sales Leaders to define and execute account and deal strategy for SoftwareOne portfolio of services. - Develop creative, value-based presentations for customer discovery calls to uncover key business objectives and associated value, working independently, or in collaboration with Solutions Sales or Account Managers. - Assemble and coordinate Solution Sales teams with Practice Leads to determine resources best suited to win opportunities. - Facilitate bi-directional communication, sharing best practices, competitive intelligence, and new approaches with the regional team and Practice Leaders. - Orchestrate and participate in customer-facing events, ensuring SoftwareOne differentiation is reinforced and transitions are smooth. - Understand level of effort estimates and engage in strategic conversations to craft winning deal strategies. - Participate in regional QBRs and directly engage in all strategic regional deals. - Share knowledge with other Solution Principals and Practice Leads, providing real-time coaching and feedback. We need to ensure each bullet is

  • . Now Requirements bullet points from "Job Requirements" and "What you offer". Let's extract: From "Job Requirements What you offer": - Proven success record for 10+ years in Technology, Cost Optimization and Cloud Services sales to healthcare, government/public sector, education, nonprofit, or similarly regulated and mission-driven organizations. - Accountability and strong momentum to achieve both customer impact and revenue goals by demonstrating activity and progress in CRM pipeline and weekly forecast. - Working knowledge of common sector priorities such as regulatory compliance, data privacy and security, procurement governance, grant or budget constraints, public accountability, constituent or patient experience, and modernization of legacy systems. - Ability to tailor executive-level business cases and value propositions for mission-oriented stakeholders, including CIOs, CFOs, procurement leaders, clinical or operational leaders, program executives, and public-sector