AI Solutions Engineer at safetyculture-2

Why join us? We’re a global tech company,  just not the kind you’re picturing. Sure, we’ve got catered lunches, team events, cool merch, and yes... dogs in the office. But that’s not why people join. Our team of nearly a thousand people wakes up every day to make our product and our customers’ lives better. At SafetyCulture, you’ll hear “yes, let’s give it a shot” more often than “that’s not how we do things here.” People join because we’re building tools that make work better for the 3 billion people who keep the world moving - factory floor operators, baggage handlers, truck drivers, servers, store assistants. The ones who make things happen. We’ve got the scale and innovation you’d expect from big tech. The difference? No endless layers of sign-off. No corporate theatre. Just smart, experienced people solving real problems fast . The scale is big. But the ownership’s personal. Every full-time team member gets equity - real skin in the game. When we grow, you do too. We’re not perfect, no company is. But this next chapter of our growth is about scaling with intelligence, not just size - fueled by operational maturity, a clear vision, and a strong focus on AI.  This is big tech impact, without the big tech ick. If that excites you more than it scares you, you’ll fit right in. Key responsibilities Platform and infrastructure • Own the AI Ops platform layer – containerised services, authentication layers, hosting, and deployment pipelines – so Business Unit engineers can build and ship reliably without depending on Platform Engineering for every component • Build and maintain custom MCP (Model Context Protocol) connectors and integration components that multiple teams can rely on without duplicating effort – built to security and reliability standards from the start • Implement CI/CD pipelines, automated testing, and deployment workflows for platform components • Turn technical processes into easy-to-use skills for non-technical users, for example, building a governance-check skill that validates submissions before IT publishes them to the business Architecture and technical decisions • Collaborate with the AI Ops Engineer to take conceptual architecture into detailed, implementable technical designs, then author Architecture Decision Records (ADRs) that document those decisions for new components and integration patterns • Run Requests for Comment (RFCs) for cross-cutting proposals (e.g. skill governance and distribution): gathering input, driving consensus, and documenting outcomes • Evaluate build-vs-buy decisions, factoring in maintenance burden, vendor lock-in, and platform alignment Governance and automation • Co-own the technical implementation of skill governance with the broader AI Ops team: building and scaling the review, publish, and distribution pipeline so it handles company wide volume without becoming a bottleneck • Progressively automate governance steps – replacing the highest-friction manual work first – so the review-to-publish pipeline scales without adding headcount • Implement adoption tracking and usage instrumentation so the team can measure ROI, without necessarily owning the ongoing analysis • Define and enforce platform standards: connector patterns, skill composition rules, metadata schemas, through tooling rather than process overhead Business Unit engineer guidance • Act as the go-to peer consultant for Business Unit engineers – unblocking them on auth, hosting, and solution design before they build the wrong thing, and raising the quality of their builds over time • Co-own application maturity with Business Unit engineers (the subject-matter experts for their domains): guiding them in the right way to take solutions from prototype through to production, and ensuring standards are met • Create reusable patterns, templates, and reference implementations that lower the barrier for Business Unit engineers to build well, drive regular collaborative discussions with the Business Unit engineers to keep the community connected and encourage partnering on common requirements PDE community • Bridge PDE best practices and tooling into the Business Unit context – so the AI Ops platform benefits from what engineering is already building, rather than reinventing it Required Skills & Experience Required skills & experience You have built and operated production systems end-to-end, not just contributed to them. You make sound architectural decisions without needing sign-off on every call, move fast without breaking things, and have the judgment that only comes from having shipped at pace and owned what breaks. This role won’t slow down while you find your feet. You’ll be expected to drive from day one. Technical • Expert in at least one of Python, TypeScript, or Go, and comfortable picking up the others • Strong understanding of containerisation (Docker as a minimum): able to design, build, and debug containerised services confidently • Experience with authentication and authorisation systems: OAuth, service accounts, API keys, Role-Based Access Control (RBAC) • Solid experience with a major cloud provider: deploying services, managing infrastructure, and operational monitoring • Proven experience with CI/CD principles and GitHub-based automation (Actions, webhooks, branch protection) AI and platform • Proven hands-on experience building Large Language Model (LLM)-powered applications in production: agents, skills, or AI-native workflows. Experience with the Claude/Anthropic ecosystem is a strong advantage; deep experience with any major AI provider is what matters. • Solid understanding of MCP (Model Context Protocol) or similar AI integration patterns: how AI connects to external systems and what good connector design looks like • Experience with skills-based or plugin-based AI architectures: composable, reusable components that serve multiple users or teams Behavioural • Works with an AI-first approach to development and documentation, using AI tools as a core part of your workflow, not as an afterthought • Collaborates strongly with other Engineers and stakeholders, building strong relationships with them, with a win-win mindset • Produces clear engineering documentation – design rationale, implementation patterns, technical proposals – and treats it as a tool for alignment and continuity, not overhead • Strong sense of ownership without needing authority. Influences through architecture and quality, and can set standards for engineers who don’t report to you • Builds for others. Designs systems with internal consumers in mind – balancing what Business Unit engineers need right now against platform integrity and long-term maintainability • Bias toward shipping over perfecting • Navigates ambiguity well. This is a new function in a fast-moving space. You break down undefined problems, make a call, and adjust as you learn • Self-directed and autonomous. You don’t need daily oversight to stay productive. You set your own priorities, know when to escalate, and own your outcomes • Curious and constantly learning. You stay current with the AI ecosystem, experiment with new tools and patterns, and bring what you learn back into the platform • Solution-oriented. When you hit a blocker, you come with options, not just the problem. You keep things moving We’re committed to building inclusive teams and cultivating a sense of belonging so our people can bring their whole authentic selves to work each day. We seek to make reasonable adjustments throughout our recruitment process to create an even playing field for all candidates. Thanks to the tireless efforts of the entire SafetyCulture team we’ve built an incredible culture which has seen us recognised as a Best Place to Work in Australia, the US and the UK . Even if you don't meet every requirement listed in the ad, please consider applying for this role. We prioritise inclusion and value individuals with potential over a checklist of qualifications. Don't rule yourself out, hit that apply button if this job resonates with you. You can find out more about life at SafetyCulture via Youtube, Twitter, Instagram and LinkedIn. To all recruitment agencies, we do not accept resumes or partnership opportunities. Please do not forward resumes to SafetyCulture or any of our employees. We are not responsible for any fees associated with unsolicited resumes.