GTM Engineer
Safetyculture
| Company | Safetyculture |
| Category | Engineering |
| Location | Sydney |
| Remote | Hybrid |
| Employment | Not stated |
| Level | Not stated |
| Salary | Not stated by the employer |
| Posted | 29 Jul 2026 |
| Last verified | 30 Jul 2026 |
| Source | Employer career page (ashby) |
Description
Why join us?
We're a global tech company, just not the kind you're picturing. Our almost 1,000-person team builds tools that make work better for the three billion frontline workers who keep the world moving. We've got big tech scale, without the sign-off layers or corporate theatre. Every permanent team member gets equity, so when we grow, you do too. This next chapter is about scaling smart, powered by AI, a clear vision and real ownership. Big tech impact, without the big tech ick.
THE ROLE
This role exists to eliminate friction from the sales and customer success process by embedding deep technical and AI capability directly into the Go-to-Market (GTM) team. The GTM Engineer identifies pain points holding salespeople back, builds intelligent automations that remove manual toil, and drives meaningful AI adoption across the GTM organisation — turning Marketing Technology’s tools and ideas into things salespeople actually use every day.
KEY RESPONSIBILITIES
- Embed within the Sales and Customer Success teams to uncover and prioritise friction points, translating real workflow pain into concrete technical solutions with measurable impact.
- Design, build, and deploy automated outbound capabilities that enable the sales team to engage prospects at scale, with higher quality and less manual effort.
- Drive AI adoption across the GTM team by building practical, production-ready AI powered tools and workflows that become embedded in day-to-day sales and customer success activity.
- Own the technical integrations between GTM tools — including Salesforce and Redshift — ensuring salespeople have clean, timely, and actionable data without needing to go looking for it.
- Build and maintain JavaScript-based automations and lightweight applications that solve specific GTM workflow problems quickly and reliably.
- Establish a continuous feedback loop with the sales and customer success teams, iterating on tools based on real usage rather than assumptions.
- Contribute to the Marketing Technology team’s broader GTM innovation agenda, bringing a builder’s mindset to identifying where technology and AI can change how the GTM org operates.
WHAT YOU'LL NEED
Technical Skills
- Proven ability to build and deploy automation and integration solutions across enterprise GTM tech stacks, with hands-on Salesforce (CRM) experience — including custom objects, flows, APIs, and data management.
- JavaScript development capability sufficient to build lightweight applications, custom integrations, and browser-based tooling that solves real GTM workflow problems.
- Experience querying Amazon Redshift or a comparable cloud data warehouse to extract, transform, and surface data that powers automation logic and sales insights.
- Ability to design and ship AI-powered workflows using modern large language model (LLM) APIs — particularly Anthropic’s Claude — including prompt design, tool use, and reliable production deployment.
- Enough understanding of sales and customer success processes to independently identify root causes of workflow friction and scope solutions without heavy business analyst support.
Behavioural Skills
- Walks into ambiguous situations and finds the real problem — listens carefully to what salespeople say is slowing them down, then digs to understand what’s actually causing it, and comes back with a clear proposal rather than more questions.
- Builds for the person using it, not for themselves — measures success by whether salespeople actually adopt and rely on what they’ve built, not by the technical elegance of the solution.
- Bias for action — ships working prototypes quickly, puts them in front of real users, and iterates based on feedback rather than over-engineering before launch.
- Comfortable working across technical and non-technical boundaries — can discuss API design with an engineer in the morning and explain the same solution to a sales rep in the aftern