The Service Engineer II independently resolves more complex issues and assumes full ownership for end-to-end resolution. This role requires stronger technical judgment, efficiency, proactive communication, and disciplined execution in a metric-driven environment. This role may include dedicated client service assignments requiring broad technical execution, independent ownership, and cross-functional collaboration within Executech standards.
Key Responsibilities
Resolve issues beyond Service Engineer I scope across devices, identity, Microsoft 365, networking fundamentals, and core business systems, acting as a consistent technical lead for assigned clients and queues.
Own tickets end-to-end: client updates, vendor/carrier coordination, resolution confirmation, and handoff when scope spans multiple teams.
Apply structured troubleshooting and sound judgment on when to proceed independently, escalate, or engage additional resources.
Use scripting and automation for repeatable tasks (e.g., PowerShell for standard admin actions) within approved standards.
Support security posture through correct identity verification, suspicious-activity handling, and incident escalation workflows.
Contribute to operational improvement: surface recurring issues, recommend remediation, and update KB/runbooks.
Mentor Service Engineer I staff through shadowing, pairing, and high-quality escalation feedback.
Balance client advocacy with scalability, security, and Executech standards, operating across functional boundaries when needed while adhering to change control, documentation, and escalation practices.
Typical Work Scope (Examples)
Multi-step M365 administration (licenses, groups, mailbox permissions, SharePoint/Teams access issues) with judgment and minimal supervision.
Endpoint and device management (Intune policies, device compliance basics, BitLocker recovery, Autopilot resets) within SOP.