Assistant Critical Operations Manager
for section headings: 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.
We need to parse the posting.
Content:
Company description: "The Company STACK INFRASTRUCTURE (STACK) provides digital infrastructure..." This is about the company. Could be "About the role"? Actually "About the role" is typical heading for role description. The posting includes "The Position STACK is looking for an Assistant Critical Operations Manager (ACOM) to support a local data center campus." That's about the role. Also there is description of responsibilities etc.
We need sections: About the role (maybe a paragraph summarizing role). Responsibilities (list). Requirements (maybe qualifications). Qualifications (maybe must-have qualifications). Skills (maybe specific skills). Benefits (list). Pay (compensation range). Schedule (maybe travel? Not schedule). There's no explicit schedule but maybe "Willingness to work outside normal business hours, including weekends, holidays, and on-call support" could be schedule. But schedule section only if posting actually states schedule. It does mention willingness to work outside normal business hours, etc. That's schedule info. So we can include Schedule.
We must not include placeholder text like "commensurate with experience". Not present.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to include details from posting.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must not include duplicated lines, cookie/navigation/legal/EEO etc. Remove EEO paragraph, note to external agencies, etc.
We need to keep location, travel, benefits, must be eligible to work in US, must pass background/drug screening. Those could be part of Requirements or Qualifications. Probably under Requirements.
We need to decide sections:
- About the role: paragraph describing the position: "STACK is looking for an Assistant Critical Operations Manager (ACOM) to support a local data center campus. As a leader in STACK’s Critical Operations team, the ACOM must possess an expert level of knowledge and will be responsible for assisting the Critical Operations Manager in maintaining the mechanical, electrical, fire life safety, base building, and other various internal data center systems. The ACOM will also be focused on the implementation of programs related to Safety, Team, Availability, Communication, and Knowledge. The Assistant Critical Operations Manager will report to the Critical Operations Manager. The ACOM is responsible for the implementation of the Data Center Operations Program at their site and is responsible for employee training and ensuring all staff is adequately qualified to perform their duties. Holding regular team meetings and individual 1:1 sessions is required. The ACOM will assist the Critical Operations Manager in developing and maintaining CAPEX and OPEX budgets at the site level. They will also be responsible for project execution and management including developing scopes, obtaining proposals, creating purchase requisitions, and ensuring invoices are routed properly."
That seems like responsibilities though. But we can put that as About the role (overview). Then Responsibilities list the bullet points from "Responsibilities Include But Are Not Limited To". Those are many bullet points.
We need to ensure we don't duplicate content. The About the role paragraph may overlap with responsibilities list; but we must preserve all substantive info. Could we keep both? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep everything. If we put overview paragraph and also list responsibilities, we may be duplicating some info but that's okay as long as we don't omit. However we should avoid redundant duplication? Not explicitly forbidden, but better to avoid duplication if possible. However we need to keep all details; we can put overview in About the role and then responsibilities list includes many specifics; the overview may be covered partially by list but it's okay.
Alternatively we could make About the role just a short paragraph: "STACK is looking for an Assistant Critical Operations Manager (ACOM) to support a local data center campus." Then responsibilities list includes all duties. That would preserve all info because responsibilities list includes the details. The overview paragraph may be redundant but we can keep minimal.
We need to include Requirements: location, travel, eligibility, background/drug screening. Also maybe "Must be eligible to work in the United States", "Must pass comprehensive background and drug screening". Also "Travel: None or less than 5%". Also location: San Jose, CA.
Qualifications: Must-have Qualifications list: high school diploma or equivalent, 4-5 years experience in data center or related mission critical operations role, knowledge of data center and telecommunications industries, experience with MS Office and database software, 3-5 years experience managing facility preventative maintenance programs, 3-5 years experience in vendor and project management, ability to handle multiple tasks and perform well in stressful situations, expert understanding of electrical and mechanical systems (list), expert knowledge of NFPA70e, NFPA72, NFPA25, and fire life safety compliance standards, experience in data center trending and analysis with ability to learn PC-based monitoring systems, proficiency in data center commissioning standards, ability to perform physical tasks including standing, walking, climbing, and lifting up to 25 pounds, willingness to work outside normal business hours, including weekends, holidays, and on-call support, comfortable working in a high-stress, fast-paced environment with shifting priorities.
Skills: maybe we can extract from qualifications: knowledge of systems, etc. But we already have qualifications. The instruction says use sections only when posting has real specific content. We have qualifications content. Could combine qualifications and skills? But we have separate headings: Qualifications, Skills. We could put qualifications under "Requirements" (like must-have qualifications) and skills under "Skills" (like expert understanding, etc). However the posting lumps them together as "Must-have Qualifications". Might be better to treat that as "Qualifications". Then we could have a "Skills" section for things like "Expert understanding of electrical and mechanical systems", "Expert knowledge of NFPA...", "Experience in data center trending and analysis", "Proficiency in data center commissioning standards", "Ability to perform physical tasks", "Willingness to work outside normal business hours", "Comfortable working in high-stress...". But those are also qualifications. Might be splitting hairs. Safer to have one section "Qualifications" containing all must-have qualifications. Then we could omit Skills section if no distinct skills beyond qualifications. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can combine.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Check each:
- About the role: we have a paragraph.
- Responsibilities: list from "Responsibilities Include But Are Not Limited To". We'll output each as
- .
- Requirements: location, travel, eligibility, background/drug screening. Possibly also "Must be eligible to work in the United States", "Must pass comprehensive background and drug screening". Also maybe "Location: San Jose, CA", "Travel: None or less than 5%". Also maybe "Job duties, roles, and responsibilities are subject to change over time." That's a generic statement; could be included but it's not specific? It's a statement about change; we could include but it's not a requirement. Might be considered boilerplate? It's not EEO but it's a generic disclaimer. Might be okay to keep but it's not a requirement. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is not exactly boilerplate but it's a generic statement. Might be safe to keep in Requirements? It's not a requirement but it's a note. Could be placed in About the role? Might be considered filler. Safer to omit.
- Qualifications: Must-have Qualifications list.
- Benefits: list: Healthcare, Dental Care, Vision Insurance, Life Insurance, Paid Time Off, and Paid Leave Programs. Also later in "WHY STACK?" they mention competitive compensation package with strong benefits, including medical, dental, and vision insurance, a 401K program, flexible spending accounts – even a cell phone subsidy. Also fun events etc. But we should only include benefits that are explicitly stated. The posting lists "Benefits: Healthcare, Dental Care, Vision Insurance, Life Insurance, Paid Time Off, and Paid Leave Programs". Then later "WHY STACK? We offer a competitive compensation package with strong benefits, including medical, dental, and vision insurance, a 401K program, flexible spending accounts – even a cell phone subsidy." That's additional benefits. We should include all substantive benefits: Healthcare, Dental Care, Vision Insurance, Life Insurance, Paid Time Off, Paid Leave Programs, 401K program, flexible spending accounts, cell phone subsidy. Also maybe "Fun is part of our DNA, with events, game nights, happy hours, and barbecues." That's more culture, not benefit. Could be omitted.
- Pay: Compensation Range $73.00 - $76.50. Likely per hour? Not specified but we keep as is.
- Schedule: Willingness to work outside normal business hours, including weekends, holidays, and on-call support. Also maybe travel less than 5% (but that's travel). So schedule section: "Willingness to work outside normal business hours, including weekends, holidays, and on-call support."
We must not include placeholder text like "commensurate with experience". Not present.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
Location: San Jose, CA
Travel: None or less than 5%
Must be eligible to work in the United States
Must pass comprehensive background and drug screening
Qualifications
- High school diploma or equivalent
- Minimum of 4–5 years' experience in a data center or other related mission critical operations role
- Knowledge of data center (hyperscale, enterprise, and colocation) and telecommunications industries
- Experience working with Microsoft Office applications and database software
- 3–5 years' experience managing facility preventative maintenance programs
- 3–5 years' experience in vendor and project management
- Ability to handle multiple tasks and perform well in stressful situations
- Expert understanding of electrical and mechanical systems used in a data center environment (e.g., UPS, Transformers, PDUs, RPPs, Chillers, CRAH, CRAC, STS, ATS, Pre-action systems)
- Expert knowledge of NFPA70e, NFPA72, NFPA25, and fire life safety compliance standards
- Experience in data center trending and analysis with ability to learn PC-based monitoring systems
- Proficiency in data center commissioning standards
- Ability to perform physical tasks including standing, walking, climbing, and lifting up to 25 pounds
- Willingness to work outside normal business hours, including weekends, holidays, and on-call support
- Comfortable working in a high-stress, fast-paced environment with shifting priorities
Benefits
- Healthcare
- Dental Care
- Vision Insurance
- Life Insurance
- Paid Time Off
- Paid Leave Programs
- 401K program
- Flexible spending accounts
- Cell phone subsidy
Pay
for prose. We must not include duplicated lines, cookie/navigation/legal/EEO etc. Remove EEO paragraph, note to external agencies, etc. We need to keep location, travel, benefits, must be eligible to work in US, must pass background/drug screening. Those could be part of Requirements or Qualifications. Probably under Requirements. We need to decide sections: - About the role: paragraph describing the position: "STACK is looking for an Assistant Critical Operations Manager (ACOM) to support a local data center campus. As a leader in STACK’s Critical Operations team, the ACOM must possess an expert level of knowledge and will be responsible for assisting the Critical Operations Manager in maintaining the mechanical, electrical, fire life safety, base building, and other various internal data center systems. The ACOM will also be focused on the implementation of programs related to Safety, Team, Availability, Communication, and Knowledge. The Assistant Critical Operations Manager will report to the Critical Operations Manager. The ACOM is responsible for the implementation of the Data Center Operations Program at their site and is responsible for employee training and ensuring all staff is adequately qualified to perform their duties. Holding regular team meetings and individual 1:1 sessions is required. The ACOM will assist the Critical Operations Manager in developing and maintaining CAPEX and OPEX budgets at the site level. They will also be responsible for project execution and management including developing scopes, obtaining proposals, creating purchase requisitions, and ensuring invoices are routed properly." That seems like responsibilities though. But we can put that as About the role (overview). Then Responsibilities list the bullet points from "Responsibilities Include But Are Not Limited To". Those are many bullet points. We need to ensure we don't duplicate content. The About the role paragraph may overlap with responsibilities list; but we must preserve all substantive info. Could we keep both? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep everything. If we put overview paragraph and also list responsibilities, we may be duplicating some info but that's okay as long as we don't omit. However we should avoid redundant duplication? Not explicitly forbidden, but better to avoid duplication if possible. However we need to keep all details; we can put overview in About the role and then responsibilities list includes many specifics; the overview may be covered partially by list but it's okay. Alternatively we could make About the role just a short paragraph: "STACK is looking for an Assistant Critical Operations Manager (ACOM) to support a local data center campus." Then responsibilities list includes all duties. That would preserve all info because responsibilities list includes the details. The overview paragraph may be redundant but we can keep minimal. We need to include Requirements: location, travel, eligibility, background/drug screening. Also maybe "Must be eligible to work in the United States", "Must pass comprehensive background and drug screening". Also "Travel: None or less than 5%". Also location: San Jose, CA. Qualifications: Must-have Qualifications list: high school diploma or equivalent, 4-5 years experience in data center or related mission critical operations role, knowledge of data center and telecommunications industries, experience with MS Office and database software, 3-5 years experience managing facility preventative maintenance programs, 3-5 years experience in vendor and project management, ability to handle multiple tasks and perform well in stressful situations, expert understanding of electrical and mechanical systems (list), expert knowledge of NFPA70e, NFPA72, NFPA25, and fire life safety compliance standards, experience in data center trending and analysis with ability to learn PC-based monitoring systems, proficiency in data center commissioning standards, ability to perform physical tasks including standing, walking, climbing, and lifting up to 25 pounds, willingness to work outside normal business hours, including weekends, holidays, and on-call support, comfortable working in a high-stress, fast-paced environment with shifting priorities. Skills: maybe we can extract from qualifications: knowledge of systems, etc. But we already have qualifications. The instruction says use sections only when posting has real specific content. We have qualifications content. Could combine qualifications and skills? But we have separate headings: Qualifications, Skills. We could put qualifications under "Requirements" (like must-have qualifications) and skills under "Skills" (like expert understanding, etc). However the posting lumps them together as "Must-have Qualifications". Might be better to treat that as "Qualifications". Then we could have a "Skills" section for things like "Expert understanding of electrical and mechanical systems", "Expert knowledge of NFPA...", "Experience in data center trending and analysis", "Proficiency in data center commissioning standards", "Ability to perform physical tasks", "Willingness to work outside normal business hours", "Comfortable working in high-stress...". But those are also qualifications. Might be splitting hairs. Safer to have one section "Qualifications" containing all must-have qualifications. Then we could omit Skills section if no distinct skills beyond qualifications. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can combine. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check each: - About the role: we have a paragraph. - Responsibilities: list from "Responsibilities Include But Are Not Limited To". We'll output each as
About the role
...
Responsibilities
- ... ...
Requirements
Location: San Jose, CA
Travel: None or less than 5%
Must be eligible to work in the United States
Must pass comprehensive background and drug screening
Qualifications
- High school diploma or equivalent
- Minimum of 4–5 years' experience in a data center or other related mission critical operations role
- Knowledge of data center (hyperscale, enterprise, and colocation) and telecommunications industries
- Experience working with Microsoft Office applications and database software
- 3–5 years' experience managing facility preventative maintenance programs
- 3–5 years' experience in vendor and project management
- Ability to handle multiple tasks and perform well in stressful situations
- Expert understanding of electrical and mechanical systems used in a data center environment (e.g., UPS, Transformers, PDUs, RPPs, Chillers, CRAH, CRAC, STS, ATS, Pre-action systems)
- Expert knowledge of NFPA70e, NFPA72, NFPA25, and fire life safety compliance standards
- Experience in data center trending and analysis with ability to learn PC-based monitoring systems
- Proficiency in data center commissioning standards
- Ability to perform physical tasks including standing, walking, climbing, and lifting up to 25 pounds
- Willingness to work outside normal business hours, including weekends, holidays, and on-call support
- Comfortable working in a high-stress, fast-paced environment with shifting priorities
Benefits
- Healthcare
- Dental Care
- Vision Insurance
- Life Insurance
- Paid Time Off
- Paid Leave Programs
- 401K program
- Flexible spending accounts
- Cell phone subsidy