Outside Sales Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
- About Us: description of company: "Join a dynamic engineering sales company that is helping to bring New England into a carbon-free future. Established in 1986, APA offers a vast selection of products for the HVAC industry. Everything we do is rooted in our commitment to offer quality products and solutions. Our focus remains on delivering dependable products, strong technical knowledge, and responsive service to help our customers successfully design, build, and maintain efficient HVAC systems."
- Job Description: Role: Outside Sales Engineer (Maine/New Hampshire) ... This is an exciting time at APA with explosive growth and representation of the best products in the industry. We are looking for results-oriented team members that take pride in the products and services they can offer to their customers and colleagues. This is a great opportunity to learn the ins and outs of major projects while gaining exposure to our impressive portfolio of work.
- Responsibilities: list bullet points.
- Requirements: list bullet points.
- Locations: Ability to work out of our MA office in Newburyport or our ME office in Kennebunk.
- Compensation: This is a commission-based sales opportunity with earning potential directly tied to sales performance and results.
- Then EEO boilerplate: "Ambient Enterprises provides equal employment opportunities..." This is boilerplate, should be removed.
We need to decide sections: About Us (maybe as "About the company"? The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use other headings if appropriate? Probably we should stick to those headings where applicable. There's no "About the role" but we have "About Us" which is about company. Could we use "About the role"? Not exactly. The posting includes "Job Description" and "Role: Outside Sales Engineer". Could we treat that as "About the role"? Probably yes: we can put a heading About the role
and include the role description. The instruction says do NOT repeat the job title as a heading (the page already shows it). So we shouldn't put the job title as heading, but we can have a section about the role.
Thus sections:
- About the role (contains description of role and maybe company intro? Actually "About Us" is separate. Could we have "About the company"? Not in list. But we could incorporate company description into About the role? Might be okay. However we need to preserve all substantive info. The "About Us" paragraph is about company. Could we put it under a heading like "About the company"? Not in examples but maybe allowed. The instruction says 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. ...)" implying those are typical. Safer to stick to those headings. We could put company info under "About the role" as part of role description? Might be mixing.
Alternatively we could have sections: About the role, Responsibilities, Requirements, Pay (compensation), maybe Locations? Not in list but could be part of About the role or Requirements? Locations is specific info; we could put it under a short
after Requirements? The instruction says fold minor metadata into a short
or drop it. Locations could be considered minor metadata; we could put it in a
after Requirements.
Compensation: we have commission-based sales opportunity. That's substantive; we should include a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation: commission-based sales opportunity with earning potential directly tied to sales performance and results. That's Pay info. So we should include a
Pay
with that info.
We should not include Benefits or Schedule as not mentioned.
We should not include Qualifications or Skills unless present; we have Requirements which includes some qualifications; we could treat Requirements as the heading. Could also have Skills separate but not needed.
Thus sections: About the role, Responsibilities, Requirements, Pay.
We need to output HTML fragment only.
We need to use - for any list of duties/requirements/benefits. So Responsibilities and Requirements should be lists.
Prose for other sections: About the role and Pay.
We need to preserve all substantive information: Let's extract.
About the role: from posting:
"Job Description Role: Outside Sales Engineer (Maine/New Hampshire) You will play a crucial role as a sales team member helping to promote the APA brand. This is an exciting time at APA with explosive growth and representation of the best products in the industry. We are looking for results-oriented team members that take pride in the products and services they can offer to their customers and colleagues. This is a great opportunity to learn the ins and outs of major projects while gaining exposure to our impressive portfolio of work."
Also maybe include the About Us paragraph? That is about company, not role. Could we incorporate it under About the role? Might be okay but it's about company. However we could also add a separate section like "About the company" but not in list. The instruction says we can use headings like About the role etc. It doesn't forbid other headings, but to be safe we could include About the company as a heading? Might be considered extra but not prohibited. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for sections; but we could also use other headings if needed? The examples are just examples; they didn't say "only these". But they said "use for section headings (e.g. ...)" meaning we should use h3 for any section heading. So we can use any heading we want as long as it's h3. So we could have About the company, About the role, etc. However they also said "Prefer a few substantive sections over many thin ones." So we might combine About Us and About the role into one section maybe "About the role and company". But better to keep them separate? Might be thin.
Let's think: The About Us paragraph is substantive; we could put it under a heading "About the company". That's a substantive section. Then we have About the role section. That's two sections. Could we combine them? Possibly but then we lose clarity. The instruction says prefer a few substantive sections over many thin ones. Two sections is fine.
Thus we will have:
About the company
Join a dynamic engineering sales company that is helping to bring New England into a carbon-free future. Established in 1986, APA offers a vast selection of products for the HVAC industry. Everything we do is rooted in our commitment to offer quality products and solutions. Our focus remains on delivering dependable products, strong technical knowledge, and responsive service to help our customers successfully design, build, and maintain efficient HVAC systems.
About the role
Role: Outside Sales Engineer (Maine/New Hampshire). You will play a crucial role as a sales team member helping to promote the APA brand. This is an exciting time at APA with explosive growth and representation of the best products in the industry. We are looking for results-oriented team members that take pride in the products and services they can offer to their customers and colleagues. This is a great opportunity to learn the ins and outs of major projects while gaining exposure to our impressive portfolio of work.
Then Responsibilities list.
Responsibilities bullet points from posting:
- Establish, develop and maintain strong relationships with owners, engineers, and end users.
- Infiltrate accounts to position APA’s manufacturers as Basis of Design.
- Sell the complete APA portfolio of products and work directly and consistently with APA’s manufacturers.
- Identify, develop and pursue new business opportunities while growing existing customer accounts.
- Develop technical knowledge of our products through commitment to professional development through online and in-person factory training.
- Review design documents and specifications, perform takeoffs and utilize various manufacturer tools and software to develop project-specific quotes.
- Partner with internal team members to support successful project execution.
- Oversee projects from design through start-up & commissioning to ensure effective closeout.
- Visit job sites as required to assess field conditions/issues and assist with developing action plan to remedy.
- Assist in resolving technical issues that arise during project execution.
- Actively participate in company sales meetings.
- Manage virtual files for projects that you are involved with.
- Support database management, bid forecast and pipeline providing regular updates to leadership.
- Periodic travel for training, national sales meetings, industry events and customer factory trips.
We need to output as - each.
Then Requirements:
- Must be self-motivated, organized and detail orientated.
- The ability to thrive in a fast-paced environment.
- Collaborate closely with cross-functional teams.
- Clear communication. You will be interacting with team members, manufacturers, and clients. Strong written and verbal communication is key.
- Strong computer skills. Proficient in Word, Excel, Adobe or Bluebeam.
- Preferred Mechanical Engineering Degree, or equivalent experience in the HVAC industry.
Note: "Preferred Mechanical Engineering Degree, or equivalent experience in the HVAC industry." is a requirement? It's under Requirements but says Preferred. We'll keep as list item.
Then Locations: Ability to work out of our MA office in Newburyport or our ME office in Kennebunk. This is minor metadata; we can put as a
after Requirements maybe.
Then Pay: Compensation: This is a commission-based sales opportunity with earning potential directly tied to sales performance and results.
We should not include EEO boilerplate.
Thus final HTML:
About the company
...
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Locations: Ability to work out of our MA office in Newburyport or our ME office in Kennebunk.
Pay
This is a commission-based sales opportunity with earning potential directly tied to sales performance and results.
Check for any duplicated lines: none.
Check for any boilerplate removed: EEO removed.
Check for any minor metadata folded: Locations as short p.
Check for any missing substantive info: Did we miss anything? The posting also includes "Ambient Enterprises provides
for prose. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: description of company: "Join a dynamic engineering sales company that is helping to bring New England into a carbon-free future. Established in 1986, APA offers a vast selection of products for the HVAC industry. Everything we do is rooted in our commitment to offer quality products and solutions. Our focus remains on delivering dependable products, strong technical knowledge, and responsive service to help our customers successfully design, build, and maintain efficient HVAC systems." - Job Description: Role: Outside Sales Engineer (Maine/New Hampshire) ... This is an exciting time at APA with explosive growth and representation of the best products in the industry. We are looking for results-oriented team members that take pride in the products and services they can offer to their customers and colleagues. This is a great opportunity to learn the ins and outs of major projects while gaining exposure to our impressive portfolio of work. - Responsibilities: list bullet points. - Requirements: list bullet points. - Locations: Ability to work out of our MA office in Newburyport or our ME office in Kennebunk. - Compensation: This is a commission-based sales opportunity with earning potential directly tied to sales performance and results. - Then EEO boilerplate: "Ambient Enterprises provides equal employment opportunities..." This is boilerplate, should be removed. We need to decide sections: About Us (maybe as "About the company"? The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use other headings if appropriate? Probably we should stick to those headings where applicable. There's no "About the role" but we have "About Us" which is about company. Could we use "About the role"? Not exactly. The posting includes "Job Description" and "Role: Outside Sales Engineer". Could we treat that as "About the role"? Probably yes: we can put a heading About the role
and include the role description. The instruction says do NOT repeat the job title as a heading (the page already shows it). So we shouldn't put the job title as heading, but we can have a section about the role.
Thus sections:
- About the role (contains description of role and maybe company intro? Actually "About Us" is separate. Could we have "About the company"? Not in list. But we could incorporate company description into About the role? Might be okay. However we need to preserve all substantive info. The "About Us" paragraph is about company. Could we put it under a heading like "About the company"? Not in examples but maybe allowed. The instruction says 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. ...)" implying those are typical. Safer to stick to those headings. We could put company info under "About the role" as part of role description? Might be mixing.
Alternatively we could have sections: About the role, Responsibilities, Requirements, Pay (compensation), maybe Locations? Not in list but could be part of About the role or Requirements? Locations is specific info; we could put it under a short
for section headings (e.g. ...)" implying those are typical. Safer to stick to those headings. We could put company info under "About the role" as part of role description? Might be mixing. Alternatively we could have sections: About the role, Responsibilities, Requirements, Pay (compensation), maybe Locations? Not in list but could be part of About the role or Requirements? Locations is specific info; we could put it under a short
after Requirements? The instruction says fold minor metadata into a short
or drop it. Locations could be considered minor metadata; we could put it in a
after Requirements. Compensation: we have commission-based sales opportunity. That's substantive; we should include a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation: commission-based sales opportunity with earning potential directly tied to sales performance and results. That's Pay info. So we should include a
Pay
with that info. We should not include Benefits or Schedule as not mentioned. We should not include Qualifications or Skills unless present; we have Requirements which includes some qualifications; we could treat Requirements as the heading. Could also have Skills separate but not needed. Thus sections: About the role, Responsibilities, Requirements, Pay. We need to output HTML fragment only. We need to use- for any list of duties/requirements/benefits. So Responsibilities and Requirements should be lists.
Prose for other sections: About the role and Pay.
We need to preserve all substantive information: Let's extract.
About the role: from posting:
"Job Description Role: Outside Sales Engineer (Maine/New Hampshire) You will play a crucial role as a sales team member helping to promote the APA brand. This is an exciting time at APA with explosive growth and representation of the best products in the industry. We are looking for results-oriented team members that take pride in the products and services they can offer to their customers and colleagues. This is a great opportunity to learn the ins and outs of major projects while gaining exposure to our impressive portfolio of work."
Also maybe include the About Us paragraph? That is about company, not role. Could we incorporate it under About the role? Might be okay but it's about company. However we could also add a separate section like "About the company" but not in list. The instruction says we can use headings like About the role etc. It doesn't forbid other headings, but to be safe we could include About the company as a heading? Might be considered extra but not prohibited. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for sections; but we could also use other headings if needed? The examples are just examples; they didn't say "only these". But they said "use
for section headings (e.g. ...)" meaning we should use h3 for any section heading. So we can use any heading we want as long as it's h3. So we could have About the company, About the role, etc. However they also said "Prefer a few substantive sections over many thin ones." So we might combine About Us and About the role into one section maybe "About the role and company". But better to keep them separate? Might be thin. Let's think: The About Us paragraph is substantive; we could put it under a heading "About the company". That's a substantive section. Then we have About the role section. That's two sections. Could we combine them? Possibly but then we lose clarity. The instruction says prefer a few substantive sections over many thin ones. Two sections is fine. Thus we will have:
About the company
Join a dynamic engineering sales company that is helping to bring New England into a carbon-free future. Established in 1986, APA offers a vast selection of products for the HVAC industry. Everything we do is rooted in our commitment to offer quality products and solutions. Our focus remains on delivering dependable products, strong technical knowledge, and responsive service to help our customers successfully design, build, and maintain efficient HVAC systems.
About the role
Role: Outside Sales Engineer (Maine/New Hampshire). You will play a crucial role as a sales team member helping to promote the APA brand. This is an exciting time at APA with explosive growth and representation of the best products in the industry. We are looking for results-oriented team members that take pride in the products and services they can offer to their customers and colleagues. This is a great opportunity to learn the ins and outs of major projects while gaining exposure to our impressive portfolio of work.
Then Responsibilities list. Responsibilities bullet points from posting: - Establish, develop and maintain strong relationships with owners, engineers, and end users. - Infiltrate accounts to position APA’s manufacturers as Basis of Design. - Sell the complete APA portfolio of products and work directly and consistently with APA’s manufacturers. - Identify, develop and pursue new business opportunities while growing existing customer accounts. - Develop technical knowledge of our products through commitment to professional development through online and in-person factory training. - Review design documents and specifications, perform takeoffs and utilize various manufacturer tools and software to develop project-specific quotes. - Partner with internal team members to support successful project execution. - Oversee projects from design through start-up & commissioning to ensure effective closeout. - Visit job sites as required to assess field conditions/issues and assist with developing action plan to remedy. - Assist in resolving technical issues that arise during project execution. - Actively participate in company sales meetings. - Manage virtual files for projects that you are involved with. - Support database management, bid forecast and pipeline providing regular updates to leadership. - Periodic travel for training, national sales meetings, industry events and customer factory trips. We need to output as- each.
Then Requirements:
- Must be self-motivated, organized and detail orientated.
- The ability to thrive in a fast-paced environment.
- Collaborate closely with cross-functional teams.
- Clear communication. You will be interacting with team members, manufacturers, and clients. Strong written and verbal communication is key.
- Strong computer skills. Proficient in Word, Excel, Adobe or Bluebeam.
- Preferred Mechanical Engineering Degree, or equivalent experience in the HVAC industry.
Note: "Preferred Mechanical Engineering Degree, or equivalent experience in the HVAC industry." is a requirement? It's under Requirements but says Preferred. We'll keep as list item.
Then Locations: Ability to work out of our MA office in Newburyport or our ME office in Kennebunk. This is minor metadata; we can put as a
after Requirements maybe. Then Pay: Compensation: This is a commission-based sales opportunity with earning potential directly tied to sales performance and results. We should not include EEO boilerplate. Thus final HTML:
About the company
...
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Locations: Ability to work out of our MA office in Newburyport or our ME office in Kennebunk.
Pay
This is a commission-based sales opportunity with earning potential directly tied to sales performance and results.
Check for any duplicated lines: none. Check for any boilerplate removed: EEO removed. Check for any minor metadata folded: Locations as short p. Check for any missing substantive info: Did we miss anything? The posting also includes "Ambient Enterprises provides
- each.
Then Requirements:
- Must be self-motivated, organized and detail orientated.
- The ability to thrive in a fast-paced environment.
- Collaborate closely with cross-functional teams.
- Clear communication. You will be interacting with team members, manufacturers, and clients. Strong written and verbal communication is key.
- Strong computer skills. Proficient in Word, Excel, Adobe or Bluebeam.
- Preferred Mechanical Engineering Degree, or equivalent experience in the HVAC industry.
Note: "Preferred Mechanical Engineering Degree, or equivalent experience in the HVAC industry." is a requirement? It's under Requirements but says Preferred. We'll keep as list item.
Then Locations: Ability to work out of our MA office in Newburyport or our ME office in Kennebunk. This is minor metadata; we can put as a