Senior System Administrator (IT Infrastructure and Security)

About this role

This is a remote position.

Senior System Administrator (IT Infrastructure and Security)Remote (India) | Full-Time
Also searched as: Senior Systems Engineer, IT Infrastructure Engineer, L3 Support Engineer, IT Security EngineerIf you were handed admin rights to every system a 425-person company runs on, what would you harden first?

On a typical day you might take an escalation off the systems engineer in the morning and turn its root cause into a runbook they can run next time, walk the MSP through a segmentation change on a Melbourne campus network after lunch, and end the day confirming with the People team that a leaver's access is actually gone.

About Contour

We started in 2020 with a handful of students and a belief that great education should not be out of reach. Today we operate across three brands with 8,000+ students and 425+ team members: roughly 100 in India and 325 onshore in Australia. The India team runs publishing, student experience, CRM and technology, operations, and people and culture.

The people we hire now will shape how Contour grows. This is one of those roles.

About This Role

You are the senior engineer in Contour's first in-house IT team, and the escalation point above it. You run the systems the company works in: Google Workspace, Slack, HubSpot, Rippling and the LMS; the identity platform and the device fleet; the network, CCTV and door access at each campus; and the security posture across all of it.

You report to the interim IT lead in Melbourne until the handover is complete, then to the VP of Global Enablement and Support. They own the technology budget, vendor contracts and the call on which platforms we standardise on. Risk acceptance sits with the senior leadership team. Everything else is yours: the design, the configuration, the hardening, and the no when a vendor does not pass your review.

Expect roughly two thirds of your week on system ownership, hardening and project work, and one third on escalations. The team is you and a systems engineer who runs the L1 and L2 queue. You mentor them and review their work, but this is a hands-on-keyboard seat. Leading the team as it grows is open to you if you want it: welcome, not required.

The standard here is different in two ways. First, you fix the cause. An escalation you close carries a root cause and, if it has come up before, a runbook. Second, you hold the line on security and can explain why. You have said no to something convenient because it was not safe, and you can walk a non-technical executive through that trade-off without dumbing it down or hiding behind acronyms.

Contour has grown to three brands and two countries on systems that were administered alongside other jobs. The interim IT lead has spent the past few months setting the security baseline and documenting it. You take that handover and make it permanent, then build what comes after: identity done properly, a managed fleet, campuses you can see and control from India, and a change process people trust.

By the end of month three, you will have MFA and 2SV at full coverage, a first access review done, and offboarding revocation confirmed rather than assumed. You will have a change record on every production change, the top repeat escalations written into runbooks and handed to the systems engineer, the findings from our recent security review triaged into a dated remediation plan with the first fixes shipped, and the UniFi stack documented for each campus with SPF, DKIM and DMARC enforced on the domain. The controls you put in place in those first months will still be holding when the company is twice this size.

Where the Work Lives

•
Google Workspace:the identity core for staff and where most of the business's data sits. Admin console settings here are security settings: group-driven access, external sharing rules, and audit logs someone reads.

•
Slack:where the company talks and where tickets arrive. Most of what you decide gets explained here, to people who do not administer anything.

•
Rippling and the identity platform:Rippling is the HR system of record, and we are choosing a dedicated identity and device management platform now. Joiner, mover and leaver flows start in Rippling and end with confirmed access, or confirmed revocation, in every system downstream. You inherit the platform decision and run the rollout across a largely BYOD fleet of several hundred macOS and Windows devices.

•
HubSpot and the LMS:the CRM and our own learning platform. Sales, tutors and students work in them, so admin rights, integrations and data flow here protect student data as much as they serve the teams using them.

•
UniFi:the network at each campus, managed from one controller with alerts you cannot ignore. Segmentation, firmware and capacity discipline here are what keep a campus network boring.

•
1Password:the enterprise password manager. Shared credentials get retired into it, and break-glass accounts are documented, sealed and tested.

•
Suptask:tickets come in through Slack. Each escalation you close records why it happened, so the trend report means something.

• ​Make.com and Zapier:the automation layer. A scenario that fails silently is worse than the manual step it replaced, so alerting is part of the build.

What You Will Do

•
Take the L2 and L3 escalations and stop them coming back.Close what the systems engineer cannot, record the cause, then write the runbook so that ticket type is theirs from then on.Design identity and access.Role-based access, group-driven permissions, SSO where it is available, MFA and 2SV at full coverage. Run the periodic access review and own the technical side of offboarding.

•
Administer the workplace stack at senior level.The platforms above plus the approved AI platforms, device management across macOS and Windows, and the systems that finance, sales and tutors work in: hardening, admin rights, audit logging, licence use, and the integrations and data flow between them.

•
Run the campus…