Inside Sales Account Manager

We need to output HTML fragment with sections: Overview? 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 (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. The posting includes: - Overview About PowerSchool (mission statement) - Team Overview (Sales team description) - Description (maybe not needed) - Responsibilities (list of duties) - Your Day-to-day Job Will Consist Of (list) - Success Indicators (list) - Qualifications (Minimum Qualifications, Preferred Qualifications) - Compensation & Benefits (list of benefits and compensation range) - EEO Commitment (should be removed as boilerplate) - Also there is "Overview About PowerSchool" maybe we can treat as "About the role"? Actually "Overview About PowerSchool" is about company, not role. Could be considered "About the role"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include "About the role" heading for company overview? Might be okay. Or we could combine "Overview About PowerSchool" and "Team Overview" into a section like "About the role" or maybe "Team Overview". But they said only include sections when posting has real, specific content. We have content for responsibilities, qualifications, compensation & benefits, success indicators maybe could be part of responsibilities? But success indicators are separate metrics; could be a section like "Performance Expectations" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: could include Overview About PowerSchool and Team Overview (mission, team description). That seems appropriate. - Responsibilities: list of duties (Your Day-to-day Job Will Consist Of) plus maybe the bullet list under Responsibilities (the earlier bullet list). Actually there is a "Responsibilities" heading then a paragraph: "The Inside Sales Account Manager drives expansion and supports retention for a high-volume territory. They drive bookings and multi-suite growth through disciplined digital selling, value reinforcement, and coordinated customer engagement. The role works closely with Solution Consulting and Customer Success to support renewal readiness and ensure customers realize value." Then "Your Day-to-day Job Will Consist Of" list. So we can combine those into responsibilities. - Qualifications: Minimum Qualifications and Preferred Qualifications. - Benefits: list under Compensation & Benefits (benefits). Also compensation range (Pay). So we need separate Pay section? The instruction says include Pay section only if posting actually states them. It does state compensation range: "A reasonable estimate of the base compensation range for this position is $58,700 - $73,400 USD." So we should include a Pay section with that range. Benefits section for benefits list. - Schedule: not mentioned (no schedule info). So omit. - Skills: not explicitly listed; maybe we could infer from qualifications but better not to create unless explicit. So omit Skills. - Requirements: maybe same as Qualifications? But they said we can use Requirements heading. However we already have Qualifications. Could combine Minimum and Preferred under Qualifications. Or we could split: Requirements for minimum, Qualifications for preferred? But they said prefer few substantive sections over many thin ones. So better to have Qualifications covering both minimum and preferred. Or we could have Requirements for minimum and Qualifications for preferred. But we need to decide. Given allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Qualifications (both min and pref), Benefits, Pay. We could omit Requirements if we put everything under Qualifications. Or we could put minimum under Requirements and preferred under Qualifications. That would be two sections but still substantive. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." Having both Requirements and Qualifications may be thin if we split. Better to have one Qualifications section covering both. So we will not include Requirements. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now we need to format: - Use

for each section heading. - Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists or paragraphs. We must remove boilerplate: EEO Commitment, maybe also "Overview About PowerSchool" includes some fluff but it's substantive about company mission; we keep. We must not repeat job title as heading (not needed). No Job ID. We must not include application instructions (none present). Also remove duplicated lines. Now let's extract content. About the role: From "Overview About PowerSchool": "At PowerSchool, we power education for students around the world. As the global leader in cloud-based K-12 software, we support the full education ecosystem—from the central office to the classroom to the home. Joining PowerSchool means being part of a mission-driven team that is transforming K-12 education by helping schools operate more effectively and deliver better outcomes for educators, students, and families." From "Team Overview": "The Sales team gets PowerSchool into the hands of the educators and students who need it. Working side by side with Solution Consulting and Customer Success, we build executive relationships, lead account planning, and run deals end to end to renew on time and expand multi-suite adoption, delivering predictable bookings and revenue retention that empower better K-12 outcomes." We can combine into a few paragraphs. Responsibilities: Paragraph: "The Inside Sales Account Manager drives expansion and supports retention for a high-volume territory. They drive bookings and multi-suite growth through disciplined digital selling, value reinforcement, and coordinated customer engagement. The role works closely with Solution Consulting and Customer Success to support renewal readiness and ensure customers realize value." Then list under "Your Day-to-day Job Will Consist Of": - Build and execute a quarterly territory plan with whitespace targets, sequences, and next plays by persona. - Create expansion pipeline through outbound sequences, inbound lead conversion, micro-demos, event follow up, and partner referrals. - Run deals end to end for standard motions including pricing within bands, co-op purchases, and light RFP response. - Maintain forecast accuracy and CRM hygiene with stage exits tied to MEDDPICC. - Partner with Solution Consulting and Customer Success to reinforce value and support renewal readiness. - Participate in manager-led pipeline and forecast reviews with inspection-ready opportunities. - Travel occasionally up to 10% for key moments such as team summits and other high-priority events (e.g., training, conferences, client demos), with increased frequency during peak periods based on business demands. Also there is "Success Indicators" list: - Bookings and renewal targets met or exceeded for the territory. - Activity and conversion standards met across sequences, meetings set, and stage progression. - Revenue retention at or above the Inside Sales benchmark, for example 105 percent plus. - Pipeline forecast accuracy within acceptable standards. Should we include Success Indicators as part of Responsibilities? Could be separate section but not in allowed headings. Could incorporate into Responsibilities as additional bullet points? Might be okay to add as a subsection under Responsibilities. But we must not invent headings. We could add a

  summarizing success indicators? But we must preserve all substantive information; we can include them as a list under Responsibilities as well (makes sense). Or we could add a separate section like "Performance Expectations" but not allowed. So better to include them under Responsibilities as additional bullet points. Thus Responsibilities section will have a paragraph intro, then a

  with all duties and success indicators. Qualifications: Minimum Qualifications: - Consistent attainment against bookings goals in a high-velocity SaaS motion. - Experience running 3- to 6- month sales cycles with a focused set of personas and public-sector purchasing paths. - Demonstrated CRM discipline and pipeline quality suitable for weekly inspection. - 2+ years sales experience, ideally in SaaS or EdTech, or an equivalent combination of experience and skills that demonstrates sales aptitude. - Associate’s degree or equivalent experience. Preferred Qualifications: - Proficiency with MEDDPICC and mutual close plans appropriate for transactional and mid-complexity deals. - Familiarity with K-12 or public sector cycles including funding calendars, co-ops, and basic RFP processes. - Evidence of trustworthy partnership behavior from customer, partner, or cross-functional advocates. We can combine into a single Qualifications section with two sub-lists? Could separate with headings but we cannot add extra headings beyond allowed. Could use

  to introduce Minimum Qualifications and Preferred Qualifications then lists. That's okay. Benefits: List from "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 need to preserve all. Could format as

  with each benefit as
  • . For optional benefits, we can include as a single
  • "Optional Benefits: Pet Insurance, Identity Theft Protection, Student Debt Repayment Program and Prepaid Legal coverage". Or split. Pay: "A reasonable estimate of the base compensation range for this position is $58,700 - $73,400 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 all that. Could be a

    . Now we must ensure we don't include any boilerplate like EEO Commitment. Also remove duplicated lines (none). Also remove any navigation etc. Now produce HTML fragment:

    About the role

    At PowerSchool, we power education for students around the world. As the global leader in cloud-based K-12 software, we support the full education ecosystem—from the central office to the classroom to the home. Joining PowerSchool means being part of a mission-driven team that is transforming K-12 education by helping schools operate more effectively and deliver better outcomes for educators, students, and families.

    The Sales team gets PowerSchool into the hands of the educators and students who need it. Working side by side with Solution Consulting and Customer Success, we build executive relationships, lead account planning, and run deals end to end to renew on time and expand multi-suite adoption, delivering predictable bookings and revenue retention that empower better K-12 outcomes.

    Responsibilities

    The Inside Sales Account Manager drives expansion and supports retention for a high-volume territory. They drive bookings and multi-suite growth through disciplined digital