Software Engineer : Elekta

  

We continually look for motivated and skilled individuals who are interested in supporting our customers – healthcare professionals who use our products to help patients and their communities.

We currently have the following opportunity available - please contact us for more details!

RESPONSIBILITIES - AT ALL LEVELS

 

• ENSURE THAT ALL PRODUCTS ARE DEVELOPED IN ACCORDANCE WITH THE APPLICABLE PUBLISHED DEVELOPMENT PROCESS, INCLUDING CODING STANDARDS.
• ENSURE CHANGES ARE APPROPRIATELY COMPONENT AND SMOKE TESTED BEFORE MERGED TO TRUNK.
• ENSURE CHANGES ARE APPROPRIATELY INTEGRATION TESTED BEFORE VERIFICATION TESTING.
• RESOLVE SAFETY HAZARDS IN THE WORKING ENVIRONMENT. ESCALATE TO SOFTWARE SYSTEMS MANAGER IF UNABLE TO RESOLVE YOURSELF.
• RESOLVE SAFETY HAZARDS IN PRODUCTS UNDER DEVELOPMENT OR IN USE. ESCALATE TO PROJECT MANAGER IF UNABLE TO RESOLVE YOURSELF.
• SHOWS SELF-STARTING ABILITY TO ANALYSE AND PROVIDE PRACTICAL SOLUTIONS TO PROBLEMS.
• COMPLETE A WEEKLY TIMESHEET.
• MAINTAIN AN ORGANISED, TIDY, PLEASANT AND NON-OFFENSIVE WORKING ENVIRONMENT.
• ADDITIONAL ROLES AND RESPONSIBILITIES MAY BE ASSIGNED AS REQUIRED BY THE SOFTWARE SYSTEMS MANAGER.

ADDITIONAL EXPECTATIONS FOR ENGINEER LEVEL

 

TECHNICAL COMPETENCIES:

 

• WITH ADEQUATE INPUT FROM STAKEHOLDERS, DEFINE THE SOFTWARE REQUIREMENTS AT COMPONENT LEVEL.
• PROVIDE INPUT IN TO SOFTWARE DESIGN AT THE SYSTEM, SUBSYSTEM AND COMPONENT LEVELS.

BEHAVIOURAL COMPETENCIES:

 

• SHOW RESPECT TO ALL COLLEAGUES.
• BE A STRONG COMMUNICATOR BOTH WITHIN A TEAM AND ACROSS TEAMS.

ADDITIONAL EXPECTATIONS FOR SENIOR ENGINEER LEVEL

 

A TECHNICAL EXPERT WHO:

 

• WITH ADEQUATE INPUT FROM STAKEHOLDERS, DEFINES THE SOFTWARE REQUIREMENTS AT SUBSYSTEM AND COMPONENT LEVEL.
• COLLABORATES WITH OTHER FUNCTIONS AND COLLEAGUES, AS NEEDED, TO DRIVE THE SOFTWARE DESIGN AT COMPONENT AND SUB-SYSTEM LEVEL.
• IS A ‘GO-TO PERSON’ FOR QUESTIONS IN A TECHNICAL AREA, AT SUB SYSTEM AND COMPONENT LEVELS.
• HAS AN AWARENESS OF, AND ACTS UPON, BUSINESS AND TECHNICAL DRIVERS TO THEIR WORK.
• IS INVOLVED IN OTHER FUNCTIONAL ENGINEERING ACTIVITIES OUTSIDE OF PURE SOFTWARE (E.G. SAFETY ANALYSIS, TEST CASE REVIEW).
• DEVELOPS SKILLS IN BUILDING AND MAINTAINING EXTERNAL AND INTERNAL RELATIONSHIPS.
• HAS ABILITY TO TECHNICALLY LEAD A SMALL TEAM.

A ROLE MODEL WHO:

 

• WORKS LARGELY AUTONOMOUSLY.
• HAS A SIGNIFICANT DEGREE OF PERSONAL ACCOUNTABILITY.
• DEVELOPS RESPECTFUL AND TRUST BASED RELATIONSHIPS WITH COLLEAGUES.
• ASSISTS IN BUILD THE CAPABILITY OF OTHERS.
• HAS STRONG ORAL AND WRITTEN REPORTING AND COMMUNICATION SKILLS.
• CONTINUOUSLY IMPROVES THEIR OWN CAPABILITY.

ADDITIONAL EXPECTATIONS FOR PRINCIPAL ENGINEER LEVEL

 

A TECHNICAL LEAD WHO:

 

• DEFINES THE TECHNICAL DIRECTION FOR A SUBSYSTEM OR SYSTEM BASED UPON MULTIPLE FACTORS E.G. TECHNICAL, COST, BENEFIT TO CUSTOMER, TIME TO MARKET, ARCHITECTURE, AND RISK. THIS COULD BE DEMONSTRATED THROUGH THE ASSIGNMENT OF A HIGH LEVEL OF RESPONSIBILITY, SUCH AS A TCCB CHAIR OR OWNER OF KEY PRODUCT RELEASE DOCUMENTATION SUCH AS RELEASE NOTE OR DESIGN & MAKE PLAN.
• DEFINES THE SOFTWARE REQUIREMENTS AT ALL LEVELS.
• AS WELL AS BEING A TECHNICAL EXPERT IN ONE SUBSYSTEM IS WELL INFORMED IN OTHER SUBSYSTEM AREAS.
• CONTRIBUTES TO ORGANISATIONAL PLANNING AND MANAGEMENT.

A ROLE MODEL WHO:

 

• WORKS FULLY AUTONOMOUSLY, WHEN REQUIRED, AND PROACTIVELY REPORTS AND PRESENTS FINDINGS.
• IS HIGHLY RESPECTED BY COLLEAGUES AND STAKEHOLDERS.
• ACTIVELY DEVELOPS THE CAPABILITY OF OTHERS.
• ACTIVELY DEMONSTRATES CONTINUOUS IMPROVEMENT OF THEIR CAPABILITY.