Service Engineer - AI Automation, Cloud & Security

IT Support & Automation Engineer (Managed Services)

Utica, MI (office-first with flexibility / hybrid options) | Microsoft 365
• Azure
• Networking
• Security
• Automation
• MSP Tooling
Speak Geek. Be Human. Make IT better for People.

At SMART I.T. Services, we help real businesses run smoothly with proactive managed IT-cloud, cybersecurity, networking, and support that people actually enjoy working with. A big part of how we do that is automation: smarter workflows, fewer repetitive tasks, better service, and modern tools that help teams move fast without cutting corners.

If you love technology, like talking to people, and get real satisfaction from turning messy problems into clean systems, you'll fit in here.
What you'll do

• Support end users and business owners with clear communication and calm troubleshooting.
• Own tickets end-to-end: diagnose, resolve, document, and follow through.
• Work proactively (not just break/fix): monitoring, patching, security improvements, and prevention.
• Build and improve workflows using modern tooling-process automation, integrations, and orchestrated runbooks (think n8n / Zapier-style approaches, plus service workflow improvements).
• Help clients adopt modern productivity tooling (including Microsoft Copilot and AI-assisted use cases) in practical, secure ways.

Technologies you'll touch (varies by client)

• Microsoft 365 / Azure, Windows Server, Active Directory / Entra  (identity)
• Networking: firewalls, switching, wireless, VPNs (Cisco / Cisco Meraki exposure is a plus)
• VoIP phone systems
• Cybersecurity best practices and tools (MFA, endpoint hardening, least privilege, backup awareness)
• MSP operations: ticketing + RMM (Connect Wise / Kaseya-style)
• Virtual desktop environments (VDI / VMware-style platforms)
• Cloud + "data-center style" environments (hybrid happens)

You might be our person if...

• You're the one friends/family/neighbors call when "the Wi-Fi is weird" or a laptop is doing something unholy.
• You tinker because you want to-home setup, cloud sandbox, scripts, automations, integrations, security settings... anything that helps you learn.
• You enjoy making systems simpler: fewer clicks, fewer steps, fewer repeat issues.
• You can "speak geek," but you genuinely like people-and you explain things without making anyone feel dumb.

Nice-to-have (not required)

We'll love it if you have any of these-but they're not required:

• Open Claw (AI framework) experience for building/operating agentic workflows
• Docker familiarity
• Kubernetes fundamentals (or curiosity to learn)
• Linux, especially Ubuntu (basic admin + troubleshooting)
• Local/private LLMs (local model setups), RAG, self-hosted agent tools, or building a small "AI server"/lab
• Experience supporting insurance agencies / regulated SMBs
• Scripting/automation mindset (Power Shell, Python, low-code, APIs)
• Cloud/security exposure (certs welcome, not required)

Experience level

We're open to multiple experience levels. If you bring strong fundamentals, curiosity, and a service mindset, we'll match responsibilities to your skills and help you level up quickly.
Hybrid/Flex Role - Local Residency Required

This position offers some flexible and hybrid scheduling; however, candidates must reside within 150 miles of Detroit, MI to support on-site client needs, occasional in-person meetings, and time-sensitive dispatches.
Benefits

• 401(k) retirement program
• Health insurance
• Paid time off
• Your birthday off

Ready to apply?

If you want a role where you combine people-first support with cloud, security, networking, and automation-apply today.
3 quick questions (so I can finalize the best version for posting)

What exact job title do you want on the ad:
Service Desk Engineer, IT Support Engineer, Managed Services Engineer, or something else?

For this role, should networking (firewalls/switching/wireless) be framed as a core expectation, or "exposure is a plus"?

Do you want the posting to mention client site visits as "occasional," "regular," or keep it implied via the 150-mile requirement?