Elekta
Principal Systems Architect

How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Are you a current Elekta employee?
Please click here to apply through our internal career site Find Jobs - Elekta.
We don’t just build technology. We build hope for everyone dealing with Cancer.
Elekta is shaping the standard of care, together with healthcare providers, by developing precision radiation medicine that brings advanced radiotherapy into routine clinical practice. Our solutions support consistent, efficient and personalized care, addressing evolving patient needs. Through adaptive radiotherapy, precision treatment delivery and integrated workflows, Elekta supports care teams across a range of clinical settings. Each year more than 2 million patients are treated using Elekta solutions across over 130 countries. Elekta is headquartered in Stockholm, Sweden, with over 4,000 employees and offices in more than 40 countries. The company is listed on Nasdaq Stockholm. For more information, visit elekta.com.
Description
The Principal Systems Architect has technical software responsibility for one or more product software systems or subsystems. They are responsible for the product architecture and leading the design with the engineering teams, which allows successful implementation of projects to meet the business needs; including time, cost, quality, and productivity. This is done in conjunction with supporting the Senior Principal Systems Architect or Chief Architect for the solution area, who has the overall technical authority.
Responsibilities
The Principal Systems Architect responsibilities include (but are not limited to):
- Take technical responsibility for system or subsystem architectures, ensuring they are designed to best practice. Ensure that business goals of modularity, maintainability and efficiency are continuously met. Develop and document the architecture and high-level designs to a level of detail that allows the designs to successfully go through detailed design and development.
- During the early design phase; identify and resolve critical technical, performance, usability, reliability, cost and timescale risks within the proposed solutions by modelling, prototypes or feasibility studies as required.
- Lead the direction of system & subsystem development across teams, domain and release trains. Ensure software design is in line with the architecture and best practice. Review designs and new ideas of others as needed.
- Creates and approves technical requirements and non-functional requirements based on product requirements.
- Produce software technology and tools roadmaps for the domain area. Be involved in the sourcing and deployment of these.
- Develop a great breadth and deep level of understanding of the technical domain and support engineers to develop theirs too. Share this technical expertise, knowledge and experience with project teams and functional areas.
- Maintain a good high-level awareness of architecture, technology, tools, applications, and general vendor and industry trends. Communicate and liaise with Product Management, Service, Research and other stakeholders to maintain awareness of business and product strategy, clinical advances and competitor developments.
- Deploy Elekta and departmental technical strategies to engineers.
- Maintain awareness of and comply with the relevant Elekta quality system processes. Raise awareness of relevant systems engineering related process to the engineers as needed.
- Maintain awareness of regulatory changes to ensure proposed designs meet relevant safety, regulatory and performance requirements. Reduce safety risks through involvement in safety analysis. Communicate relevant project risks to the group to drive continuous improvement of the tools and processes.
- Involvement in audits and resolving non-conformances.
- Be open, honest and respectful with your opinion sharing technical insight to innovate and improve our products and ways of working.
- Maintain a professional approach, attending and contributing to team meetings as required, and completing a timesheet.
- Additional roles and responsibilities may be assigned as required.
Reasons to use Rodeo
I’m in my final year doing Economics and I don’t know whether to apply for grad schemes now or do a masters first. What do you think?
Honest answer — it depends on where you want to end up. A lot of top grad schemes (Big 4, civil service, banking) don’t need a masters. Let’s look at the ones you’d be competitive for now, and we can decide if a masters actually adds anything.
Also worth knowing: most autumn 2026 applications are open now. Timing matters more than you think.
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
Graduate Consultant — 2026 Scheme
Why you're a good match
StrongYour economics background and your summer at a regional bank line up with what PwC looks for on the consulting scheme. Applications close in four weeks.
See breakdownIt searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Why you're a good match
You’ve got the grades and the economics background, and your bank internship is exactly the experience this scheme looks for. Apply soon — deadlines close within the month.
Experience fit
Your summer at the bank plus your econometrics coursework map directly to the day-one responsibilities on this scheme — client modelling, market briefings, and deal support.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
Authorities


Get help with your application
Your very own career expert that helps elevate your application to the next level.
- Perform the role of Technical Authority, being the final decision maker on technical matters within the system or subsystem. (Chief Architect or Senior Systems Architect is the overall product technical authority.)
- Architectural and design decisions for a system or sub-system.
Relevant Knowledge, skills and competencies
All of the following:
- Degree in an engineering discipline.
- Fluent in English with strong communication skills.
- Strong leadership, organisation and interpersonal skills and experience.
- Structured and professional approach to engineering.
- Effective problem solving and systems thinking.
- Understanding and experience of Agile & Scrum methodologies
- Knowledge and understanding of product development disciplines practices, projects, tools, technologies, and techniques.
- Object oriented software design.
- Service or micro-service based architectures.
- Enterprise Architect, SysML, UML.
- Hands on development experience (C#/.NET).
- Working in a regulated safety or security environment.
One or more of the following skills:
- Knowledge of medical technology and the regulatory framework.
- Azure DevOps/Git.
- User interface design and development.
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Location