Data Center Technician

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "Who We Are" (company description) but not required as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. The posting includes "Who We Are" (company overview) maybe not needed as a heading; but we could treat as "About the role"? Actually "About the role" is typical heading for role description. The posting includes "The Job" description. Could map that to "About the role". Then "Responsibilities" heading present. Then "Qualifications" heading present. There's also "Reports To", "Location", "Travel", "Work Environment", "Physical Demands", "Position Type/ Expected Hours of Work", "Supervisory Experience". Those could be considered under "Requirements" or "Skills"? The instruction: Use headings only for those listed; we can combine multiple items under a heading. For example, under "Requirements" we could put the qualifications like experience, technical knowledge, etc. Under "Skills" we could put communication, math, driver's license, etc. Under "Benefits", "Pay", "Schedule": we need to see if posting includes any. It mentions "Willingness to work nights is required." That's schedule info. Also "Position Type/ Expected Hours of Work: This is a full-time, onsite position." That's schedule. So we can include a Schedule section with that info. Pay: not mentioned. Benefits: not mentioned. So we omit Benefits and Pay headings. We must not repeat job title as heading. The job title is Data Center Technician; we should not put that as heading. We must not include Job ID/requisition numbers. We must remove boilerplate like EEO etc. Not present. We need to preserve all substantive information. So we need to include company description? Possibly under "About the role"? But "About the role" is about the role, not company. However we could include a brief "About the role" paragraph summarizing the role description (The Job). Then we could also include a separate section maybe not listed? But instruction says use those headings; we can also include other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those. Thus we need to map: - About the role: description of the role (The Job paragraph). Could also include "Who We Are"? Might be considered company overview but not required. Might be okay to include as part of About the role? But better to keep it separate? The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should follow the pattern. I'd include About the role with the role description (The Job). Then Responsibilities with the list. Then Qualifications with the qualifications list (education, experience, technical knowledge, etc.). Then Skills with skills like communication, math, driver's license, networking, report writing, etc. Then Schedule with full-time, onsite, willingness to work nights, minimal travel. We must not invent or summarize away detail. Must preserve all substantive information. So we need to include each piece of info somewhere. Let's extract all substantive info: Company description (Who We Are) - maybe not required but it's substantive. Could we include it under About the role? Might be okay to include a brief paragraph about the company as part of About the role? But it's not about the role. However we could add a separate heading like "About Core Scientific" but not in list. Might be considered extra heading; risk of being penalized? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings if needed, but better to stick to those. However we must preserve all substantive information; if we omit company description, we lose info. So we need to include it somewhere. Could we incorporate it into About the role as a preamble? Eg: About the role: Core Scientific is ... The Data Center Technician will... That would preserve company info while still under About the role heading. That seems acceptable. Thus About the role section will contain both company overview and role description. Now Responsibilities: list all bullet points from Responsibilities section. Qualifications: list education, experience, technical knowledge, etc. Also includes "Reports To", "Location", "Travel", "Work Environment", "Physical Demands", "Position Type/ Expected Hours of Work", "Supervisory Experience". Some of those could be considered qualifications or additional info. We could put them under Qualifications as well, but maybe better to put under Requirements? The instruction includes Requirements heading. Could use Requirements for things like experience, education, technical knowledge, etc. And Qualifications for preferred certifications, etc. But we have both Required and Preferred. Let's parse: Qualifications section in posting: - A high school diploma/GED is required. - A degree in a related field or a technical certification is preferred. - A minimum of 3 years of experience working in a data center environment is required. - Technical knowledge of systems such as electrical distribution, emergency/standby power, HVAC, fire protection, UPS systems, floor PDUs, rack PDUs, CRAH units, and monitoring and control systems (BMS/CMMS) is required. - Proficiency in algebraic math computations is required. - Must have a valid driver's license. - Understanding networking hardware and software, including routers, switches, and protocols, is preferred. - Ability to write reports and understand schematic and architectural drawings is required. - Strong communication skills required. - Must be able to understand, follow, and communicate verbal and written instructions effectively in English. - Knowledge of Microsoft Office Suite and other standard software programs is required. Then after that: Reports To Data Center Manager, Location On-Site, Travel Minimal travel may be required as needed., Work Environment..., Physical Demands..., Position Type/ Expected Hours of Work..., Supervisory Experience (Yes Or No) No. Thus we could treat "Reports To", "Location", "Travel", "Work Environment", "Physical Demands", "Position Type/ Expected Hours of Work", "Supervisory Experience" as additional details maybe under Requirements or a separate section like "Additional Information". But we only have headings list; we could put them under Requirements (makes sense) or under Qualifications. Let's decide: Use Requirements for mandatory items (education, experience, technical knowledge, driver's license, math, communication, software, etc.) and Qualifications for preferred items (degree/certification, networking knowledge). But the posting lumps them together; we can still split. Better: Use Requirements heading for all required items (including education, experience, technical knowledge, math, driver's license, communication, software, ability to write reports, understand instructions). Use Qualifications heading for preferred items (degree/certification, networking knowledge). Then we can put Reports To, Location, Travel, Work Environment, Physical Demands, Position Type/Expected Hours, Supervisory Experience under a separate heading maybe "Details"? Not in list. Could we incorporate them under Requirements as well? They are not exactly requirements but job details. Could be under Requirements as well; it's okay. Alternatively, we could create a section "Details" but not in list; risk. Safer to put them under Requirements as extra bullets. Thus:

About the role

Core Scientific is a leading provider of infrastructure for high-performance compute in North America... (the Who We Are paragraph) The Data Center Technician will monitor and manage power, cooling capacity, and environmental conditions in the data center. Act as a first responder to incidents that arise within the data center envelope. This position will manage workflow for planned and unplanned data center work to ensure timely completion and ensure processes adhere to federal and local safety laws and policies.

Then Responsibilities:

Responsibilities

• ... each bullet

Then Requirements:

Requirements

• High school diploma/GED required.
• Minimum of 3 years of experience working in a data center environment required.
• Technical knowledge of systems such as electrical distribution, emergency/standby power, HVAC, fire protection, UPS systems, floor PDUs, rack PDUs, CRAH units, and monitoring and control systems (BMS/CMMS) required.
• Proficiency in algebraic math computations required.
• Valid driver's license required.
• Ability to write reports and understand schematic and architectural drawings required.
• Strong communication skills required.
• Must be able to understand, follow, and communicate verbal and written instructions effectively in English.
• Knowledge of Microsoft Office Suite and other standard software programs required.
• Reports to Data Center Manager.
• On-site location.
• Minimal travel may be required as needed.
• Work environment: data center environment, routine use of standard data center equipment (laptop computers, smartphones, voltmeters, scissor lifts, forklifts, ladders, screwdrivers, and other hand tools); exposure to hot and cold environments.
• Physical demands: frequently required to sit, stand, walk, use hands, and lift up to 50 pounds.
• Position type: full-time, onsite.
• Willingness to work nights required.
• Supervisory experience: No.

Then Qualifications (preferred):

Qualifications

• Degree in a related field or technical certification preferred.
• Understanding of networking hardware and software, including routers, switches, and protocols, preferred.

Then Skills: maybe we could include communication, math, driver's license etc but we already placed them under Requirements. Could still have Skills heading for things like communication, math, etc. But we might duplicate. Better to follow instruction: Use Skills heading for skills like communication, math, etc. But we already placed them under Requirements. Could move them to Skills and keep Requirements for experience/education. Let's think. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can assign: - About the role: company + role description. - Responsibilities: list. - Requirements: education, experience, technical knowledge, driver's license, ability to write reports, understand instructions, knowledge of MS Office, etc. (the required hard qualifications). - Qualifications: preferred items (degree/certification, networking knowledge). - Skills: communication skills, math proficiency, ability to follow instructions, etc. But some overlap. We need to avoid duplication. Let's decide: Requirements: mandatory items that are not skills? Actually many are skills. But we can separate: Requirements = education, experience, technical knowledge, driver's license, ability to write reports, understand instructions, MS Office knowledge. Skills = communication, math proficiency, ability to follow instructions (though that's also ability). But we can keep simple: Requirements = education, experience, technical knowledge, driver's license, ability to write reports, understand instructions, MS Office. Qualifications = preferred degree/cert, networking knowledge. Skills = communication skills, math proficiency, ability to understand/follow/communicate instructions (maybe redundant). Actually ability to understand/follow/communicate instructions is a skill; we could put under Skills. Let's list all items from posting: