Mechanical Design Engineer, Data Center Design Engineering
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the description.
Key sections:
- Description (intro) about AWS Infrastructure Services, role, team, etc. Could be "About the role" or maybe "About the team". The posting includes "About The Team" with subpoints: *Why AWS*, *Diverse Experiences*, *Work/Life Balance*, *Inclusive Team Culture*, *Mentorship and Career Growth*. Those are bullet points.
- "Key job responsibilities" list.
- "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 including health insurance ... Learn more about our benefits at https://amazon.jobs/en/benefits. USA, VA, Herndon - 116,800.00 - 160,000.00 USD annually". So we have pay range and benefits description.
- Schedule: Not mentioned explicitly. Travel occasionally necessary but shouldn't be more than 20%; International support may be part of job, some international travel may be necessary. That's not schedule but travel. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting actually states them. It does not state schedule like "Full-time" etc. So we omit Schedule.
- Benefits: The posting mentions comprehensive benefits including health insurance etc. So we can create Benefits section.
- Pay: Yes, we have base salary range. So we create Pay section.
- Skills: Not explicitly listed as a separate section; but we could incorporate skills within Responsibilities or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if there is real specific content. We have Responsibilities (Key job responsibilities). We have Qualifications (Basic Qualifications and Preferred Qualifications could be combined under Qualifications or separate? The instruction says we can have Qualifications heading. We could put both basic and preferred under Qualifications, maybe separate sub-sections? But we should avoid many thin sections. Could combine basic and preferred into one Qualifications section with two lists: Basic Qualifications and Preferred Qualifications as subheadings? But subheadings not allowed? Only h3 for section headings. Could we use
? Not allowed per instruction; only h3 for section headings. So we could have one Qualifications section and within it we could have paragraphs distinguishing basic vs preferred. Or we could have two sections: Basic Qualifications and Preferred Qualifications, but that might be thin. However they are substantive. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one Qualifications section with two
paragraphs: one for basic, one for preferred, each with
- . That seems okay.
- Skills: Not explicitly separate; we could omit Skills section if no explicit skills list. However there are skills implied in qualifications (Microsoft Office, etc). But we can incorporate into Qualifications.
- About the role: The initial description could be About the role. Also there is "About The Team" section. Could combine into About the role/team. We could have About the role (intro) and About the team (maybe separate). But to avoid many thin sections, we could have one About the role section that includes the introductory paragraphs and the About The Team bullet points. However the About The Team bullet points are distinct; but we could still include them under About the role as a list.
- Responsibilities: Already have Key job responsibilities list.
- Qualifications: combine basic and preferred.
- Benefits: we have benefits description.
- Pay: we have salary range.
- Schedule: not present, omit.
We must not include boilerplate like EEO, accommodation link, etc. Also remove duplicated lines, navigation, cookie, legal, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe we can keep the benefits description but not the link? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The link is part of benefits info; but it's a reference. Could we keep it? It's not boilerplate; it's a link to benefits. Might be considered part of benefits. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not exactly those; it's a reference. I'd keep it as part of benefits description.
Also remove "Company - Amazon Data Services, Inc." maybe minor metadata; we can fold into a short
or drop it. Probably drop it.
Also remove "Job ID: A10485482". Drop.
Also remove "USA, VA, Herndon - 116,800.00 - 160,000.00 USD annually" is pay info; we keep that in Pay section.
Now craft HTML.
Structure:
About the role
Intro paragraph(s) describing AWS Infrastructure Services, role, team, etc.
Maybe include the About The Team bullet points as - inside this section.
Then
Responsibilities
- ... each responsibility.
Then
Qualifications
Basic Qualifications:
- ... each basic qualification.
Preferred Qualifications:
- ... each preferred qualification.
Then Benefits
Description of benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention link.
Then Pay
Base salary range: $116,800.00 - $160,000.00 USD annually, plus sign-on payments and restricted stock units (RSUs). Final compensation based on experience, qualifications, location.
We should not include Schedule.
Check for duplicated lines: The description repeats some sentences; we need to preserve all substantive information but not duplicate. We need to avoid repeating same sentences. We'll need to condense but preserve meaning. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details, but we can avoid duplicate repetition of same sentence. If the same info appears multiple times, we should include it once. So we need to identify unique substantive points.
Let's extract unique points from the description.
Intro paragraph:
"AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who want to help. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion."
Then: "Amazon Web Services is seeking a Mechanical Engineer to become part of a global engineering team, responsible for the design and continuous innovation of our rapidly expanding data center foot print. Engineers at Amazon work to design resilient, cost effective mechanical distribution systems. As engineers at Amazon we are responsible for achieving a world class uptime for our customers. We justify and communicate the technical decisions we make to Sr. Management and work hard to drive continuous advancements and improvements with our designs. As an engineer at Amazon you have the ability to drive change and define/design the systems our customers rely on. Amazon offers a fast paced, fun, and exciting work environment. We continue to grow at exponential rates and are looking for individuals that can support our speed to market, enjoy a challenge, and have a desire for professional growth and continuous learning experiences. Amazon’s work environment is unique in every aspect and offers an exceptional opportunity for the right candidate. We are looking for engineers with hands on mechanical design experience. If you can design a mechanical system, have an understanding of the critical equipment needs for a data center, and understand the constructability of varying designs you may be a good fit. As we grow we are structuring our team to own more of our engineering in house. Engineers will be responsible for taking designs from concept to the permit and construction document set. You must be capable of defining critical equipment specifications and approving equipment submittals. Engineers will directly support construction and be a part of the process from site selection review through commissioning and ultimately turnover. You will be relied on as a subject matter expert in the mechanical engineering field. At Amazon we do highly support continued learning opportunities and focus on continued employee development. At Amazon team work is absolutely necessary for us to accomplish our goals. You must be able to work within a team and depend on others to accomplish the required work. As a mechanical engineer at Amazon you will be working with other internal groups as well as external groups including utilities, manufacturers, vendors, and contractors. Amazon has a global presence. Travel will occasionally be necessary but shouldn’t be more than 20%. International support will be part of the job, some international travel may be necessary. Support could consist of working on international teams and could require developing detailed schematic design packages. An understanding of international mechanical design requirements is helpful but not necessary."
Then "Key job responsibilities" list:
- Work with internal teams to understand user requirements.
- Data center mechanical designs and collaboration with other disciplines to create a construction document set.
- Creation of designs which meet or exceed our quality requirements and fall within our budgetary requirements.
- Work with regional vendors and manufactures to specify the appropriate mechanical equipment.
- Work with local utilities to understand and define site utility requirements.
- Work with local agencies having jurisdiction to ensure compliance with city/county requirements and building codes.
- Review and approval of equipment submittals.
- Define project scopes and provide technical support for information requests during construction phases.
- Work with commissioning teams to properly validate installation, operation, and performance of mechanical systems.
- Ability to work on concurrent projects in multiple geographical regions.
- Travel to sites for site review and work with onsite field engineers, engineering evaluations, mechanical systems audits, and startup as needed.
- Having fun and offering creative, out of the box solutions.
Then "About The Team" bullet points (with subheadings *Why AWS*, *Diverse Experiences*, *Work/Life Balance*, *Inclusive Team Culture*, *M
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the description. Key sections: - Description (intro) about AWS Infrastructure Services, role, team, etc. Could be "About the role" or maybe "About the team". The posting includes "About The Team" with subpoints: *Why AWS*, *Diverse Experiences*, *Work/Life Balance*, *Inclusive Team Culture*, *Mentorship and Career Growth*. Those are bullet points. - "Key job responsibilities" list. - "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 including health insurance ... Learn more about our benefits at https://amazon.jobs/en/benefits. USA, VA, Herndon - 116,800.00 - 160,000.00 USD annually". So we have pay range and benefits description. - Schedule: Not mentioned explicitly. Travel occasionally necessary but shouldn't be more than 20%; International support may be part of job, some international travel may be necessary. That's not schedule but travel. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting actually states them. It does not state schedule like "Full-time" etc. So we omit Schedule. - Benefits: The posting mentions comprehensive benefits including health insurance etc. So we can create Benefits section. - Pay: Yes, we have base salary range. So we create Pay section. - Skills: Not explicitly listed as a separate section; but we could incorporate skills within Responsibilities or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if there is real specific content. We have Responsibilities (Key job responsibilities). We have Qualifications (Basic Qualifications and Preferred Qualifications could be combined under Qualifications or separate? The instruction says we can have Qualifications heading. We could put both basic and preferred under Qualifications, maybe separate sub-sections? But we should avoid many thin sections. Could combine basic and preferred into one Qualifications section with two lists: Basic Qualifications and Preferred Qualifications as subheadings? But subheadings not allowed? Only h3 for section headings. Could we use
? Not allowed per instruction; only h3 for section headings. So we could have one Qualifications section and within it we could have paragraphs distinguishing basic vs preferred. Or we could have two sections: Basic Qualifications and Preferred Qualifications, but that might be thin. However they are substantive. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one Qualifications section with two
paragraphs: one for basic, one for preferred, each with
- . That seems okay.
- Skills: Not explicitly separate; we could omit Skills section if no explicit skills list. However there are skills implied in qualifications (Microsoft Office, etc). But we can incorporate into Qualifications.
- About the role: The initial description could be About the role. Also there is "About The Team" section. Could combine into About the role/team. We could have About the role (intro) and About the team (maybe separate). But to avoid many thin sections, we could have one About the role section that includes the introductory paragraphs and the About The Team bullet points. However the About The Team bullet points are distinct; but we could still include them under About the role as a list.
- Responsibilities: Already have Key job responsibilities list.
- Qualifications: combine basic and preferred.
- Benefits: we have benefits description.
- Pay: we have salary range.
- Schedule: not present, omit.
We must not include boilerplate like EEO, accommodation link, etc. Also remove duplicated lines, navigation, cookie, legal, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe we can keep the benefits description but not the link? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The link is part of benefits info; but it's a reference. Could we keep it? It's not boilerplate; it's a link to benefits. Might be considered part of benefits. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not exactly those; it's a reference. I'd keep it as part of benefits description.
Also remove "Company - Amazon Data Services, Inc." maybe minor metadata; we can fold into a short
or drop it. Probably drop it. Also remove "Job ID: A10485482". Drop. Also remove "USA, VA, Herndon - 116,800.00 - 160,000.00 USD annually" is pay info; we keep that in Pay section. Now craft HTML. Structure:
About the role
Intro paragraph(s) describing AWS Infrastructure Services, role, team, etc.
Maybe include the About The Team bullet points as- inside this section.
Then
Responsibilities
- ... each responsibility.
Then
Qualifications
Basic Qualifications:
- ... each basic qualification.
Preferred Qualifications:
- ... each preferred qualification.
Benefits
Description of benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention link.
ThenPay
Base salary range: $116,800.00 - $160,000.00 USD annually, plus sign-on payments and restricted stock units (RSUs). Final compensation based on experience, qualifications, location.
We should not include Schedule. Check for duplicated lines: The description repeats some sentences; we need to preserve all substantive information but not duplicate. We need to avoid repeating same sentences. We'll need to condense but preserve meaning. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details, but we can avoid duplicate repetition of same sentence. If the same info appears multiple times, we should include it once. So we need to identify unique substantive points. Let's extract unique points from the description. Intro paragraph: "AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who want to help. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion." Then: "Amazon Web Services is seeking a Mechanical Engineer to become part of a global engineering team, responsible for the design and continuous innovation of our rapidly expanding data center foot print. Engineers at Amazon work to design resilient, cost effective mechanical distribution systems. As engineers at Amazon we are responsible for achieving a world class uptime for our customers. We justify and communicate the technical decisions we make to Sr. Management and work hard to drive continuous advancements and improvements with our designs. As an engineer at Amazon you have the ability to drive change and define/design the systems our customers rely on. Amazon offers a fast paced, fun, and exciting work environment. We continue to grow at exponential rates and are looking for individuals that can support our speed to market, enjoy a challenge, and have a desire for professional growth and continuous learning experiences. Amazon’s work environment is unique in every aspect and offers an exceptional opportunity for the right candidate. We are looking for engineers with hands on mechanical design experience. If you can design a mechanical system, have an understanding of the critical equipment needs for a data center, and understand the constructability of varying designs you may be a good fit. As we grow we are structuring our team to own more of our engineering in house. Engineers will be responsible for taking designs from concept to the permit and construction document set. You must be capable of defining critical equipment specifications and approving equipment submittals. Engineers will directly support construction and be a part of the process from site selection review through commissioning and ultimately turnover. You will be relied on as a subject matter expert in the mechanical engineering field. At Amazon we do highly support continued learning opportunities and focus on continued employee development. At Amazon team work is absolutely necessary for us to accomplish our goals. You must be able to work within a team and depend on others to accomplish the required work. As a mechanical engineer at Amazon you will be working with other internal groups as well as external groups including utilities, manufacturers, vendors, and contractors. Amazon has a global presence. Travel will occasionally be necessary but shouldn’t be more than 20%. International support will be part of the job, some international travel may be necessary. Support could consist of working on international teams and could require developing detailed schematic design packages. An understanding of international mechanical design requirements is helpful but not necessary." Then "Key job responsibilities" list: - Work with internal teams to understand user requirements. - Data center mechanical designs and collaboration with other disciplines to create a construction document set. - Creation of designs which meet or exceed our quality requirements and fall within our budgetary requirements. - Work with regional vendors and manufactures to specify the appropriate mechanical equipment. - Work with local utilities to understand and define site utility requirements. - Work with local agencies having jurisdiction to ensure compliance with city/county requirements and building codes. - Review and approval of equipment submittals. - Define project scopes and provide technical support for information requests during construction phases. - Work with commissioning teams to properly validate installation, operation, and performance of mechanical systems. - Ability to work on concurrent projects in multiple geographical regions. - Travel to sites for site review and work with onsite field engineers, engineering evaluations, mechanical systems audits, and startup as needed. - Having fun and offering creative, out of the box solutions. Then "About The Team" bullet points (with subheadings *Why AWS*, *Diverse Experiences*, *Work/Life Balance*, *Inclusive Team Culture*, *M
- ... each responsibility.
Then
- inside this section.
Then