Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Software Engineer II - Integrations

Safetyculture
CompanySafetyculture
CategoryEngineering
LocationSydney
RemoteHybrid
EmploymentNot stated
LevelNot stated
SalaryNot stated by the employer
Posted31 Jul 2026
Last verified3 Aug 2026
SourceEmployer ATS (ashby)
Applications are handled by the employer, not by us.Apply on the employer's site →
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 You'll join a team in our Foundations engineering group, working alongside engineers responsible for the architecture and implementation of integrations that move data into and out of the SafetyCulture platform. The team sits under a manager who also oversees billing and pricing work, since much of what we build supports our enterprise and higher-tier pricing packages. Over the next 12 months, the team expects to spend more time on AI Connectors (currently working with Model Context Protocol (MCP) servers), which let SafetyCulture's AI assistant interact with external systems, alongside work on the underlying authentication and authorization platform that supports our integrations. As an engineering team, we also maintain, operate and improve existing integrations that including 3rd-party HR systems, automations on Workato, and the SafetyCulture public API and webhook stack for external developers. WHAT YOU'LL WORK ON - Help design and build an ecosystem for MCP-based and other data connectors that extend our platform-level AI agentic capabilities into third-party and internal systems. - Contribute to the shared foundational platform that supports our integrations as they scale (we’re always thinking about things like authentication, permissions, rate limiting) . - Support and evolve our existing integrations, automations, webhooks, and public API. - Work with billing engineers and stakeholders on integrations that target enterprise-grade tiers, including usage-based billing and tiered rate limits. - Build with enterprise-grade fundamentals in mind, since our larger customers run complex environments and expect standards like single sign-on (SSO), System for Cross-domain Identity Management (SCIM), and solid data governance. - Take ownership of features from inception to delivery, working directly with stakeholders, product, and design. - Participate in code review, testing, and improving how the team works. - Keep user experience in mind, even in platform-facing work. ABOUT YOU We're less focused on specific technologies and more on how you think and operate. That said, a few things will help: MUST-HAVES - Solid experience in a strongly-typed backend language – Go is our primary stack, though we care more about strong fundamentals than specific Go experience. Comfort working in frontend and infrastructure when needed, with a backend focus overall. - Strong design patterns and distributed systems thinking – able to consider design trade-offs and business constraints with the team, and comfortable proposing a better approach rather than just working through assigned tickets. - Practical experience building third-party integrations of meaningful complexity, whether at work or in personal projects – for example, webhook handling, working with external APIs, or sync and Extract-Transform-Load (ETL) pipelines. - Thrives working with ambiguity, including some genuinely open-ended areas where you'll help define the direction rather than follow an existing one. - Experience using AI tools as part of your regular development workflow, and an interest in helping the team improve how it uses AI. GREAT TO HAVE - An understanding of authentication and authorization patterns – API key management at minimum, OAuth is great, and any exposure to SSO, Security Assertion Markup Language (SAML), or SCIM is a plus. - Direct experience with one or more enterprise business systems and orchestrators -
HOUSE ADYou found the opening. Now track it.Tracker, radar and AI drafts in one place.erioun.com →