Senior Platform Engineer
About the role
- Working on cutting-edge distributed systems and backend platforms
- Opportunities to lead technical initiatives and mentor engineers
- Contributing to impactful projects that optimize supply chains and reduce emissions
- Greenfield development with—multiple MQs, legacy microservices, IoT data ingestion, and 600+ rulesets to be replatformed
- High volume data environment: 30M+ data points from detectors
- What type of experience does the right candidate have:8+ years in software engineering with a strong focus on distributed systems and backend platforms
- Proficiency in languages such as Java, Go, or PythonStrong understanding of cloud platforms (AWS, Azure, or GCP) and container orchestration (Kubernetes)
- Experience with messaging systems (Kafka, RabbitMQ) and data stores (SQL/NoSQL)
- Hands-on experience with CI/CD pipelines, monitoring tools, and incident management
- What the responsibilities are of the right candidate:
- Design, develop, and operate distributed backend platform components
- Enable automation of critical workflows across operations
- Implement predictive analytics and AI-driven logistics for smarter asset utilization
- Optimize supply chains through real-time visibility and decision-making
- Drive sustainability initiatives through fuel efficiency and reduced emissions
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
