Automation Engineer I
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes "About Lucid" which is about company, not exactly "About the role". Could we treat that as "About the role"? Probably not; but we could include a section "About Lucid"? Not allowed headings list only those specific headings. We must use those headings only. So we need to map content to those headings. The posting includes responsibilities (list of duties). Requirements/Qualifications/Skills: we have education, experience, technical proficiencies. Could combine into Requirements and Qualifications and Skills sections. Benefits: we have compensation & benefits details. Pay: not specified (no salary). Schedule: not specified. So we should not include Pay or Schedule sections because no specific content. Also we should not include empty headings.
Thus we will output sections: About the role? Could we use "About the role" to include the Lucid description? Might be okay as it's about the role context. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. We need to include a section only when posting has real, specific content for it. Does the posting have content for "About the role"? It has a paragraph about Lucid and the role description: "The Automation Engineer, Powertrain will be responsible of ensuring new and existing control systems..." That's more role description. So we can put that under About the role.
Responsibilities: we have a bullet list of duties (starting with "You Will Have familiarity..." etc). We'll extract those as list items.
Requirements: maybe education and years experience.
Qualifications: maybe technical proficiencies.
Skills: maybe specific skills like PLC programming, safety standards, etc. But we might combine to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements, Qualifications, Skills into one section? But headings are distinct; we could choose to include only those with substantive content. Could we put all under Requirements? Might be okay but we need to follow headings. Perhaps we include Requirements (education + experience), Qualifications (technical proficiencies), Skills (specific abilities). That's three sections, each substantive.
Benefits: we have compensation & benefits paragraph.
We must not include Pay or Schedule.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: EEO, accessibility, privacy, agency, etc.
We must preserve all substantive information.
Let's extract content.
About Lucid paragraph: "At Lucid, we are creating exceptional mobility experiences through innovation to drive the world forward. Built on Lucid’s proprietary technology and software-defined vehicle architecture, our award-winning vehicles bring our “Compromise Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed and built vehicles that have redefined their segments, combining exceptional range, performance, design, and expansive space in a single experience. We achieve this through deep vertical integration, with design, engineering, and production happening in-house across our global offices and manufacturing facilities. Our teams come from industries around the world, united by a shared commitment to excellence. By refusing to settle, you can help redefine what’s possible and shape the future of mobility."
Then role description: "The Automation Engineer, Powertrain will be responsible of ensuring new and existing control systems meet throughput, safety, and quality requirements for production, as well as designing and developing continuous improvement projects according to the company's needs."
We can combine that as About the role.
Now responsibilities list: after "You Will Have familiarity with equipment control systems, equipment I/Os and basic machine coding logic." then a series of sentences each starting with a verb. We'll turn each into
. Now ensure we don't include any boilerplate like Equal Opportunity etc. Now produce HTML fragment:
About the role
At Lucid, we are creating exceptional mobility experiences through innovation to drive the world forward. Built on Lucid’s proprietary technology and software-defined vehicle architecture, our award-winning vehicles bring our “Compromise Nothing™” approach to the global automotive market. That means refusing to choose between performance and sustainability, design and engineering, ambition and integrity. In Lucid Air and Lucid Gravity, we have designed and built vehicles that have redefined their segments, combining exceptional range, performance, design, and expansive space in a single experience. We achieve this through deep vertical integration, with design, engineering, and production happening in-house across our global offices and manufacturing facilities. Our teams come from industries around the world, united by a shared commitment to excellence. By refusing to settle, you can help redefine what’s possible and shape the future of mobility. The Automation Engineer, Powertrain will be responsible of ensuring new and existing control systems meet throughput, safety, and quality requirements for production, as well as designing and developing continuous improvement projects according to the company's needs.
Responsibilities
- Work with layout engineering to prepare and optimize Powertrain line layouts
- Experience working with the following equipment: robotics, end of arm tooling, pick and place automation, position sensors, material handling, fluid dispensing, vision systems, conveyor and laser cleaning and welding.
- Develop company level, factory level, and line/machine level controls standards and specification for application by internal equipment development team and external partners
- Create data management and tracking communications network architecture and interface with cross-functional teams for product, processes and quality traceability control implementation
- Architect, write and debug PLC ladder logic with an emphasis on generating code that is organized, structured, documented, maintainable and reusable. PLC code will interact with subsystems such as conveyors, robots, Manufacturing Execution System (MES), LabView, machine vision, and 3rd party equipment
- Implement (ANSI/RIA15.06/OSHA compliant) control reliable safety systems for safeguarding robots, gantries, conveyors, and other high volume manufacturing equipment
- Generate aesthetically simple HMI screens for complex machinery while providing sufficient feedback for troubleshooting
- Enforce application of Lucid Motors standards, Manage external integrators during specification, design review, design approval
- Establish test plans and control test plan execution at Vendor and at Lucid Motors facility during installation and buy-off
- Train Maintenance and Production teams to support automated equipment after deployment into production
- Create machine interactions with plant-wide Manufacturing Execution System (MES) to communicate product acceptability, machine status, and process variables
- Debug and optimize automated processes to maximize cycle time, improve availability and yield
Requirements
- Bachelor’s Degree in Electrical, Mechanical, Computer engineering or related field is preferred; a combination of years of experience may