Jobs · Engineering · Tennessee

Manufacturing Automation Engineer

Ryder System, Inc. · Spring Hill, TN · 1 mo ago
Engineering$47k/yrFull-time
We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like privacy policy links, EEO, etc. Also remove duplicated lines, navigation, cookie, legal, EEO, scam-warning, application instructions. Also remove "Job Seekers can review the Job Applicant Privacy Policy..." lines. We need to parse the job description. Let's extract sections: - Summary Job Description: This Automation Engineering position can be responsible for the effort in identifying, evaluating, piloting and deploying new warehouse automation technologies, followed by the installation and deployment of new and optimization of warehouse automation technologies. This dedicated teams and capability differentiates Ryder by driving efficiencies to grow existing and win new business. This position will require a breadth of knowledge across many business types and automation technologies. Work directly with internal operations, solution design, continuous improvement, information technology, product teams and stakeholders to identify, select, and deploy new technology with automation partners. Consult with internal and external contacts to quickly demonstrate the value and feasibility of warehouse automation capabilities to create a competitive differentiator. Work directly with the customer and business owners to identify new ideas and collaborate across verticals, regions, and functional areas to evaluate, pilot, develop and implement warehouse automation solutions. That's about the role. Then "Essential Functions" with many bullet-like sentences. Those are responsibilities. Then "Additional Responsibilities" with more bullet-like sentences. Then "Skills And Abilities" list. Then "Qualifications" list. Then "Compensation Information" with pay range. Then "Benefits Information" with benefits. Then "Our Culture & Commitment" maybe not needed as a section; but we could include as About the role? Probably not needed. We need sections: About the role (summary), Responsibilities (essential functions + additional responsibilities), Requirements? Might be same as Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which to include based on content. We have content for About the role (summary). Responsibilities (essential functions + additional). Qualifications (education, experience). Skills (skills and abilities). Benefits (benefits info). Pay (compensation). Schedule? Not present. Requirements? Could be same as Qualifications? Usually Requirements could be separate but we have Qualifications. We could include Requirements as maybe "Required" items? But we have Qualifications already. To avoid duplication, we could include Requirements as maybe "Required" experience? But we have Qualifications covering education and experience. The instruction says include a section ONLY when posting has real, specific content for it. So we need to see if there is a distinct "Requirements" section separate from Qualifications. The posting includes "Required" and "Preferred" under Qualifications and Skills. There's no separate "Requirements" heading. So we might not include Requirements. Schedule: not present. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We must not include empty sections. Now we need to format: - Use

for each section heading. - Use
  • for any list of duties/requirements/benefits. - Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to extract the prose for About the role: The summary paragraph(s). Could be multiple sentences; we can put them in a

    . Responsibilities: We need to list duties as list items. The essential functions and additional responsibilities are many sentences, each could be a list item. We should not lose any detail. We'll need to parse them into discrete items. Let's extract essential functions bullet points from the text: Essential Functions RFP and New Business Support: Lead minor RFP project and support lead engineer on major RFP projects by leading automation selection and validation on new business sale projects by identifying potential automation technologies. Build ROI and justification based upon multiple criteria in order to select the optimal solution design Support build of presentation with Lead Automation Solutions EngineerSOW (Scope of Work) Contractual Validation:Support automation project lead on identifying gaps in vendor FSD/SOW using the FSD Checklist processDesign Validation: Provide input on automation solution designs to ensure that key items are considered for implementation and ongoing operational performance Review design options for clearance issues, power requirments, cost effeictiveness and SLA targets.Automation Procurement: Help lead build collateral for vendor tech review request and requests for quotes. Review design options for various vendors and solutionsImplementation Project Management: Some Project Management of smaller projects, including updating of Punch List, Project Plan Track milestones and requirements for implementation of projectsImplementation Support: Attend implementation status calls when needed. Verify and prioritize optimal on-stie support is utilized on all projects Ensure communication to vendor and on-site staff and handle escalation events. Coordiante support for onsite team for post-go live hypercare . Support on-site Solution Acceptance Test (SAT) testing plan Support tracking of Punch List after go-live for Uptime itemsData Analytics: Profile data from dashboard and systems to support system optimization projects Perform data analysis on reports technology controls systems and WMS/WESImplementation Commissioning and Solution Validation: Support Solutions Acceptance Testing (SAT )testing plan Support tracking of Punch ListStrategy and Success Measurements: Review team strategy with manager to set personal goalsFinancial Responsibilities: Validate spend with manager Support Project Leads on tracking project budgetAutomation Troubleshooting: Partner with vendor to resolve Priority 1-5 tickets related to down/degregated performance with site automation Join on P1/P1 Resolutions calls That's a wall of text with colon-separated sections. We need to split into list items perhaps by each colon heading? But we must preserve all substantive info; we can keep as a single paragraph? However instruction says use

    • for any list of duties/requirements/benefits. If we have a block of prose that is not a list, we could keep as

      . But the essential functions are clearly a list of duties; we should break them into items. We can split by the headings before colon: "RFP and New Business Support:", "SOW (Scope of Work) Contractual Validation:", "Design Validation:", "Automation Procurement:", "Implementation Project Management:", "Implementation Support:", "Data Analytics:", "Implementation Commissioning and Solution Validation:", "Strategy and Success Measurements:", "Financial Responsibilities:", "Automation Troubleshooting:". Each heading is followed by description. We'll create

    • with the heading bold? Not required but we can keep text as is. We also have Additional Responsibilities: "Support vendor communication for minor projects.Develops pilot activities and the hypothesis to be tested. Defines the proof of concept, formalizes the team, identifies a pilot location, obtains approvals, evaluates vendors and determines a pilot timeline. Deploys acceptable pilots to quickly evaluate business fit & operational feasibility. These results will help feed the solution design team to include proven technologies into new business proposals. Evaluate, pilot and deploy new warehouse automation technologies.Validation of new technology and automation will be supported by this role through Proof of Concept implementations. These POC implementations will be driven by the automation team, as they will also coordinate the value-justification of the project with Senior Management and the cross-functional team involved.Performs other duties as assigned." We can split that into list items as well, maybe each sentence. Now Skills And Abilities: list of items each ending with ", Required" or ", Preferred". We need to preserve all. We'll create
      • for each skill. Qualifications: list includes Bachelor's Degree..., Master's Degree..., 3 years or more..., 2 years or more..., 2 years or more..., Experience in warehouse automation that may would preferable include some of the following..., Automation, Management Consulting, Physical & Process Robotic experience. Beginner, RequiredKnowledge of Warehouse Management operations, data analytics, Industrial Engineering, warehouse types (ambient, temp control) and Lean methods. Beginner, RequiredKnowledge of all available material handling equipment and automation types such as: forklift applications, racking designs, packaging devices and automation design. Intermediate, RequiredWarehouse Design Tools i.e.; CAD, slotting, MOST, simulation, WMS, Labor Mgt. Network Design Tools a plus (e.g., Llamasoft). Data Visualization Software (e.g., Tableau, Power BI) a plus. Beginner, RequiredIndustrial or Mechanical Engineering or with equivalent warehouse operational knowledge. Beginner, RequiredExperienced in financial business case analysis to help support targeted return on investment. Intermediate, Preferred Travel Yes, 30-40% This is messy; many items are concatenated without clear separation. We need to preserve all substantive info; we could treat each sentence separated by period as an item. But there are also commas. Might be better to keep as a paragraph? However instruction says use
        • for any list of duties/requirements/benefits. Qualifications is a list; we should make list items. We need to parse the qualifications text into discrete items. Let's extract the qualifications section exactly: "Qualifications Bachelor's Degree in Industrial Engineering, Mechanical Engineering or related field of study, RequiredMaster's Degree in Industrial Engineering, Mechanical Engineering or related field of study, Preferred3 years or more in 3 years or more experience in warehouse automation, material handling technologies, industrial engineering or warehouse systems integration., Preferred2 years or more in Demonstrated experience in warehouse automation, Preferred2 years or more in Experience in warehouse automation that may would preferable include some of the following, sortation conveyor, goods-to-person, autonomous vehicles/robots, ASRS’s, RequiredAutomation, Management Consulting, Physical & Process Robotic experience. Beginner, RequiredKnowledge of Warehouse Management operations, data analytics, Industrial Engineering, warehouse types (ambient, temp control) and Lean methods. Beginner, RequiredKnowledge of all available material handling equipment and automation types such as: forklift applications, racking designs, packaging devices and automation design. Intermediate, RequiredWarehouse Design Tools i.e.; CAD, slotting, MOST, simulation, WMS, Labor Mgt. Network Design Tools a plus (e.g., Llamasoft). Data Visualization Software (e.g., Tableau, Power BI) a plus. Beginner, RequiredIndustrial or Mechanical Engineering or with equivalent warehouse operational knowledge. Beginner, RequiredExperienced in financial business case analysis to help support targeted return on investment. Intermediate, Preferred Travel Yes, 30-40%" We need to split by commas? But many items have internal commas. This is messy. Perhaps better to keep as a paragraph (

          ) because it's not a clear list. However instruction says use

          • for any list of duties/requirements/benefits. Qualifications is a list of requirements; but the text is not clearly delimited. We could still make each sentence separated by period as an item, but there are periods inside abbreviations like "ASRS’s". Might be okay. Given the complexity, maybe we can keep qualifications as a paragraph (

            ) and still comply? The instruction: "Use

            • for any list of duties/requirements/benefits, and

              for prose." If qualifications is a list of requirements, we should use

              • . But if we cannot reliably parse into items without losing detail, maybe we can still use

                and note it's prose. However risk of not following instruction. We could attempt to split by the pattern ", Required" or ", Preferred". Each item ends with either ", Required" or ", Preferred". Then after that there is a space and next item starts with a capital letter? Let's try. Text: "Bachelor's Degree in Industrial Engineering, Mechanical Engineering or related field of study, RequiredMaster's Degree in Industrial Engineering, Mechanical Engineering or related field of study, Preferred3 years or more in 3 years or more experience in warehouse automation, material handling technologies, industrial engineering or warehouse systems integration., Preferred2 years or more in Demonstrated

Similar jobs