Sr Application Engineer - US
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We must not repeat job title. No Pay/Schedule unless present. Benefits present. So include Benefits section. We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. The posting includes a Diversity & Inclusion paragraph and EEO statement; that is boilerplate, should be removed. Also "Please let us know confidentially..." is accommodation request; maybe keep? It's not boilerplate? It's a request for accommodations; might be considered part of application instructions? It's not exactly application instructions but could be considered EEO. Safer to remove? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accommodation request is not exactly EEO but could be considered part of application instructions. I'd remove it. Also remove "Working at Watlow Watlow is a global technology..." maybe that's introductory fluff but it's substantive about company; we can keep as part of About the role? Actually "About The Role" heading appears later. The introductory paragraph before About The Role is about company; we could include it under About the role? Might be considered company overview; but we can keep as a paragraph before the About the role heading? The instruction: 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. There's no job ID. So we can keep the introductory paragraph as a
before the first heading? The output should be only HTML fragment; we can include a
describing Watlow, then
About the role
etc. We need to preserve all substantive information: responsibilities list, qualifications, preferred qualifications, key competencies, benefits list. We need to use- for any list of duties/requirements/benefits. So for responsibilities, we need a
- . For qualifications, we need a
- for any list of duties/requirements/benefits. Could have multiple lists under same heading.
We also have Key Competencies -> Skills section.
Benefits section.
We must not include Pay or Schedule.
We must not include placeholder text.
Let's extract content.
Company intro: "Working at Watlow Watlow is a global technology and manufacturing leader who provides world class engineering expertise through innovative thermal products and systems, enabling our customers to thrive. We are making a positive impact every day as our solutions enrich the lives of people everywhere. We have been providing breakthrough thermal solutions for over 100 years! Our corporate values guide us uncompromisingly to always do the right thing, continually learn and improve, respect everyone, and lead with service and humility."
We can keep that as a
. About the role: after "About The Role" heading, there is description: "Watlow is looking for an experienced Senior Application Engineer to serve as a technical resource for customers, sales channels and internal teams. You will translate customer needs into practical product and application solutions, lead complex or non-routine technical activities, and support the development of standard, modified-standard and smaller engineered solutions. This role partners closely with Sales, Engineering, Operations, Quality and customers to develop quotes, drawings, bills of material, prototypes, tests and production instructions that meet technical and commercial requirements." We can keep that as a
under About the role. Then "Products and Applications You'll Support" with bullet list? Actually it's a heading then a list of items separated by commas? It says: Products and Applications You'll Support Watlow thermal products, controls and related systems Standard and modified-standard products, assemblies and services Customer applications requiring product selection, application and set-up guidance Tools, equipment, prototypes, drawings and documentation supporting product and process development We could treat that as a
- under About the role or a separate section? Could be part of About the role. We'll include as a
- . The headings like "Technical application support", "Product and process documentation", "Quoting and commercial support", "Problem solving and continuous improvement" could be considered subheadings but we can just treat each line as a list item; but we might want to keep them as separate items. The instruction: use
- for any list of duties/requirements/benefits. So we can make a single
- with each line as
- . That's fine.
Then "Required Qualifications" heading then list items each starting with a bold phrase? Actually they are:
Bachelor's degree in engineering, technical field or related discipline; or a two-year degree with significant related experience; or equivalent experience.
Typically 7+ years of application engineering, technical sales support, product engineering, customer support or related experience.
Demonstrated expertise in products, applications and processes, with the ability to recommend and implement solutions.
Experience creating or interpreting CAD drawings, bills of material, routings and technical documentation.
Ability to develop quotations and work within pricing and business guidelines.
Strong customer-facing communication, listening, presentation and conflict-resolution skills.
Ability to manage multiple priorities, exercise sound judgment and work independently while seeking guidance when appropriate.
We'll make a
- under Required Qualifications.
Then "Preferred Qualifications" heading then list:
Experience supporting highly regulated markets such as aerospace, military/defense or medical.
Experience with industrial heating, temperature controls, sensors, electrical products or related thermal applications.
Experience with product investigations, returned-material evaluations, prototypes, testing or manufacturing support.
Experience training sales representatives, distributors, customers or internal teams on products and applications.
Make a
- .
Now we need to ensure we don't repeat any boilerplate. Also remove duplicated lines.
Now construct HTML.
We'll start with a
for company intro. Then
About the role
thenwith role description. Then maybe
Products and Applications You'll Support
with- . But we could incorporate under About the role. However the instruction: use heading only when posting has real specific content. It does have specific content. So we could add a heading for that. But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits,
- under Preferred Qualifications.
Then "Key Competencies" heading then list:
Deep knowledge of assigned products and applications.
Leads technical work and cross-functional teams without requiring direct authority.
Uses business judgment to assess fit, risk, feasibility and when additional evaluation or escalation is needed.
Communicates technical information clearly to customers, sales teams, production teams and other nontechnical audiences.
Demonstrates credibility, approachability, openness and strong interpersonal listening skills.
Uses the Watlow Business System to achieve results and demonstrates behaviors consistent with Watlow culture.
Make a
- under Skills (since they said Skills heading). We'll use
Skills
. Then Benefits: after "Benefits:" heading there is paragraph then list: The Watlow Total Compensation Plan Benefits The health, well-being and financial stability of you and your family is a high priority to us. The Watlow Total Rewards Plan includes competitive compensation and a full range of life and career enhancing benefits: Annual Incentive Program 401(k) plan that includes a company match on your contribution and an annual company contribution that is tied to company performance Wellness incentives Employee Personal Assistance Program Dental, medical, vision and short-term and long-term disability insurance Paid holidays, personal time, and vacation Parental leave Tuition reimbursement Diversity & Inclusion We proactively embrace diversity in all its dimensions across our company and cultivate a culture of inclusion and forward thinking that respects and reflects each team member’s individual strengths, views, and experiences. Watlow takes pride in being an inclusive equal opportunity employer and considers for employment qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability or protected veteran status. Please let us know confidentially if you need or require any special accommodations to participate in our recruiting process by emailing us at accommodations@Watlow.com. We need to remove EEO/diversity boilerplate and accommodation request. So we should keep the benefits list up to Tuition reimbursement, and maybe exclude Diversity & Inclusion paragraph and EEO statement and accommodation request. Also the line "Diversity & Inclusion" is a heading; we should drop that and following paragraphs. Thus Benefits section: we can have aintro: "The Watlow Total Compensation Plan Benefits The health, well-being and financial stability of you and your family is a high priority to us.The Watlow Total Rewards Plan includes competitive compensation and a full range of life and career enhancing benefits:" but that's a bit messy. Better to keep as a
then a
- of benefits.
Let's parse benefits list items:
- Annual Incentive Program
- 401(k) plan that includes a company match on your contribution and an annual company contribution that is tied to company performance
- Wellness incentives
- Employee Personal Assistance Program
- Dental, medical, vision and short-term and long-term disability insurance
- Paid holidays, personal time, and vacation
- Parental leave
- Tuition reimbursement
We'll output those as
- .
Now we need to ensure we don't repeat any boilerplate. Also remove duplicated lines.
Now construct HTML.
We'll start with a
- . That's fine.
Then "Required Qualifications" heading then list items each starting with a bold phrase? Actually they are:
Bachelor's degree in engineering, technical field or related discipline; or a two-year degree with significant related experience; or equivalent experience.
Typically 7+ years of application engineering, technical sales support, product engineering, customer support or related experience.
Demonstrated expertise in products, applications and processes, with the ability to recommend and implement solutions.
Experience creating or interpreting CAD drawings, bills of material, routings and technical documentation.
Ability to develop quotations and work within pricing and business guidelines.
Strong customer-facing communication, listening, presentation and conflict-resolution skills.
Ability to manage multiple priorities, exercise sound judgment and work independently while seeking guidance when appropriate.
We'll make a
- for any list of duties/requirements/benefits. So we can make a single
- under About the role after the paragraph.
Then "Key Responsibilities" heading then list of responsibilities each starting with a bold phrase? Actually they are:
Technical application support
Serve as a senior technical resource to business unit sales agents, customers and distributors, including training and customer-facing support as needed.
Advise on product selection, product application, set-up and programming, including control products when applicable.
Translate customer requirements into clear technical instructions and practical solutions for production and internal teams.
Serve as a post-sale technical resource and support orders, customer questions and technical follow-up.
Read and interpret customer drawings and technical requirements; identify risks, gaps and opportunities for clarification.
Product and process documentation
Modify product and process designs using defined design standards, process standards and trade-off curves.
Create and review CAD drawings, product documentation and process documentation for new, standard and modified-standard products.
Assemble bills of material and routings; process rework, prototype and modified-standard orders.
Prepare drawings for new parts and assemblies based on customer and engineering requirements.
Convert application requirements into documentation that supports manufacturing, quality and service.
Quoting and commercial support
Prepare and present technical and commercial quotes for standard and modified products and services.
Develop quotations within pricing guidelines and assess opportunities for business fit, technical feasibility and attractiveness.
Provide input to sales volume, sales trends, forecasts, market intelligence, competitor activity and product growth strategies.
Support Sales in developing new customers and maintaining productive relationships with established customers.
Problem solving and continuous improvement
Assist with returned-material issues, product investigations and quality investigations; help identify root causes and effective corrective actions.
Conduct or support experiments, tests and evaluations of products, processes, tools and prototypes.
Identify product gaps, process improvements and opportunities to improve customer experience, manufacturability and business results.
Lead or contribute to customer projects, internal Watlow projects and cross-functional teams.
We need to turn each bullet into
- . The headings like "Technical application support", "Product and process documentation", "Quoting and commercial support", "Problem solving and continuous improvement" could be considered subheadings but we can just treat each line as a list item; but we might want to keep them as separate items. The instruction: use
- for Required Qualifications and maybe another for Preferred Qualifications? Could combine under Requirements heading with subheadings? But instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits...). So we could have separate headings: Requirements (maybe includes Required Qualifications), Preferred Qualifications (maybe as part of Requirements? but we could have a separate heading Preferred Qualifications). However they said prefer a few substantive sections over many thin ones. So maybe combine Required and Preferred under Requirements heading with two
- lists? But they said use
- for any list of duties/requirements/benefits. Could have multiple lists under same heading.
We also have Key Competencies -> Skills section.
Benefits section.
We must not include Pay or Schedule.
We must not include placeholder text.
Let's extract content.
Company intro: "Working at Watlow Watlow is a global technology and manufacturing leader who provides world class engineering expertise through innovative thermal products and systems, enabling our customers to thrive. We are making a positive impact every day as our solutions enrich the lives of people everywhere. We have been providing breakthrough thermal solutions for over 100 years! Our corporate values guide us uncompromisingly to always do the right thing, continually learn and improve, respect everyone, and lead with service and humility."
We can keep that as a