• Architect and build HubSpot solutions for US pod clients: data migrations, CRM implementations, custom UI extensions, workflows, website development, and API/systems integrations.
• Write clean, maintainable code across Huble's backend stack, and own your own bug fixes and feature builds end to end.
• Review API documentation to assess feasibility before committing to a scope.
• Identify technical risk in a proposed solution early and propose alternatives, rather than surfacing problems after a build has started.
• Provide code review and QA on US pod work, including work handed over from or to the South Africa team.
• Maintain strong working knowledge of HubSpot's platform, APIs, and native capabilities, with a focus on where custom development is genuinely needed versus where native functionality already solves the problem.
• Act as the client-facing technical expert during pre-sales, discovery, and scoping calls in US business hours.
• Own technical validation of scope for US pod work: translate business requirements into accurate specifications, development hours, and cost estimates.
• Partner directly with Solutions Architects on scoping, joining early rather than reviewing after the fact. Recurring feedback from the US pod is that requests reaching development are often missing detail. Closing that gap before it becomes a build problem is a core part of this role.
• Give Sales and Account teams a straight, credible technical read during prospecting and deal-scoping conversations, including where something isn't feasible or needs to be scoped differently.
• Be Huble's live technical presence for US clients: attend client calls, escalations, and discovery sessions during US hours.
• Provide timely troubleshooting and technical response on live issues without needing to wait for South Africa hours to overlap.
• Build direct technical credibility and trust with US clients through consistent, visible presence, not just delivered output.
• Follow Huble's Back End Development standards and deployment process in full.
• Join Back End team routines (stand-ups, architecture discussions, knowledge-sharing) on a regular cadence, even where full daily overlap isn't possible, to stay current with shared standards and avoid drifting into ad hoc practices.
• Document scope, decisions, and handovers clearly and consistently.
• Escalate to the Head of Back End Development when something is outside your judgement call, rather than resolving it alone and reporting it after the fact.
• Feed learnings from US-specific client work back into Huble's broader Back End practices.
