Sales Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Remove boilerplate. Must preserve all substantive info. Let's parse the posting. First paragraph: "It’s your time, make it matter. At Peterson, we partner with our customers to build the future. For over 90 years, our peoples’ work has shaped the communities where we live, where we raise our families, and where we thrive. Peterson’s legacy permeates every aspect of our communities. From roads and bridges, back-up power at hospitals, fire-fighting, concerts and moving goods; we are everywhere you look. At Peterson, you don’t just have a career, you have a purpose. Our family-oriented environment is built on safety, winning, growth, and professional achievement. Hiring and developing exceptional people is critical to our continued success. We have high standards for a good reason: our people represent Peterson, our family, our brand, and our values. You have high expectations too. You are exceptionally motivated, have outstanding skills, and want your work to matter. Peterson offers competitive wages, generous benefits, and promotional opportunities at a family-owned and operated business. It’s time to use your skills and passion to do work that matters!" This is about the company, maybe "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections accordingly. We have a "Job Description" heading then description of role. Let's extract sections: - About the role: maybe the initial paragraph describing Peterson and the role? Could be "About the role" includes description of position: "Peterson Cat Power Systems has the immediate need for an experienced Sales Engineer based at our Hillsboro, OR location. When not traveling for customer support, persons in this position will work On Site at our Hillsboro, OR location. Reporting to General Manager responsible for Amazon (“AWS”) or the Mission Critical Team ("MCT") account management team, the Sales Engineer provides support for the AWS or MCT account by facilitating product development that meets customer and site requirements. The sales engineer will work directly with Cat and other manufacturers to integrate their product and technology into our product portfolio. This position is required to travel to customer installations to audit our product solution to confirm it is meeting or exceeding the customer’s requirements and facilitate product improvement. Provide technical support and recommendations to the assigned Sales Representative to Amazon or the Mission Critical Team." That seems like role description. - Responsibilities: The "Essential Job Functions" list. - Requirements: maybe "Qualifications" section includes education/experience, certificates, etc. But we also have a separate "Qualifications" heading. The instruction says we can have both Requirements and Qualifications sections. We need to decide what goes where. Typically "Requirements" could be the essential functions? But they already have "Essential Job Functions". Might map to Responsibilities. The "Qualifications" section includes education, experience, certificates, driver's license, etc. Also "Other Job Functions" list includes soft skills etc. Those could be Skills. We need to avoid filler like "commensurate with experience". Not present. We need to include Pay, Benefits, Schedule only if stated. The posting mentions "Peterson offers competitive wages, generous benefits, and promotional opportunities". That's about benefits and wages but not specific numbers. It says "competitive wages" (Pay) and "generous benefits" (Benefits). No schedule specifics besides travel up to 50% expected. That's schedule/travel info. So we can include Pay, Benefits, Schedule sections with that info. However we must not include placeholder like "commensurate with experience". Here we have "competitive wages" and "generous benefits". That's substantive enough? It's vague but still mentions they offer competitive wages and generous benefits. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive wages" and "generous benefits" are not exactly filler; they are statements. So we can include. Schedule: "Up to 50% travel expected." That's schedule/travel. So we can include Schedule section. Now we need to output HTML fragment only, no /. Use

for each section heading. Use

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

  for prose. We need to 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. Let's extract all substantive info: Company intro paragraph (first big paragraph). Should we include that? It's about Peterson, not necessarily role. Could go under About the role or maybe a separate "About the company" but not in allowed headings. We could put it under About the role as introductory prose. Job Description paragraph: "Peterson Cat Power Systems has the immediate need for an experienced Sales Engineer based at our Hillsboro, OR location. When not traveling for customer support, persons in this position will work On Site at our Hillsboro, OR location. Reporting to General Manager responsible for Amazon (“AWS”) or the Mission Critical Team ("MCT") account management team, the Sales Engineer provides support for the AWS or MCT account by facilitating product development that meets customer and site requirements. The sales engineer will work directly with Cat and other manufacturers to integrate their product and technology into our product portfolio. This position is required to travel to customer installations to audit our product solution to confirm it is meeting or exceeding the customer’s requirements and facilitate product improvement. Provide technical support and recommendations to the assigned Sales Representative to Amazon or the Mission Critical Team." That's prose. Essential Job Functions list: bullet points: - Review technical aspects of project bid documents to assure requirement are met and offer solutions to assure compliance. - Review project requirements and propose value added solutions when applicable. - In coordination sales representatives and estimators draft Customer Solution Quoter (CSQ) configuration to establish project cost on complex projects. - Work with AWS or MCT support team, communicate with engineers, contractors, and end user customers to answer application and installation questions. - Meet with AWS or MCT site construction teams on continuous product improvement processes. - Work with Caterpillar factory and other vendors to gather required information for quoting purposes. - Work in concert with Project Managers or the MCT on assigned projects. - Travel to customer sites and manufacturers. Up to 50% travel expected. Other Job Functions list (maybe skills/behaviors): - Occasional attendance at factory witness testing of equipment. - Customer meeting attendance with sales and/or project manager teams - Information research - Maintains punctual, regular, and predictable attendance. - Works collaboratively in a team environment with a spirit of cooperation. - Displays excellent communication skills including presentation, persuasion, and negotiation skills required in working with customers/ coworkers, including the ability to communicate effectively and remain calm and courteous under pressure. - Respectfully takes direction from supervisor/ manager. Qualifications section: - EDUCATION And/or EXPERIENCE: Bachelor of Science Degree from a fully accredited college in Electrical or Mechanical Engineering or other closely related field; and a minimum of three years of directly related experience in power generation or construction industry; or an equivalent combination of education and work experience. - CERTIFICATES, LICENSES, REGISTRATIONS: Valid driver’s License with an acceptable driving record. - Peterson Power Systems, Inc. is committed to equal employment opportunity and affirmative action. Minorities, females, veterans, and individuals with disabilities are encouraged to apply. (This is EEO boilerplate; we should remove per instruction: remove EEO/equal-opportunity boilerplate.) - A drug screen and background check is required. (This is also boilerplate? Might be considered legal/EEO? It's a requirement; maybe keep as it's a condition of employment. Not sure if considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "A drug screen and background check is required." is a legal requirement; could be considered legal boilerplate. Might be safer to remove? But it's a substantive requirement for the job. However typical job postings include that; but instruction says remove legal boilerplate. I'd remove it to be safe. Also there is "Peterson Power Systems, Inc. is committed to equal employment opportunity and affirmative action. Minorities, females, veterans, and individuals with disabilities are encouraged to apply." That's EEO, remove. Now Benefits: "Peterson offers competitive wages, generous benefits, and promotional opportunities at a family-owned and operated business." So we can extract: competitive wages, generous benefits, promotional opportunities. Pay: competitive wages. Benefits: generous benefits, promotional opportunities. Schedule: Up to 50% travel expected. Now we need to decide which sections to include. Possible sections: - About the role (intro + job description paragraph) - Responsibilities (Essential Job Functions) - Other Job Functions maybe could be Skills? Or we could combine Other Job Functions into Skills section. - Qualifications (Education/Experience, Certificates/Licenses) - Skills (maybe from Other Job Functions) - Benefits (competitive wages, generous benefits, promotional opportunities) - Pay (competitive wages) maybe duplicate; we could combine Pay and Benefits? But instruction says prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they asked to use headings for Benefits, Pay, Schedule separately if content exists. However we can decide to include only those that have real specific content. We have competitive wages (Pay) and generous benefits (Benefits) and promotional opportunities (maybe also Benefits). Schedule: Up to 50% travel expected. We could have:

  About the role

  with intro paragraph and job description paragraph.

  Responsibilities

  with ul of Essential Job Functions.

  Skills

  with ul of Other Job Functions (soft skills).

  Qualifications

  with ul of Education/Experience and Certificates/Licenses.

  Benefits

  with p: competitive wages, generous benefits, promotional opportunities.

  Schedule

  with p: Up to 50% travel expected. We could also include Pay separate but we already have wages in Benefits. Might be redundant. Better to have Pay section: competitive wages. Benefits: generous benefits, promotional opportunities. But that splits similar info. The instruction: prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section, and not include Pay heading. However they said use headings for Benefits, Pay, Schedule if posting actually states them. The posting states competitive wages (Pay) and generous benefits (Benefits). So we could have both. But that's two thin sections. Could we merge them into one Benefits section that includes both wages and benefits? The heading would be Benefits, but then we lose explicit Pay heading. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's a list of examples, not mandatory to use all. It says "include a section ONLY when the posting has real, specific content for it". So if we have content for Pay (competitive wages) we could make a Pay section. If we also have content for Benefits (generous benefits, promotional opportunities) we could make a Benefits section. That's two sections. Are they thin? Each contains maybe a sentence. Could be considered thin but still specific. The instruction says prefer a few substantive sections over many thin ones. So maybe better to combine Pay and Benefits into one Benefits section, and not have a Pay heading. But then we would not be using Pay heading even though we have Pay content. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay,