IT Engineer
Job Description
LiveKit is building the infrastructure layer for the voice-driven era of computing. Our platform gives developers everything they need to build, test, deploy, scale, and observe agents in production.
Key Responsibilities
- Own identity and access engineering in Okta — group strategy, app assignments, SSO configuration, lifecycle automation, and access request patterns that are secure without being miserable to use
- Run endpoint engineering across a macOS-first fleet in Workspace ONE — provisioning, configuration baselines, patching, encryption posture, inventory hygiene, and compliance reporting
- Administer Google Workspace and Slack at scale: user lifecycle, groups, shared drives, permissions, roles, and the governance patterns that keep them from drifting
- Bring the SaaS estate under real governance — who owns each tool, who has access, what it costs, and what happens to all three when someone changes teams or leaves
- Build the automation that keeps IT load from scaling with headcount — onboarding, deprovisioning, access reporting, device compliance, and whatever else you catch yourself doing twice
- Translate security, compliance, and engineering requirements into IT controls that generate their own audit evidence instead of a quarterly scramble
- Serve as the technical escalation point for complex issues across identity, access, endpoints, and internal infrastructure — and then engineer the class of problem out of existence
Requirements
- 4+ years in IT engineering, IT operations, systems administration, endpoint engineering, or identity engineering — ideally somewhere fast-moving and remote-first
- You’ve administered Okta or a comparable identity provider as the owner: SSO, groups, app assignments, lifecycle workflows, real access management decisions
- Hands-on with modern MDM — Workspace ONE or equivalent — including provisioning, configuration enforcement, patching, encryption, and inventory
- Strong Google Workspace administration and genuine macOS endpoint depth
- You’ve built or meaningfully improved operational workflows, automation, reporting, or internal controls — not just operated someone else’s
- An excellent writer. You can explain a technical decision clearly, document a system so the next person doesn’t have to reverse-engineer it, and keep stakeholders informed without burying them
- Strong ownership and judgment. You can prioritize under ambiguity and you build things that reduce future work rather than adding to it
- You want to stay hands-on. This is an individual contributor role, and the work is building and operating systems, not managing people who do
