IT Systems Administrator

This is a remote position.

IT Systems Administrator, IndiaRemote (India) | Full-Time

When a colleague is locked out, a new hire needs access on day one, or someone cannot work out which CRM button to press, do you want to be the person who sorts all of it, fast?

On a typical day you might clear the morning tech ticket queue and unblock two people before their first meeting, set up a new joiner's accounts and access in Rippling and Google Workspace after lunch, and answer a CRM workflow question and update the tech guide so it stops coming in before end of day.

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.

A remote team of hundreds only moves as fast as its access, its tools, and its ability to use them. This is the seat that keeps all three working.

About This Role

You are the tech-savvy generalist who keeps Contour's team unblocked. You own the tech ticket queue, you run the system administration behind accounts and access, and you are the person people go to when a tool or a CRM workflow is not doing what they need.

The job has four parts that all sit with you. You run the tickets: every tech and access request comes through Suptask, and you triage, resolve first line, and escalate the rest with clear context. You do the system administration: Google Workspace, Rippling, and seats and access across Monday and HubSpot. You own onboarding and offboarding: setting new joiners up in the right systems on day one through Rippling, removing access cleanly when someone leaves, and building basic automations in Rippling so that setup is reliable rather than manual. And you run the audits: regular access and license checks so the right people have the right access, nothing is over-provisioned, and no leaver is left with a login.

On top of the pure IT work, you handle the non-IT but tech-based tickets: the CRM questions. Which button, which workflow, why did this behave that way. You resolve them, and just as importantly you train the team and keep the tech guide and knowledge base current, so the same questions stop coming in. This is where being genuinely tech-savvy matters: you learn a system fast, explain it plainly, and turn a repeat question into a bit of documentation.

You report to the VP of Global Enablement and Support. The automation and engineering teams own the deep builds, the Make scenarios, the HubSpot development, and the LMS code; your patch is first-line support, system administration, access, audits, and enablement, and you escalate the deep technical items to them. Because Contour is remote-first, the weight is on accounts, access, and the SaaS tools the team lives in, not physical hardware. By the end of month three, the ticket queue runs with reliable response times, onboarding and offboarding through Rippling runs like clockwork, Google Workspace and CRM access is clean and audited, and the tech guide is deflecting the questions that used to come in over and over.

Where the work lives

• Suptask (the Contour Help Hub):every tech and access request becomes a tracked ticket, so nothing slips and response times are measurable.

• Rippling:identity, onboarding, and accounts. Where you set people up, remove them cleanly, and build the automations that make that reliable.

• Google Workspace admin:accounts, groups, permissions, and shared drives, kept clean and current.

• Monday.com and HubSpot:seats and access, plus the CRM workflows the team asks you about.

• The tech guide and knowledge base:where you turn a repeat question into an answer the team can self-serve.

Requirements

What You Will Do

• Run the ticket queue.Own the tech and access tickets in Suptask: triage by urgency, resolve first-line issues, and escalate the deep ones with clear context.

• Do the system administration.Administer Google Workspace, Rippling, and seats and access across Monday and HubSpot, keeping everything accurate.

• Own onboarding and offboarding.Set new joiners up in the right systems on day one through Rippling, remove access cleanly when someone leaves, in step with People and Culture, and build basic Rippling automations so it runs reliably.

• Run access and license audits.Check regularly that the right people have the right access, flag over-provisioning and unused licenses, and make sure no leaver keeps a login.

• Handle the CRM tickets and train the team.Resolve the tool and CRM workflow questions, coach the team so they can self-serve, and keep the tech guide and knowledge base current so repeat questions drop.

• Fix at the root.When the same issue keeps coming back, fix the cause and document it, rather than closing the same ticket twice.

If a better tool would make support or setup faster, make the case and we will back it.

What You Need

• 1 to 3 years in IT support, helpdesk, service desk, or a systems administration role, resolving real user issues.

• Hands-on Google Workspace administration: accounts, groups, and access.

• Comfort with an HRIS or identity tool like Rippling for onboarding and access, or the aptitude to own it quickly.

• A genuinely tech-savvy generalist: you pick up new tools fast and are comfortable across a SaaS stack, not just one platform.

• Clear, patient communication: you explain a fix or a workflow to a non-technical colleague without making them feel small, and you can train a group.

• Accuracy with access, and ownership by default: you follow a ticket to resolution and close the loop.

• Cross-timezone comfort: your day runs on India hours with overlap into Australian time.

Nice to Have

• Rippling experience, or experience administering a comparable HRIS or identity platform.

• Experience building simple automations or workflows, in Rippling or a no-code tool.

• Experience with an ITSM or ticketing tool (Suptask, Freshservice, Zoho Desk, Jira Service Management, or similar).

• Familiarity with ITIL basics: incident, request, and access management.

• Experience supporting or administering a CRM like Monday.com or HubSpot.

• Experience in a remote-first company.

The Kind of People Who Thrive Here

The people who do well here see a gap and close it without being asked, holding the bar even when the clock is short. They give a direct read on the work in front of them, including when it's wrong, and when their own idea doesn't hold up, they say so and bring a better one. They build something that keeps running after they step back. Problems here don't show up on schedule or in the same shape twice, and they'd rather make the right call on limited information than let something break while they wait for a sign-off. That's the job. They name the blocker and the ask the moment they have it, on a call or a text, because decisions get made on the information you bring.

Contour's current cluster heads started as team leads. The path from operator to leader is real here.

What good looks like

• Nobody stays blocked:access, tool, and CRM problems get resolved fast, and people get back to work.

• Onboarding just works:a new hire has the right access on day one, every time, and leavers are removed promptly.

• Access stays clean:audits are current, the right people have the right access, and there are no stray logins or unused licenses.

• Repeat questions shrink:the tech guide and your training mean the same CRM questions stop filling the queue.

Benefits

Fully remote, anywhere in India. Compensation is competitive and benchmarked to the role and your experience,and we discuss it openly early in the process. From application to offer: a short screen, a practical IT support and systems administration task, a culture conversation with our People team, and a final interview with the VP of Global Enablement and Support, in about four weeks.

Apply with a CV and one paragraph on a recurring tech or access problem you made stop coming back: what it was, and what you changed, fixed, or documented so it stopped.

Originally posted on Himalayas