Jobs · Consulting · Ohio

Sr. Electrical Engineer, Data Center Engineering

Amazon Web Services (AWS) · Columbus, OH · 1 mo ago
ConsultingFull-time
We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the description and extract sections. Let's identify content: - About the role: The initial paragraphs describing AWS Infrastructure Services, role description, team, etc. Could be "About the role". We'll put that as

About the role

with paragraphs. - Responsibilities: There's a "Key job responsibilities" list bullet points. Also "A day in the life" maybe part of responsibilities? We'll treat responsibilities as bullet list. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: Not explicitly listed; maybe we can infer from responsibilities? But we should not create a Skills section unless posting actually states them. The posting does not have a separate "Skills" heading. So we skip Skills. - Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave." Also earlier: "Amazon offers a fast paced, fun, and exciting work environment." But benefits specifics are given. So we can include Benefits section with that info. - Pay: The posting includes salary ranges for various locations: "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." Then lists ranges for several cities. So we have Pay info. We'll include Pay section with those ranges. - Schedule: Not mentioned explicitly. There's travel up to 20% but not schedule. So we skip Schedule. We must not include filler like "commensurate with experience". The Pay section includes specific ranges, good. We need to format lists with
  • . For prose use

    . We must not repeat job title. No markdown. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep details like responsibilities bullet points exactly as given (maybe rephrase? Must preserve all substantive information; we can keep the same wording but maybe we need to keep them as list items. We can copy the bullet points. Let's extract responsibilities bullet points from "Key job responsibilities" section: - Data center electrical 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 local agencies having jurisdiction to ensure compliance with federal, state and municipal requirements and building codes. - Review and approval of equipment submittals. - Define project scope and provide technical support for information requests prior to, and during construction phases. - Work with commissioning teams to properly test and validate installation, operation, and performance of electrical systems. - Ability to work on concurrent projects in multiple geographical regions. - Travel to sites for site review and work with onsite field engineers, as well as provide engineering evaluations, electrical systems audits, and startup as needed. - Having fun and offering creative, out of the box solutions. Also "A day in the life" paragraph could be part of responsibilities or about role. Might be considered responsibilities but we can include as prose under About the role or Responsibilities. Since it's descriptive of a day, maybe we can put under About the role. But we already have About the role covering role description. Could add as a paragraph under About the role. Better: Keep About the role as initial description up to "Key job responsibilities". Then Responsibilities as the bullet list. Then maybe include "A day in the life" as a paragraph under About the role or Responsibilities? I'd put it under About the role as it's more narrative. Now Basic Qualifications bullet points: - 6+ years of industrial or commercial engineering in mission critical facilities including but not limited to: data centers, power generation or oil and gas facilities experience - Bachelor's degree in Engineering or a related field - Knowledge of critical data center/mission critical mechanical and electrical equipment - Experience in data center/mission critical design, construction, operations, or facility maintenance - Experience researching new designs, technologies, and construction methods of data center/mission critical equipment and facilities Preferred Qualifications bullet points: - 6+ years of data center design, construction, operations, or facility maintenance experience - Professional Engineering or Architectural License - Knowledge of building codes and regulations for your region - Experience carrying design concepts through exploration, development, and into deployment or mass production - Experience reading, interpreting, and creating construction drawings, specifications, and submittal documents Benefits: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Also earlier: "Amazon offers a fast paced, fun, and exciting work environment." Could be part of benefits or about role. We'll include in Benefits maybe as a sentence. Pay: The base salary range list: - USA, GA, Atlanta - 136,600.00 - 184,800.00 USD annually - USA, OH, COLUMBUS - 136,600.00 - 184,800.00 USD annually - USA, TX, Austin - 136,600.00 - 184,800.00 USD annually - USA, VA, Herndon - 136,600.00 - 184,800.00 USD annually - USA, WA, Seattle - 136,600.00 - 184,800.00 USD annually Also mention sign-on payments and RSUs. We'll include Pay section with that info. Now we need to ensure we don't include boilerplate like EEO, accommodation link, etc. Remove those. We also need to remove duplicated lines. Now craft HTML. Structure:

    About the role

    ... paragraphs ...

    Maybe multiple paragraphs. We'll combine the initial description up to before "Key job responsibilities". Let's extract that: "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. Amazon Web Services is seeking a Senior Electrical 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 electrical 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. If you are a creative, smart and driven individual that enjoys working with complex problems we want YOU! At Amazon you will be responsible for working on multi-million dollar designs that support our array of businesses and wide variety of customers. Great ideas are encouraged and supported. Ingenuity is the main mechanism which supports our focus on quality, speed, and cost. We are looking for engineers with hands on electrical design experience. If you can design an electrical 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 electrical engineering field. At Amazon we 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 an electrical 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 should be up to 20% of your time and in-person collaboration efforts in your assigned office location." Then after that we have "Key job responsibilities" heading (but we will not replicate heading; we will make our own

    Responsibilities

    and list. Then after responsibilities we have "A day in the life" paragraph: "You'll start your day connecting with global team members to review ongoing projects. You might analyze energy efficiency data, collaborate on innovative cooling solutions, or mentor fellow engineers. You'll participate in design reviews, engage with vendors, and contribute to sustainability initiatives that shape our environmental footprint." We could include that as a paragraph under About the role after the main description, or as part of Responsibilities. I'll add as a separate paragraph under About the role after the main description. Then "About The Team" section: "We are a diverse group of engineers committed to revolutionizing data center design. Our team values creativity, sustainability, and continuous learning. We support each other's growth while working on projects that impact millions of customers worldwide. Our inclusive environment encourages sharing ideas and celebrating collective achievements." That could be part of About the role or maybe a separate section? There's no predefined heading for About The Team; we could incorporate into About the role as another paragraph. Then there are sections like "*Why AWS*", "*Diverse Experiences*", "*Work/Life Balance*", "*Inclusive Team Culture*", "*Mentorship and Career Growth*". Those are basically boilerplate but they contain substantive info about culture. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections might be considered boilerplate but they contain info about culture, benefits, etc. However they are formatted with asterisks and seem like standard AWS blurb. The instruction says to remove boilerplate; but also says preserve ALL substantive information; do NOT invent or summarize away detail. The sections like *Why AWS* etc are likely considered boilerplate but they contain substantive info about AWS. However they are generic across many postings. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove culture blurbs. But they might be considered boilerplate. However they are not EEO or legal; they are about culture. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we can include a short paragraph about AWS culture under About the role or Benefits? But we already have Benefits and Pay. The culture bl

Similar jobs