met-jobs@lists.reading.ac.uk
March 2015
Message 32

[Periods|Index by:DateThreadSubjectAuthor|Date:PreviousNext|Thread:(Previous)(Next)|List Information]

[Met-jobs] Met Office job vacancy - Unified Model Development Software Engineer

From "Verney, Fiona" <fiona.verney@metoffice.gov.uk>
To "met-jobs@lists.reading.ac.uk" <met-jobs@lists.reading.ac.uk>
Date Tue, 10 Mar 2015 11:28:12 +0000

Unified Model Development Software Engineer

Location: Exeter
Region: South West
Job number: MO-CM00122
Salary: per Year Min 21675.00 Max 29100.00 In GBP
Agreement Type: Permanent

Salary Information:  
£21,675 and for exceptional candidates up to £29,100 + competitive benefits including Civil Service Pension


Background:

This is a great opportunity to join a world-class scientific organisation,  
with some of the largest supercomputers in the UK, to work on developing our scientific software.  
             
The Met Office undertakes research in weather and climate modelling.  
This research enables the delivery of high performance production models to meet the needs of a wide range of customers, including the general public, government bodies and commercial companies.   
 
A core component is the Met Office weather and climate model; the Unified Model (UM).   
UM technical development and its release management is led by the UM system development team.  
You will join a team dedicated to enhancing the UM code capability to support scientific advances from within the Met Office and from our collaborators in national forecasting centres, climate institutions and academia.  As work has also just begun on the next Generation UM, this is a good time to get involved.

Job Purpose:

Contribute to the design, development and/or optimisation of Met Office Weather and Climate modelling capability.  Enabling scientific advancement within the Met Office and by our international and academia partners

Job Responsibilities:

This post is being advertised across a range of levels. Although the responsibilities of the post are very similar for all levels the degree of autonomy they are delivered with and the level of complexity of tasks the individual is expected to deliver increase with role level. The default expectations are for a Foundation Scientific Software Engineer and then additional expectations for a Scientific Software Engineer are shown as additional responsibilites and criteria below.

Responsibilities:-

  • Design, develop, analyse and implement changes to the Met Office weather and climate modelling codes,  enhancing technical capability in support of science advances and/or improving performance on the supercomputers to make the most efficient use of the supercomputer resource.
  • Liaise with UM users and developers in order to understand their scientific and software requirements, to provide technical guidance and advice; with UM developments and/or to ensure developments will be efficient on current and forthcoming supercomputer hardware.
  • Contribute to the reviewing and testing of code changes, upholding the correct development procedures, ensuring that code changes meet the software standards and quality criteria as detailed in the working practices of the system being modified.
  •  Share knowledge and expertise with colleagues in order to enhance both team and inter team effectiveness.

Additional responsibilities for Scientific Software Engineer

  • Act as a key interface with our science/research colleagues.
  • Be a technical lead and responsible code owner for a selection of UM code sections and sub-systems, maintaining, documenting and supporting their use so as to facilitate their maximum utilisation and longevity.

Essential Qualifications, Skills & Abilities:

As the post is advertised at a couple of role levels note there are some criteria that are required for all levels but there are also additional criteria listed below for the higher level.

Essential criteria:

Default criteria are for Foundation software engineer. Additional expectations for a Scientific sofatware engineer post are included below.

  1. Bachelor’s degree or equivalent, at level 2.2 or above, in a physical science, mathematics or computing subject or equivalent experience
  2. Experience of developing or maintaining software, in a high-level language such as Fortran or C showing an aptitude to understand complex applications and to learn to adapt them. 
    • To be considered for Scientific Software Engineer role:
      Experience of developing or maintaining complex modelling software in a high-level language such as Fortran or C, with limited supervision, demonstrating breadth and depth of understanding.
  3. Experience of developing code on Unix or Linux systems.
    • To be considered for Scientific Software Engineer role:
      An understanding of scripting languages coupled with experience of leading development of code within a Unix and/or Linux operating system environment.
  4. The drive to be able to see complex technical tasks through, from initial analysis to a robust implementation in an operational environment.
  5. Ability to work in a united way with scientists and technical staff both within the team and outside of the immediate team to deliver code improvements.
  6. An understanding of relevant scientific areas required to allow the applicant to communicate effectively with scientists and to understand scientific requirements of technical work.

Desirable Qualifications, Skills & Abilities:

  1. Experience of using High Performance Computers to run scientific applications
  2. Experience of developing code for use on High Performance Computers using MPI or OpenMP
  3. Experience with one or more dynamic language and/or shell script: Python, Perl, Bash etc.

To be considered for Scientific Software Engineer role:
Experience of developing or maintaining scientific codes within a formal configuration management process.

Additional Supplementary Information:

Please note interviews for this post will be held week commencing 15 June 2015

Closing Date for applications: 01/05/2015

 

Click here to apply online

 



Go to: Periods · List Information · Index by: Date (or Reverse Date), Thread, Subject or Author.