IT Engineer
Job description
About the role
This role delivers hands-on IT support and infrastructure operations for employees, devices, and SaaS platforms across identity, endpoints, and networks. The position manages hardware lifecycles, security hygiene, and documentation while collaborating with distributed teams. Success requires balancing autonomous execution with coordinated practices across locations.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Employees resolve Help Desk tickets efficiently to keep desktops, devices, and A/V systems operational for in-office and remote staff.
The MDM fleet operates smoothly across macOS and selected Linux devices through consistent configuration and monitoring.
Network and A/V issues are troubleshot quickly in the office to minimize disruption for on-site teams.
Identity and access integrations run reliably as administrators manage Okta, core SaaS tooling, role-based access, and integration workflows.
IT initiatives advance on schedule as stakeholders receive regular updates, priorities are managed, and communication stays consistent.
Onboarding and offboarding proceed smoothly for employees, interns, and contractors through coordinated support and documentation.
Manual tasks are reduced as reliable automations improve operational efficiency for the broader IT team.
Practices remain consistent across locations, with aligned documentation, asset management, and process execution.
Requirements
Administrators use Terraform to manage Okta, handling users, groups, and basic app integrations.
Google Workspace is supported with strong knowledge of its tools and security features.
macOS device management works reliably, often using FleetDM for monitoring and remediation.
Devices running macOS, Linux, iOS, and Android receive consistent support across hardware and user scenarios.
Procurement and asset management processes are followed, including tracking and lifecycle responsibilities.
Documentation and knowledge base entries are clear, concise, and easy to understand for technical and non-technical audiences.
Communication and customer service remain excellent when interacting with employees and stakeholders.
Security principles and basic practices are applied to access reviews and identity-related tasks.
Low-code automation tools such as Serval, Okta Workflows, or Gumloop streamline repetitive workflows.
Scripting skills in Bash or Python automate routine tasks and support operational needs.
API integrations and webhooks are used effectively to connect systems and services.
Experience with AWS provisioning and Identity Center supports identity and access workflows.
Nice to have
Exposure to security and compliance frameworks such as SOC 2, ISO 27001, NIST, CIS, or FedRAMP strengthens implementation.
Experience with AI tools, agents, MCPs, automations, and prompting improves tooling and process options.
Familiarity with Notion and Linear supports documentation and project tracking.
HRIS integration experience with platforms like HiBob or Workday enhances employee lifecycle workflows.
Practical notes
The role may require US work authorization and compliance with local regulations. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.