Electrical Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like Job ID. Remove boilerplate: EEO, legal, etc. Also remove application instructions (none present). Need to preserve all substantive info. We need to parse the description. Sections present: - Description (intro) maybe "About the role"? The first paragraph: "Electrical Engineer At Okuma, innovation and engineering excellence drive everything we do. As an Electrical Engineer, you will play a key role..." That's about the role. So we can put that under

About the role

with

. - How You'll Make an Impact: list of duties. That's responsibilities. So

Responsibilities

with

• each bullet. - What We're Looking For: includes Required Qualifications and Preferred Qualifications & Skills. Could split into Requirements (maybe required) and Qualifications (maybe preferred) and Skills. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for Requirements (required qualifications). We have content for Qualifications (maybe preferred qualifications). We have content for Skills (maybe preferred skills). However the posting lumps them: "Required Qualifications" list then "Preferred Qualifications & Skills". We can separate: Requirements = Required Qualifications. Qualifications = Preferred Qualifications. Skills = maybe the skills listed under Preferred Qualifications & Skills? But they already include skills. Could treat "Skills" as the bullet list of skills under Preferred Qualifications & Skills. But we need to avoid duplication. Better: Use Requirements for Required Qualifications. Use Qualifications for Preferred Qualifications (maybe just the line "Preferred Qualifications & Skills" but we need specific content). Use Skills for the bullet list of skills under Preferred Qualifications & Skills (like Strong understanding..., Experience..., etc). However the Preferred Qualifications & Skills includes both qualifications and skills. Might be okay to put all under Qualifications and leave Skills empty? But we must not emit empty sections. So we need to decide. We could treat: - Requirements: Required Qualifications (list) - Qualifications: Preferred Qualifications (the bullet points that are qualifications: Strong understanding..., Experience..., Prior software coding experience..., Strong analytical..., Ability..., Commitment...) - Skills: maybe the specific technical skills: Working knowledge of PLC programming, motor drives, industrial communication protocols; Ability to progress from problem statement... etc. But those are also in Required Qualifications. Better approach: Use the headings as they appear in the posting: "Required Qualifications" and "Preferred Qualifications & Skills". But the instruction says to use those specific headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we must map. Thus: - About the role: intro paragraph. - Responsibilities: How You'll Make an Impact bullet list. - Requirements: Required Qualifications bullet list. - Qualifications: Preferred Qualifications & Skills bullet list (maybe treat as qualifications). - Skills: maybe we could extract specific skills from the Preferred Qualifications & Skills that are skill-based: "Strong understanding of industrial electrical systems and controls." etc. But that seems redundant. Alternatively, we could omit Skills section if no distinct skill content beyond what's already covered. But we need to check if there is any explicit skill list separate. The posting includes: "Working knowledge of PLC programming, motor drives, and industrial communication protocols." That's a skill. Also "Skilled at progressing from problem statement to well-documented and tested design solutions." That's a skill. Also "Understanding and application of national and international standards..." That's a skill. Also "Strong written and verbal technical communication skills." That's a skill. Also "Ability to work independently..." etc. Those are more abilities. Thus we could put Skills section with those skill statements. But we must not duplicate content. If we put skill statements in Skills, we should not also put them in Requirements or Qualifications. However the Required Qualifications already includes many of those statements. To avoid duplication, we could split: Requirements = the list of required qualifications (degree, years experience, experience processing RFEQs, etc). Qualifications = preferred qualifications (the bullet points under Preferred Qualifications & Skills that are more about experience/knowledge). Skills = the specific skill statements (like working knowledge of PLC, etc). But we need to ensure we don't lose any info. Let's extract Required Qualifications bullet points: - Bachelor of Science degree in Electrical Engineering or equivalent preferred. - 3-7 years of electrical design experience in a manufacturing, industrial, automation, or related environment. - Experience processing and supporting RFEQs, ECOs, Sales Orders, and ERP-driven engineering workflows. - Experience creating electrical designs and engineering documentation, including wiring diagrams, BOMs, functional specifications, and installation documentation. - Experience troubleshooting electromechanical systems and performing root cause analysis. - Working knowledge of PLC programming, motor drives, and industrial communication protocols. - Skilled at progressing from problem statement to well-documented and tested design solutions. - Understanding and application of national and international standards, including ISO, OSHA, and ANSI standards. - Strong written and verbal technical communication skills. - Ability to work independently on standard designs while collaborating on more complex engineering challenges. - Ability to effectively partner with sales, service, manufacturing, suppliers, distributors, and customers. - Ability to travel up to 10% to support customers, distributors, and partners. Preferred Qualifications & Skills bullet points: - Strong understanding of industrial electrical systems and controls. - Experience working within ERP-driven engineering environments. - Experience supporting cost reduction initiatives and design standardization efforts. - Prior software coding experience. - Strong analytical, problem-solving, and root cause analysis skills. - Ability to manage multiple projects and priorities while maintaining quality and accuracy. - Commitment to continuous improvement and engineering excellence. Now we need to map to sections. Requirements: maybe the Required Qualifications list. Qualifications: maybe the Preferred Qualifications list (the first four items? Actually they are all under Preferred Qualifications & Skills). But we need to separate skills. Skills: maybe the skill-oriented items from Preferred Qualifications & Skills: Strong understanding..., Experience..., Experience..., Prior software coding experience..., Strong analytical..., Ability..., Commitment... Those are more like qualifications/skills. Hard to separate. Alternative: Use Requirements for Required Qualifications, Qualifications for Preferred Qualifications & Skills (all), and omit Skills section because no distinct skill-only content beyond those. But we need to check if there is any skill-specific content not captured elsewhere: The Required Qualifications includes "Working knowledge of PLC programming, motor drives, and industrial communication protocols." That's a skill but it's in Required Qualifications. If we put that in Requirements, it's fine. Then we don't need a separate Skills section. Thus we can have: - About the role - Responsibilities - Requirements (Required Qualifications) - Qualifications (Preferred Qualifications & Skills) - Benefits (from "Supporting Your Success" paragraph) - Pay (none explicit) - Schedule (none explicit) We must not create Pay or Schedule sections if not stated. The posting does not mention pay or schedule specifics. So we omit those sections. Benefits: The paragraph under "Supporting Your Success" lists benefits: structured bonus opportunities, pension plan, 401(k), medical, dental, vision coverage, company-paid disability insurance, flexible spending accounts, wellness and gym reimbursement programs, tuition reimbursement, generous paid time off, paid holidays, parental leave, flexible scheduling options. That's substantive. So we create

  Benefits

  with
  • each. We must also include any other sections like maybe "About the role" includes the first paragraph plus maybe the "How You'll Make an Impact" is responsibilities. Good. Now we need to ensure we don't include boilerplate: EEO, legal, etc. Remove the "Equal Opportunity & Accommodations" paragraph and the disclaimer about job description not exhaustive. Also remove "The Okuma Difference" paragraph? That is substantive about company but maybe not required? It's about company culture; could be considered part of About the role? But it's not a heading. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info somewhere. Where to put? Could be part of About the role (maybe after intro). Or we could create a separate section like "About Okuma" but not in allowed headings. Since only allowed headings are those list, we must fit into one of them. The "About the role" heading could encompass both role description and company info. So we can add that paragraph under About the role as additional

    . Thus About the role will have two paragraphs: first about role, second about Okuma difference (The Okuma Difference...). Also maybe "Supporting Your Success" is benefits, already covered. Now check for any other substantive content: The "How You'll Make an Impact" list we already used for responsibilities. Ensure we capture each bullet exactly. Let's list responsibilities bullets: - Process Requests for Engineering Quotations (RFEQs) to support sales activities and project execution. - Provide direct technical support to sales, service, distributors, and partners as required. - Develop and maintain electrical designs for manufacturing solutions, including peripheral equipment integration. - Create and maintain engineering documentation, including: - Functional specifications - Installation instructions - Wiring diagrams and wiring tables - Bills of Materials (BOMs) - Process and implement Engineering Change Orders (ECOs). - Conduct investigations and root cause analysis related to Notifications of Problem (NOPs). - Drive continuous improvement of electrical designs, systems, and engineering processes. - Support standardization initiatives, including common components and design practices. - Create and maintain project schedules to support delivery commitments. - Perform conceptual and detailed electrical design work. - Support U.S. sourcing activities for electrical components and systems. - Manage cost control and cost reduction initiatives while meeting project objectives. - Evaluate and specify electrical and electromechanical components. - Troubleshoot electromechanical systems, components, and integrated solutions. - Perform basic setup, programming, and troubleshooting of: - PLCs - Motor drives - Industrial communication systems Note that some bullets have sub-bullets (like Create and maintain engineering documentation, including: then sublist). We need to represent as nested

    • maybe. The instruction: Use
      • for any list of duties/requirements/benefits. So we can have nested lists. Similarly for Requirements and Qualifications we have simple bullet lists. Now Benefits list: structured bonus opportunities, pension plan, 401(k), medical, dental, and vision coverage, company-paid disability insurance, flexible spending accounts, wellness and gym reimbursement programs, tuition reimbursement, generous paid time off, paid holidays, parental leave, and flexible scheduling options. We'll make each as
      • . Now ensure we don't include any boilerplate like "Equal Opportunity & Accommodations", "This job description is intended..." etc. Now produce HTML fragment. Structure:

        About the role

        Electrical Engineer At Okuma, innovation and engineering excellence drive everything we do. As an Electrical Engineer, you will play a key role in supporting customer-focused manufacturing solutions by processing engineering requests, developing electrical designs, supporting product improvements, and troubleshooting integrated systems. This position combines technical design work with cross-functional collaboration, helping ensure projects are delivered efficiently, accurately, and in alignment with quality, cost, and standardization objectives. This role is ideal for an engineer who enjoys both design and hands-on problem-solving, thrives in a manufacturing or automation environment, and is passionate about delivering reliable solutions that support customers and business growth.

        For more than a century, Okuma has been a global leader in CNC machine tool technology, delivering innovative solutions that help manufacturers maximize productivity and precision. Our engineers work on meaningful projects that directly support customer success while collaborating with experienced professionals across engineering, sales, service, and manufacturing. At Okuma, you'll find an environment that encourages innovation, technical growth, collaboration, and continuous learning.