Robotics Systems Engineer II, Tech Deployment
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the description and extract sections.
Let's identify content:
- Description: introductory paragraph about role.
- "Key job responsibilities" list.
- "A day in the life" paragraph.
- "Amazon offers a full range of benefits..." paragraph.
- "If you are not sure..." (encouragement) maybe not needed? It's not a section.
- "About The Team" paragraph.
- "Basic Qualifications" list.
- "Preferred Qualifications" list.
- Pay: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits ..." Then later "USA, WA, Bellevue - 104,500.00 - 160,000.00 USD annually". So pay info present.
- Schedule: Not explicitly mentioned. Travel-based role, travel 75% or more. That could be schedule? It's about travel requirement. Not exactly schedule like full-time/part-time. Might not include schedule section unless explicit. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Travel is not schedule. So we may omit Schedule.
- Benefits: Yes, there is benefits paragraph. So include Benefits section.
- Pay: Yes, include Pay section.
- Skills: Not explicit separate list; but we could include Skills if we infer from qualifications? Probably better to not create Skills unless explicit. The posting does not have a "Skills" heading. So we omit Skills.
- About the role: The initial description could be considered About the role. We'll use About the role
with paragraphs.
- Responsibilities: from "Key job responsibilities" and maybe "A day in the life". We'll combine.
- Requirements: Could be Basic Qualifications? Or Requirements vs Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which to use. We have Basic Qualifications and Preferred Qualifications. Could map Basic Qualifications to Requirements, Preferred Qualifications to Qualifications. Or we could combine both into Qualifications. But we have both sections; we could make Requirements for basic, Qualifications for preferred. That seems logical.
- Benefits: include.
- Pay: include.
- Schedule: not present, omit.
We must not repeat job title. No Job ID.
We must preserve all substantive information. So we need to include all details from description, responsibilities, day in the life, benefits, about the team, basic qualifications, preferred qualifications, pay range, location, etc.
We must not include boilerplate like EEO, accommodation link, etc. Remove those.
We must not include application instructions like "please apply!" etc. Remove.
We must not include duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
Join Amazon's Robotics (AR) Technology Deployment team within Amazon Robotics (AR) organization to deploy innovative industrial robotics across North America's fulfillment network. In AR TD, we have the unique role and privilege of deploying leading edge industrial robotics and customer fulfillment technologies across the North America Stores operations. We raise the bar on the speed, quality and cost of deploying industrial technologies at scale across North America, functioning as the field team who plan, execute and launch the technologies that our internal design and product strategy partners in A develop. As a Systems Engineer in AR TD, you will be overseeing large scale project planning, installation, and launch of industrial automation technologies across Amazon's growing Stores network. This field engineering position demands strong technical skills for deploying robotic equipment, including mechanical and electrical systems, network configurations, and software coordination. The ideal candidate has experience with complex electro-mechanical and network systems, large scale installations, and system troubleshooting. You will work with cross-functional partners across the Amazon Fulfillment Technology & Robotics engineering, safety, product strategy, software, supply chain, third-party installers, contracted deployment engineers, construction teams, and internal operations customer teams, functioning as the lead on-site project manager to provide technical oversight on installation Amazon-designed automation equipment. This Systems Engineer position is an individual contributor role, influencing and leading stakeholders from planning through go-live of each project. Project durations vary from a few days to several months each. This is a travel-based role and you will be expected to travel to meet the requirements of your projects across North America, upwards of 75% or more. Relocation to Amazon Corporate offices in Seattle, Boston, Nashville or Austin will be required for the role.
Responsibilities
- Own multiple simultaneous deployments of a single technology across multiple sites or oversee multi-technology deployments within a single site; delivering within documented standards.
- Balance experience in working with high-complexity industrial technologies and complex, multi-dependency project management.
- Take independent initiative in improving system performance and handling end-to-end deployment.
- Drive continuous improvement ideas into deployment cycle time (safety, quality and productivity).
- Share engineering design improvements feedback to hardware engineering and product teams to simplify installation.
- Build relationships and capture and synthesize the voice of the customer.
- Manage tactical deployment of large scale industrial automation technologies, ranging in technical complexity and product maturity from early alpha/beta to mature Generally Available.
- Own tactical execution (onsite coordination of installation and acceptance testing) to achieve target “go-live” date for each project assigned; delivering independently.
- Collaborate with hardware engineering, technical program managers, product managers, and internal customers including site maintenance and operations teams to convert technical requirements into refined deployment execution documents (schedules, Standard Operating Procedures, dependencies, etc.).
- Improve operational metrics and team processes through automation and optimization.
- Independently resolve difficult technical problems during deployment, considering operational burden and making appropriate trade-offs between time, quality, and resources.
- Create and improve standard work documents and operational guidebooks, and work towards automating or improving team processes.
- Influence internal and partner teams towards meeting team level goals.
- Develop subject matter expertise in one or more deployment domains.
- Mentor junior engineers and participate in technical assessment.
- Drive operational excellence initiatives with measurable results.
A day in the life
but not in allowed headings list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add other headings. So we incorporate day in the life into Responsibilities or About the role. Probably Responsibilities is fine; we can add a paragraph after the list describing day-to-day.
Let's add a
after the list: "In this role you will be focused on execution of end-to-end deployment and manage technical ambiguity around integration of workcells in fulfillment centers. On a daily basis you will collaborate with hardware engineering, technical program managers, product managers, construction teams, and internal customers including site maintenance and operations teams, to ensure a safe, on time, high quality product is delivered to the internal customer. You will travel to your project sites, collaborate both virtually and in person, to ensure all business stakeholders are aligned on program status. You will manage the day-to-day project execution, and work on continuous improvement activities to improve deployment execution first pass yield. You will work with senior engineers and your manager to develop technical depth and begin building strategic thinking skills for future growth." That preserves day in the life.