Mid-Level Account Executive

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate (EEO, AI tools, etc). Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: description of company and role: "Technology Advancement Group (TAG) is a veteran-owned systems integrator in Ashburn, Virginia. We design, build and integrate assured positioning, navigation and timing (PNT) hardware and software for the Department of Defense and the companies that build for it. Our products include anti-jam CRPA antennas, horizon-nulling antennas and a miniature M-code GPS receiver. All of them are shipping today, with test data behind them, and our engineers integrate them into the systems our customers already run. We're hiring an Account Executive to build and close DoD business across an open territory. You'll find the customers, run discovery with their engineers and program staff, shape the solution with ours, and close the deal. We sell outcomes, which usually means an integrated solution that draws on several products and sometimes a partner's capability. You'll report to the Director of Sales and work on-site in Ashburn with a small team. There's no big-company sales machine behind you here, so you'll help build how TAG sells." That's about role. - Responsibilities: list of duties: "You'll find the customers, run discovery with their engineers and program staff, shape the solution with ours, and close the deal." Also "You'll report to the Director of Sales and work on-site in Ashburn with a small team." Also "You'll help build how TAG sells." Also maybe "You'll keep enough in the pipeline to carry you between closes." Also "You'll follow up for months, and customers keep taking your calls because each touch gives them something useful." Also "You'll tell a customer when our product isn't the right fit, and you'll tell us when a process is slowing you down." Also "You'll want to be in the room. You'd rather be on a conference floor or at a test range than behind a screen all day." Those are more traits but could be responsibilities. But we need to separate responsibilities vs requirements vs qualifications vs skills. The posting includes a "Who You Are" section describing desired traits. Then "Required Experience" list bullet points: Cold outreach that built pipeline, Full-cycle deal ownership, CRM discipline, Selling a technical solution, Consultative selling, Builder, U.S. person status, Clearance eligibility. Then "Nice to haves": Active clearance, DoD customers, Industry partnerships, Multiple accounts in parallel. Then Pay: "$90,000 - $130,000 a year This role is subject to variable compensation of base plus OTE." Also mention "TAG is a small, veteran-owned company, and more than a quarter of our team has served. You'll work directly with leadership and engineering, and your results will show up in the company's numbers." That's maybe benefits? Not exactly benefits but could be about culture. Benefits: Not explicitly listed besides maybe "more than a quarter of our team has served" not a benefit. No explicit benefits like health, 401k. So we should not create Benefits section unless there is real specific content. There's none. Schedule: Not mentioned besides "work on-site in Ashburn". No schedule details. So we should not create Schedule. Pay: we have specific salary range and variable compensation. So include Pay section. Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. But we need to differentiate Requirements vs Qualifications vs Skills. The posting lumps many items under "Required Experience". Those could be considered Requirements. Also "Nice to haves" could be Qualifications or Skills. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use only when posting has real specific content. We can map: - About the role: as above. - Responsibilities: list of duties: find customers, run discovery, shape solution, close deal, report to Director, work on-site, help build sales process, maintain pipeline, follow up, give useful touch, tell customer when product not fit, tell us when process slowing, be in room (conference floor/test range). Could be many. - Requirements: the "Required Experience" bullet points (Cold outreach, Full-cycle deal ownership, CRM discipline, Selling a technical solution, Consultative selling, Builder, U.S. person status, Clearance eligibility). Also maybe "You must be a U.S. person..." and "Clearance eligibility". - Qualifications: maybe "Nice to haves" (Active clearance, DoD customers, Industry partnerships, Multiple accounts in parallel). Could also include "You want your pay tied to what you close" etc but that's more about motivation. - Skills: maybe specific skills like "Cold outreach using email, phone, LinkedIn", "Conference floor lead generation", "CRM usage", "Technical solution selling", "Consultative selling", "Builder mindset". But those overlap with requirements. Might be better to treat Requirements as the list, and Skills as maybe the technical understanding: "Understanding of CRPA antenna, M-code receiver, etc." But not explicit. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But headings are predefined; we can omit sections if no content. We could have About the role, Responsibilities, Requirements, Pay. That's four sections. That seems sufficient. We must not invent sections like Benefits or Schedule if no content. Thus output:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Pay

$90,000 - $130,000 a year. This role is subject to variable compensation of base plus OTE.

We must ensure we preserve all substantive information. Let's extract all substantive info from posting and ensure we include it somewhere. Let's list all substantive sentences: Company description: - Technology Advancement Group (TAG) is a veteran-owned systems integrator in Ashburn, Virginia. - We design, build and integrate assured positioning, navigation and timing (PNT) hardware and software for the Department of Defense and the companies that build for it. - Our products include anti-jam CRPA antennas, horizon-nulling antennas and a miniature M-code GPS receiver. - All of them are shipping today, with test data behind them, and our engineers integrate them into the systems our customers already run. Role description: - We're hiring an Account Executive to build and close DoD business across an open territory. - You'll find the customers, run discovery with their engineers and program staff, shape the solution with ours, and close the deal. - We sell outcomes, which usually means an integrated solution that draws on several products and sometimes a partner's capability. - You'll report to the Director of Sales and work on-site in Ashburn with a small team. - There's no big-company sales machine behind you here, so you'll help build how TAG sells. Who You Are (traits): - You're a seller who wants to help build a company, and you want your pay tied to what you close. - You bet on yourself. A large share of your pay here is commission, and that's how you want it. - DoD deals take months, so you keep enough in the pipeline to carry you between closes. - You're curious about the technology. You want to know how a CRPA antenna nulls a jammer and what an M-code receiver changes for the customer, because understanding it is how you sell it. - You keep asking engineers questions until the answer makes sense to you. - You're persistent without wearing people out. - You follow up for months, and customers keep taking your calls because each touch gives them something useful. - You say what you think. You'll tell a customer when our product isn't the right fit, and you'll tell us when a process is slowing you down. - You'd rather have the hard conversation now than lose the deal later. - You care who's on the other end. Our products go to warfighters who need to know where they are when GPS is jammed or spoofed. You take that seriously, and it shows in how you sell. - You want to be in the room. You'd rather be on a conference floor or at a test range than behind a screen all day. Required Experience (bullet points): - Cold outreach that built pipeline. You've built pipeline from nothing using email, phone, LinkedIn and other digital channels. You can show which sequences and messages got you meetings. - You've also worked conference floors and industry events, walking up to strangers and leaving with qualified leads. - Full-cycle deal ownership. You've owned deals from first contact to signed contract. Pick one and you can walk us through it: how you qualified it, who the stakeholders were, where it nearly died and what you did to close it. - You've run deals with several decision-makers and sales cycles that lasted months. - CRM discipline. You use a CRM to run your own pipeline. You can show how the data told you where to spend your time, which deals were stalling and what your forecast really was. - Selling a technical solution. You've learned a technical product well enough to sell it credibly, and you can explain a solution you sold in plain language. You've worked with your own engineers to shape the offer, and you've held your own with the customer's engineers during discovery. - It's a plus if you've carried several products at once and matched each one to the right problem. - Consultative selling. You start with discovery and find the customer's real problem before you pitch anything. You've reshaped a deal, or walked away from one, when your first answer wasn't the right fit. - Builder. You've helped build a company or team that was still taking shape. When a process didn't exist, you created it. When something wasn't working, you said so and fixed it. You can work without big-company support: no sales ops team, no playbook and no one to hand the admin to. - U.S. person status. This role involves access to technical data controlled under the International Traffic in Arms Regulations (ITAR). You must be a U.S. person as defined in 22 CFR 120.62. That includes U.S. citizens, lawful permanent residents, and certain protected individuals such as refugees and asylees. - Clearance eligibility. You must be able to obtain and maintain a U.S. government security clearance, which requires U.S. citizenship. Nice to haves: - Active clearance. You hold a current security clearance, or you've held one recently. - DoD customers. You've sold to the Department of Defense, whether to program offices, prime contractors or operational units. You understand how requirements, funding and buying decisions move through defense organizations. - Industry partnerships. You've looked at a customer requirement, seen where a partner's product or capability could close a gap, and put that partnership together to win the deal. - Multiple accounts in parallel. You've run several active customers and deals at once without letting any of them go cold. You can explain how you decided each week where your time went. Pay: - $90,000 - $130,000 a year This role is subject to variable compensation of base plus OTE. Additional: - TAG is a small, veteran-owned company, and more than a quarter of our team has served. You'll work directly with leadership and engineering, and your results will show up in the company's numbers. - TAG is an equal opportunity employer... (boilerplate to remove) - AI tools usage... (remove) - Contact for data processing... (remove) We must remove boilerplate: EEO, AI tools, contact info. We must preserve all substantive info: includes