At a Glance
- Tasks: Join a small team to build and scale CurieOS, our AI operating system for engineering.
- Company: Orbital Industries, a cutting-edge AI Industrial company transforming physical product production.
- Benefits: Competitive salary, inclusive culture, and opportunities for rapid career growth.
- Other info: Collaborate with top researchers and engineers in a dynamic, innovative environment.
- Why this job: Shape the future of AI in engineering and see your impact in days.
- Qualifications: Experience in cloud systems, backend services, and a passion for AI technology.
The predicted salary is between 75600 - 92400 £ per year.
Orbital Industries is an AI Industrial company, with frontier AI embedded at every step in the production of critical physical products - from creating advanced materials to engineering and manufacturing. Every Orbital Industries product is developed using CurieOS, our AI operating system, uniting AI-automated hardware engineering with AI-designed material science to achieve breakthrough real-world performance. We also offer CurieOS to our customers and partners, extending the same platform and workflows that power Orbital Industries to their own teams and products. We have an ambitious mission and need excellent people in all our teams - AI research, operations, advanced materials, mechanical engineering, chemical engineering and manufacturing.
Working at Orbital Industries means working in vertically integrated teams across the full stack, from molecules to manufacturing. We're looking for people who have a love of physical technology, curiosity in AI and a desire to learn.
The role of Physical engineering is one of the hardest domains for AI. Designs have to meet standards, calculations must be deterministic and checkable, and a wrong number can end up in a power system or a data centre. CurieOS is built to let agents do real engineering work and to show exactly how every output was produced. The platform team builds the foundation that every workflow, agent and product on CurieOS depends on, and runs it in production for people who need to trust it. Your work sets the floor for how reliable our AI is, and the ceiling for what it can do. This is a small team, and you'll shape what we build as well as how. You'll see the results of those decisions in production within days.
If you want a narrow, well-defined slice of a large system, this isn't the role. If you want to own a platform while it scales, it is.
How we work: We build with agents, not just for them. Everyone on the team works with the latest frontier models and coding agents every day, and token budgets won't hold you back. Part of what we build is CurieOS's ability to work on itself: triaging defects, proposing fixes and opening pull requests for engineers to review. So engineers here spend more of their time on design, review and judgement, and less on typing. If you already work this way, you'll feel at home. If you want to see how far it can go, this is the place to find out. You'll also work alongside our AI researchers, turning cutting-edge research and evals into things that run in the platform and in production.
What you'll work on first: In your first six months you'll work across the parts of CurieOS that customers have to be able to trust. Like everyone on the team you'll touch most of them, and go deepest where your interests take you:
- Tenancy, isolation and identity: How CurieOS keeps each customer separate, from shared multi-tenant accounts to dedicated single-tenant deployments. That covers data isolation, SSO and access control. You'll also be an engineering voice in customer security reviews.
- Release and production: How changes get to production safely: release gates, staged rollouts and rollback, automated smoke tests, on-call and incident response. We ship often, and you'll build what lets us keep doing that without breaking what customers rely on.
- Agent quality in production: Measuring how well agents perform on real customer workflows, working with our researchers to bring the latest evals into the platform, and using those measurements to decide what is good enough to release.
- Observability and cost: Knowing the platform is healthy and what it costs. That means SLOs, tracing and alerting, plus cost telemetry and usage metering for every workflow and every customer, so we can see where model and compute spend goes and make deliberate choices about it.
- Infrastructure and deployment: One standard for how CurieOS is deployed, configured and upgraded in each environment, across our own cloud accounts, GPU capacity and customer-dedicated deployments.
Where the platform is going: Once those foundations are solid, there's a lot to shape next:
- Traceable results: Provenance for every number an agent produces: which inputs, tools, models and versions went into it, so our users can check it and sign it off.
- Agent runtime and context: How agents plan, call tools, manage context across long-running work and hand off to people at the right moment.
- Durable workflows: Orchestration that survives failures, retries and runs lasting hours, mixing agent steps with deterministic calculations.
At Staff level, you'd set technical direction across these areas, not just within one. You'd own one of them end to end, run the design reviews that our research and forward deployed teams build on, make the architecture calls that are hard to reverse, and help shape how we hire and grow engineers.
Our stack: Python services on Kubernetes, running on AWS plus specialist GPU clouds for heavy compute. Strong engineers from Go, Kotlin, Java or a comparable stack will pick up the language quickly. What matters more is that you've run real systems in the cloud. You'll have most of these:
- Designed and built backend services that other teams or customers relied on, and made the key decisions yourself.
- Owned a system in production after it shipped: the cloud infrastructure it ran on, on-call, incidents, how changes went out, and the monitoring that told you it was healthy.
- Built and run something where LLMs do real work for real users, and dealt with the cost, latency and quality trade-offs that come with it.
- Used coding agents heavily in your own work, with opinions on where they help and where they break.
- Led a project end to end, made trade-offs you can explain, and raised the bar for the engineers around you.
Bonus points:
- Shipped software to external enterprise customers: SSO, tenant isolation, per-customer deployments, security reviews.
- Run infrastructure as code at scale, or GPU workloads across more than one cloud provider.
- Helped a system or a company through a scaling phase, such as a platform going from internal use to many external customers.
- Worked closely with researchers, scientists, engineers or other domain experts and built what they actually needed.
- For Staff: a track record of setting technical direction beyond your own team, such as architecture other teams adopted, a migration you led across several teams, or engineers you've grown into senior roles.
You don't need a background in materials, chemistry or engineering. You'll pick up the domain from the people who have it.
Why Orbital: Orbital Industries is an AI Industrial company. We put frontier AI into the making of critical physical products, from advanced materials to data-centre engineering. Our research team works at the cutting edge, from universal interatomic potentials to GPU-native simulation, and we turn that research into tools engineers use every day. CurieOS is the platform that brings it together: the AI operating system the whole company runs on, which customers are starting to depend on for their own engineering work too. Orbital is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees.
Senior/Staff Software Engineer, Platform employer: Orbital
At Orbital Industries, we pride ourselves on being an exceptional employer that fosters a culture of innovation and collaboration. Our commitment to employee growth is evident through hands-on opportunities in cutting-edge AI technology and a supportive environment that encourages continuous learning. Located at the forefront of industrial AI, we offer unique advantages such as working with world-class teams and contributing to impactful projects that shape the future of manufacturing.
StudySmarter Expert Advice🤫
We think this is how you could land Senior/Staff Software Engineer, Platform
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Orbital or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Orbital.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Orbital.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Orbital that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Senior/Staff Software Engineer, Platform
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Orbital.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Orbital and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at Orbital
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Orbital uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.