Principal Systems Architect

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 re-quired.
• 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 an 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.

Authorities

• Perform the role of Technical Authority, being the final decision maker on technical matters within the sys-tem 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.