Automation and Integrations Specialist
Hands-on with Make.com and Google Apps Script, delivering internal automations and small tools, comfortable using AI, strong product sense, safe maintainable builds, cross-timezone collaboration.
This is a remote position.
When a team is drowning in a manual, repetitive process, do you want to be the person who quietly automates it away by the end of the week?
On a typical day you might wire up a Make scenario that takes a form submission and files it correctly across Drive and Monday, patch an Apps Script that runs the printing operations, and use AI to prototype a small internal tool that saves a team an hour a day.
About Contour
We started in 2020with a handful of students and a belief that great education should not be out of reach. Today we operate across three brands with8,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.
When the internal plumbing works, hundreds of people move faster and students feel none of the friction. That plumbing is what you build.
About This Role
You build the internal tools and automations that make Contour's teams faster. This is an enablement function: engineering owns the core product and anything that touches money or student data, while your team builds the internal, non-mission-critical tools and automations that offshore and onshore teams use every day. You work mostly in Google Apps Script, Make.com, light code, and AI, shipping quick, practical systems rather than long-term product.
The work is real and already running. Think of the automations behind the resource development pipeline, the class schedule and printing operations, and the Apps Script printing spreadsheet. You build new ones like these, improve the existing ones, and use AI to ship faster, which is not just allowed here, it is how the team works.
The bar that separates a good hire from a great one is real-world product and business sense. The best person here understands how Contour actually works, so the tool they build solves the real problem, not just the one that was described in a message. You scope the problem with the team first, then build. You also build safely: the architecture has to be right, SSO, server-side versus client-side set up properly, no exposed API keys, so nothing can leak sensitive data. You report to the VP of Global Enablement and Support. You do not build the LMS or heavy, long-term student-facing features; that is engineering's patch, and you flag anything that belongs there.
By the end of month three, you are shipping automations and small tools independently, the teams you build for are visibly faster, your builds are safe and documented, and you are the person who hears a manual process described and already sees how to automate it.
Where the work lives
Google Apps Script and Workspace:the scripts and spreadsheet tools that run inside Contour's Google environment.
Make.com:the automation scenarios that move and transform data between systems.
Monday.com and Google Drive:the systems your automations read from, write to, and keep in order.
AI (Gemini and similar):how you prototype, build, and ship faster than a manual build would allow.
Requirements
What You Will Do
Automate manual processes.Build Make scenarios and Apps Script automations that remove repetitive work from teams across Contour.
Ship small internal tools.Prototype and build practical tools, AI-assisted, that save real time, then get them into people's hands.
Improve what exists.Maintain and extend the automations already running (resource pipeline, class schedule, printing operations) without breaking them.
Scope the real problem.Talk to the team, understand how the work actually happens, and build for the real need rather than the first description.
Build safely.Keep architecture sound, SSO, no exposed keys, no sensitive data exposure, and document so others can maintain what you ship.
What You Need
You have delivered working automations or internal tools in a professional setting. Years do not matter, evidence of shipped solutions does.
Hands-on with Make.com, Google Apps Script, or both.
Comfortable using AI to build and ship faster.
Strong real-world product and business sense: you understand a process well enough to automate the right thing.
You can scope a problem with a team and turn it into a practical, working solution.
Care for safe, maintainable builds, and cross-timezone comfort with overlap into Australian time.
Nice to Have
Light coding in JavaScript.
Experience with Monday.com, Google Workspace administration, or other no-code and low-code tools.
Background in edtech or a fast-moving operations environment.
The Kind of People Who Thrive Here
The people who do well here get a genuine kick out of deleting manual work. They are pragmatic and product-minded, they use AI to move fast, and they still care that what they ship does not fall over. They would rather understand the process and build the right thing once than ship the literal request and watch it miss. As the function grows, the strongest builders move into the developer track or take ownership of larger internal systems.
What good looks like
Manual work disappears:processes that ate hours now run themselves.
Tools get used:what you ship is adopted, not abandoned.
Builds are safe:sound architecture, no exposed keys, no sensitive data at risk.
You solved the real problem:you scoped it right, so it actually landed.
Benefits
Fully remote, anywhere in India. Your day runs on India hours with overlap into Australian business time. Compensation is competitive and bench marked to the role and your experience. We discuss it openly early in the process.
Apply witha CV and one paragraph on something you automated or built in a professional setting that saved real time: what the problem was, what you shipped, and how.