Account Executive - Public Sector Sales

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. We need to parse the posting. Sections present: - Who We Are; What We Do; Where We’re Going (intro) – not a heading we need? Possibly could be "About the company" but not requested headings. The requested headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include About the role (there is "About The Role" section). Responsibilities (there is "What You’ll Do"). Requirements/Qualifications/Skills: there is "What We’re Looking For" which includes experience, etc. Could split into Requirements, Qualifications, Skills. But we need to decide based on content. Also there is "Compensation & Benefits" section with pay range and benefits list. Also "Travel: roughly 50%" and location requirement. Also "How We Work" (hybrid-flexible) maybe schedule? Not explicit schedule. There's no explicit schedule (like full-time, part-time). Could infer full-time but not stated. So we should not create Schedule section unless explicit. Benefits: there is a list: "Generous time off policies Competitive compensation Volunteer opportunities Reward and recognition programs Employee committees & resource groups Healthcare and retirement benefits". Also earlier mention "learning and development". But we can include Benefits section with that list. Pay: compensation range $170,000 - $220,000 (USD) a year. Also note about incentive component etc. We'll include Pay section. Schedule: Not explicit. Could infer full-time but not stated. So we should not create Schedule. Now we need to produce HTML with headings

and appropriate content:

for prose,

• for lists. We must not repeat job title. No extra headings like "Who We Are". We'll only include headings that have content: About The Role, What You’ll Do (Responsibilities), What We’re Looking For (could be Requirements/Qualifications/Skills), Compensation & Benefits (maybe split into Benefits and Pay). But we need to follow the requested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: use the "About The Role" paragraph(s). That's a prose description. - Responsibilities: use "What You’ll Do" bullet list (the list of duties). We'll output as
  • . - Requirements: maybe the "What We’re Looking For" includes experience, etc. Could treat as Requirements. - Qualifications: maybe also part of same. But we need to avoid duplication. Could split: Requirements = experience running a software sales territory, deep familiarity with Challenger, history selling into state/local gov, consistent quota attainment, strong negotiation skills, knowledge of markets advantage. Qualifications = maybe education? Not present. Could note "A note for law enforcement professionals" maybe as Qualifications? But better to treat Requirements as the list, Qualifications maybe empty -> we should not create heading if no specific content. So we should not create Qualifications heading if no distinct content. Similarly Skills: maybe we could extract skills from the list: "Experience running a software sales territory", "Deep familiarity with Challenger sales model", etc. But that overlaps. Given instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements, Qualifications, Skills into one section? But headings are prescribed; we must only emit heading when posting has real specific content for it. If we cannot differentiate, we could omit those headings that lack distinct content. However we might still include Requirements as the "What We’re Looking For" section, and omit Qualifications and Skills if no separate content. But we need to check if there is any content that could be considered Qualifications: maybe "Must reside in Nevada, Nebraska, North Dakota, South Dakota, Wyoming, or Kansas" and "Travel: roughly 50%" could be considered Qualifications? Not exactly. Could be considered Requirements (location, travel). So we could include those in Requirements. Thus we will have:

    About the role

    ... (the About The Role paragraph)

    Responsibilities

    • ... list items from What You’ll Do

    Requirements

    • ... list items from What We’re Looking For (experience, Challenger, gov sales, quota attainment, negotiation, market knowledge advantage, law enforcement note, location, travel)
    We could also include Benefits and Pay sections. Benefits: list from "Magnet Is Proud To Offer Benefits Such As ..." plus maybe learning and development? We'll include that list. Pay: compensation range. We should not include Schedule. Now we need to strip boilerplate: remove "Who We Are; What We Do; Where We’re Going" intro? That's not under requested headings, but we could keep as a preamble? The instruction: "Output ONLY the HTML fragment". It didn't say we must exclude intro text; but we should preserve ALL substantive information. The intro is substantive about company. However the requested headings list does not include a generic "About the company". But we could still include it as a

    before any headings? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use

    for section headings (e.g. those). It doesn't say we cannot have other headings. However they said "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." They didn't forbid other headings. But they also said "Prefer a few substantive sections over many thin ones." So we could include a brief intro as a

    before the first heading, not as a heading. That seems okay. Thus we can output:

    Magnet Forensics is a global leader in the development of digital investigative software that acquires, analyzes, and shares evidence from computers, smartphones, tablets, and IoT-related devices. We are continually innovating so our customers can deploy advanced and effective tools to protect their companies, communities, and countries. Serving thousands of customers globally, our solutions are playing a crucial role in modernizing digital investigations, helping investigators fight crime, protect assets, and guard national security. With employees based around the world, Magnet Forensics has been expanding our global presence. As a part of Magnet Forensics, you can expect to make a difference in the world, no matter what role you play. You’ll be supported through learning and development, not to mention an incredible team with unbelievable talent and integrity. If you think you would be the right person to join our team working towards this goal, we would love to hear from you!

    Then About the role heading with its paragraph(s). The About The Role section includes multiple paragraphs: "You'd be joining a team that finished last year over plan and is on pace to do it again...." We'll combine into one

    maybe multiple

    but we can keep as one

    with line breaks? Better to keep as multiple

    for readability but still okay. We'll extract the About The Role text: "You'd be joining a team that finished last year over plan and is on pace to do it again. That's not luck. The territory is real, the support is real, and the product does what we say it does. A territory with a running start. Active customers, renewals, and expansion opportunities are already in the region. Your first months are spent growing accounts that already trust us, not cold-calling a blank map. Support behind you. A dedicated SDR team sets qualified meetings, regional marketing runs events and campaigns in your area, and inbound demand is steady. It doesn't replace your own prospecting, but you're never building pipeline alone. Technical partners in every deal. Platform Consultants and Solutions Consultants work with you on strategy and demos. You don't need to be the deepest technical person in the room, just the one who knows when to bring them in. Expansion first. The fastest wins are upsells, cross-sells, and platform conversions inside existing accounts. New logos matter, but they're not where your quarter lives. A product that changes outcomes for victims. In most investigations the evidence is on a phone, a laptop, or in the cloud, and how fast an agency can get to it decides whether a case moves or stalls. Magnet shortens time to evidence. Investigators clear cases faster, prosecutors walk into court prepared, and victims and families see justice sooner. Forensic examiners, investigators, and prosecutors use our tools because they work, and you'll hear that directly when you're on-site. Enablement that actually enables. Our sales enablement program is built to make you a product and industry expert in under three months. You'll be running credible conversations with examiners and command staff well before your first quarter closes. A plan from day one. Your manager and your sales support team build the territory plan with you: who to call, where to visit, which deals to close. From there, you own the execution." We'll put that in

    . Responsibilities: "What You’ll Do" list: - Build and run annual and quarterly territory plans. - Structure to start, autonomy as the territory teaches you what works. - Structure deals of every size, from single products to multiyear platform agreements. - Public sector budgets come in odd shapes, and the reps who win here fit the deal to the agency's reality. - Grow existing accounts through cross-sell and upsell. - Most of your number comes from here, and it's the best selling we do because the customer already knows the value. - Prospect and network across the public sector. - SDRs contribute, but your own relationships in the law enforcement community are what compound. - Qualify inbound leads and turn the right ones into opportunities. - Get in front of customers. - Agency visits, regional conferences, and training events are a big part of the job and a big part of why it's fun. - Run demos and trials with Solutions Consultants. - They're one piece of the process, and doing them well keeps deals moving. - Manage quoting and keep the CRM current. - Accurate records are how we forecast and how you get paid. - Keep learning what customers need. - The reps who keep asking questions spot the next expansion first. - Work across the company, not around it. - Cross-collaboration is real here. - When a customer needs something, you go straight to the person in product, marketing, support, or customer success who can make it happen. - No gatekeepers, no waiting on a chain of approvals. - Decisions get made in minutes, not days or weeks, and it's a big reason we move faster than most startups. We'll output each as

    . Requirements: "What We’re Looking For" plus location/travel note. List: - Experience running a software sales territory with a deliberate strategy - Deep familiarity with the Challenger sales model - A history of selling into state and local government - Consistent quota attainment you can walk us through - Strong negotiation skills and comfort with long, multi-stakeholder procurement cycles - Knowledge of the digital forensics, cybersecurity, or physical security markets and their competitive landscape is an advantage - A note for law enforcement professionals: If you've worked in law enforcement or public safety and are considering the private sector, we want to hear from you even if you've never carried a quota. Your understanding