Mechatronics & Robotics Tech
About the role
), Responsibilities (Responsibilities
), Requirements (Requirements
), Qualifications (Qualifications
), Skills (Skills
), Benefits (Benefits
), Pay (Pay
), Schedule (Schedule
). But we should only include sections if posting has real specific content. Let's see: - About the role: we have paragraph about role. Yes. - Responsibilities: we have list of responsibilities (Key job responsibilities). Yes. - Requirements: we have Basic Qualifications (maybe considered Requirements). Also maybe "Work a flexible schedule/shift/work area, including weekends, nights, and/or holidays" is a requirement. So we can put Requirements section with basic qualifications. - Qualifications: we have Preferred Qualifications. Could be Qualifications section. - Skills: maybe we can extract skills from responsibilities or qualifications? The posting mentions skills like troubleshooting, reading blueprints, etc. Could be placed under Skills. But we need to avoid thin sections. Could combine skills into Qualifications? However instruction says prefer a few substantive sections over many thin ones. We could have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Schedule: we have mention of flexible schedule, shift work, up to 12 hour shifts, weekends, nights, holidays. That's schedule info. So we could have Schedule section. But we must not create sections with filler like "not specified". We have actual schedule info: "Work a flexible schedule/shift/work area, including weekends, nights, and/or holidays" and "stand and walk during shifts lasting up to 12 hours". So we can include Schedule. Pay: we have hourly range 31.85-33.85 USD, plus shift differential etc. So Pay section. Benefits: we have healthcare benefits Day 1, matching 401(k), up to 20 weeks paid parental leave, lightweight fire-resistant daily wear and composite toe safety shoes, EAP, Mental Health Support, Medical Advice Line, 401(k) matching (already mentioned). Also maybe mention "Amazon offers competitive compensation packages including comprehensive healthcare benefits starting on Day 1, matching 401(k) program, and up to 20 weeks of paid parental leave." plus safety gear. So Benefits section. Now we need to format lists with- . For prose use
. Must not repeat job title. Must not include Job ID. Must not include application instructions (the selection process steps). So we must remove the steps (Step 1-5). Also remove "Here is what you can expect with the Reliability & Maintenance Engineering (RME) selection process for Mechatronics & Robotics Technicians: (Timeframe: Approximately 30-days)" etc. Also remove "If you have a disability..." EEO boilerplate. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "Learn more about our benefits at https://hiring.amazon.com/why-amazon/benefits." maybe that's okay as part of benefits? It's a link; but it's not boilerplate? Might be okay to keep as part of benefits? It's a reference; but it's not prohibited. However it's not essential; but we can keep as part of benefits description. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact details: e.g., "You will promote a safe working environment by following all safety procedures", etc. Must keep them as list items. We need to avoid duplication: there is duplicate "Key job responsibilities Key Job Responsibilities Include, But Are Not Limited To". We'll just output once. Now let's extract content. Intro paragraph: "Description About Maintenance at Amazon Operations is at the heart of Amazon’s business. We are known for our speed, accuracy, and exceptional service. Our buildings deliver tens of thousands of products to hundreds of countries worldwide, every day. Reliability Maintenance & Engineering (RME) are the business partners that work tirelessly behind the scenes to make it all happen. We drive continuous improvement and maintain all of the Robotics and Material Handling Equipment (MHE) to ensure our customers are met with the Amazon smile. Come join us on our journey!" This is descriptive; could be part of About the role? But we have separate About the role section. The intro could be considered part of About the role or maybe we could include as a preamble before sections. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It didn't say we cannot have a preamble paragraph before headings. We could include it as a
before the first heading. That's fine. Now About the role: "As a Mechatronics & Robotics Technician, you will use your skills to support the Operations Maintenance team in repairing and maintaining material handling equipment and pneumatic systems throughout the building. You will have the opportunity to install, maintain, and repair automated packaging and distribution equipment. In addition to developing your skills, you will mentor junior technicians to grow in their roles." Now Responsibilities: list items: - You will promote a safe working environment by following all safety procedures - You will complete preventative maintenance routines with proper documentation - You will troubleshoot electrical and mechanical problems related to all Material Handling Equipment (MHE) which includes belts, motors, photo-eyes, relays, and more - You will maintain a positive working relationship across all of the Amazon Operations facility - You must be able to move up to 49lbs, stand and walk during shifts lasting up to 12 hours, climb ladders and gangways safely, and without limitation, as well as perform regular bending, lifting, stretching, and reaching both below the waist and above the head - Please note that while we strive to accommodate employees' preferences for shift assignments, due to operational requirements and scheduling constraints, we cannot guarantee a specific shift assignment. Note: The last bullet about shift assignment could be considered schedule, but it's also a responsibility? It's more about schedule constraints. Might be better placed under Schedule. However it's a note about shift assignment; we could keep under Responsibilities or Schedule. Since we have a Schedule section, we could move that note there. But the instruction says preserve ALL substantive information; we can place it where appropriate. Let's put shift assignment note under Schedule. Now Requirements (Basic Qualifications): - High school or equivalent diploma - 1+ years of Microsoft Office products and applications experience - Work a flexible schedule/shift/work area, including weekends, nights, and/or holidays - 2+ years of automated conveyor systems and controls experience, or certification from Amazon's Mechatronics and Robotics Apprenticeship Program - 2+ years of conducting predictive and preventative maintenance procedures experience - 2+ years of reading blueprints and electrical schematics experience - 2+ years of demonstrating safety standards experience - 2+ years of troubleshooting and diagnostics of material handling equipment (MHE) experience Note: The flexible schedule item could also go under Schedule; but it's a qualification. We'll keep it under Requirements. Now Qualifications (Preferred Qualifications): - Experience with robotic operation and maintenance - 2+ years of electrical and electronic principles experience - Associate's degree in Mechnical or Electrical (typo: Mechnical) - 2+ years of Mechanical or Electrical apprenticeship experience Now Skills: Could extract from responsibilities and qualifications: e.g., troubleshooting, preventive maintenance, reading blueprints, safety standards, etc. But we might avoid a thin Skills section; maybe we can combine skills into Responsibilities or Qualifications. However the instruction says we can include Skills section if there is real specific content. We could list skills like: troubleshooting electrical/mechanical problems, preventive maintenance, reading blueprints, demonstrating safety standards, etc. But that overlaps with responsibilities. Might be considered duplication. Safer to omit Skills section if not explicitly listed. The posting does not have a separate "Skills" heading; it's embedded. So we might not create a Skills section to avoid thin content. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills. Now Benefits: list: - Competitive compensation packages including comprehensive healthcare benefits starting on Day 1 - Matching 401(k) program - Up to 20 weeks of paid parental leave - Lightweight fire-resistant daily wear and composite toe safety shoes for safety - EAP, Mental Health Support, Medical Advice Line (starting Day 1 of employment) - 401(k) matching (already mentioned but we can note) - Learn more about our benefits at https://hiring.amazon.com/why-amazon/benefits. We should avoid duplication: "matching 401(k) program" and "401(k) matching" are same; we can combine. Now Pay: we have: - Starting pay range: 31.85 - 33.85 USD hourly (USA, IA, Davenport) - Base pay rate plus highest available shift differential depending on shift selected - Additional earnings may include shift differentials and overtime pay - Final pay based on factors including shift selection and location - Starting Day 1 of employment, Amazon offers EAP, Mental Health Support, Medical Advice Line, 401(k) matching (already in benefits but okay) We should keep the specifics. Now Schedule: we have: - Work a flexible schedule/shift/work area, including weekends, nights, and/or holidays - Shifts lasting up to 12 hours - While we strive to accommodate employees' preferences for shift assignments, due to operational requirements and scheduling constraints, we cannot guarantee a specific shift assignment. - Must be able to move up to 49lbs, stand and walk during shifts lasting up to 12 hours, climb ladders and gangways safely, and without limitation, as well as perform regular bending, lifting, stretching, and reaching both below the waist and above the head (this is more physical demand; could be under Responsibilities or Schedule). We already used physical demand in Responsibilities. We'll keep it there. Thus Schedule section includes flexible schedule, up to 12 hour shifts, weekends/nights/holidays, no guaranteed shift assignment. Now we need to output HTML fragment:
About the