Files
nexus/Interview/SBM_IT_Support_Manager_Interview.md
2026-09-19 06:16:35 +08:00

132 lines
5.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# SBM Offshore — IT Support Manager Interview Notes
## Self-Introduction (1 min)
10+ years in enterprise IT ops & end-user support. Led 3–6 person teams across multi-site operations, ServiceNow rollouts, full IT asset lifecycle, IDC colocation, and group-wide IT projects. Long-term owner of HQ + branch + project-site IT delivery. Familiar with ITIL, change management, security awareness, and cross-region collaboration in MNCs. Fluent English for meetings, emails, and global IT coordination.
Five core strengths aligned to this role: **multi-site ops, colocation IDC, distributed team management, asset audit, group project delivery.**
---
## 1. Multi-Site IT Infrastructure (Shanghai / Tianjin / Nantong Shipyard)
Three distinct environments:
- **Shanghai HQ office** — stability, SLA, standardized desktops, O365/Azure AD.
- **Tianjin branch** — remote standardized ops, periodic inspections, closed-loop tickets, synced asset台账.
- **Nantong FPSO shipyard** — high-density, project-based, temporary: concentrated onboarding, frequent seat changes, ad-hoc network needs, high incident rate.
**Delivery approach:**
- **Pre-project:** network drops, VPN, standard image, batch account provisioning.
- **Peak:** on-site staff augmentation, 7×12 response, frequent inspections.
- **Steady-state:**固化 SLA, periodic asset counts, decommission idle devices & zombie accounts.
*Summary: office = stability & standards; shipyard = fast delivery, elastic scale, emergency readiness.*
---
## 2. Equinix Colocation IDC Operations
Not a build-out role — it's **operations of a colo environment**:
- Daily: resource inspection, bandwidth monitoring, cabinet台账, device health.
- Ops: escalate to Equinix on hardware alerts, network jitter, port faults, capacity expansion.
- Governance: strict change logs, cost control, compliance reporting to global IT.
- Incident: clear escalation path — isolate line vs. hardware vs. config.
Core principle: **stable, auditable, traceable, cost-controlled.**
---
## 3. ServiceNow CMDB & IT Asset Lifecycle
Full lifecycle, closed-loop:
1. **Procurement** — unified models, admission standards,台账 entry upfront.
2. **Deployment** — intake, user binding, CMDB record, labeling.
3. **Operations** — tickets linked to assets, periodic inspection, version standardization.
4. **Offboarding** — device回收, account disable, status update.
5. **Decommission** — compliant disposal,台账 closure, audit trail.
Solved common pain points:账实不符, idle stock, asset leakage, failed audits. After ServiceNow rollout: accuracy, audit pass rate, and device reuse rate all improved materially.
---
## 4. ITIL Change Management
Three change classes, strictly enforced:
- **Standard** — routine desktop/software, standard ticket.
- **Normal** — network/permission/config changes: review first, execute in window, record.
- **Emergency** — restore first, ticket later, post-mortem + corrective action.
Principle: **every change traceable, rollback-ready, pre-planned, low-risk.**
---
## 5. Distributed Team Management (Shanghai + Tianjin + Nantong)
- **Standardized division of labor:** HQ = standards, audit, projects; branch/on-site = L1 response.
- **SLA metrics:** response time, resolution rate, CSAT — monitored daily.
- **Cadence:** weekly progress, monthly retrospective, closed-loop issue log.
- **Unified enablement:** shared runbooks, fault KB, device standards.
- **People:** quantified performance, on-site rotation, peak staffing, morale management.
*Result: remote but orderly, consistent standards, controllable outcomes, stable team.*
---
## 6. Group IT Project Delivery (China Execution)
Familiar with the MNC model: **HQ sets standards, China executes.**
Four-step method:
1. Receive group requirements, timeline, compliance needs precisely.
2. Map local business reality, identify risks, surface blockers early.
3. Pilot → roll out → train → go-live, in phases.
4. Data review, issue closure, on-time delivery.
On resistance: persuade with scenarios, risks, and efficiency value — 100% China-side delivery.
---
## 7. Cybersecurity Awareness
- Annual security training, phishing drills, office-security campaigns.
- Account/permission compliance, remote-access rules, device encryption, offboarding cleanup.
- Partner with overseas security team on audits & remediation.
Principle for offshore MNC: **zero tolerance on security; compliance > convenience.**
---
## 8. Vendor & Cost Management
Full vendor lifecycle — IDC, desktop outsourcing, hardware, network:
1. Admission criteria + SLA in contract.
2. Monthly quality scoring, accountability on issues.
3. Cost optimization: clear idle resources, scale on demand.
4. Escalation closure, stable long-term service quality.
*Outcome: service, cost, and risk all under control.*
---
## 9. Why Me — Closing Summary
1. **System fit** — ITIL, ServiceNow, asset audit, group compliance — aligned to SBM global IT.
2. **Scenario fit** — HQ + branch + shipyard project site, all three covered.
3. **Management fit** — distributed team, SLA, quality, cost.
4. **Language fit** — English for overseas meetings, emails, coordination.
5. **Industry fit** — understand offshore project cycles; resilient, stable, rigorous.
---
## 10. Smart Questions to Ask the Interviewer
1. Current China IT headcount, on-site structure, outsourcing ratio?
2. Nantong shipyard travel frequency — any extended on-site stints?
3. KPIs for this role — which ones matter most?
4. Group IT project roadmap for China this year — what's the priority?