Sr. Engineer Process
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive info, remove boilerplate like EEO, etc. There's none.
We need to include sections only when posting has real specific content. So we can have sections: About the role (maybe from Position Summary), Responsibilities, Qualifications (maybe combine Qualification Requirements and Preferred Qualifications?), Essential Functions.
But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have content. The spec says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but we can use those headings if appropriate. We need to map content.
Position Summary -> About the role.
Position Responsibilities -> Responsibilities.
Qualification Requirements -> Requirements (or Qualifications?). The spec includes both Requirements and Qualifications as possible headings. We need to decide. Usually Requirements = mandatory qualifications, Qualifications = preferred? But we have both Qualification Requirements and Preferred Qualifications. Could map Qualification Requirements to Requirements, Preferred Qualifications to Qualifications (or Skills). Also there is Essential Functions maybe could be part of Responsibilities or separate? Could be Skills? But Essential Functions are more like core duties; could be included under Responsibilities. However we must not invent sections; we can include Essential Functions as a separate section if we think it's substantive. But the allowed headings list does not include Essential Functions; we could still use a heading not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; but not strictly limited? Probably we should stick to those headings. So we need to map content to those headings.
Thus:
- About the role: Position Summary paragraph.
- Responsibilities: list of responsibilities (bulleted). Use - .
- Requirements: Qualification Requirements (education, years, etc.) maybe also include some of the Preferred Qualifications? But we have separate Qualifications heading for preferred? Could put Preferred Qualifications under Qualifications.
- Skills: maybe we can list specific skills like DFMEA, RACI, etc. But we already have them in qualifications. Could put under Skills.
But we must not create thin sections. Let's think: We have Qualification Requirements (mandatory) and Preferred Qualifications (preferred). Could combine into Requirements and Qualifications sections.
Thus:
About the role
...Position Summary...
Responsibilities
- ... each responsibility...
Requirements
- ... education, years, etc....
Qualifications
- ... preferred qualifications...
We could also add Skills section if we have distinct skills not covered. But we already have many skills in qualifications; maybe we can omit Skills to avoid thin.
We must not include Pay/Benefits/Schedule as they are not present.
Now we need to extract the content exactly, preserving all substantive information, not inventing or summarizing away detail.
Let's parse the posting.
Position Summary paragraph:
"The Senior Engineer, Process is responsible for defining, maintaining, and continuously improving the engineering processes used across the Hardware Engineering organization. This role ensures that engineering teams consistently follow structured workflows, use standard templates, and adhere to best practices across all product lifecycle phases. The Senior Engineer will develop clear process documentation, deliver process training, and perform audits to validate process compliance and identify improvement opportunities. This role requires the ability to work with global teams, influence across functions without authority, and collaborate closely with Mechanical, Hydraulic, Electrical, Electronics, Firmware, Systems, Test, and Quality teams. The ideal candidate brings strong knowledge of engineering workflows, lifecycle management, DFMEA, design reviews, RACI modeling, and structured documentation practices. They must be highly organized, detail-oriented, and capable of driving continuous improvement across a distributed engineering environment."
We'll put that in .
Now Responsibilities list: each line starting with a verb.
List:
- Provide L1 support (basic) on Global HW Engineering Tools Environment, in the US.
- Perform L1 sustaining tasks and trouble shootings on Global HW Engineering Tools Environment, in the US.
- Develop, establish, and maintain engineering processes that support consistent execution across all hardware engineering disciplines.
- Create, manage, and organize all process templates, checklists, and documentation including KPI’s.
- Train engineering teams on processes, workflows, tools, templates, and best practices to ensure consistent adoption.
- Conduct process audits to assess compliance, identify gaps, and drive corrective actions or improvement initiatives on critical-to-quality metrics (CTQ’s) and KPI’s.
- Partner with engineering leaders, SMEs, and cross-functional stakeholders to refine processes for clarity, efficiency, and alignment with Engineering Operations.
- Maintain and improve workflows for New Product Introduction (NPI), Sustaining Engineering, Continuous Improvement, and Engineering Change Management.
- Establish and manage RACI models that define roles, responsibilities, and approval paths for engineering activities.
- Partner with Program Management and System Engineering to align processes with stage-gate reviews, design reviews, and system-level deliverables.
- Support the development and refinement of DFMEA processes and facilitate risk assessments as part of design workflows.
- Ensure documentation repositories, process libraries, and template systems are well organized and easily accessible.
- Provide guidance and coaching to engineering teams on proper process execution and documentation practices.
- Collaborate with global engineering teams and support remote participation in process reviews and audits.
- Identify opportunities to streamline workflows, eliminate inefficiencies, and implement process improvements that enhance engineering productivity.
- Demonstrate leadership qualities such as influence, accountability, attention to detail, and a systematic approach to solving process-related challenges.
We need to preserve each as
- .
Now Qualification Requirements (mandatory):
- Education: Bachelor’s degree in Engineering or related technical field required.
- 5–8 years of engineering, process engineering, or engineering operations experience.
- Strong understanding of hardware development lifecycles, engineering workflows, and cross-disciplinary processes.
- Experience creating and managing process documentation, templates, and structured engineering artifacts.
- Working knowledge of DFMEA, design reviews, RACI models, and stage-gate or structured development methodologies.
- Strong organizational skills and detail orientation with the ability to maintain clarity and structure across complex processes.
- Ability to influence teams across functions and geographies without direct authority.
- Excellent communication, facilitation, and training capabilities.
- Experience working with distributed or global teams.
We'll put each as
- under Requirements.
Preferred Qualifications:
- Experience with Lean, Six Sigma, DFSS, or similar process improvement methodologies.
- Knowledge of PDM/PLM systems and process workflows associated with product data management.
- Experience participating in or supporting engineering audits or compliance reviews.
- Familiarity with failure analysis, quality systems, or root cause methodologies (5 Whys, Fishbone, etc.).
- Understanding of mechanical, electrical, or embedded system engineering processes.
We'll put under Qualifications.
Essential Functions: maybe we could incorporate into Responsibilities or Skills, but we have no Skills section. Could we add a Skills section? The list includes: Serve as the process owner for the Hardware Engineering organization. Represent process and governance needs in cross-functional team discussions. Support process training, documentation updates, and audit readiness. Work independently and collaboratively with global teams. Exhibit strong leadership, initiative, and attention to detail. Fluent English is required.
These are somewhat similar to responsibilities but could be considered Skills or Additional responsibilities. Since we already have Responsibilities covering many, we could add these as additional responsibilities. But to preserve all substantive info, we should include them. Perhaps we can add them under Responsibilities as additional bullets. That would be okay; we are not creating a new section.
Thus we can append those essential functions bullets to the Responsibilities list.
Let's list them:
- Serve as the process owner for the Hardware Engineering organization.
- Represent process and governance needs in cross-functional team discussions.
- Support process training, documentation updates, and audit readiness.
- Work independently and collaboratively with global teams.
- Exhibit strong leadership, initiative, and attention to detail.
- Fluent English is required.
We'll add them.
Now we need to ensure we don't include boilerplate like "The information contained within this job description overview is not intended to be all-inclusive..." etc. Remove that.
Also remove "#SWE" at end.
Now produce HTML fragment.
We'll wrap sections in appropriate tags.
Make sure no extra text.
Let's craft:
About the role
The Senior Engineer, Process is responsible for defining, maintaining, and continuously improving the engineering processes used across the Hardware Engineering organization. This role ensures that engineering teams consistently follow structured workflows, use standard templates, and adhere to best practices across all product lifecycle phases. The Senior Engineer will develop clear process documentation, deliver process training, and perform audits to validate process compliance and identify improvement opportunities. This role requires the ability to work with global teams, influence across functions without authority, and collaborate closely with Mechanical, Hydraulic, Electrical, Electronics, Firmware, Systems, Test, and Quality teams. The ideal candidate brings strong knowledge of engineering workflows, lifecycle management, DFMEA, design reviews, RACI modeling, and structured documentation practices. They must be highly organized, detail-oriented, and capable of driving continuous improvement across a distributed engineering environment.
Responsibilities
- Provide L1 support (basic) on Global HW Engineering Tools Environment, in the US.
- Perform L1 sustaining tasks and trouble shootings on Global HW Engineering Tools Environment, in the US.
- Develop, establish, and maintain engineering processes that support consistent execution across all hardware engineering disciplines.
- Create, manage, and organize all process templates, checklists, and documentation including KPI’s.
- Train engineering teams on processes, workflows, tools, templates, and best practices to ensure consistent adoption.
- Conduct process audits to assess compliance, identify gaps, and drive corrective actions or improvement initiatives on critical-to-quality metrics (CTQ’s) and KPI’s.
- Partner with engineering leaders, SMEs, and cross-functional stakeholders to refine processes for clarity, efficiency, and alignment with Engineering Operations.
- Maintain and improve workflows for New Product Introduction (NPI), Sustaining Engineering, Continuous Improvement, and Engineering Change Management.
- Establish and manage RACI models that define roles, responsibilities, and approval paths for engineering activities.
- Partner with Program Management and System Engineering to align processes with stage-gate reviews, design reviews, and system-level deliverables.
- Support the development and refinement of DFMEA processes and facilitate risk assessments as part of design workflows.
- Ensure documentation repositories, process libraries, and template systems are well organized and easily accessible.
- Provide guidance and coaching to engineering teams on proper process execution and documentation practices.
- Collaborate with global engineering teams and support remote participation in process reviews and audits.
- Identify opportunities to streamline workflows, eliminate inefficiencies, and implement process improvements that enhance engineering productivity.
- Demonstrate leadership qualities such as influence, accountability, attention to detail, and a systematic approach to solving process-related challenges.
- Serve as the process owner for the Hardware Engineering organization.
- Represent process and governance needs in cross-functional team discussions.
- Support process training, documentation updates, and
for prose. We need to preserve all substantive info, remove boilerplate like EEO, etc. There's none. We need to include sections only when posting has real specific content. So we can have sections: About the role (maybe from Position Summary), Responsibilities, Qualifications (maybe combine Qualification Requirements and Preferred Qualifications?), Essential Functions. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have content. The spec says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but we can use those headings if appropriate. We need to map content.
Position Summary -> About the role.
Position Responsibilities -> Responsibilities.
Qualification Requirements -> Requirements (or Qualifications?). The spec includes both Requirements and Qualifications as possible headings. We need to decide. Usually Requirements = mandatory qualifications, Qualifications = preferred? But we have both Qualification Requirements and Preferred Qualifications. Could map Qualification Requirements to Requirements, Preferred Qualifications to Qualifications (or Skills). Also there is Essential Functions maybe could be part of Responsibilities or separate? Could be Skills? But Essential Functions are more like core duties; could be included under Responsibilities. However we must not invent sections; we can include Essential Functions as a separate section if we think it's substantive. But the allowed headings list does not include Essential Functions; we could still use a heading not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; but not strictly limited? Probably we should stick to those headings. So we need to map content to those headings.
Thus:
- About the role: Position Summary paragraph.
- Responsibilities: list of responsibilities (bulleted). Use - .
- Requirements: Qualification Requirements (education, years, etc.) maybe also include some of the Preferred Qualifications? But we have separate Qualifications heading for preferred? Could put Preferred Qualifications under Qualifications.
- Skills: maybe we can list specific skills like DFMEA, RACI, etc. But we already have them in qualifications. Could put under Skills.
But we must not create thin sections. Let's think: We have Qualification Requirements (mandatory) and Preferred Qualifications (preferred). Could combine into Requirements and Qualifications sections.
Thus:
About the role
...Position Summary...
Responsibilities
- ... each responsibility...
Requirements
- ... education, years, etc....
Qualifications
- ... preferred qualifications...
We could also add Skills section if we have distinct skills not covered. But we already have many skills in qualifications; maybe we can omit Skills to avoid thin.
We must not include Pay/Benefits/Schedule as they are not present.
Now we need to extract the content exactly, preserving all substantive information, not inventing or summarizing away detail.
Let's parse the posting.
Position Summary paragraph:
"The Senior Engineer, Process is responsible for defining, maintaining, and continuously improving the engineering processes used across the Hardware Engineering organization. This role ensures that engineering teams consistently follow structured workflows, use standard templates, and adhere to best practices across all product lifecycle phases. The Senior Engineer will develop clear process documentation, deliver process training, and perform audits to validate process compliance and identify improvement opportunities. This role requires the ability to work with global teams, influence across functions without authority, and collaborate closely with Mechanical, Hydraulic, Electrical, Electronics, Firmware, Systems, Test, and Quality teams. The ideal candidate brings strong knowledge of engineering workflows, lifecycle management, DFMEA, design reviews, RACI modeling, and structured documentation practices. They must be highly organized, detail-oriented, and capable of driving continuous improvement across a distributed engineering environment."
We'll put that in .
Now Responsibilities list: each line starting with a verb.
List:
- Provide L1 support (basic) on Global HW Engineering Tools Environment, in the US.
- Perform L1 sustaining tasks and trouble shootings on Global HW Engineering Tools Environment, in the US.
- Develop, establish, and maintain engineering processes that support consistent execution across all hardware engineering disciplines.
- Create, manage, and organize all process templates, checklists, and documentation including KPI’s.
- Train engineering teams on processes, workflows, tools, templates, and best practices to ensure consistent adoption.
- Conduct process audits to assess compliance, identify gaps, and drive corrective actions or improvement initiatives on critical-to-quality metrics (CTQ’s) and KPI’s.
- Partner with engineering leaders, SMEs, and cross-functional stakeholders to refine processes for clarity, efficiency, and alignment with Engineering Operations.
- Maintain and improve workflows for New Product Introduction (NPI), Sustaining Engineering, Continuous Improvement, and Engineering Change Management.
- Establish and manage RACI models that define roles, responsibilities, and approval paths for engineering activities.
- Partner with Program Management and System Engineering to align processes with stage-gate reviews, design reviews, and system-level deliverables.
- Support the development and refinement of DFMEA processes and facilitate risk assessments as part of design workflows.
- Ensure documentation repositories, process libraries, and template systems are well organized and easily accessible.
- Provide guidance and coaching to engineering teams on proper process execution and documentation practices.
- Collaborate with global engineering teams and support remote participation in process reviews and audits.
- Identify opportunities to streamline workflows, eliminate inefficiencies, and implement process improvements that enhance engineering productivity.
- Demonstrate leadership qualities such as influence, accountability, attention to detail, and a systematic approach to solving process-related challenges.
We need to preserve each as
- .
Now Qualification Requirements (mandatory):
- Education: Bachelor’s degree in Engineering or related technical field required.
- 5–8 years of engineering, process engineering, or engineering operations experience.
- Strong understanding of hardware development lifecycles, engineering workflows, and cross-disciplinary processes.
- Experience creating and managing process documentation, templates, and structured engineering artifacts.
- Working knowledge of DFMEA, design reviews, RACI models, and stage-gate or structured development methodologies.
- Strong organizational skills and detail orientation with the ability to maintain clarity and structure across complex processes.
- Ability to influence teams across functions and geographies without direct authority.
- Excellent communication, facilitation, and training capabilities.
- Experience working with distributed or global teams.
We'll put each as
- under Requirements.
Preferred Qualifications:
- Experience with Lean, Six Sigma, DFSS, or similar process improvement methodologies.
- Knowledge of PDM/PLM systems and process workflows associated with product data management.
- Experience participating in or supporting engineering audits or compliance reviews.
- Familiarity with failure analysis, quality systems, or root cause methodologies (5 Whys, Fishbone, etc.).
- Understanding of mechanical, electrical, or embedded system engineering processes.
We'll put under Qualifications.
Essential Functions: maybe we could incorporate into Responsibilities or Skills, but we have no Skills section. Could we add a Skills section? The list includes: Serve as the process owner for the Hardware Engineering organization. Represent process and governance needs in cross-functional team discussions. Support process training, documentation updates, and audit readiness. Work independently and collaboratively with global teams. Exhibit strong leadership, initiative, and attention to detail. Fluent English is required.
These are somewhat similar to responsibilities but could be considered Skills or Additional responsibilities. Since we already have Responsibilities covering many, we could add these as additional responsibilities. But to preserve all substantive info, we should include them. Perhaps we can add them under Responsibilities as additional bullets. That would be okay; we are not creating a new section.
Thus we can append those essential functions bullets to the Responsibilities list.
Let's list them:
- Serve as the process owner for the Hardware Engineering organization.
- Represent process and governance needs in cross-functional team discussions.
- Support process training, documentation updates, and audit readiness.
- Work independently and collaboratively with global teams.
- Exhibit strong leadership, initiative, and attention to detail.
- Fluent English is required.
We'll add them.
Now we need to ensure we don't include boilerplate like "The information contained within this job description overview is not intended to be all-inclusive..." etc. Remove that.
Also remove "#SWE" at end.
Now produce HTML fragment.
We'll wrap sections in appropriate tags.
Make sure no extra text.
Let's craft:
About the role
The Senior Engineer, Process is responsible for defining, maintaining, and continuously improving the engineering processes used across the Hardware Engineering organization. This role ensures that engineering teams consistently follow structured workflows, use standard templates, and adhere to best practices across all product lifecycle phases. The Senior Engineer will develop clear process documentation, deliver process training, and perform audits to validate process compliance and identify improvement opportunities. This role requires the ability to work with global teams, influence across functions without authority, and collaborate closely with Mechanical, Hydraulic, Electrical, Electronics, Firmware, Systems, Test, and Quality teams. The ideal candidate brings strong knowledge of engineering workflows, lifecycle management, DFMEA, design reviews, RACI modeling, and structured documentation practices. They must be highly organized, detail-oriented, and capable of driving continuous improvement across a distributed engineering environment.
Responsibilities
- Provide L1 support (basic) on Global HW Engineering Tools Environment, in the US.
- Perform L1 sustaining tasks and trouble shootings on Global HW Engineering Tools Environment, in the US.
- Develop, establish, and maintain engineering processes that support consistent execution across all hardware engineering disciplines.
- Create, manage, and organize all process templates, checklists, and documentation including KPI’s.
- Train engineering teams on processes, workflows, tools, templates, and best practices to ensure consistent adoption.
- Conduct process audits to assess compliance, identify gaps, and drive corrective actions or improvement initiatives on critical-to-quality metrics (CTQ’s) and KPI’s.
- Partner with engineering leaders, SMEs, and cross-functional stakeholders to refine processes for clarity, efficiency, and alignment with Engineering Operations.
- Maintain and improve workflows for New Product Introduction (NPI), Sustaining Engineering, Continuous Improvement, and Engineering Change Management.
- Establish and manage RACI models that define roles, responsibilities, and approval paths for engineering activities.
- Partner with Program Management and System Engineering to align processes with stage-gate reviews, design reviews, and system-level deliverables.
- Support the development and refinement of DFMEA processes and facilitate risk assessments as part of design workflows.
- Ensure documentation repositories, process libraries, and template systems are well organized and easily accessible.
- Provide guidance and coaching to engineering teams on proper process execution and documentation practices.
- Collaborate with global engineering teams and support remote participation in process reviews and audits.
- Identify opportunities to streamline workflows, eliminate inefficiencies, and implement process improvements that enhance engineering productivity.
- Demonstrate leadership qualities such as influence, accountability, attention to detail, and a systematic approach to solving process-related challenges.
- Serve as the process owner for the Hardware Engineering organization.
- Represent process and governance needs in cross-functional team discussions.
- Support process training, documentation updates, and
- .
- Requirements: Qualification Requirements (education, years, etc.) maybe also include some of the Preferred Qualifications? But we have separate Qualifications heading for preferred? Could put Preferred Qualifications under Qualifications.
- Skills: maybe we can list specific skills like DFMEA, RACI, etc. But we already have them in qualifications. Could put under Skills.
But we must not create thin sections. Let's think: We have Qualification Requirements (mandatory) and Preferred Qualifications (preferred). Could combine into Requirements and Qualifications sections.
Thus:
About the role
...Position Summary...
Responsibilities
- ... each responsibility...
Requirements
- ... education, years, etc....
Qualifications
- ... preferred qualifications...
. Now Responsibilities list: each line starting with a verb. List: - Provide L1 support (basic) on Global HW Engineering Tools Environment, in the US. - Perform L1 sustaining tasks and trouble shootings on Global HW Engineering Tools Environment, in the US. - Develop, establish, and maintain engineering processes that support consistent execution across all hardware engineering disciplines. - Create, manage, and organize all process templates, checklists, and documentation including KPI’s. - Train engineering teams on processes, workflows, tools, templates, and best practices to ensure consistent adoption. - Conduct process audits to assess compliance, identify gaps, and drive corrective actions or improvement initiatives on critical-to-quality metrics (CTQ’s) and KPI’s. - Partner with engineering leaders, SMEs, and cross-functional stakeholders to refine processes for clarity, efficiency, and alignment with Engineering Operations. - Maintain and improve workflows for New Product Introduction (NPI), Sustaining Engineering, Continuous Improvement, and Engineering Change Management. - Establish and manage RACI models that define roles, responsibilities, and approval paths for engineering activities. - Partner with Program Management and System Engineering to align processes with stage-gate reviews, design reviews, and system-level deliverables. - Support the development and refinement of DFMEA processes and facilitate risk assessments as part of design workflows. - Ensure documentation repositories, process libraries, and template systems are well organized and easily accessible. - Provide guidance and coaching to engineering teams on proper process execution and documentation practices. - Collaborate with global engineering teams and support remote participation in process reviews and audits. - Identify opportunities to streamline workflows, eliminate inefficiencies, and implement process improvements that enhance engineering productivity. - Demonstrate leadership qualities such as influence, accountability, attention to detail, and a systematic approach to solving process-related challenges. We need to preserve each as
- . Now Qualification Requirements (mandatory): - Education: Bachelor’s degree in Engineering or related technical field required. - 5–8 years of engineering, process engineering, or engineering operations experience. - Strong understanding of hardware development lifecycles, engineering workflows, and cross-disciplinary processes. - Experience creating and managing process documentation, templates, and structured engineering artifacts. - Working knowledge of DFMEA, design reviews, RACI models, and stage-gate or structured development methodologies. - Strong organizational skills and detail orientation with the ability to maintain clarity and structure across complex processes. - Ability to influence teams across functions and geographies without direct authority. - Excellent communication, facilitation, and training capabilities. - Experience working with distributed or global teams. We'll put each as
- under Requirements.
Preferred Qualifications:
- Experience with Lean, Six Sigma, DFSS, or similar process improvement methodologies.
- Knowledge of PDM/PLM systems and process workflows associated with product data management.
- Experience participating in or supporting engineering audits or compliance reviews.
- Familiarity with failure analysis, quality systems, or root cause methodologies (5 Whys, Fishbone, etc.).
- Understanding of mechanical, electrical, or embedded system engineering processes.
We'll put under Qualifications.
Essential Functions: maybe we could incorporate into Responsibilities or Skills, but we have no Skills section. Could we add a Skills section? The list includes: Serve as the process owner for the Hardware Engineering organization. Represent process and governance needs in cross-functional team discussions. Support process training, documentation updates, and audit readiness. Work independently and collaboratively with global teams. Exhibit strong leadership, initiative, and attention to detail. Fluent English is required.
These are somewhat similar to responsibilities but could be considered Skills or Additional responsibilities. Since we already have Responsibilities covering many, we could add these as additional responsibilities. But to preserve all substantive info, we should include them. Perhaps we can add them under Responsibilities as additional bullets. That would be okay; we are not creating a new section.
Thus we can append those essential functions bullets to the Responsibilities list.
Let's list them:
- Serve as the process owner for the Hardware Engineering organization.
- Represent process and governance needs in cross-functional team discussions.
- Support process training, documentation updates, and audit readiness.
- Work independently and collaboratively with global teams.
- Exhibit strong leadership, initiative, and attention to detail.
- Fluent English is required.
We'll add them.
Now we need to ensure we don't include boilerplate like "The information contained within this job description overview is not intended to be all-inclusive..." etc. Remove that.
Also remove "#SWE" at end.
Now produce HTML fragment.
We'll wrap sections in appropriate tags.
Make sure no extra text.
Let's craft:
About the role
The Senior Engineer, Process is responsible for defining, maintaining, and continuously improving the engineering processes used across the Hardware Engineering organization. This role ensures that engineering teams consistently follow structured workflows, use standard templates, and adhere to best practices across all product lifecycle phases. The Senior Engineer will develop clear process documentation, deliver process training, and perform audits to validate process compliance and identify improvement opportunities. This role requires the ability to work with global teams, influence across functions without authority, and collaborate closely with Mechanical, Hydraulic, Electrical, Electronics, Firmware, Systems, Test, and Quality teams. The ideal candidate brings strong knowledge of engineering workflows, lifecycle management, DFMEA, design reviews, RACI modeling, and structured documentation practices. They must be highly organized, detail-oriented, and capable of driving continuous improvement across a distributed engineering environment.
Responsibilities
- Provide L1 support (basic) on Global HW Engineering Tools Environment, in the US.
- Perform L1 sustaining tasks and trouble shootings on Global HW Engineering Tools Environment, in the US.
- Develop, establish, and maintain engineering processes that support consistent execution across all hardware engineering disciplines.
- Create, manage, and organize all process templates, checklists, and documentation including KPI’s.
- Train engineering teams on processes, workflows, tools, templates, and best practices to ensure consistent adoption.
- Conduct process audits to assess compliance, identify gaps, and drive corrective actions or improvement initiatives on critical-to-quality metrics (CTQ’s) and KPI’s.
- Partner with engineering leaders, SMEs, and cross-functional stakeholders to refine processes for clarity, efficiency, and alignment with Engineering Operations.
- Maintain and improve workflows for New Product Introduction (NPI), Sustaining Engineering, Continuous Improvement, and Engineering Change Management.
- Establish and manage RACI models that define roles, responsibilities, and approval paths for engineering activities.
- Partner with Program Management and System Engineering to align processes with stage-gate reviews, design reviews, and system-level deliverables.
- Support the development and refinement of DFMEA processes and facilitate risk assessments as part of design workflows.
- Ensure documentation repositories, process libraries, and template systems are well organized and easily accessible.
- Provide guidance and coaching to engineering teams on proper process execution and documentation practices.
- Collaborate with global engineering teams and support remote participation in process reviews and audits.
- Identify opportunities to streamline workflows, eliminate inefficiencies, and implement process improvements that enhance engineering productivity.
- Demonstrate leadership qualities such as influence, accountability, attention to detail, and a systematic approach to solving process-related challenges.
- Serve as the process owner for the Hardware Engineering organization.
- Represent process and governance needs in cross-functional team discussions.
- Support process training, documentation updates, and