Site Engineer I
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: "Your role" (description), "What You’ll Do" (responsibilities), "What You’ll Need" (requirements/qualifications/skills), "A Bit About Us" (maybe not needed), "Operations" (maybe not needed), "What We Can Offer You" (maybe benefits?), "Training and Development", "Health and Safety", "Our Compensation Philosophy" (pay), "Benefits". Also "Compensation range: $39.50- $40.76 perhour." That's pay. Benefits listed.
We need to avoid repeating job title as heading. No Job ID. Remove boilerplate like EEO etc (none). Remove navigation/legal etc. Remove duplicated lines.
We need to preserve all substantive info. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role (maybe from "Your role" paragraph). Responsibilities (from "What You’ll Do" bullet list). Requirements/Qualifications/Skills (from "What You’ll Need" list). Benefits (from Benefits paragraph). Pay (from compensation range). Possibly Schedule? Not present. So omit Schedule.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We need to include all substantive info: The "Your role" paragraph: "The Site Engineer I position is a contributing member to the site level Data Center Operations team assigned to one or more of our data center properties reporting directly to the Manager Engineering Operations. The Site Engineer I will have experience in mission critical infrastructure, including Generators, UPS Systems, HVAC Systems, Fire/Life Safety Systems, BMS Systems, and CMMS systems. It is expected that the Site Engineer I candidate has expertise in either electrical work or mechanical work and it would be expected that he/she would be competent in the area of non expertise. The responsibilities of the Engineer-I are: to contribute to the daily site operation, including creation and modification of site operating procedures, contribute to creation of change management tickets, creation of timely incident reporting, site maintenance and repairs/inspections to help ensure Digital Realty’s data center operations achieve the highest level of availability."
We could combine that into About the role.
Responsibilities: The "What You’ll Do" section is a long list of items. We need to turn each bullet into
- . The text includes many sentences separated by periods. We need to parse into list items. Probably each sentence starting with capital letter after a period is a separate duty. Let's extract:
"Gain a complete understanding of the following DLR and site related items:" then list:
- Facility layout and operation of MEP systems and the ability to illustrate site specific system one-lines with good accuracy.
- Equipment nomenclature standards and equipment locations
- Facility drawings and equipment specifications
- Equipment sequence of operations (SOO’s), standard operating procedures (SOP’s), and emergency operating procedures (EOP’s).
- Customer SLA’s and engineering specific lease obligations critical to data center operations.
- Facility top 20 EOP’s.
- BMS alarm functionality, alarm escalation/acknowledgement, and ability to extract data and trends
- DLR event management, event escalation, and incident reporting procedures
- Computerized Maintenance Management System (CMMS), including the ability to create, edit, implement, and close change management work orders.
- Create/edit/resolve/close incident reports following a site incident
- Maintenance and Operations Standards
- Digital Realty’s Environmental and Occupational Health and Safety standards
- Gain a complete understanding of all aspects of data center operations including the operation, maintenance and repair of all mission critical equipment and systems supporting a 24x7 data center operation to achieve 100% uptime and 100% compliance with all customer SLAs.
- Supervision of construction activity and installations as required.
- Ability to be the executor in the site specific change management processes including the creation of Method of Procedures (MOPs) for low risk preventative maintenance and repairs as well as the oversight of those maintenances as they are carried out.
- Ability to effectively troubleshoot site mechanical and electrical systems.
- Ability to respond to unplanned events without immediate supervision.
- Ability to efficiently complete rounds/inspections and to detect anomalies during those rounds.
- Develop or improve SOPs for site specific equipment.
- Gain a good understanding and knowledge of the local customers business and datacenter operation.
- Support various accreditation initiatives, including, but not limited to, SSAE16, SOC2, ISO 27001, etc. as may be required by Digital Realty.
- Complete DLR Critical Awareness Training
We need to ensure each is a
- . Also there may be some duplication like "Gain a complete understanding of the following DLR and site related items:" is a heading; we can treat that as intro
then list.
Now Requirements/Qualifications/Skills: "What You’ll Need" list:
- At least 1 year of experience in mission critical facilities operating / engineering or equivalent equipment experience including assets associated with mission critical engineering relevant to the specific site. (UPS, HVAC, generators, fire/life safety systems).
- Hands-on electrical or mechanical skill and competence in the area of non-expertise (for example, electrical expertise with mechanical competence, or vice-versa).
- Strong knowledge of various UPS Systems and architectures.
- Strong knowledge of various cooling systems and architectures.
- Strong understanding of infrastructure redundancy configurations and equipment and their risks (N+1, 2N, ATS/ STS, Failover Scenarios)
- Strong knowledge of energy efficiency principals.
- Strong interpersonal, presentation and communication skills.
- Ability to respond effectively, verbally in writing to sensitive issues, complex inquiries or complaints.
- Detail Oriented with strong organizational skills
- Proficiency in Microsoft Word, Excel and Outlook and familiarity with Microsoft Project, Adobe Acrobat, Visio or AutoCad
- Basic understanding of emergency situations and escalation processes.
- Strong understanding of Computerized Maintenance Management Systems (CMMS), Data Center Infrastructure Management (DCIM), and power metering systems
- Lift and handle up to 50 pounds
- Bend, stoop, and stretch as required for placement and retrieval of network devices, materials, or equipment
- Work under a raised data center floor
- Climb ladders (up to 16 feet) to reach plenum spaces
We could split into Requirements and Skills sections, but the instruction says prefer few substantive sections over many thin ones. Could combine into one "Requirements" section that includes experience, knowledge, skills, physical demands. Or we could have "Qualifications" and "Skills". But to keep few sections, maybe one "Requirements" covering all.
Benefits: from "Benefits:" paragraph: "Benefits: For this role, Benefits include medical, dental, vision, life and AD&D insurance, 401k match, disability benefits, wellness and education benefits, employee stock purchase plan, paid time off, holidays, and more."
We can make a
- list of each benefit.
Pay: from "Compensation range: $39.50- $40.76 perhour." We'll put in a
maybe under
Pay
.
Schedule: not present, omit.
We also have "Training and Development", "Health and Safety", "Our Compensation Philosophy", "What We Can Offer You", "A Bit About Us", "Operations". These may be considered boilerplate or not specific to the role? They contain some substantive info but maybe not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all substantive info. However, many of those sections are generic company description; they might be considered boilerplate but they are still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections are not those. They are about company culture, training, health and safety, compensation philosophy. They might be considered relevant to the job posting. But we have limited sections headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add arbitrary headings like "Training and Development". So we need to incorporate that info into existing sections if possible, or maybe we can create additional sections only if they have real specific content and we have a heading from the allowed list? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but likely we should only use those headings. It also says: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can only use those headings. So we need to fit all substantive info under those headings.
Thus we need to distribute content: About the role (intro), Responsibilities (duties), Requirements (experience, knowledge, skills), Qualifications (maybe education/certifications? none), Skills (maybe we can split knowledge vs skills), Benefits, Pay. Since we have limited headings, we can combine Qualifications and Skills into Requirements or separate if we have content. But we have no explicit qualifications like degree; we could omit Qualifications section if no specific content. Similarly Skills we could embed in Requirements.
Thus we will output:
About the role
... (the "Your role" paragraph)
Responsibilities
- ... each duty
Requirements
- ... each requirement/skill/physical demand
Benefits
- ... each benefit
Pay
Compensation range: $39.50- $40.76 per hour.
We need to ensure we didn't miss any substantive info like "Training and Development", "Health and Safety", "Our Compensation Philosophy", "What We Can Offer You", "A Bit About Us", "Operations". Those are generic company info; maybe they are considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those are not those. However they might be considered "boilerplate" as they are generic company description not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit them, we are summarizing away detail. But maybe they are considered not substantive for the role? The instruction is ambiguous. However typical job posting reformatting tasks often discard generic "About us" sections. The instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not explicitly say to remove "About us". But later: "Prefer a few substantive sections over many thin ones." So we could include a short paragraph under About the role that includes some of that info? But About the role is supposed to be about the role, not company. However we could incorporate some of that into About the role if we want to preserve. But the heading "About the role" is defined; we could put company overview there? Might be odd.
Better to follow the instruction strictly: only use those headings; we can put any relevant info under them. The "About the role" could include a brief sentence about the company if we want, but the original "Your role" paragraph is about the role. The "A Bit About Us", "Operations", "What We Can Offer You", "Training and Development", "Health and Safety", "Our Compensation Philosophy"
for prose. We need to decide sections: About the role (maybe from "Your role" paragraph). Responsibilities (from "What You’ll Do" bullet list). Requirements/Qualifications/Skills (from "What You’ll Need" list). Benefits (from Benefits paragraph). Pay (from compensation range). Possibly Schedule? Not present. So omit Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to include all substantive info: The "Your role" paragraph: "The Site Engineer I position is a contributing member to the site level Data Center Operations team assigned to one or more of our data center properties reporting directly to the Manager Engineering Operations. The Site Engineer I will have experience in mission critical infrastructure, including Generators, UPS Systems, HVAC Systems, Fire/Life Safety Systems, BMS Systems, and CMMS systems. It is expected that the Site Engineer I candidate has expertise in either electrical work or mechanical work and it would be expected that he/she would be competent in the area of non expertise. The responsibilities of the Engineer-I are: to contribute to the daily site operation, including creation and modification of site operating procedures, contribute to creation of change management tickets, creation of timely incident reporting, site maintenance and repairs/inspections to help ensure Digital Realty’s data center operations achieve the highest level of availability." We could combine that into About the role. Responsibilities: The "What You’ll Do" section is a long list of items. We need to turn each bullet into
then list. Now Requirements/Qualifications/Skills: "What You’ll Need" list: - At least 1 year of experience in mission critical facilities operating / engineering or equivalent equipment experience including assets associated with mission critical engineering relevant to the specific site. (UPS, HVAC, generators, fire/life safety systems). - Hands-on electrical or mechanical skill and competence in the area of non-expertise (for example, electrical expertise with mechanical competence, or vice-versa). - Strong knowledge of various UPS Systems and architectures. - Strong knowledge of various cooling systems and architectures. - Strong understanding of infrastructure redundancy configurations and equipment and their risks (N+1, 2N, ATS/ STS, Failover Scenarios) - Strong knowledge of energy efficiency principals. - Strong interpersonal, presentation and communication skills. - Ability to respond effectively, verbally in writing to sensitive issues, complex inquiries or complaints. - Detail Oriented with strong organizational skills - Proficiency in Microsoft Word, Excel and Outlook and familiarity with Microsoft Project, Adobe Acrobat, Visio or AutoCad - Basic understanding of emergency situations and escalation processes. - Strong understanding of Computerized Maintenance Management Systems (CMMS), Data Center Infrastructure Management (DCIM), and power metering systems - Lift and handle up to 50 pounds - Bend, stoop, and stretch as required for placement and retrieval of network devices, materials, or equipment - Work under a raised data center floor - Climb ladders (up to 16 feet) to reach plenum spaces We could split into Requirements and Skills sections, but the instruction says prefer few substantive sections over many thin ones. Could combine into one "Requirements" section that includes experience, knowledge, skills, physical demands. Or we could have "Qualifications" and "Skills". But to keep few sections, maybe one "Requirements" covering all. Benefits: from "Benefits:" paragraph: "Benefits: For this role, Benefits include medical, dental, vision, life and AD&D insurance, 401k match, disability benefits, wellness and education benefits, employee stock purchase plan, paid time off, holidays, and more." We can make a
- list of each benefit.
Pay: from "Compensation range: $39.50- $40.76 perhour." We'll put in a
maybe under
Pay
. Schedule: not present, omit. We also have "Training and Development", "Health and Safety", "Our Compensation Philosophy", "What We Can Offer You", "A Bit About Us", "Operations". These may be considered boilerplate or not specific to the role? They contain some substantive info but maybe not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all substantive info. However, many of those sections are generic company description; they might be considered boilerplate but they are still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections are not those. They are about company culture, training, health and safety, compensation philosophy. They might be considered relevant to the job posting. But we have limited sections headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add arbitrary headings like "Training and Development". So we need to incorporate that info into existing sections if possible, or maybe we can create additional sections only if they have real specific content and we have a heading from the allowed list? The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but likely we should only use those headings. It also says: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can only use those headings. So we need to fit all substantive info under those headings. Thus we need to distribute content: About the role (intro), Responsibilities (duties), Requirements (experience, knowledge, skills), Qualifications (maybe education/certifications? none), Skills (maybe we can split knowledge vs skills), Benefits, Pay. Since we have limited headings, we can combine Qualifications and Skills into Requirements or separate if we have content. But we have no explicit qualifications like degree; we could omit Qualifications section if no specific content. Similarly Skills we could embed in Requirements. Thus we will output:
About the role
... (the "Your role" paragraph)
Responsibilities
- ... each duty
Requirements
- ... each requirement/skill/physical demand
Benefits
- ... each benefit
Pay
Compensation range: $39.50- $40.76 per hour.
We need to ensure we didn't miss any substantive info like "Training and Development", "Health and Safety", "Our Compensation Philosophy", "What We Can Offer You", "A Bit About Us", "Operations". Those are generic company info; maybe they are considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those are not those. However they might be considered "boilerplate" as they are generic company description not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit them, we are summarizing away detail. But maybe they are considered not substantive for the role? The instruction is ambiguous. However typical job posting reformatting tasks often discard generic "About us" sections. The instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not explicitly say to remove "About us". But later: "Prefer a few substantive sections over many thin ones." So we could include a short paragraph under About the role that includes some of that info? But About the role is supposed to be about the role, not company. However we could incorporate some of that into About the role if we want to preserve. But the heading "About the role" is defined; we could put company overview there? Might be odd. Better to follow the instruction strictly: only use those headings; we can put any relevant info under them. The "About the role" could include a brief sentence about the company if we want, but the original "Your role" paragraph is about the role. The "A Bit About Us", "Operations", "What We Can Offer You", "Training and Development", "Health and Safety", "Our Compensation Philosophy"