Event Manager, India

This is a remote position.

Event Manager, IndiaRemote (India) | Full-Time

Also searched as: Event Coordinator, Event Project Manager, Event Operations Manager, Project Manager

Could you deliver a flawless day for hundreds of students in a city you have never set foot in?

On a typical day you might walk a venue coordinator in Melbourne through your room and AV requirements in the morning, lock catering numbers against the live registration count and follow up two presenter confirmations with the academic team after lunch, and update the run sheet and brief the on-ground leads before you log off.

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, and this role sits with the events function that delivers Contour's event calendar across Australia.

A great event looks effortless to the family walking in. Someone has to be the reason it looks that way.

About This Role

You are the dedicated project manager behind Contour's events. The calendar runs from full exam simulation days for hundreds of students to revision lecture series selling thousands of tickets across Victoria and Queensland, with parent workshops and online sessions in between. You take each one from first brief to post-event review: timeline, venue, suppliers, registration milestones, comms deadlines, run sheet, event-day coordination, wrap-up.

You report to the Chief Marketing Officer (CMO). The CMO owns marketing strategy and the onshore event-day call when someone must be in the room. Everything else about how events get planned and delivered is yours. Marketing owns promotion, creative, and the registration campaigns. Academics owns session content and who presents it. Operations owns student data and check-in technology. On event day, teams on the ground in Australia execute in the room. The plan that ties them together, the dates they all work to, and the accountability for the day landing well: those are yours.

Two qualities separate a strong hire from an average one here. First, you think in dependencies: you see that catering numbers hang off registration close, which hangs off a reminder email, which hangs off a presenter confirming a title, and you fix the weak link three weeks early instead of discovering it three days out. Second, you follow up without souring relationships: you ask specifically, escalate when twice was enough, and people still enjoy working with you.

One more reality worth naming: you will rarely be in the room. You run events from India that are delivered in Australia, which means your plans, run sheets, and briefings have to be strong enough that the day runs without you standing in it.

You start as the sole dedicated event project manager, plugged into established marketing, academic, operations, and student experience teams. The calendar has grown faster than the way it is run: the biggest series now sell out lecture theatres, and until now no single person has owned how events get delivered. You build that playbook: the standard project plan, the run sheet format, the review loop that makes each event sharper than the last.

By the end of month three, you will have taken at least one major event from brief through delivery to review, built the project plan and run sheet templates the team reuses, and mapped the full calendar with owners, dates, and dependencies visible to everyone involved. What you build in those months will run every event Contour delivers after them.

Where the Work Lives

• monday.com: project plans and task ownership live here. Keeping status current is how a remote team knows an event is on track without asking.

• Google Sheets: run sheets, attendee lists, and event-day logistics. The people delivering the day work from your latest version, so document discipline is part of the job.

• Eventbrite: registrations and ticketing. You watch the numbers daily because rooms, catering, and comms decisions all key off them.

• HubSpot: student and guardian event comms run through it, alongside the lifecycle comms team.

• Slack: where cross-team, cross-timezone coordination happens, in writing.

What You Will Do

• Own each event end to end.Scope, timeline, suppliers, delivery, invoices, review: nothing about the event is someone else's problem.

• Build and drive the project plan.Every task with an owner, a date, and a dependency in monday.com. When something slips, you catch it while there is still room to re-sequence.

• Keep the full event calendar visible.Every event, owner, and key date in one place in monday.com, so anyone can see what's coming without asking you.

• Coordinate Marketing, Academics, and Operations.Registration launches, presenter confirmations, resource handovers, comms milestones: you set the dates and hold every team to them.

• Lock venues and suppliers.Room requirements, AV, catering, printing, signage: briefed clearly, confirmed in writing, and settled before their cutoffs.

• Run registrations as a control signal.Work with the digital team on ticket setup in Eventbrite, track numbers daily, and trigger capacity, waitlist, and extra-session calls in good time, because 850 registrations against 760 seats is a problem you want weeks of notice on, not days.

• Write the run sheet and brief the day.Minute by minute, with named owners for every stage, and briefings that leave the teams in the room certain of their part.

• Close the loop.Attendance data, feedback, supplier invoices, a short post-event report, and fixes carried into the next plan.

If a better tool exists for something we are doing manually, make the case and we will back it.

Requirements

What You Need

• 4 to 6 years delivering projects or events where you held the whole timeline, not a slice of it

• You have delivered work that depended on people who did not report to you, and it landed anyway

• Comfortable chasing and escalating. A quiet slip three weeks out becomes an event-day crisis, so persistence here is method, not personality, and the people you chase still want to work with you again.

• Writing that lands exactly as intended. Your documents are how a remote coordinator directs a live day, so they carry more weight than they would in an office

• Clean document and data habits: plans, lists, and versions other people can trust without checking with you

• Comfortable working across the India and Australia time difference, with the flexibility to be on deck when events go live

Nice to Have

• You have run an event remotely, delivered in a city or country you were not in

• Events for education, exams, or student and family audiences

• Hands-on with monday.com, Eventbrite, or HubSpot

• Negotiating with venues and suppliers

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.

What Good Looks Like

• Nothing slips silently:every at-risk date is flagged with a re-plan attached, not just an apology.

• The day runs off the document:venue and floor teams execute from your run sheet without needing you on the phone every ten minutes.

• Stakeholders answer you:your asks are specific, dated, and easy to action, so people respond instead of stalling.

• Every event beats the last:reviews turn into changes in the next plan, not a document nobody opens.

Originally posted on Himalayas