Why join us?

Mitti by SafetyCulture is 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 explicit vision and real ownership.

Big tech impact, without the big tech ick.

As a Software Engineer II in the Customer Identity and Access Management (CIAM) team, you deliver well-scoped services and features inside an architecture our Senior and Staff engineers set, and grow real depth in the identity domain as we modernise the platform.

You will work with a modern tech stack including Golang on the backend, identity and access technologies such as OpenID Connect and Security Assertion Markup Language (SAML), Amazon Web Services (AWS) , Auth0 and Kafka for infrastructure, and datastores such as PostgreSQL.

Key Responsibilities:

- Design, build and maintain backend services in a large-scale software-as-a-service platform, including distributed systems and data stores.

- Take ownership of features from inception to delivery, collaborating with product, design and other engineers.

- Build and maintain authentication and user lifecycle flows — signup, login, multi-factor authentication and single sign-on and user orchestration — and grow real depth in the identity domain.

- Contribute to safe, incremental migration off legacy identity services using feature flags, backwards compatibility and staged rollout.

- Treat security as part of the craft:



handle credentials and tokens carefully, and raise concerns early rather than working around them.

- Participate actively in code review, testing and the continuous improvement of our engineering practices.

- Make foundational capability easy for other engineering teams to consume, treating them as the customer of platform work.

- Demonstrate SafetyCulture's values — Think Customer, Open Honest Always, Better as a Team, Be Bold Bring Action.

Required Skills and Experience:

Technical skills:

- Solid capability in back-end programming languages and frameworks, with growing expertise in building scalable systems; prior experience with Golang is highly desirable.

- Practical experience owning and delivering software features end to end in a collaborative environment.

- Relational data modelling and PostgreSQL — sound schema design, safe migrations, and the ability to reason about indexing and query cost.

- Familiarity with cloud platforms such as AWS, including deploying, operating and debugging your own services in production.

- An understanding of distributed systems concepts — application programming interface design, retries, idempotency, timeouts and eventual consistency.

- Exposure to authentication, sessions or identity — login and signup flows,



token handling, or standards such as single sign-on, OpenID Connect, OAuth 2.0 or SAML. Depth here is welcome but not required; appetite to go deep is.

- Experience in multi-tenant systems where organisation and membership boundaries have to hold under scale and change.

- A commitment to writing clean, maintainable, well-tested code, and to giving and receiving code review well.

Behavioural skills:

- Self-direction on well-scoped problems — takes a defined problem and drives it to done without daily direction.

- Good judgement about when to push on and when to ask; raises risks and blockers early rather than burning a week.

- Works effectively with product, design and engineers on other teams, and can explain a technical constraint to someone non-technical.

- Builds for others, not just for self — cares whether what they ship is easy for the next team to consume.

- Comfort working in a domain that is being actively re-architected around them, and with priorities that shift.

Artificial intelligence skills:

- Uses artificial intelligence coding assistants as a normal part of the working day, and can critically evaluate what they generate for correctness, quality and security.

- Identifies practical opportunities to apply automation or intelligence within feature development.

- Minimum expected: hands-on daily use with informed scepticism. Not expected at this level: defining tooling, guardrails or adoption patterns for other teams.

We’re committed to building inclusive teams and cultivating a sense of belonging so our people can bring their whole authe

📌 Software Engineer II (Sydney)
🏢 Mitti
📍 Sydney