Controls Manager, US-West, PDX

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the description. We must not repeat job title as heading. No Job ID etc. We need to include

for each section heading. We need to use

• for any list of duties/requirements/benefits. We need

  for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to include Pay section if posting actually states them. It does: "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 ..." Also location: "USA, OR, Boardman - 153,200.00 - 254,500.00 USD annually". So we have Pay and Benefits. Schedule: Not mentioned. So we should not include Schedule. We need sections: About the role (maybe from description about role?), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. We need to decide what goes where. The description includes: - Intro paragraph about Amazon, Data Center Capacity Delivery team looking for Controls Manager. - "The ideal candidate will have experience managing a team of highly technically skilled individuals. The candidate will possess industrial Controls System experience, project management, mechanical, electrical or technology background that enables him/her to undertake the challenges of sophisticated controls platforms and a demonstrated ability to think broadly and strategically in aligning building controls and automation with the larger objectives of the business." - "Key job responsibilities" then a long list of bullet-like sentences. - "A day in the life" paragraph. - "About The Team" paragraph. - "Why AWS" paragraph. - "Diverse Experiences", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth" - these are generic boilerplate? Might be considered EEO/equal-opportunity? They are more about culture but could be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections like Diverse Experiences, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth might be considered generic corporate culture boilerplate. However they are not exactly EEO but could be considered fluff. The instruction says "Prefer a few substantive sections over many thin ones." So we might combine culture info into About the role or About the Team? But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop those if they are substantive. However they are generic statements that could be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Those sections are not exactly EEO but they are about diversity, work-life balance, inclusive culture, mentorship. Might be considered part of company culture but could be considered boilerplate. However they are not duplicated lines; they are specific to Amazon's culture. The instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". It doesn't explicitly say remove culture sections. But they might be considered generic fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. If we remove them, we might be summarizing away detail. But they are not specific to the job; they are generic company statements. The instruction says "Prefer a few substantive sections over many thin ones." So we could incorporate them into a single "About Amazon/AWS" section or "About the Team". But we already have "About The Team" which is substantive about AWS Infrastructure Services. That is specific. The other culture sections could be merged into that or omitted? The instruction says do NOT invent or summarize away detail. Summarizing away detail would be to condense multiple bullet points into a generic statement. If we drop those sections entirely, we are removing detail (though it's generic). Might be considered okay? Not sure. Better to keep them but maybe combine into a single "About Amazon" section with subpoints? However we need to use headings only for sections that have real specific content. If we combine them, we still preserve the content. Let's extract substantive content: - Intro: "At Amazon, we're working to be the most customer-centric company on earth. To get there, we need exceptionally talented, bright, and driven people. If you'd like to help us build the place to find and buy anything online, this is your chance to make history. The Data Center Capacity Delivery team is looking for exceptional individuals to join our organization as a Controls Manager, responsible for the building management systems and electrical power monitoring system (BMS/EPMS) deployment and service within Amazon data centers. If you are passionate about the Customer Experience, think and act globally and have the ability to contribute to major new innovations in the area of building controls and automation this is the challenge you are looking for!" That's about the role. - Ideal candidate paragraph: "The ideal candidate will have experience managing a team of highly technically skilled individuals. The candidate will possess industrial Controls System experience, project management, mechanical, electrical or technology background that enables him/her to undertake the challenges of sophisticated controls platforms and a demonstrated ability to think broadly and strategically in aligning building controls and automation with the larger objectives of the business." That could be part of Requirements/Qualifications. - Key job responsibilities: list of responsibilities. - "A day in the life" paragraph. - "About The Team" paragraph. - "Why AWS" paragraph. - "Diverse Experiences", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth" paragraphs. - Basic Qualifications list. - Preferred Qualifications list. - Pay and Benefits info. We need to decide sections. Possible sections: - About the role (intro + ideal candidate? maybe separate) - Responsibilities (key job responsibilities + day in the life?) - About the Team (AWS Infrastructure Services description) - Why AWS (maybe part of About the Team? but could be separate) - Qualifications (Basic and Preferred) - Skills (maybe extracted from responsibilities? but we have separate Skills section; we could list skills from responsibilities and qualifications) - Benefits - Pay We must not create sections with filler like "commensurate with experience". We have actual pay range and benefits. We need to use

  • for any list of duties/requirements/benefits. Thus: - Responsibilities: list each responsibility as
  • . - Requirements: maybe split into Basic Qualifications and Preferred Qualifications as separate lists? Could combine under Requirements heading with subheadings? But we only allowed headings

    . Could have

    Requirements

    then

    Basic Qualifications:

    ... then

    Preferred Qualifications:

    ... That's okay. - Skills: maybe we can extract skills from responsibilities and qualifications: e.g., "Industrial control systems experience", "Project management", "Mechanical/Electrical/Technology background", "Strong writing skills", "Understanding of electrical diagrams, control diagrams, building operations, control circuits, industrial HVAC", "Ability to ascertain customer needs", "Ability to manage project engineering", "Ability to read and interpret specifications", "Experience developing drawings for control panels, power distribution, junction boxes", "Experience developing logic diagrams in International Automation format", "Experience performing inspects, testing, and commission", "Provide technical assistance", "Coordinate project work". Could list as
    . But we already have responsibilities list; skills may overlap. However instruction says use
    • for any list of duties/requirements/benefits. So we need to list duties under Responsibilities, requirements under Requirements, benefits under Benefits. Skills section maybe not needed if we already have responsibilities and requirements. But we could still include Skills if there is specific content. The posting does not have a separate "Skills" heading; but we can create one if we have specific skill list. However we must not invent or summarize away detail. If we create a Skills section, we need to extract skill statements from the text. That is summarizing but not inventing; we are pulling out skill phrases. That might be acceptable. However we risk creating a thin section. The instruction says prefer a few substantive sections over many thin ones. So maybe we omit Skills section and incorporate skill statements into Responsibilities and Requirements. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We also have About The Team and Why AWS; maybe combine into About the Team/AWS. We could have About the role (intro + ideal candidate), About the Team (AWS Infrastructure Services description + Why AWS + culture sections), Responsibilities, Requirements, Benefits, Pay. Let's extract content for each. **About the role**: combine intro paragraph and ideal candidate paragraph. Intro: "At Amazon, we're working to be the most customer-centric company on earth. To get there, we need exceptionally talented, bright, and driven people. If you'd like to help us build the place to find and buy anything online, this is your chance to make history. The Data Center Capacity Delivery team is looking for exceptional individuals to join our organization as a Controls Manager, responsible for the building management systems and electrical power monitoring system (BMS/EPMS) deployment and service within Amazon data centers. If you are passionate about the Customer Experience, think and act globally and have the ability to contribute to major new innovations in the area of building controls and automation this is the challenge you are looking for!" Ideal candidate: "The ideal candidate will have experience managing a team of highly technically skilled individuals. The candidate will possess industrial Controls System experience, project management, mechanical, electrical or technology background that enables him/her to undertake the challenges of sophisticated controls platforms and a demonstrated ability to think broadly and strategically in aligning building controls and automation with the larger objectives of the business." We can combine into one

      or two

      s. Use

      for prose. **About the Team**: combine "About The Team", "Why AWS", "Diverse Experiences", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth". Let's extract each. About The Team: "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." Why AWS: "Amazon Web Services (AWS) is the world's most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating, that's why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses." Diverse Experiences: "Amazon values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn't followed a traditional path, or includes alternative experiences, don't let it stop you from applying." Work/Life Balance: "We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace