Robotics Systems Engineer II, Tech Deployment
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include details from description.
Let's extract content.
Description paragraph: "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 Amazons 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."
That's the About the role content.
Responsibilities: The "Key job responsibilities" section lists many bullet-like sentences. We need to extract each as list items.
Let's list them:
- As a Systems Engineer II, a candidate will typically own multiple simultaneous deployments of a single technology across multiple sites or oversee multi-technology deployments within a single site; delivering within documented standards.
- This role requires a balance of experience both in working with high-complexity industrial technologies, with complex, multi-dependency project management.
- The ideal candidate is proactive and takes independent initiative in improving system performance and handling end-to-end deployment.
- In parallel to the execution, candidates will be responsible for driving continuous improvement ideas into both the deployment cycle time (safety, quality and productivity), and will be responsible for sharing engineering design improvements feedback to the hardware engineering and product teams, to simplify the installation.
- This role will require the ability to build relationships and capture and synthesize the voice of the customer.
- You will manage the tactical deployment of large scale industrial automation technologies, ranging in technical complexity and product maturity from early alpha/beta to mature Generally Available.
- You will own the tactical execution (onsite coordination of installation and acceptance testing) to achieve the target “go-live” date for each project assigned; delivering independently.
- You will 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.)
- You will improve operational metrics and team processes through automation and optimization
- You will independently resolve difficult technical problems during deployment, considering operational burden and making appropriate trade-offs between time, quality, and resources
- You will create and improve standard work documents and operational guidebooks, and work towards automating or improving team processes.
- You will influence internal and partner teams towards meeting team level goals.
- You will develop subject matter expertise in one or more deployment domains
- You will mentor junior engineers and participate in technical assessment
- You will drive operational excellence initiatives with measurable results
Also "A day in the life" paragraph could be part of responsibilities or separate but we can incorporate into responsibilities as prose? Might be considered responsibilities. But we can keep as prose under Responsibilities or maybe separate "Day in the life". But we only have allowed sections; we could incorporate into Responsibilities as prose.
Better to keep Responsibilities as list of duties; we can also add a paragraph summarizing day-to-day.
But we must not invent or summarize away detail; we can include the "A day in the life" paragraph as a
under Responsibilities.
Let's extract that paragraph:
"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."
We can include that as a
after the list.
Now Requirements: Basic Qualifications list.
- Bachelor's degree in Systems Engineering, Computer Science, or related field or relevant work experience
- 5+ years experience in troubleshooting robotics systems or other complex mechanical-electrical or networked systems to resolve escalations including quality hand-off, live order testing, site acceptance testing, operational readiness testing, and monitoring system performance
- 5+ years experience in project management related to the deployment, retrofits or technical maintenance of large-scale industrial robotics
- 5+ years experience in use of project management and supply management tools/software including managing Bills of Material, deployment work instructions, and project task management
- Experience working with technical drawings and/or reading CAD models (mechanical and electrical) for use in deployment, maintenance or support of large-scale industrial robotics
- Demonstrated ability to work with PLCs, SCADA systems, and network infrastructure.
- Ability to travel domestically 75% or more of the year
We should keep as list.
Qualifications: Preferred Qualifications.
- Experience working in 24/7 production environment
That's it.
Skills: Could be derived from responsibilities but maybe we can combine some skills like "Project management", "Systems troubleshooting", "CAD reading", "PLC/SCADA", "Cross-functional collaboration", "Continuous improvement", "Technical documentation", "Mentoring". However we must not invent details; we should only include if explicitly stated. The posting does not have a separate "Skills" section. We could omit Skills section if no explicit content. The instruction: "Prefer a few substantive sections over many thin ones." So we can skip Skills if not explicitly present. But we need to decide: The posting includes many skill-like statements but not under a heading "Skills". We could create a Skills section but that would be inventing a heading not present; but the instruction says we should use headings for sections only when posting has real, specific content for it. It does not say we cannot create a Skills section if we can extract skill-related content from the posting. However the heading "Skills" is not in the original; but we are allowed to reformat into semantic HTML; we can create sections based on content. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. It says "include a section ONLY when the posting has real, specific content for it". So we can create a Skills section if we can extract skill-specific content. The posting does mention skills like "strong technical skills for deploying robotic equipment, including mechanical and electrical systems, network configurations, and software coordination." Also "experience with complex electro-mechanical and network systems", "project management", "use of project management and supply management tools", "working with technical drawings and/or reading CAD models", "ability to work with PLCs, SCADA systems, and network infrastructure." Those are skills. So we could create a Skills section with those items as list.
But we must be careful not to duplicate content already in Requirements or Responsibilities. However it's okay to have overlapping if it's distinct categorization. The instruction says preserve ALL substantive information; not to invent or summarize away detail. Duplication is okay as long as we don't lose info. But better to avoid duplication? Not prohibited. However we might want to keep Requirements as qualifications, Skills as abilities. Let's decide to include Skills section with list of technical skills extracted.
Benefits: we have content.
Pay: salary range.
Schedule: travel expectation and relocation.
Now we need to output HTML fragment only, no /, no markdown fences.
Let's craft.
Structure:
About the role
...
Responsibilities
- ...
...
... day in the life paragraph ...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
Make sure to not include boilerplate like EEO, accommodations, etc.
Now extract precise text.
About the role paragraph: We'll copy the description paragraph exactly as given, maybe minor punctuation.
Let's copy:
"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
for prose. We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include details from description. Let's extract content. Description paragraph: "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 Amazons 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." That's the About the role content. Responsibilities: The "Key job responsibilities" section lists many bullet-like sentences. We need to extract each as list items. Let's list them: - As a Systems Engineer II, a candidate will typically own multiple simultaneous deployments of a single technology across multiple sites or oversee multi-technology deployments within a single site; delivering within documented standards. - This role requires a balance of experience both in working with high-complexity industrial technologies, with complex, multi-dependency project management. - The ideal candidate is proactive and takes independent initiative in improving system performance and handling end-to-end deployment. - In parallel to the execution, candidates will be responsible for driving continuous improvement ideas into both the deployment cycle time (safety, quality and productivity), and will be responsible for sharing engineering design improvements feedback to the hardware engineering and product teams, to simplify the installation. - This role will require the ability to build relationships and capture and synthesize the voice of the customer. - You will manage the tactical deployment of large scale industrial automation technologies, ranging in technical complexity and product maturity from early alpha/beta to mature Generally Available. - You will own the tactical execution (onsite coordination of installation and acceptance testing) to achieve the target “go-live” date for each project assigned; delivering independently. - You will 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.) - You will improve operational metrics and team processes through automation and optimization - You will independently resolve difficult technical problems during deployment, considering operational burden and making appropriate trade-offs between time, quality, and resources - You will create and improve standard work documents and operational guidebooks, and work towards automating or improving team processes. - You will influence internal and partner teams towards meeting team level goals. - You will develop subject matter expertise in one or more deployment domains - You will mentor junior engineers and participate in technical assessment - You will drive operational excellence initiatives with measurable results Also "A day in the life" paragraph could be part of responsibilities or separate but we can incorporate into responsibilities as prose? Might be considered responsibilities. But we can keep as prose under Responsibilities or maybe separate "Day in the life". But we only have allowed sections; we could incorporate into Responsibilities as prose. Better to keep Responsibilities as list of duties; we can also add a paragraph summarizing day-to-day. But we must not invent or summarize away detail; we can include the "A day in the life" paragraph as a
under Responsibilities. Let's extract that paragraph: "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." We can include that as a
after the list. Now Requirements: Basic Qualifications list. - Bachelor's degree in Systems Engineering, Computer Science, or related field or relevant work experience - 5+ years experience in troubleshooting robotics systems or other complex mechanical-electrical or networked systems to resolve escalations including quality hand-off, live order testing, site acceptance testing, operational readiness testing, and monitoring system performance - 5+ years experience in project management related to the deployment, retrofits or technical maintenance of large-scale industrial robotics - 5+ years experience in use of project management and supply management tools/software including managing Bills of Material, deployment work instructions, and project task management - Experience working with technical drawings and/or reading CAD models (mechanical and electrical) for use in deployment, maintenance or support of large-scale industrial robotics - Demonstrated ability to work with PLCs, SCADA systems, and network infrastructure. - Ability to travel domestically 75% or more of the year We should keep as list. Qualifications: Preferred Qualifications. - Experience working in 24/7 production environment That's it. Skills: Could be derived from responsibilities but maybe we can combine some skills like "Project management", "Systems troubleshooting", "CAD reading", "PLC/SCADA", "Cross-functional collaboration", "Continuous improvement", "Technical documentation", "Mentoring". However we must not invent details; we should only include if explicitly stated. The posting does not have a separate "Skills" section. We could omit Skills section if no explicit content. The instruction: "Prefer a few substantive sections over many thin ones." So we can skip Skills if not explicitly present. But we need to decide: The posting includes many skill-like statements but not under a heading "Skills". We could create a Skills section but that would be inventing a heading not present; but the instruction says we should use headings for sections only when posting has real, specific content for it. It does not say we cannot create a Skills section if we can extract skill-related content from the posting. However the heading "Skills" is not in the original; but we are allowed to reformat into semantic HTML; we can create sections based on content. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. It says "include a section ONLY when the posting has real, specific content for it". So we can create a Skills section if we can extract skill-specific content. The posting does mention skills like "strong technical skills for deploying robotic equipment, including mechanical and electrical systems, network configurations, and software coordination." Also "experience with complex electro-mechanical and network systems", "project management", "use of project management and supply management tools", "working with technical drawings and/or reading CAD models", "ability to work with PLCs, SCADA systems, and network infrastructure." Those are skills. So we could create a Skills section with those items as list.
But we must be careful not to duplicate content already in Requirements or Responsibilities. However it's okay to have overlapping if it's distinct categorization. The instruction says preserve ALL substantive information; not to invent or summarize away detail. Duplication is okay as long as we don't lose info. But better to avoid duplication? Not prohibited. However we might want to keep Requirements as qualifications, Skills as abilities. Let's decide to include Skills section with list of technical skills extracted.
Benefits: we have content.
Pay: salary range.
Schedule: travel expectation and relocation.
Now we need to output HTML fragment only, no /, no markdown fences.
Let's craft.
Structure:
About the role
...
Responsibilities
- ... ...
... day in the life paragraph ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
Make sure to not include boilerplate like EEO, accommodations, etc. Now extract precise text. About the role paragraph: We'll copy the description paragraph exactly as given, maybe minor punctuation. Let's copy: "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