Solution Consultant

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Overview: description of company, team overview. Could be "About the role" maybe includes overview and team overview. Responsibilities: The "Your Day-to-day Job Will Consist Of" list. Qualifications: Minimum Qualifications and Preferred Qualifications. Skills: maybe derived from qualifications? But we can include a Skills section if there is explicit skill list. The posting includes many skill-like items: working knowledge, understanding, able to co-lead, familiar with integrations, clear communication, comfortable using Salesforce, strong organization, etc. Those could go under Skills or Qualifications. The instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have content for About the role (overview + team overview). Responsibilities (Your Day-to-day...). Qualifications (Minimum and Preferred). Benefits (Compensation & Benefits section). Pay (compensation range). Schedule? Not mentioned except travel extensively (60-75%) but that's not schedule. No explicit schedule like full-time, part-time, hours. So we should not create Schedule section. Requirements? Could be same as Qualifications? The instruction says we can have Requirements section separate from Qualifications. But we have Minimum Qualifications and Preferred Qualifications; we could put those under Qualifications. Requirements maybe not needed. We could omit Requirements if no distinct content. Better to follow instruction: prefer few substantive sections over many thin ones. So we can combine Minimum and Preferred under Qualifications. Could also have Skills separate if we want to extract skill bullet list. But we already have many skill-like items in qualifications; maybe we can put them under Skills and keep Qualifications for education/experience. However the posting lumps them together. Safer to put all under Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate: EEO Commitment, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. The posting includes "EEO Commitment" which we should remove. Also "Compensation & Benefits" includes benefits list and compensation range; we keep that. We need to ensure we don't repeat the job title as heading. Not needed. We need to include all substantive info: overview, team overview, responsibilities list, qualifications (minimum and preferred), benefits list, compensation range. We must not include placeholders like "commensurate with experience". Not present. We need to format lists. Let's extract content. About the role: combine Overview and Team Overview paragraphs. Overview: "At PowerSchool, we are a dedicated team of innovators guided by our shared purpose of powering personalized education for students around the world. From the central office to the classroom to the home, PowerSchool supports the entire educational ecosystem as the global leader of cloud-based software for K-12 education. Our employees make it all possible, and a career with us means you’re joining a successful team committed to engaging, empowering, and improving the K-12 education experience everywhere." Team Overview: "The Solution Consulting team turns customer challenges into clear solution paths. Working side by side with Sales, we lead discovery, craft compelling POVs, and validate value through demos and pilots, raising win rates, expanding suites, and strengthening long-term relationships across K-12 so districts can deliver better results for every student." We can combine into a couple paragraphs. Responsibilities: list from "Your Day-to-day Job Will Consist Of" which includes multiple sentences each ending with a period. They are basically bullet points but not formatted as list. We need to turn each into

• . Let's parse: - Build deep expertise in a defined product group and associated buyer personas; act as the primary subject matter expert (SME) for active sales opportunities and represent the right product domain in multi-product pursuits. - Partner with SDRs and AEs in early discovery to qualify opportunities and assess alignment of systems, data flows, integration points, and non-functional requirements (e.g., security, scalability, accessibility) to support pursuit strategy. - Translate functional requirements into actionable solution designs and configuration options; lead product proofs of concept (POCs) to validate solution fit and convert pipeline. - Document MEDDPICC-aligned insights, particularly Metrics and Decision Criteria, in CRM in pursuit documentation. - Provide accurate, comprehensive responses to RFPs and RFIs that address the needs of functional buyers. - Serve as the SKU configuration SME to validate quotes against the proposed solution and customer technical landscape. - Design and deliver persona-specific demos, workshops, and proofs of concept that align product capabilities with buyer outcomes and Decision Criteria. - Maintain demo environments with up-to-date data, reusable scripts, scenario assets, and runbooks that support Sales progression. - Prepare detailed post-sale handoff materials to ensure seamless transitions to Services and Customer Success. - Provide structured feedback to Product and Enablement teams on gaps, objections, and content needed based on real-world sales cycles to enhance team effectiveness and performance. - Travel extensively (60–75%), with weekly customer visits common. Travel supports high-impact activities such as advancing strategic deals, conducting onsite demos, and leading executive workshops. Also there are Success Indicators after responsibilities: "Improved win rates and sales velocity on pursuits with SC involvement.Readiness of demo environments and run-of-shows finalized before demo meetings.SDR-sourced opportunities with SC involvement show a high conversion rate vs. SDR baseline.Quote accuracy (percent with no re-quotes due to configuration/SKU issues)." These could be considered part of responsibilities or maybe separate section like "Success Indicators". But we don't have a heading for that; we could include them under Responsibilities as additional bullet points. They are substantive. Let's include them as list items. Thus responsibilities list items: 1. Build deep expertise... 2. Partner with SDRs... 3. Translate functional requirements... 4. Document MEDDPICC-aligned insights... 5. Provide accurate, comprehensive responses... 6. Serve as the SKU configuration SME... 7. Design and deliver persona-specific demos... 8. Maintain demo environments... 9. Prepare detailed post-sale handoff materials... 10. Provide structured feedback... 11. Travel extensively (60–75%), with weekly customer visits common. Travel supports high-impact activities such as advancing strategic deals, conducting onsite demos, and leading executive workshops. 12. Improved win rates and sales velocity on pursuits with SC involvement. 13. Readiness of demo environments and run-of-shows finalized before demo meetings. 14. SDR-sourced opportunities with SC involvement show a high conversion rate vs. SDR baseline. 15. Quote accuracy (percent with no re-quotes due to configuration/SKU issues). We need to keep punctuation as is. Qualifications: Minimum Qualifications and Preferred Qualifications. Minimum Qualifications list: - Working knowledge of one K–12 technical domain (Student Information Systems and analytics, learning and engagement, or ERP and talent) and relevant K–12 buyer personas. - Understanding of K–12 district operations, funding models, and stakeholder priorities. - Able to co-lead customer demos and workshops and configure common demo scenarios live. - Familiar with integrations and data flows (including APIs, rostering, SFTP, authentication, basic security controls) and able to flag risks. - Clear written and verbal communication that explains technical topics to non-technical audiences. - Comfortable using Salesforce or a similar CRM for notes, artifacts, and basic MEDDPICC capture. - Strong organization and time management across multiple live pursuits. - 4+ years in solution consulting, sales engineering, implementation, or a related K–12 SaaS role. - Bachelor’s degree or equivalent experience. Preferred Qualifications list: - Experience delivering persona-based demos for K–12 buyers such as Superintendent staff, CIO, Curriculum, Finance, HR, and Procurement. - Experience contributing to RFPs, RFIs, or security questionnaires in the public sector. - Familiarity with EdTech standards and identity models such as Ed-Fi, OneRoster, LTI, SAML, and OIDC. - Able to build simple prototypes or data visualizations to show outcomes and ROI. - Able to reuse demo assets, runbooks, or checklists that improved team demo quality and consistency. We can combine into one qualifications section with two subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could keep Qualifications and maybe separate Minimum and Preferred as

  ? Not allowed. We could just list all qualifications as a single list, preserving both minimum and preferred. But we need to preserve distinction? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we combine them without labeling, we lose the distinction between minimum and preferred. However we could keep them as separate paragraphs: first a paragraph "Minimum Qualifications:" then list, then "Preferred Qualifications:" then list. That preserves info without extra headings. That's acceptable. Thus Qualifications section:

  Qualifications

  then

  Minimum Qualifications:

  ... then

  Preferred Qualifications:

  ... Benefits: from "Compensation & Benefits" section: list of benefits. We need to capture all benefits: - Comprehensive Insurance Coverage (including Medical, Dental, Vision, Pharmacy benefits, Life Insurance and AD&D) - Flexible Spending Accounts and Health Savings Accounts - Short-Term Disability and Long-Term Disability - Comprehensive 401(k) plan - Generous Parental Leave - Unrestricted paid time off (known as Discretionary Time Off - DTO) - Wellness Program, including ClassPass & Employee Assistance Program - Tuition Reimbursement - Optional Benefits: Pet Insurance, Identity Theft Protection, Student Debt Repayment Program and Prepaid Legal coverage We should keep as list. Pay: "A reasonable estimate of the base compensation range for this position is $63,900 - $119,200 USD. This compensation range is specific to the United States and it incorporates many factors including but not limited to an applicant's skills and prior relevant experience and training; licensures, degrees, and certifications; internal equity; internal pay ranges; and market data/range parameters." We need to preserve that as prose under Pay heading. Schedule: none, so omit. We must not include boilerplate: EEO Commitment, etc. Also remove any duplicated lines. Ensure we don't include "Compensation & Benefits" heading as we will use

  Benefits

  and

  Pay

  . The original had "Compensation & Benefits" heading; we split. We must not include any navigation, cookie, legal, etc. Now produce HTML fragment. Structure:

  About the role

  ...overview...

  ...team overview...

  Responsibilities

  • ...
  ...

  Qualifications

  Minimum Qualifications:

  ...

  Preferred Qualifications:

  ...

  Benefits

  ...

  Pay

  ...

  Make sure to not add extra whitespace? It's fine. Check for any missed substantive info: The "Success Indicators" we included as responsibilities. Good. Check if any other sections like "Overview" includes "Team Overview" we used. Check if any other info like "Travel extensively (60–75%), with weekly customer visits common. Travel