Senior Design Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The posting includes EEO statement at end; we should remove that. Also the "Disclaimer" about pay range maybe keep as part of Pay section? It's part of compensation details; we can keep as prose within Pay section.
We need to include About the role: The first paragraph: "Amptek is seeking a Sr. Design Engineer to collaborate with Development Engineers, Scientists, and Operations personnel in support of product development and the ongoing operation of the engineering department. This role works closely with engineering, operations, and production teams to introduce new products into manufacturing and support the continuous improvement of existing product lines."
That's prose.
Responsibilities: There's a heading "Key Responsibilities" then subheadings: Product Development & Manufacturing Support, Process Improvement & Operations Support, Strategic Collaboration. Under each there are bullet-like sentences. We need to make a list (
- ) for duties. Should we keep subheadings? Possibly we can just list all responsibilities as items. Could also group but not required. We'll just create a single list of responsibilities.
We need to preserve all substantive information: So each bullet point should be a sentence from the responsibilities.
Let's extract:
Product Development & Manufacturing Support:
- Lead the collection and evaluation of data related to engineering design, manufacturing, and product support.
- Apply product design knowledge, fabrication processes, and best practices to establish manufacturing processes for products produced at volumes of thousands per year.
- Support new product initiatives and facilitate the transition of new products into manufacturing.
- Take ownership of the design, design-for-manufacturability activities, and operational handoff for assigned product lines.
- Complete reliability testing and other required product testing.
Process Improvement & Operations Support:
- Direct the collection of manufacturing data, assist in data analysis, and communicate findings to monitor current yields and drive yield improvements.
- Evaluate existing manufacturing processes and product designs, identify improvement opportunities, and assess associated risks and return on investment.
- Communicate with engineers regarding non-conformances and product assembly issues.
- Support Operations and Manufacturing Engineering teams as needed to help meet production schedules and on-time delivery targets for assigned product lines.
- Support customer-reported and in-line product failures and assist production operators in issue resolution.
Strategic Collaboration:
- Work with the Sales & Marketing team to help define and maintain the product roadmap.
- Partner with engineering, manufacturing, operations, and production personnel to ensure successful product introduction and ongoing product support.
Now Requirements: There's "Education & Experience", "Technical & AI Capabilities", "Core Competencies". Also there is "Knowledge of engineering documentation processes and SOP development." etc.
We need to decide sections: Could have Requirements heading with sub-sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a single Requirements
and then inside we can have paragraphs or lists. However we need to use - for any list of duties/requirements/benefits. So we can list requirements as items.
We need to preserve all substantive information: Education & Experience bullet points:
- M.S. degree in an engineering technology field or science-related discipline, or equivalent relevant work experience.
- Minimum of 2 years of experience in a cleanroom-type manufacturing environment.
- Experience with X-ray, gamma-ray, vacuum, high-voltage, or scientific instrumentation products.
- Knowledge of XRF, radiation detection, or spectroscopy systems.
- Demonstrated design and mechanical skills required to establish manufacturing capabilities, including equipment startup, customization, procurement, and characterization.
- Knowledge of engineering documentation processes and SOP development.
- Six Sigma and/or Lean Manufacturing training preferred.
Technical & AI Capabilities:
- Ability to identify appropriate applications for AI tools to improve productivity, decision-making, work quality, and cost efficiency.
- Ability to critically evaluate AI-generated outputs and apply sound engineering judgment.
Core Competencies (list each):
- Adaptability - Understands changes in tasks, situations, and departmental priorities, and actively seeks information regarding changes that impact their work. Views change as an opportunity for learning and growth.
- Engineering Processes - Possesses working knowledge of responsibilities and activities across engineering disciplines, including design, testing, software, and technology functions.
- Motivation - Self-starter capable of working with minimal supervision. Proactively collaborates with others to identify and resolve potential conflicts in support of project timelines.
- Communication - Demonstrates effective written and verbal communication skills.
- Teamwork - Understands the importance of team collaboration and actively promotes communication and coordination across functions.
- Product Development - Possesses knowledge of product development processes, including product design, testing, and validation. Understands how engineering activities contribute to the successful development, improvement, and release of products.
We could also have a Qualifications section? The posting doesn't have a separate Qualifications beyond Requirements. So we may not need Qualifications.
Skills? Could be part of Requirements. But we can just have Requirements section covering all.
Pay section: We have compensation details: Employee Type: Salaried; Currency: USD; Salary Minimum: 150,000; Salary Maximum: 165,000; Incentive: No; Disclaimer about pay range. Also note "For more information on AMETEK's competitive benefits, please click here." That's not specific benefits, so we skip Benefits.
We need to include Pay section with that info. Should we present as list? Could be
- for each point. Or we could use
. The instruction: Use
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but could be considered a list. Safer to use
for prose. We'll put a paragraph summarizing.
We need to exclude boilerplate: The disclaimer about pay range is part of posting; we keep it. The EEO statement at end we remove. Also the "For more information on AMETEK's competitive benefits, please click here." is not specific benefit; we should not create Benefits section. So we can either drop that sentence or include it in Pay? It's about benefits; but since we are not making Benefits section, we could drop it as it's not specific. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That sentence is substantive? It's a pointer to benefits but not specific. Might be considered boilerplate? It's a link to benefits. It's not specific benefit detail. Might be considered navigation? I'd say we can drop it as it's not specific benefit info. However it's not boilerplate like EEO; it's a reference. But we have no Benefits section; we could include a short
under Pay that says "For more information on AMETEK's competitive benefits, please click here." That would preserve the info. But the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Since we are not making Benefits section, we can keep that sentence elsewhere (maybe under Pay). It's not a heading. So we can include it as a paragraph after Pay details.
Now About The Business Unit: That's not one of the prescribed headings but could be considered "About the role"? Actually we already have About the role (intro). The "About The Business Unit" is additional info about company. Could we include that as a separate section? Not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a heading for About The Business Unit. We could incorporate that info into About the role paragraph? But that would change meaning. However 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 those for section headings. Likely we should stick to those headings only. So we should omit About The Business Unit content? But we must preserve ALL substantive information. That's a conflict. However maybe we can treat "About The Business Unit" as part of "About the role" section? It's not exactly about the role but about the business unit. Could be considered relevant to role. We could merge it into About the role paragraph as additional prose. That would preserve the info without adding a new heading. That seems acceptable.
Thus About the role section will have two paragraphs: first the role description, second the business unit description.
Now we need to ensure we don't include any boilerplate like EEO, navigation, legal, duplicated lines, application instructions. The posting includes "For more information on AMETEK's competitive benefits, please click here." That's not application instruction. We'll keep.
Now produce HTML fragment:
About the role
...
...
Responsibilities
- ...
...
Requirements
- ...
...
Pay
Employee Type: Salaried; Currency: USD; Salary Minimum: $150,000; Salary Maximum: $165,000; Incentive: No. Disclaimer: Where a specific pay range is noted, it is a good faith estimate at the time of this posting. The actual salary offered will be based on experience, skills, qualifications, market / business considerations, and geographic location. For more information on AMETEK's competitive benefits, please click here.
We need to ensure we don't repeat job title. Good.
Check for any duplicated lines: none.
Now ensure we didn't include any headings with empty content. All sections have content.
Now output only HTML fragment, no markdown fences.
Let's craft the paragraphs.
About the role paragraph 1: "Amptek is seeking a Sr. Design Engineer to collaborate with Development Engineers, Scientists, and Operations personnel in support of product development and the ongoing operation of the engineering department. This role works closely with engineering, operations, and production teams to introduce new products into manufacturing and support the continuous improvement of existing product lines."
Paragraph 2 (business unit): "Amptek, an AMETEK company, is a global leader in the design and manufacture of advanced X-ray and gamma-ray detection systems, X-ray sources, and analytical instrumentation. Its innovative technologies support a wide range of applications, including scientific research, industrial inspection, medical diagnostics, environmental monitoring, and aerospace missions. As part of AMETEK, a
for prose. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The posting includes EEO statement at end; we should remove that. Also the "Disclaimer" about pay range maybe keep as part of Pay section? It's part of compensation details; we can keep as prose within Pay section. We need to include About the role: The first paragraph: "Amptek is seeking a Sr. Design Engineer to collaborate with Development Engineers, Scientists, and Operations personnel in support of product development and the ongoing operation of the engineering department. This role works closely with engineering, operations, and production teams to introduce new products into manufacturing and support the continuous improvement of existing product lines." That's prose. Responsibilities: There's a heading "Key Responsibilities" then subheadings: Product Development & Manufacturing Support, Process Improvement & Operations Support, Strategic Collaboration. Under each there are bullet-like sentences. We need to make a list (
- ) for duties. Should we keep subheadings? Possibly we can just list all responsibilities as items. Could also group but not required. We'll just create a single list of responsibilities.
We need to preserve all substantive information: So each bullet point should be a sentence from the responsibilities.
Let's extract:
Product Development & Manufacturing Support:
- Lead the collection and evaluation of data related to engineering design, manufacturing, and product support.
- Apply product design knowledge, fabrication processes, and best practices to establish manufacturing processes for products produced at volumes of thousands per year.
- Support new product initiatives and facilitate the transition of new products into manufacturing.
- Take ownership of the design, design-for-manufacturability activities, and operational handoff for assigned product lines.
- Complete reliability testing and other required product testing.
Process Improvement & Operations Support:
- Direct the collection of manufacturing data, assist in data analysis, and communicate findings to monitor current yields and drive yield improvements.
- Evaluate existing manufacturing processes and product designs, identify improvement opportunities, and assess associated risks and return on investment.
- Communicate with engineers regarding non-conformances and product assembly issues.
- Support Operations and Manufacturing Engineering teams as needed to help meet production schedules and on-time delivery targets for assigned product lines.
- Support customer-reported and in-line product failures and assist production operators in issue resolution.
Strategic Collaboration:
- Work with the Sales & Marketing team to help define and maintain the product roadmap.
- Partner with engineering, manufacturing, operations, and production personnel to ensure successful product introduction and ongoing product support.
Now Requirements: There's "Education & Experience", "Technical & AI Capabilities", "Core Competencies". Also there is "Knowledge of engineering documentation processes and SOP development." etc.
We need to decide sections: Could have Requirements heading with sub-sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a single
Requirements
and then inside we can have paragraphs or lists. However we need to use- for any list of duties/requirements/benefits. So we can list requirements as items.
We need to preserve all substantive information: Education & Experience bullet points:
- M.S. degree in an engineering technology field or science-related discipline, or equivalent relevant work experience.
- Minimum of 2 years of experience in a cleanroom-type manufacturing environment.
- Experience with X-ray, gamma-ray, vacuum, high-voltage, or scientific instrumentation products.
- Knowledge of XRF, radiation detection, or spectroscopy systems.
- Demonstrated design and mechanical skills required to establish manufacturing capabilities, including equipment startup, customization, procurement, and characterization.
- Knowledge of engineering documentation processes and SOP development.
- Six Sigma and/or Lean Manufacturing training preferred.
Technical & AI Capabilities:
- Ability to identify appropriate applications for AI tools to improve productivity, decision-making, work quality, and cost efficiency.
- Ability to critically evaluate AI-generated outputs and apply sound engineering judgment.
Core Competencies (list each):
- Adaptability - Understands changes in tasks, situations, and departmental priorities, and actively seeks information regarding changes that impact their work. Views change as an opportunity for learning and growth.
- Engineering Processes - Possesses working knowledge of responsibilities and activities across engineering disciplines, including design, testing, software, and technology functions.
- Motivation - Self-starter capable of working with minimal supervision. Proactively collaborates with others to identify and resolve potential conflicts in support of project timelines.
- Communication - Demonstrates effective written and verbal communication skills.
- Teamwork - Understands the importance of team collaboration and actively promotes communication and coordination across functions.
- Product Development - Possesses knowledge of product development processes, including product design, testing, and validation. Understands how engineering activities contribute to the successful development, improvement, and release of products.
We could also have a Qualifications section? The posting doesn't have a separate Qualifications beyond Requirements. So we may not need Qualifications.
Skills? Could be part of Requirements. But we can just have Requirements section covering all.
Pay section: We have compensation details: Employee Type: Salaried; Currency: USD; Salary Minimum: 150,000; Salary Maximum: 165,000; Incentive: No; Disclaimer about pay range. Also note "For more information on AMETEK's competitive benefits, please click here." That's not specific benefits, so we skip Benefits.
We need to include Pay section with that info. Should we present as list? Could be
- for each point. Or we could use
. The instruction: Use
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but could be considered a list. Safer to use
for prose. We'll put a paragraph summarizing. We need to exclude boilerplate: The disclaimer about pay range is part of posting; we keep it. The EEO statement at end we remove. Also the "For more information on AMETEK's competitive benefits, please click here." is not specific benefit; we should not create Benefits section. So we can either drop that sentence or include it in Pay? It's about benefits; but since we are not making Benefits section, we could drop it as it's not specific. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That sentence is substantive? It's a pointer to benefits but not specific. Might be considered boilerplate? It's a link to benefits. It's not specific benefit detail. Might be considered navigation? I'd say we can drop it as it's not specific benefit info. However it's not boilerplate like EEO; it's a reference. But we have no Benefits section; we could include a short
under Pay that says "For more information on AMETEK's competitive benefits, please click here." That would preserve the info. But the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Since we are not making Benefits section, we can keep that sentence elsewhere (maybe under Pay). It's not a heading. So we can include it as a paragraph after Pay details. Now About The Business Unit: That's not one of the prescribed headings but could be considered "About the role"? Actually we already have About the role (intro). The "About The Business Unit" is additional info about company. Could we include that as a separate section? Not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a heading for About The Business Unit. We could incorporate that info into About the role paragraph? But that would change meaning. However 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 those for section headings. Likely we should stick to those headings only. So we should omit About The Business Unit content? But we must preserve ALL substantive information. That's a conflict. However maybe we can treat "About The Business Unit" as part of "About the role" section? It's not exactly about the role but about the business unit. Could be considered relevant to role. We could merge it into About the role paragraph as additional prose. That would preserve the info without adding a new heading. That seems acceptable. Thus About the role section will have two paragraphs: first the role description, second the business unit description. Now we need to ensure we don't include any boilerplate like EEO, navigation, legal, duplicated lines, application instructions. The posting includes "For more information on AMETEK's competitive benefits, please click here." That's not application instruction. We'll keep. Now produce HTML fragment:
About the role
...
...
Responsibilities
- ... ...
Requirements
- ... ...
Pay
Employee Type: Salaried; Currency: USD; Salary Minimum: $150,000; Salary Maximum: $165,000; Incentive: No. Disclaimer: Where a specific pay range is noted, it is a good faith estimate at the time of this posting. The actual salary offered will be based on experience, skills, qualifications, market / business considerations, and geographic location. For more information on AMETEK's competitive benefits, please click here.
We need to ensure we don't repeat job title. Good. Check for any duplicated lines: none. Now ensure we didn't include any headings with empty content. All sections have content. Now output only HTML fragment, no markdown fences. Let's craft the paragraphs. About the role paragraph 1: "Amptek is seeking a Sr. Design Engineer to collaborate with Development Engineers, Scientists, and Operations personnel in support of product development and the ongoing operation of the engineering department. This role works closely with engineering, operations, and production teams to introduce new products into manufacturing and support the continuous improvement of existing product lines." Paragraph 2 (business unit): "Amptek, an AMETEK company, is a global leader in the design and manufacture of advanced X-ray and gamma-ray detection systems, X-ray sources, and analytical instrumentation. Its innovative technologies support a wide range of applications, including scientific research, industrial inspection, medical diagnostics, environmental monitoring, and aerospace missions. As part of AMETEK, a
- for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but could be considered a list. Safer to use
- for each point. Or we could use
- for any list of duties/requirements/benefits. So we can list requirements as items.
We need to preserve all substantive information: Education & Experience bullet points:
- M.S. degree in an engineering technology field or science-related discipline, or equivalent relevant work experience.
- Minimum of 2 years of experience in a cleanroom-type manufacturing environment.
- Experience with X-ray, gamma-ray, vacuum, high-voltage, or scientific instrumentation products.
- Knowledge of XRF, radiation detection, or spectroscopy systems.
- Demonstrated design and mechanical skills required to establish manufacturing capabilities, including equipment startup, customization, procurement, and characterization.
- Knowledge of engineering documentation processes and SOP development.
- Six Sigma and/or Lean Manufacturing training preferred.
Technical & AI Capabilities:
- Ability to identify appropriate applications for AI tools to improve productivity, decision-making, work quality, and cost efficiency.
- Ability to critically evaluate AI-generated outputs and apply sound engineering judgment.
Core Competencies (list each):
- Adaptability - Understands changes in tasks, situations, and departmental priorities, and actively seeks information regarding changes that impact their work. Views change as an opportunity for learning and growth.
- Engineering Processes - Possesses working knowledge of responsibilities and activities across engineering disciplines, including design, testing, software, and technology functions.
- Motivation - Self-starter capable of working with minimal supervision. Proactively collaborates with others to identify and resolve potential conflicts in support of project timelines.
- Communication - Demonstrates effective written and verbal communication skills.
- Teamwork - Understands the importance of team collaboration and actively promotes communication and coordination across functions.
- Product Development - Possesses knowledge of product development processes, including product design, testing, and validation. Understands how engineering activities contribute to the successful development, improvement, and release of products.
We could also have a Qualifications section? The posting doesn't have a separate Qualifications beyond Requirements. So we may not need Qualifications.
Skills? Could be part of Requirements. But we can just have Requirements section covering all.
Pay section: We have compensation details: Employee Type: Salaried; Currency: USD; Salary Minimum: 150,000; Salary Maximum: 165,000; Incentive: No; Disclaimer about pay range. Also note "For more information on AMETEK's competitive benefits, please click here." That's not specific benefits, so we skip Benefits.
We need to include Pay section with that info. Should we present as list? Could be