HubSpot Developer (India)

Job Description This is a remote position. HubSpot Developer, India Remote (India) | Full-Time Also searched as: Senior HubSpot Specialist, RevOps Engineer, CRM Automation Specialist, HubSpot Solutions Architect What would you build if HubSpot had no native answer and the business needed one anyway? On a typical day you might rebuild a broken enrolment workflow before the sales team notices it is down, pull two systems together over an API in the afternoon, and sit with an operations lead before end of day to work out why a technically correct process is not actually getting used. 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 technical backbone of Contour's HubSpot instance: the person who understands both how the CRM works and why the business needs it to work that way. You report to the COO. The COO owns strategic direction for the CRM and the calls that touch the wider business. Everything inside HubSpot, the build, the architecture, the judgment calls on when to go native and when to write custom code, is yours. What separates a strong hire here from an average one comes down to two things. First, this person does not just build what is asked: they look at a workflow from the point of view of the sales, service, or operations person using it, and push back when a technically correct answer is not a practical one. Second, they are equally comfortable in HubSpot's interface and in a JavaScript file: when native functionality runs out, they write the custom code to close the gap instead of patching around it manually. You are joining an existing team of two, with room to grow as the work justifies it. Contour is scaling from 10,000+ students today toward 15,000+ next year, and the CRM is the system that has to hold as that growth hits. The workflows and integrations you build now are what the business runs on through that scale-up. Where the Work Lives HubSpot is the core of the job: objects, properties, associations, workflows, and pipelines, understood well enough to know when native functionality is the right call and when it is not. Custom code, mostly JavaScript inside HubSpot's Custom Code actions, is how you close the gaps native functionality cannot. APIs and webhooks are how HubSpot talks to the rest of the stack, and you are expected to build and troubleshoot those connections, not just the CRM in isolation. What You Will Do Own workflow build and architecture end to end. Take an ambiguous business requirement, break it into a robust technical solution, and see it through from build to testing to deployment. Write and maintain custom code where HubSpot's native tools fall short. Read, debug, modify, and write JavaScript independently, rather than defaulting to manual workarounds. Build and troubleshoot integrations. Work with APIs, webhooks, and authentication to connect HubSpot to the other systems it needs to talk to, and work out whether a failure sits with HubSpot, the other system, or the integration itself. Partner with the people who actually use what you build. Sit with sales, service, operations, or admin teams, understand what they need, and challenge a request when a technically correct answer is not a practical one. Own email implementation. Build conditional logic, personalisation, and property-based content into templates and modules, and troubleshoot why something is not rendering the way it should. Anticipate what breaks. Look for the duplicate record, the missing data, the edge case a workflow has not accounted for, before it causes a downstream problem. Investigate and fix, not just flag. When something breaks, find the root cause and propose the fix yourself. If a better tool exists for something we are doing manually, make the case and we will back it. Requirements What You Need Deep, hands-on HubSpot expertise: you know the objects, properties, associations, workflows, pipelines, and automation tools well enough to find the native solution before reaching for a workaround Strong coding ability, particularly JavaScript, and real comfort inside HubSpot's Custom Code actions A working understanding of APIs, webhooks, authentication, and JSON, and the ability to troubleshoot an integration when it breaksBusiness and process judgment: you can look at a workflow from the point of view of the person using it, and you push back when the technical answer is not the practical one The ability to take an ambiguous requirement and turn it into a robust, end-to-end technical solution, accounting for edge cases and failure states along the way Comfortable working across the India and Australia time difference The Kind of People Who Thrive Here The people who do well here do not wait for a fully specified brief. They ask the questions a spec did not answer, spot the edge case before it becomes an incident, and own a problem through to a real fix rather than escalating it halfway. They give direct feedback and expect it back. Contour's current cluster heads started as team leads. The path from operator to leader is real here. What Good Looks Like Diagnoses before building: finds the actual cause of a problem before writing a workflow to solve it, not just the symptom in front of them. Ships robust, not brittle: the workflows and integrations they build hold up against duplicate records, missing data, and edge cases, because they thought about those before shipping. Explains the why: a non-technical stakeholder can understand what a workflow does and why it works that way, not just that it works. Benefits Fully remote, anywhere in India. Compensation is competitive and benchmarked to the role and your experience. We discuss it openly early in the process. Apply with a CV and a short write-up of one HubSpot workflow or integration you built end to end: the business problem, the technical solution, and how it has held up since.