Site Operations Director (San Fran)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the job description.
Key content:
- Job#: 3045008 (metadata, can be short p or drop)
- Job Description: Site Operations Director (SF)
- Location: San Francisco, California (Onsite 5 days a week)
- Duration: 12+ months
- Role Overview paragraph: "We are hiring a Site Operations Manager to lead a 24x7 operation supporting large-scale data collection and technical workflows. This role serves as the senior operational leader for the site, overseeing multiple shifts, Operations Managers, and overall site performance. You will be responsible for operational execution, client partnership, workforce planning, and leadership development while ensuring a safe, productive, and high-performing environment."
- What You'll Lead: bullet list (though not bullet but lines). Content:
- Directly managing Operations Managers and site leadership.
- Indirectly overseeing 300+ employees across multiple shifts.
- Driving consistency, accountability, and execution across a 24x7 operation.
- Ensuring alignment and continuity between shifts and leadership teams.
- Leading workforce planning, staffing strategy, and operational readiness.
- Partnering with HR, Recruiting, Engineering, Training, Facilities, and Safety teams.
- Building scalable processes that support growth and operational excellence.
- Site & Client Leadership: bullet list:
- Own overall site performance and operational strategy.
- Serve as the primary operational partner to the client.
- Lead business reviews, operational updates, and executive presentations.
- Communicate KPI performance, risks, escalations, and improvement plans.
- Balance client priorities with operational stability and workforce needs.
- Lead complex escalations and drive resolution across cross-functional teams.
- Performance, KPIs & Operational Excellence: bullet list:
- You will be accountable for productivity, quality, attendance, throughput, and workforce stability.
- Capacity planning, labor forecasting, and resource allocation.
- Monitoring operational performance and identifying improvement opportunities.
- Driving process improvements that increase efficiency, quality, and scalability.
- Standardizing processes and ensuring consistent execution across all shifts.
- Maintaining accurate reporting, documentation, and site-level performance metrics.
- Leadership & Culture: bullet list:
- Develop Operations Managers, Supervisors, and future leaders.
- Build a culture of accountability, engagement, and continuous improvement.
- Ensure consistent performance management practices across all shifts.
- Partner with HR on employee relations, investigations, and compliance matters.
- Foster an environment where employees feel supported, valued, and connected to the mission.
- Promote safety, professionalism, and operational discipline throughout the site.
- Required Experience: bullet list:
- 7-10+ years of experience in manufacturing, logistics, warehouse, production, technical operations, or similar environments.
- 4+ years managing managers and multiple layers of leadership.
- Experience overseeing multi-shift or 24x7 operations.
- Proven success leading organizations of 200+ employees.
- Experience in KPI-driven environments with strict operational standards.
- Strong analytical skills and data-driven decision-making ability.
- Experience managing workforce planning, staffing, and operational forecasting.
- Experience partnering directly with external clients and senior stakeholders.
- Strong employee relations, compliance, and performance management experience.
- Preferred Experience: bullet list:
- Experience supporting robotics, automation, AI, laboratory, or technical operations environments.
- Background in Lean, Six Sigma, or continuous improvement methodologies.
- Experience launching, scaling, or stabilizing high-growth operations.
- Experience managing large contingent workforces.
- Budget ownership and financial management experience.
- Everforth Apex description: about company, benefits, etc. This includes benefits details. We need to include Benefits section only if posting actually states them. It does: "Everforth Apex Benefits Overview: Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide."
Thus we can include a Benefits section with bullet list of benefits.
Pay and Schedule: Not mentioned explicitly. There's location (Onsite 5 days a week) which indicates schedule: onsite 5 days a week. That's schedule info. Should we include Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Onsite 5 days a week" under Location. That is schedule info. So we can include Schedule section with that detail. Pay: not mentioned, so omit.
We also have Duration: 12+ months. Could be considered contract length; maybe include under a short p metadata or maybe under a section like "Assignment Details"? Not required headings. We could include a short paragraph for metadata: Job ID, Location, Duration. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
with Job#: 3045008, Location: San Francisco, California (Onsite 5 days a week), Duration: 12+ months.
Now sections: We need headings
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have:
- About the role (Role Overview) -> we can use About the role
with paragraph(s) from Role Overview.
- Responsibilities: Could combine What You'll Lead, Site & Client Leadership, Performance, KPIs & Operational Excellence, Leadership & Culture. Could be one Responsibilities section with sub-sections? But we need to use - for any list of duties/requirements/benefits. So we could have a Responsibilities section with a
containing all duty items. However we have many items grouped under headings; we could keep them as separate under same section? The rule: Use - for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have a Responsibilities section with multiple
each preceded by maybe a heading? But we cannot use headings inside? Could use
for prose. Could also use
but not allowed? Only headings allowed are for section headings. So we should not use other heading levels. So we can have a Responsibilities and then maybe a
intro then multiple
each representing a grouping. That seems okay.
- Requirements: Could combine Required Experience and Preferred Experience? Usually Required vs Preferred separate. Could have Requirements section for Required Experience, and maybe Qualifications for Preferred? But we have headings: Requirements, Qualifications, Skills. We could map Required Experience to Requirements, Preferred Experience to Qualifications, and maybe Skills to something else? There's no explicit skills list; but we could include skills under Qualifications. However we need to avoid filler sections. If we have content for each, we can include.
Thus:
- About the role
Role Overview paragraph.
- Responsibilities
then maybe What you'll lead:
list items for What You'll Lead. Then another Site & Client Leadership:
list. Then another Performance, KPIs & Operational Excellence:
list. Then another Leadership & Culture:
list.
- Requirements
Required Experience:
list items.
- Qualifications
Preferred Experience:
list items.
- Benefits
Everforth Apex Benefits Overview:
list items (benefits). Could break into sublists? We'll just list each benefit as - .
-
Schedule
Onsite 5 days a week.
We also need to include metadata paragraph at top maybe: Job#: 3045008 | Location: San Francisco, California (Onsite 5 days a week) | Duration: 12+ months
We must not repeat job title as heading. The job title is Site Operations Director (SF) but we already have About the role.
We must remove boilerplate: EEO, legal, application instructions, etc. So we strip all that.
Now ensure we preserve all substantive information. Let's extract each bullet.
What You'll Lead items:
- Directly managing Operations Managers and site leadership.
- Indirectly overseeing 300+ employees across multiple shifts.
- Driving consistency, accountability, and execution across a 24x7 operation.
- Ensuring alignment and continuity between shifts and leadership teams.
- Leading workforce planning, staffing strategy, and operational readiness.
- Partnering with HR, Recruiting, Engineering, Training, Facilities, and Safety teams.
- Building scalable processes that support growth and operational excellence.
Site & Client Leadership:
- Own overall site performance and operational strategy.
- Serve as the primary operational partner to the client.
- Lead business reviews, operational updates, and executive presentations.
- Communicate KPI performance, risks, escalations, and improvement plans.
- Balance client priorities with operational stability and workforce needs.
- Lead complex escalations and drive resolution across cross-functional teams.
Performance, KPIs & Operational Excellence:
- You will be accountable for productivity, quality, attendance, throughput, and workforce stability.
- Capacity planning, labor forecasting, and resource allocation.
- Monitoring operational performance and identifying improvement opportunities.
- Driving process improvements that increase efficiency, quality, and scalability.
- Standardizing processes and ensuring consistent
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job description. Key content: - Job#: 3045008 (metadata, can be short p or drop) - Job Description: Site Operations Director (SF) - Location: San Francisco, California (Onsite 5 days a week) - Duration: 12+ months - Role Overview paragraph: "We are hiring a Site Operations Manager to lead a 24x7 operation supporting large-scale data collection and technical workflows. This role serves as the senior operational leader for the site, overseeing multiple shifts, Operations Managers, and overall site performance. You will be responsible for operational execution, client partnership, workforce planning, and leadership development while ensuring a safe, productive, and high-performing environment." - What You'll Lead: bullet list (though not bullet but lines). Content: - Directly managing Operations Managers and site leadership. - Indirectly overseeing 300+ employees across multiple shifts. - Driving consistency, accountability, and execution across a 24x7 operation. - Ensuring alignment and continuity between shifts and leadership teams. - Leading workforce planning, staffing strategy, and operational readiness. - Partnering with HR, Recruiting, Engineering, Training, Facilities, and Safety teams. - Building scalable processes that support growth and operational excellence. - Site & Client Leadership: bullet list: - Own overall site performance and operational strategy. - Serve as the primary operational partner to the client. - Lead business reviews, operational updates, and executive presentations. - Communicate KPI performance, risks, escalations, and improvement plans. - Balance client priorities with operational stability and workforce needs. - Lead complex escalations and drive resolution across cross-functional teams. - Performance, KPIs & Operational Excellence: bullet list: - You will be accountable for productivity, quality, attendance, throughput, and workforce stability. - Capacity planning, labor forecasting, and resource allocation. - Monitoring operational performance and identifying improvement opportunities. - Driving process improvements that increase efficiency, quality, and scalability. - Standardizing processes and ensuring consistent execution across all shifts. - Maintaining accurate reporting, documentation, and site-level performance metrics. - Leadership & Culture: bullet list: - Develop Operations Managers, Supervisors, and future leaders. - Build a culture of accountability, engagement, and continuous improvement. - Ensure consistent performance management practices across all shifts. - Partner with HR on employee relations, investigations, and compliance matters. - Foster an environment where employees feel supported, valued, and connected to the mission. - Promote safety, professionalism, and operational discipline throughout the site. - Required Experience: bullet list: - 7-10+ years of experience in manufacturing, logistics, warehouse, production, technical operations, or similar environments. - 4+ years managing managers and multiple layers of leadership. - Experience overseeing multi-shift or 24x7 operations. - Proven success leading organizations of 200+ employees. - Experience in KPI-driven environments with strict operational standards. - Strong analytical skills and data-driven decision-making ability. - Experience managing workforce planning, staffing, and operational forecasting. - Experience partnering directly with external clients and senior stakeholders. - Strong employee relations, compliance, and performance management experience. - Preferred Experience: bullet list: - Experience supporting robotics, automation, AI, laboratory, or technical operations environments. - Background in Lean, Six Sigma, or continuous improvement methodologies. - Experience launching, scaling, or stabilizing high-growth operations. - Experience managing large contingent workforces. - Budget ownership and financial management experience. - Everforth Apex description: about company, benefits, etc. This includes benefits details. We need to include Benefits section only if posting actually states them. It does: "Everforth Apex Benefits Overview: Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide." Thus we can include a Benefits section with bullet list of benefits. Pay and Schedule: Not mentioned explicitly. There's location (Onsite 5 days a week) which indicates schedule: onsite 5 days a week. That's schedule info. Should we include Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Onsite 5 days a week" under Location. That is schedule info. So we can include Schedule section with that detail. Pay: not mentioned, so omit. We also have Duration: 12+ months. Could be considered contract length; maybe include under a short p metadata or maybe under a section like "Assignment Details"? Not required headings. We could include a short paragraph for metadata: Job ID, Location, Duration. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
with Job#: 3045008, Location: San Francisco, California (Onsite 5 days a week), Duration: 12+ months. Now sections: We need headings
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have:
- About the role (Role Overview) -> we can use About the role
with paragraph(s) from Role Overview.
- Responsibilities: Could combine What You'll Lead, Site & Client Leadership, Performance, KPIs & Operational Excellence, Leadership & Culture. Could be one Responsibilities section with sub-sections? But we need to use - for any list of duties/requirements/benefits. So we could have a Responsibilities section with a
containing all duty items. However we have many items grouped under headings; we could keep them as separate under same section? The rule: Use - for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have a Responsibilities section with multiple
each preceded by maybe a heading? But we cannot use headings inside? Could use
for prose. Could also use
but not allowed? Only headings allowed are for section headings. So we should not use other heading levels. So we can have a Responsibilities and then maybe a
intro then multiple
each representing a grouping. That seems okay.
- Requirements: Could combine Required Experience and Preferred Experience? Usually Required vs Preferred separate. Could have Requirements section for Required Experience, and maybe Qualifications for Preferred? But we have headings: Requirements, Qualifications, Skills. We could map Required Experience to Requirements, Preferred Experience to Qualifications, and maybe Skills to something else? There's no explicit skills list; but we could include skills under Qualifications. However we need to avoid filler sections. If we have content for each, we can include.
Thus:
- About the role
Role Overview paragraph.
- Responsibilities
then maybe What you'll lead:
list items for What You'll Lead. Then another Site & Client Leadership:
list. Then another Performance, KPIs & Operational Excellence:
list. Then another Leadership & Culture:
list.
- Requirements
Required Experience:
list items.
- Qualifications
Preferred Experience:
list items.
- Benefits
Everforth Apex Benefits Overview:
list items (benefits). Could break into sublists? We'll just list each benefit as - .
-
Schedule
Onsite 5 days a week.
We also need to include metadata paragraph at top maybe: Job#: 3045008 | Location: San Francisco, California (Onsite 5 days a week) | Duration: 12+ months
We must not repeat job title as heading. The job title is Site Operations Director (SF) but we already have About the role.
We must remove boilerplate: EEO, legal, application instructions, etc. So we strip all that.
Now ensure we preserve all substantive information. Let's extract each bullet.
What You'll Lead items:
- Directly managing Operations Managers and site leadership.
- Indirectly overseeing 300+ employees across multiple shifts.
- Driving consistency, accountability, and execution across a 24x7 operation.
- Ensuring alignment and continuity between shifts and leadership teams.
- Leading workforce planning, staffing strategy, and operational readiness.
- Partnering with HR, Recruiting, Engineering, Training, Facilities, and Safety teams.
- Building scalable processes that support growth and operational excellence.
Site & Client Leadership:
- Own overall site performance and operational strategy.
- Serve as the primary operational partner to the client.
- Lead business reviews, operational updates, and executive presentations.
- Communicate KPI performance, risks, escalations, and improvement plans.
- Balance client priorities with operational stability and workforce needs.
- Lead complex escalations and drive resolution across cross-functional teams.
Performance, KPIs & Operational Excellence:
- You will be accountable for productivity, quality, attendance, throughput, and workforce stability.
- Capacity planning, labor forecasting, and resource allocation.
- Monitoring operational performance and identifying improvement opportunities.
- Driving process improvements that increase efficiency, quality, and scalability.
- Standardizing processes and ensuring consistent
- containing all duty items. However we have many items grouped under headings; we could keep them as separate
- for any list of duties/requirements/benefits. It doesn't forbid multiple lists. So we can have a Responsibilities section with multiple
- each preceded by maybe a
- .
-
Schedule
Onsite 5 days a week.
We also need to include metadata paragraph at top maybe:Job#: 3045008 | Location: San Francisco, California (Onsite 5 days a week) | Duration: 12+ months
We must not repeat job title as heading. The job title is Site Operations Director (SF) but we already have About the role. We must remove boilerplate: EEO, legal, application instructions, etc. So we strip all that. Now ensure we preserve all substantive information. Let's extract each bullet. What You'll Lead items: - Directly managing Operations Managers and site leadership. - Indirectly overseeing 300+ employees across multiple shifts. - Driving consistency, accountability, and execution across a 24x7 operation. - Ensuring alignment and continuity between shifts and leadership teams. - Leading workforce planning, staffing strategy, and operational readiness. - Partnering with HR, Recruiting, Engineering, Training, Facilities, and Safety teams. - Building scalable processes that support growth and operational excellence. Site & Client Leadership: - Own overall site performance and operational strategy. - Serve as the primary operational partner to the client. - Lead business reviews, operational updates, and executive presentations. - Communicate KPI performance, risks, escalations, and improvement plans. - Balance client priorities with operational stability and workforce needs. - Lead complex escalations and drive resolution across cross-functional teams. Performance, KPIs & Operational Excellence: - You will be accountable for productivity, quality, attendance, throughput, and workforce stability. - Capacity planning, labor forecasting, and resource allocation. - Monitoring operational performance and identifying improvement opportunities. - Driving process improvements that increase efficiency, quality, and scalability. - Standardizing processes and ensuring consistent
heading? But we cannot use headings inside? Could use
for prose. Could also use
but not allowed? Only headings allowed are
for section headings. So we should not use other heading levels. So we can have a Responsibilities
and then maybe a
intro then multiple
- each representing a grouping. That seems okay.
- Requirements: Could combine Required Experience and Preferred Experience? Usually Required vs Preferred separate. Could have Requirements section for Required Experience, and maybe Qualifications for Preferred? But we have headings: Requirements, Qualifications, Skills. We could map Required Experience to Requirements, Preferred Experience to Qualifications, and maybe Skills to something else? There's no explicit skills list; but we could include skills under Qualifications. However we need to avoid filler sections. If we have content for each, we can include.
Thus:
-
About the role
Role Overview paragraph.
-Responsibilities
then maybeWhat you'll lead:
- list items for What You'll Lead. Then another
Site & Client Leadership:
- list. Then another
Performance, KPIs & Operational Excellence:
- list. Then another
Leadership & Culture:
- list.
-
Requirements
Required Experience:
- list items.
-
Qualifications
Preferred Experience:
- list items.
-
Benefits
Everforth Apex Benefits Overview:
- list items (benefits). Could break into sublists? We'll just list each benefit as
- .
-
- under same section? The rule: Use