🚀 Looking for your next role? Join Fraxion, a high-growth SaaS company with a dynamic, collaborative culture and global reach, with offices in South Africa and the USA.
Fraxion is a leading provider of cloud-based procure-to-pay software, helping mid-market organizations take a proactive approach to spend management through intelligent, easy-to-use solutions. For over 20 years, we’ve helped finance teams worldwide gain greater visibility into spending, strengthen financial controls, and streamline business processes through innovative technology. Join a collaborative, forward-thinking team that's passionate about delivering exceptional software and customer experiences.
The role, technology, and working environment
Our engineering team is based in Cape Town, and our platform is hosted on Microsoft Azure, with build and release pipelines managed through Azure DevOps.
Fraxion serves customers across the USA, UK, and South Africa. The role therefore requires some working-hour overlap with our US-based customers and teams, particularly in the late afternoon. We follow a hybrid working model, with two days per week in the office.
This is the single infrastructure seat within the team, with end-to-end ownership of the platform that supports our products. The role reports directly to the CTO.
Job Title: DevOps Engineer
What you will do
Own and improve the Azure DevOps build and release pipelines that deploy our products through development, test, UAT and production
Keep the Azure hosting platform healthy, secure and correctly sized across our internal and production subscriptions
Automate deployment and environment tasks so a release is repeatable and needs no manual work
Manage secrets, certificates and access per environment, and keep production properly separated from the other tiers
Monitor the platform, set up alerting, and lead the technical response when a production problem occurs
Support the development and QA teams with environments, build failures and deployment problems
Track and reduce cloud cost, and remove waste in non production environments
Apply best practice and secure configuration standards, and document the platform you build
Use AI assistants as part of normal delivery, and hold generated scripts, pipelines and configuration to the same review, test and security standard as anything you write by hand
How we work with AI
We are not experimenting with AI. The team works with AI assistants every day and we expect you to do the same from week one.
For this seat that means pipeline work, scripting, infrastructure configuration and log analysis, not only application code. We want to see your method. Where you hand work to the assistant and where you do not, and how you check what comes back before it touches an environment. Generated configuration gets the same review and security standard as configuration you write yourself, and production is where that matters most.
If you are still working out how to work this way, this is not the right time for you to join us.
What we are looking for
5+ years in a DevOps, infrastructure or platform engineering role, SaaS preferred
Microsoft Azure, hands on: App Service and service plans, resource groups, storage, Key Vault, Entra ID
Azure DevOps Pipelines: YAML builds, multi stage release pipelines, environments, approvals, variable groups and service connections
Scripting with PowerShell. Bash or Python is also useful
Running multiple environments from development through to production, including promotion between tiers, and secret and certificate handling per environment
Monitoring and alerting with Azure Monitor and Log Analytics, and log analysis for fault finding
Git and branch policies: build validation, required reviewers and linked work items
Production support: incident response, root cause analysis and preventive follow up
Scrum or Agile
Able to work as the single infrastructure person in a mid sized engineering team
Daily use of AI assistants in your own infrastructure, pipeline and scripting work, and the ability to show how you use them, how you review the output and where you do not trust it
Nice to have
Infrastructure as code with Bicep, Terraform or ARM templates. We do not use it today, so the ability to introduce it is valuable
GitHub Actions
Jenkins
Networking: virtual networks, subnets, private endpoints, DNS, firewalls and VPN
Containers: Docker, Azure Container Apps or Kubernetes
Microsoft SQL Server operations: backups, restores and basic performance work
Hosting and troubleshooting .NET applications
Security and compliance exposure, for example SOC 2 or ISO 27001
Cloud cost optimisation
Microsoft Azure certification
Hours and on call
Flexible working hours, with late afternoon availability when we overlap with the USA offices. There is no on call rotation.
Our interview process
A 30 minute conversation with Marius (Chief Technology Officer) and Radia (HR Manager)
A technical session with Marius and Stephen (IT Manager)
A second conversation with Marius and Stephen
References, then offer
We move fast when we are convinced. You will hear from us either way.