Deal Desk Analyst - Public Sector
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have content for About the role (intro paragraph). Responsibilities (list of duties). Requirements (list). Benefits (salary range and benefits list). Pay? The posting includes salary range; that could be considered Pay. But we also have Benefits section includes salary and benefits. The instruction: include a section ONLY when posting has real, specific content for it. We can combine Pay and Benefits? But they are separate headings. We have salary range and benefits details. Could put Pay section with salary range, Benefits section with benefits list. However they said "Prefer a few substantive sections over many thin ones." Might combine into Benefits? But they explicitly list Pay as possible heading. The posting includes salary range; that is Pay. Benefits list is separate. So we can have both Pay and Benefits sections.
Schedule: not mentioned, so omit.
Qualifications: maybe same as Requirements? The posting includes Requirements bullet list. Could treat as Requirements. Qualifications maybe not separate; we can omit Qualifications if no distinct content.
Skills: not explicitly listed; maybe we can omit.
Thus sections: About the role, Responsibilities, Requirements, Pay, Benefits.
We need to use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate.
We need to preserve all substantive information.
Let's extract content.
About the role: first paragraph: "As a member of the Business Operations Team at OnLogic, you'll be the operational glue holding our federal and defense business together. This is a new role created to keep pace with our growing public sector footprint. You'll sit at the center of every rated order and every proposal deadline, making sure our sales team's commitments and our company's ability to deliver never drift apart. We believe in the power of in-person collaboration and the benefits of a strong workplace community. Therefore, this role requires an onsite presence at our South Burlington, Vermont office. We encourage candidates who are able to relocate or comfortably commute to apply."
That's prose.
Responsibilities: bullet list after "In this role, you'll be responsible for:" then list items:
- Govern the pipeline of all incoming Public Sector Requests for Quotes (RFQs) alongside Sales to assess capacity and manage Defense Priorities and Allocations System (DPAS) commitments.
- Align with Sales team members and Capture Manager to ensure public sector opportunities are current in our Customer Relationship Management (CRM) system (HubSpot) across long, multi-stage procurement cycles.
- Track all public sector opportunities from bid through the final award.
- Verify, log, and process Public Sector orders—including DPAS DO/DX rated and non-rated opportunities—ensuring Defense Production Act compliance while keeping priority production on track.
- Partner with Manufacturing and Supply Chain to protect priority production slots.
- Use lessons learned to train and hold the Sales team accountable to the fundamentals of rated orders and federal contracting and compliance, so customer expectations and business reality stay aligned.
We need to keep all details.
Requirements: bullet list after "Requirements":
- Bachelor's degree in Business Management or a related field (equivalent professional/military experience will be considered).
- At least 3 - 5 years of experience in Sales Operations or Federal Compliance with Government or Defense customers.
- Understanding and/or knowledge of industrial compute or rugged compute on the edge is a plus.
- Ability to work in the U.S. without visa sponsorship, now and in the future.
Also there is "Who we're looking for:" with bullet-like sentences but those are more description; could be considered part of Requirements or maybe Skills. But we can incorporate as part of Requirements? The instruction: preserve all substantive information. Could treat "Who we're looking for:" as additional requirements/skills. Might be better to include as part of Requirements or maybe a separate Skills section. Since they are not explicit requirements but desired traits. Could put under Requirements as well, but we already have a Requirements list. Could add another
under Requirements? Might be messy. Perhaps better to create a Skills section for those traits. However the instruction says prefer few substantive sections over many thin ones. So we could incorporate those traits into Requirements as additional bullet points.
Let's list them:
- Someone obsessed with the details who prioritizes pipeline hygiene and knows what we need to do internally to win public sector bids.
- A federal contracts and compliance expert who can interpret a flowdown clause and immediately translate it to actions across the organization.
- Someone who has processed DPAS rated orders before and isn't intimidated by DO/DX priority ratings or the Defense Production Act.
- A process-minded operator who holds the sales team accountable for keeping CRM data clean and procurement timelines visible, even when deals stretch over many months.
We'll add those as bullet points under Requirements.
Pay: The posting includes: "Benefits The salary range for this role is $85,000 to $105,000. We determine final compensation based on discussions with applicants and their experience in similar roles. A competitive Salary based upon your experience and the requirements of the role A competitive Salary based upon your experience and the requirements of the roleA comprehensive Benefits package401k Plan with 3% Employer ContributionAn Annual Profit Share Bonus Paid Maternity & Paternity Leave, and Short & Long Term DisabilityOpportunity to Participate in our Employee Stock Purchase PlanA personal development plan created to help you (and us) grow"
There's duplication and weird formatting. We need to extract substantive info: salary range $85,000 to $105,000. Then benefits list: competitive salary (already), 401k Plan with 3% Employer Contribution, Annual Profit Share Bonus, Paid Maternity & Paternity Leave, Short & Long Term Disability, Opportunity to Participate in Employee Stock Purchase Plan, personal development plan.
We need to avoid duplication. So Pay section: salary range. Benefits section: list of benefits.
We must not include filler like "competitive Salary based upon your experience and the requirements of the role" repeated; we can mention competitive salary based on experience.
Let's craft.
Pay section: The salary range for this role is $85,000 to $105,000, with final compensation determined based on discussions with applicants and their experience in similar roles.
Benefits section: - 401k Plan with 3% Employer Contribution
- Annual Profit Share Bonus
- Paid Maternity & Paternity Leave
- Short & Long Term Disability
- Opportunity to Participate in Employee Stock Purchase Plan
- Personal development plan to support growth
We might also mention competitive salary but that's covered in Pay.
Now ensure we don't include boilerplate like "Learn more about Life at OnLogic." etc. Also remove "Who we are:" paragraph? That's about company description; could be considered About the role? Might be extra but it's substantive about company. Could include as part of About the role? The About the role section currently only includes intro. Could add another paragraph about company values etc. But we need to preserve all substantive information. The "Who we are:" paragraph describes OnLogic employees, mission, values, etc. That's substantive. Should we include it? It's not about the role directly but about company. Could be part of About the role or maybe a separate section like "About OnLogic". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could add that content to About the role as additional paragraph.
Thus About the role will have two paragraphs: first about role, second about company.
Let's extract "Who we are:" paragraph:
"OnLogic employees have the opportunity to shape our future and drive impactful change. We design and manufacture specialized edge computing solutions for companies all over the world, helping them to make the seemingly impossible possible. Our computers are designed to work where others fail, and it's our vision to be the first choice in edge computing. To make that vision a reality, we've built a team of ambitious problem solvers, guided by the company's core values of Open, Fair, Innovative, and Independent. We have an open office, open salaries, and strive to be fair and transparent in our decision making. We encourage input and feedback from every member of our team and look to improve ourselves and our business every single day. Diversity is an essential element of our core values. Not just respecting, but actively embracing a variety of backgrounds, life experiences, and opinions, helps us foster innovation, enhances our problem-solving capabilities, and promotes learning and engagement among the members of our team. We strongly encourage those with diverse backgrounds to apply. We are committed to providing a safe, inclusive, and harassment-free workplace for all employees. We do not tolerate any form of harassment, discrimination, or bias based on race, ethnicity, gender, sexual orientation, religion, disability, age, or any other protected characteristic. To learn more about our values, our mission and what it's like to work at OnLogic, visit www.onlogic.com/careers."
We should remove the invitation to visit website? That's maybe boilerplate? It's not navigation but it's a call to action. Might be considered okay to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The visit link is not exactly those; it's more about learning more. Could keep but it's not essential. Might be considered promotional. Safer to omit? The instruction says preserve ALL substantive information; does that include the link? It's not substantive to the role. I'd lean to omit it as it's more of a navigation/link. However it's not explicitly listed as boilerplate to remove. But it's a call to action similar to "Learn more about Life at OnLogic." which we should remove. So we can omit the final sentence.
Thus About the role second paragraph: everything up to "We do not tolerate any form of harassment, discrimination, or bias based on race, ethnicity, gender, sexual orientation, religion, disability, age, or any other protected characteristic."
Now we need to ensure no duplicated lines.
Now produce HTML.
Structure:
About the role
...
...
Responsibilities
- ...
...
Requirements
- ...
...
Pay
...
Benefits
- ...
...
Make sure no extra whitespace issues.
Let's craft the paragraphs.
About the role first paragraph:
As a member of the Business Operations Team at OnLogic, you'll be the operational glue holding our federal and defense business together. This is a new role created to keep pace with our growing public sector footprint. You'll sit at the center of every rated order and every proposal deadline, making sure our sales team's commitments and our company's ability to deliver never drift apart. We believe in the power of in-person collaboration and the benefits of a strong workplace community. Therefore, this role requires an onsite presence at our South Burlington, Vermont office. We encourage candidates who are able to relocate or comfortably commute to apply.
Second paragraph (company):
OnLogic employees have the opportunity to shape our future and drive impactful change. We design and manufacture specialized edge computing solutions for companies all over the world, helping them to make the seemingly impossible possible. Our computers are designed to work where others fail, and it's our vision to be the first choice in edge computing. To make that vision a reality, we've built a team of ambitious problem solvers, guided by the company's core values of Open, Fair, Innov
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate. We need to preserve all substantive information. Let's extract content. About the role: first paragraph: "As a member of the Business Operations Team at OnLogic, you'll be the operational glue holding our federal and defense business together. This is a new role created to keep pace with our growing public sector footprint. You'll sit at the center of every rated order and every proposal deadline, making sure our sales team's commitments and our company's ability to deliver never drift apart. We believe in the power of in-person collaboration and the benefits of a strong workplace community. Therefore, this role requires an onsite presence at our South Burlington, Vermont office. We encourage candidates who are able to relocate or comfortably commute to apply." That's prose. Responsibilities: bullet list after "In this role, you'll be responsible for:" then list items: - Govern the pipeline of all incoming Public Sector Requests for Quotes (RFQs) alongside Sales to assess capacity and manage Defense Priorities and Allocations System (DPAS) commitments. - Align with Sales team members and Capture Manager to ensure public sector opportunities are current in our Customer Relationship Management (CRM) system (HubSpot) across long, multi-stage procurement cycles. - Track all public sector opportunities from bid through the final award. - Verify, log, and process Public Sector orders—including DPAS DO/DX rated and non-rated opportunities—ensuring Defense Production Act compliance while keeping priority production on track. - Partner with Manufacturing and Supply Chain to protect priority production slots. - Use lessons learned to train and hold the Sales team accountable to the fundamentals of rated orders and federal contracting and compliance, so customer expectations and business reality stay aligned. We need to keep all details. Requirements: bullet list after "Requirements": - Bachelor's degree in Business Management or a related field (equivalent professional/military experience will be considered). - At least 3 - 5 years of experience in Sales Operations or Federal Compliance with Government or Defense customers. - Understanding and/or knowledge of industrial compute or rugged compute on the edge is a plus. - Ability to work in the U.S. without visa sponsorship, now and in the future. Also there is "Who we're looking for:" with bullet-like sentences but those are more description; could be considered part of Requirements or maybe Skills. But we can incorporate as part of Requirements? The instruction: preserve all substantive information. Could treat "Who we're looking for:" as additional requirements/skills. Might be better to include as part of Requirements or maybe a separate Skills section. Since they are not explicit requirements but desired traits. Could put under Requirements as well, but we already have a Requirements list. Could add another
- under Requirements? Might be messy. Perhaps better to create a Skills section for those traits. However the instruction says prefer few substantive sections over many thin ones. So we could incorporate those traits into Requirements as additional bullet points.
Let's list them:
- Someone obsessed with the details who prioritizes pipeline hygiene and knows what we need to do internally to win public sector bids.
- A federal contracts and compliance expert who can interpret a flowdown clause and immediately translate it to actions across the organization.
- Someone who has processed DPAS rated orders before and isn't intimidated by DO/DX priority ratings or the Defense Production Act.
- A process-minded operator who holds the sales team accountable for keeping CRM data clean and procurement timelines visible, even when deals stretch over many months.
We'll add those as bullet points under Requirements.
Pay: The posting includes: "Benefits The salary range for this role is $85,000 to $105,000. We determine final compensation based on discussions with applicants and their experience in similar roles. A competitive Salary based upon your experience and the requirements of the role A competitive Salary based upon your experience and the requirements of the roleA comprehensive Benefits package401k Plan with 3% Employer ContributionAn Annual Profit Share Bonus Paid Maternity & Paternity Leave, and Short & Long Term DisabilityOpportunity to Participate in our Employee Stock Purchase PlanA personal development plan created to help you (and us) grow"
There's duplication and weird formatting. We need to extract substantive info: salary range $85,000 to $105,000. Then benefits list: competitive salary (already), 401k Plan with 3% Employer Contribution, Annual Profit Share Bonus, Paid Maternity & Paternity Leave, Short & Long Term Disability, Opportunity to Participate in Employee Stock Purchase Plan, personal development plan.
We need to avoid duplication. So Pay section: salary range. Benefits section: list of benefits.
We must not include filler like "competitive Salary based upon your experience and the requirements of the role" repeated; we can mention competitive salary based on experience.
Let's craft.
Pay section:
- 401k Plan with 3% Employer Contribution
- Annual Profit Share Bonus
- Paid Maternity & Paternity Leave
- Short & Long Term Disability
- Opportunity to Participate in Employee Stock Purchase Plan
- Personal development plan to support growth
- ... ...
- ... ...
- ... ...
The salary range for this role is $85,000 to $105,000, with final compensation determined based on discussions with applicants and their experience in similar roles.
Benefits section:About the role
...
...
Responsibilities
Requirements
Pay
...
Benefits