Sr. Program Operations Manager
- LocationFremont, California, United States
- Work typeHybrid
- Salary95k to 110k USD a year
- Posted14 November 2026
- SourceEOS's careers page (Greenhouse)
Last checked1 h ago: still listed on EOS's careers page. First seen 2 days ago.
Moves fastWhen EOS takes a role down early, it is usually about 8 days after posting. Apply soon.
At a glance
- Experience6+ years
- EducationBachelor's degree or equivalent
- Skills and toolsPMP, Six Sigma
Read from the ad by RoleFinder, with rules and an AI reading; the description is the source.
About the role
OUR COMPANY:
EOS IT Solutions is a Global Technology and Logistics company, providing Collaboration and Business IT Support services to some of the world’s largest industry leaders, delivering forward-thinking solutions based on multi-domain architecture. Customer satisfaction and commitment to superior quality of service are our top business priorities, along with investing in and supporting our partners and employees.
We are a true International IT provider and are proud to deliver our services through global simplicity with trusted transparency.
What You Will Do
Reports to the Hardware Solutions Service Delivery Manager, who owns the team's operational direction, priorities, and standards.
Directly manages the Coordination vertical, and builds trusting relationships with partners as they manage the first point of contact for all requests.
This role drives execution: designing, building, and maintaining the dashboards, automations, and runbooks that operationalize the service's goals; driving process adoption and accountability across internal teams and external partners; and bringing operational rigor to an environment where live events demand constant, legitimate improvisation.
Key Responsibilities
1. Operational infrastructure — dashboards, automations, runbooks
- Contribute to the team's KPI and service-metric definition as part of the leads group, owning the metrics for the Coordination vertical and recommending refinements based on what the data shows.
- Build and maintain the reporting and dashboards behind those metrics — and lean into automation across all verticals where applicable, so other leads are not hand-assembling their own numbers.
- Identify recurring manual effort across intake, triage, deployment, and reporting, and replace it with automation (forms, routing rules, task-manager workflows, scheduled reporting, agent-assisted workflows).
- Author and maintain service runbooks for every HS service — covering intake criteria, roles, escalation paths, SLAs, hardware and imaging requirements, regional variants, and post-event closeout.
- Drive cross-event / cross-program roadmapping, forecasting, and deliverable tracking for leadership.
- Own the task system and GSD tracking for overall HS service.
- Maintain a single source of truth for SOPs and runbooks, with a scheduled audit cadence so documentation does not drift from practice.
- Produce and maintain reporting packs that pull service health, spend position, and delivery milestones into a single view, and keep reporting timely, accurate, and tailored to the audience.
- Support the SDM in preparing Business Review and business-review supported materials.
- Onboard new team members with a focus on ensuring service parity across verticals and regions.
2. Process accountability — Internal and External
- Hold internal teams and external partners accountable to established intake, escalation, and documentation standards — through visible metrics and direct follow-up, not reminders alone.
- Make non-compliance visible: surface out-of-process requests, missed SLAs, and undocumented work within existing reporting structures.
- Distinguish necessary improvisation from process erosion . Event work will always require real-time deviation; the expectation is that deviations are captured, reviewed, and either codified into the runbook or corrected.
- Run a closed loop on exceptions: every significant deviation, escalation, or Root Cause Analysis (RCA) produces either a documentation change, an automation, or an explicit decision to accept the variance.
- When an issue recurs, set a process. Recurrence is the trigger — a second or third occurrence of the same problem is treated as a signal that a process, runbook entry, or automation is missing, not as bad luck. This role is expected to notice the pattern and close it.
- Actively bring process-improvement recommendations forward rather than waiting to be asked. Recommendations are an expected output of the role.
- Collaborate with partner leads to align their internal processes to TPGHS standards during onboarding, and re-baseline at regular business reviews.
3. Execution Partnership With the Service Delivery Manager
- Operate as the SDM's execution arm. The SDM sets the goalposts — service strategy, client commitments, priorities, and standards. This role owns the detailed work of reaching them: the systems, documentation, data, and day-to-day discipline that make delivery repeatable.
- Maintain live tracking against the Plan of Record (PoR) owned by the SDM and the client — keeping milestones, dependencies, resource needs, and status current so execution stays aligned to the agreed plan and timeline.
- Proactively identify and escalate risks, blockers, and interdependencies, and recommend mitigation options for the SDM or client to decide.
- Take ownership of the operational detail and program-administration workload on behalf of the SDM, so SDM time goes to decisions, KPIs, and stakeholder relationships.
- Translate the SDM's priorities into an operational excellence roadmap — a prioritized, time-bound backlog of process, tooling, and documentation improvements with named owners — then drive it to completion and report progress back.
- Present the Coordination vertical at business reviews — trend analysis, cost and effort drivers, and recommended changes — alongside the other leads reporting on their own functions, with the SDM framing the overall narrative.
- Serve as the standing escalation layer between the SDM and service coordination. The coordinator population reports directly into this role, and coordinators, vertical leads, and partners escalate here first; this role resolves what it can within established guardrails and routes upward only what genuinely requires the SDM — with context, options, and a recommendation attached.
- Protect the SDM's capacity by filtering signal from noise: absorb recurring operational questions into documentation and automation so the same escalation does not arrive twice.
- Act as the SDM's delegate in the SDM's absence, with sufficient context and documentation to decide rather than stall, and a clear record of what was decided for later review.
4. Continuous Improvement and Program Execution
- Perform site visits and on-site event support to observe actual workflows and conditions, and convert those observations into documented improvements.
- Attend post-mortems for major events; call for and review RCAs; own the resulting action items to closure.
- Manage operational and program deployment projects end to end.
- Onboard new partners and team members to the HS service model, using the runbooks and dashboards as the onboarding curriculum.
- Maintain working knowledge of current Meta products and hardware to keep operational design credible.
What success looks like
First 90 days
- Full inventory of existing services, runbooks, and reporting, with gaps mapped.
- An operational excellence roadmap built from the SDM's stated priorities and approved by the SDM, with at least one process-improvement recommendation brought forward.
- At least one high-friction manual process automated.
6 months
- Every active service has an updated runbook and a dashboard view for ease of service health snapshots.
- Manual reporting effort reduced by 50% across all verticals.
12 months
- Operational metrics reviewed on a fixed cadence with leadership.
- Measurable improvement in SLA adherence and process compliance.
- Exception-to-documentation loop running consistently.
- Onboarding time for new partners and team members is measurably shorter.
What You Need to Succeed
- Demonstrated ownership of process and operational improvement in a live-operations, events, or field-services environment — not just process documentation, but adoption.
- Comfort building reporting and lightweight automation: dashboards, task-manager workflows, forms and routing, spreadsheet and data tooling. Appetite for agentic and AI-assisted tooling.
- Ability to hold peers, senior stakeholders, and external partners accountable without formal authority — direct, evidence-based, and relationship-preserving — while escalating cleanly to the SDM when accountability requires positional weight.
- Judgment to tell the difference between a process that is being broken and a process that is wrong.
- Strong written communication: runbooks, SOPs, and executive-ready operational summaries.
- High tolerance for ambiguity and a fast-moving, improvisational event environment, paired with an instinct to leave structure behind afterward.
- Willingness and ability to travel for site visits and events, roll up your sleeves, and assist wherever necessary during high-demand periods.
Essential Criteria
- 6+ years of operational management experience in a technical, hardware deployment, live-events, or field-services environment.
- Bachelor's degree in a relevant field, or equivalent experience; PMP or equivalent certification.
- Demonstrated proficiency using project and task management software to coordinate workstreams, monitor progress, and ensure delivery against defined timelines and objectives.
- Strong leadership skills, with experience managing a coordination team and coordinating vendor and delivery resources.
- Exceptional communication and stakeholder management skills.
- Ability to adapt to changing priorities and business needs in a fast-paced environment.
- Analytical mindset with strong problem-solving and decision-making capabilities.
- Familiarity with forecasting, budget reporting, and reporting on delivery KPIs such as on-time delivery, milestone adherence, standards compliance, data accuracy, and forecast accuracy.
- Experience driving operational excellence through process optimization, automation, and adoption of new technologies.
- Experience developing and implementing operational plans for managed services, aligned to organizational or client goals.
- Demonstrated integrity and ability to manage sensitive and confidential information.
- Self-motivated and able to take responsibility in an autonomous environment.
- Strong influencing, negotiation, and decision-making skills.
Desirable criteria
- Working knowledge of VR/AR/MR hardware, wearable tech, consumer device portfolio,and of device imaging and provisioning workflows.
- Experience supporting large-scale live events or product launches.
- Proven track record of applying Six Sigma or Lean methodologies to improve service processes, reduce operational costs, and enhance service quality.
- Experience with emerging technologies such as AI and agentic tooling to enhance service delivery.
- Experience operating across multiple global regions.
The EOS pay range for this job is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, experience, education, knowledge, skills, and abilities, as well as internal equity, market data, or other laws.
EOS is committed to creating a diverse and inclusive work environment and is proud to be an equal opportunity employer. We invite you to consider opportunities at EOS regardless of your gender; gender identity; gender reassignment; age; religious or similar philosophical belief; race; national origin; political opinion; sexual orientation; disability; marital or civil partnership status or other non-merit factor.
#LI-GM1
#LI-Hybrid
#INDNAMER
Pay Range
$95,000 — $110,000 USD
Get open roles ranked against your CV
Add your CV once. RoleFinder ranks the open roles where you want to work, plus remote ones, against it, shows your best 12 with a one-line reason each, and emails you new matches once a week. The file is read once by AI and not kept; employers never see it.
Sign in with Google or email to start. How we handle your CV