Electrical Design Engineer III, New Product Development
Woodstream Corporation · Lancaster, PA · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. Not present.
We need to preserve all substantive info.
Let's parse posting:
Company description: Woodstream is the largest independent pest & animal control platform... (first paragraph). That's about company, maybe "About the role"? Actually "About the role" is a section heading we can use for overview of role. Could also have "About the company" but not in list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for overview. Responsibilities for duties. Requirements maybe for required experience/education. Qualifications maybe similar; but we should avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can combine.
We need to include Benefits section because posting lists benefits. Pay and Schedule only if stated. No pay mentioned. Schedule not mentioned (only travel up to 5-10%). Not schedule. So we omit Pay and Schedule.
We need to include Skills maybe? Could include technical skills as part of Requirements/Qualifications. But we can have a Skills section for specific software/firmware etc. However we must not create thin sections. Let's think.
We have:
- Overview of the role: description of responsibilities.
- Key responsibilities list (bulleted).
- Essential Functions & Responsibilities (more detailed bullet list).
- Other Functions (travel etc.)
- Successful Candidate Profile: education, experience, required skills, desired skills.
- Benefits list.
Thus we can structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. Not present.
We need to preserve all substantive info.
Let's parse posting:
Company description: Woodstream is the largest independent pest & animal control platform... (first paragraph). That's about company, maybe "About the role"? Actually "About the role" is a section heading we can use for overview of role. Could also have "About the company" but not in list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for overview. Responsibilities for duties. Requirements maybe for required experience/education. Qualifications maybe similar; but we should avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can combine.
We need to include Benefits section because posting lists benefits. Pay and Schedule only if stated. No pay mentioned. Schedule not mentioned (only travel up to 5-10%). Not schedule. So we omit Pay and Schedule.
We need to include Skills maybe? Could include technical skills as part of Requirements/Qualifications. But we can have a Skills section for specific software/firmware etc. However we must not create thin sections. Let's think.
We have:
- Overview of the role: description of responsibilities.
- Key responsibilities list (bulleted).
- Essential Functions & Responsibilities (more detailed bullet list).
- Other Functions (travel etc.)
- Successful Candidate Profile: education, experience, required skills, desired skills.
- Benefits list.
Thus we can structure:
About the role
Overview paragraph.
Responsibilities
- ...
Requirements
- Bachelor’s degree in Electrical Engineering or related field.
- At least 5 years’ experience in consumer product development, PCB level product design, IC selection, BOM development and other related EE engineering activities
- Experience writing embedded firmware code is required.
- Experience in RF (radio frequency) product design is highly desirable.
- Expertise in IOT and machine learning is highly desirable.
- Strong problem solving and organizational skills.
- Strong communication and presentation skills.
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...