diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 9d4ed87d..929576a5 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -105,5 +105,5 @@ jobs: run: | htmlproofer ./public \ --swap-urls "^https\://alan-turing-institute.github.io/REG-handbook/:/,^/REG-handbook/:/,/edit/main:/edit/$(git branch --show-current)" \ - --ignore-urls '/REG-handbook,/turing.ac.uk/,/github.com/,/docs.github.com/,/twitter.com/' \ + --ignore-urls '/REG-handbook,/turing.ac.uk/,/github.com/,/docs.github.com/,/twitter.com/,/code.visualstudio.com/,/forms.office.com/' \ --ignore-files './public/docs/contributors/index.html' diff --git a/content/docs/contributing/editing_a_page.md b/content/docs/contributing/editing_a_page.md index 54ee33ee..33d225c9 100644 --- a/content/docs/contributing/editing_a_page.md +++ b/content/docs/contributing/editing_a_page.md @@ -111,7 +111,6 @@ The theme has a [number of shortcodes](https://github.com/alex-shpak/hugo-book#s In particular - [hints](https://hugo-book-demo.netlify.app/docs/shortcodes/hints/) -- [expand](https://hugo-book-demo.netlify.app/docs/shortcodes/expand/) - [KaTeX](https://hugo-book-demo.netlify.app/docs/shortcodes/katex/) - [tabs](https://hugo-book-demo.netlify.app/docs/shortcodes/tabs/) diff --git a/content/docs/join_us/recruitment_FAQs.md b/content/docs/join_us/recruitment_FAQs.md index 38412cf1..dae90619 100644 --- a/content/docs/join_us/recruitment_FAQs.md +++ b/content/docs/join_us/recruitment_FAQs.md @@ -19,44 +19,68 @@ Questions are grouped by: - [Application Stage](#application-stage) - [Profile](#profile) -- [Position](#position) +- [Role](#role) - [Interview](#interview) - [Offer](#offer) ## Application Stage -### Is the position open to applicants outside of the UK who do not currently have a UK working Visa but could obtain one? +### Is the position open to applicants outside of the UK who do not currently have a UK work visa? -Yes, the positions are open to applicants outside the UK and our HR team ([HR@turing.ac.uk](mailto:HR@turing.ac.uk)) will be able to offer you additional information on the process of obtaining a working Visa. +Yes, the positions are open to applicants outside the UK. +If you do not currently have the Right to Work in the UK, the Turing is able to sponsor a Skilled Worker visa application (see [below](#does-the-turing-cover-relocation-and-visa-costs) for details). +If you have general questions about the process, feel free to reach out to the [REG recruitment team][recruitment]; however, once your application has started, you should direct any questions about your specific situation to the Resourcing Officer who is handling your application. ### Are you accepting remote applicants? Members need to be based in the UK. -However, you do not need to be in the London office every day: almost all of our work is done in a hybrid manner, and we have team members as far away as Scotland and the South West of England. +However, you do not need to be in the London office every day nor on a regular weekly schedule, as almost all of our work is done in a hybrid manner. +We have team members that live further away in places such as Scotland and the South West of England who come to the office less frequently. +The on-paper expectation is that it would not be unreasonable to ask team members to spend four days a month in the office, but in practice we have been able to support a range of hybrid working patterns with fewer days in the office. +We prefer to let the work to be done dictate the most effective collaboration style for carrying it out, and thus there may be some reasonable variation across projects in terms of requirements for in-office work. +We also hold two in-person team events per year, the Team Away Day (actually two days) in the winter and Hack Week in June. ### What would be the starting date? -We are keen to grow the team so would prefer if people can start within 3 months of an offer being made and would be happy for successful candidates to start sooner. -However, we are looking to recruit multiple people and we are hiring for the long term, so we can support later starting dates if a successful candidate's circumstances require it. +We generally prefer that people start within three months of an offer being made. +However, if necessary, we can also accommodate shorter or longer periods between the offer and starting; for previous candidates this time has ranged from 1 month to ~6 months. +If you have a specific date in mind, please feel free to contact [the REG recruitment team][recruitment]. ### How many open positions are available? -To be determined. +We don't have this information for 2024 yet. +We will update this page when we do. + +### What roles are you currently hiring for? + +The roles within our team are **Research Data Scientist** (RDS), **Research Software Engineer** (RSE), and **Research Computing Engineer** (RCE). +You can read more about these roles [below](#role) or on our [website](https://www.turing.ac.uk/research/research-engineering/meet-the-team). + +The RDS and RSE roles form part of the same job description; the skillset we look for is the same and there is no difference as to the projects you are given when you join. +You are given a choice of which job title you prefer when starting. +You can also change your job title later if you feel that the other is a more accurate description. + +For this recruitment round, we will be hiring at Junior, Standard, and Senior levels. +The difference between these are explained in the respective job descriptions. +If you think you have enough experience to apply for the higher position, you can do so. +You can also apply to the more junior role and mention in your cover letter that you are also considering the more senior position, in case you feel your profile or working experience is between the two. +Every application at a given level will also be considered at the other levels if more appropriate. ### If my application was unsuccessful in the past, am I allowed to apply again this time? If you applied and did not get selected to interview you are welcome to apply again, but we suggest to revise your cover letter and CV and make them more in line with the requirements specified in the job ad. If you applied and were unsuccessful at the interview stage, you are welcome to reapply if your profile has significantly progressed since the interview (new projects, job roles or other sources of experience). -In general, we suggest to wait for at least one year before applying again. +In general, we suggest you wait for at least one year before applying again. ### Does the Turing cover relocation and visa costs? -Yes. -The Turing recognises that relocating and applying for a visa have different associated costs and therefore will provide support for both. -All claims should be submitted within a year of the employment start date to Finance. -For existing staff, visa claims should be submitted within one year of the visa renewal or amendment. -More information can be found on [Mathison](https://mathison.turing.ac.uk/Interact/Pages/Section/ContentListing.aspx?subsection=4141&utm_source=interact&utm_medium=quick_search&utm_term=relocation). +Yes; the Turing recognises that relocating and applying for a visa have different associated costs and therefore will provide support for both. +The Turing will reimburse up to: + +- £4000 for the cost of a visa application (including the NHS immigration surcharge); +- £2000 for relocation costs (if you are moving from Europe or the UK, as long as the move is over 50 miles); and +- £4000 for relocation costs (if you are moving from further overseas). ### Do you provide reasonable adjustments to the application process for people with disabilities or health conditions ? @@ -71,24 +95,50 @@ For more information about the Institute's reasonable adjustment policy see [the ### Are there particular domains or skill sets that you are interested in for these roles? -We are really open to any domain, area of expertise, skill set that is broadly related to research data science or research software engineering. +We are really open to any domain, area of expertise, or skill set that is broadly related to research data science or research software engineering. If you have experience or are interested in High Performance Computing, as part of the open positions, we are actively looking for new members of the team to work on that area as Research Computing Engineers. -You can drop an email to the REG recruitment team ([reg-recruitment-inbox@turing.ac.uk](mailto:reg-recruitment-inbox@turing.ac.uk)) to learn more about it. +You can drop an email to [the REG recruitment team][recruitment] to learn more about it. However, we are recruiting for multiple positions, and are interested in a wide range of skills and experience, so please do apply if you are interested and have experience relevant to research software engineering and data science, broadly defined. You can see the [range of projects](https://www.turing.ac.uk/research/research-engineering/reg-projects) the team works on and [backgrounds of current team members](https://www.turing.ac.uk/research/research-engineering/meet-the-team) on our website. Some of the team have also been featured in project and institute spotlight interviews and the [Turing podcast](https://www.podbean.com/media/share/pb-vrci3-1366a21?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share) (including episodes on [AI for the Skies](https://www.podbean.com/media/share/pb-zzidx-d7bb24?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [Fantasy Football AI](https://www.podbean.com/media/share/pb-5afja-df2052?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [3D printed bridges](https://www.podbean.com/media/share/pb-qekh3-dfe740?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [Reproducible data science](https://www.podbean.com/media/share/pb-wxkjp-ecfa7f?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [The problems of AI](https://www.podbean.com/media/share/pb-dyq36-112350b?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share) and [Living with Machines](https://www.podbean.com/media/share/pb-s9das-1275eb2?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share)). -### What is a Research Computing Engineer? +### I don't have a physics / maths / computer science background. Is that okay? + +That is completely fine. +Our team includes people with backgrounds in a broad range of subjects, including chemistry and biology, as well as the social sciences. + +In practice, we do not often work on projects that align closely with our own academic backgrounds. +As long as you are willing to pick up new skills and domains as you go along, your own background will not be a barrier. + +### I'm a woman / person of colour / LGBTQIA+ / person with disabilities / part of an underrepresented group(s). Will I feel welcome and supported in the team? + +**We'd love to have you join our team!** +Inclusivity and diversity aren't just things we encourage because we're beholden to some corporate criteria; we believe they are *essential* to good research. +We'd really encourage you to apply! -This role presents a new exciting opportunity to join the growing team of research computing experts at The Turing. The team assists the Turing community with designing, building, deploying, and maintaining research infrastructures, as well as providing service delivery and user support for the Institute’s research computing platforms. This is an opportunity for a technically-skilled professional with a good understanding of either cloud or high-performance computing (HPC), experience with both application and infrastructure, and an interest in facilitating and enhancing world-leading data science and AI research. -You will build tools and automation to eliminate mundane operations and craft repeatable processes. As part of the team, you will also work with other research software engineers and data scientists on various projects and will participate in all phases of cloud / HPC development, from requirements-capture, definition, and design; to development, deployment, and maintenance; to performance tuning and monitoring. You are also expected to keep up-to-date with the latest cutting-edge developments, and/or make use of the UK’s most advanced computing facilities like Dawn, ARCHER 2, JADE 2, and Baskerville. +Our team has a very motivated group of people that work on things such as: + +- inputting to institute-wide policies (e.g. trans and non-binary inclusion) +- doing analysis of diversity data, like for our [Gender Pay Gap Report](https://www.turing.ac.uk/sites/default/files/2023-03/2023.03.30_gender_pay_gap_report.pdf) +- making job ads more inclusive (not closing applications early, publishing salary bands, using clear language) +- being ambassadors for REG and the Turing at events like the [Hopper Colloquium](https://www.ucl.ac.uk/computer-science/about/equity-diversity-and-inclusion/gender-equality-athena-swan/london-hopper-colloquium) and the [BCSWomen Lovelace event](https://bcswomenlovelace.bcs.org/) +- Attending network groups – a place to find community, organise events, and work on issues specific to that network. They exist for + - LGBTQIA+ + - Race equality + - Gender equality + - Disability and wellbeing +- and much more! + +You can read more about a sample of the Equality, Diversity and Inclusion (EDI) initiatives in REG and the Turing on [this page]({{< relref "docs/working_at_the_turing/edi" >}}). +Also, if you would like to arrange to speak to somebody in REG (in confidence) about this before applying, let us know; we would be happy to arrange that. That person will not subsequently be involved in evaluating your application. +Reach out to the [REG recruitment team][recruitment] – we'd love to chat! ### Should the cover letter address each of the skills and requirements in the person specification section of the job description? -It is important that the cover letter, in conjunction with the CV, highlights the requirements listed as "check at Application" on the Person Specification, and shows a (general) understanding of the role of a research data scientist or software engineer. +It is important that the cover letter, in conjunction with the CV, highlights the requirements listed as "check at application" on the Person Specification, and shows a (general) understanding of the role of a research data scientist or software engineer. Also, it is important to highlight: - Your past experience working with code and/or data @@ -99,15 +149,38 @@ Also, it is important to highlight: If you do not have a PhD degree but have worked for a few years and believe you have gained the essential skills mentioned in the Person Specification, we encourage you to apply! -Such experience might include exposure to research projects, awareness of the importance of reproducible software and tools, working with or leading a team of people with different skill sets, deciding on how to best achieve an objective from a data science perspective, or presenting advice/results to an audience. +Such experience might include exposure to research projects, awareness of the importance of reproducible software and tools, working with or leading a team of people with different skillsets, deciding on how to best achieve an objective from a data science perspective, or presenting advice/results to an audience. We would like to hear about your prior experience in your cover letter. -If you prefer, feel free to get in touch with the REG recruitment team ([reg-recruitment-inbox@turing.ac.uk](mailto:reg-recruitment-inbox@turing.ac.uk)) about this point. +If you prefer, feel free to get in touch with the REG recruitment team ([reg-recruitment-inbox@turing.ac.uk][recruitment]) about this point. ### Would not having a PhD prevent me from career progression, in terms of becoming a Senior Research Data Scientist/Research Software Engineer at the Turing Institute? Absolutely not, our internal career progression is based on internal milestones and contributions to the group and the Turing community - do not worry about this at all. -## Position +## Role + +### What is a research software engineer? + +The RSE role is fundamentally about using skills in data science and/or software engineering to support research projects. + +Compared to a traditional academic postdoctoral role, a RSE is typically more likely to: + +- focus on the software aspects of a project, with a particular emphasis on writing good code that is maintainable and reproducible (as opposed to the bare minimum needed to get a scientific result) +- be involved in a wider range of projects, often moving between different projects on a timescale of months to years +- be less involved in writing academic papers or grants, as these are less relevant metrics for career progression + + +For more information, you can read this page on the UKRSE website: [What is a Research Software Engineer?](https://ukrse.github.io/who.html). +(The UKRSE has since become the [Society of Research Software Engineering](https://society-rse.org/), but their new website doesn't have as thorough a description of the role.) + +### What is a research computing engineer? + +This role presents a new exciting opportunity to join the growing team of research computing experts at the Turing. +The team assists the Turing community with designing, building, deploying, and maintaining research infrastructures, as well as providing service delivery and user support for the Institute’s research computing platforms. +This is an opportunity for a technically-skilled professional with a good understanding of either cloud or high-performance computing (HPC), experience with both application and infrastructure, and an interest in facilitating and enhancing world-leading data science and AI research. +You will build tools and automation to eliminate mundane operations and craft repeatable processes. +As part of the team, you will also work with other research software engineers and data scientists on various projects and will participate in all phases of cloud / HPC development, from requirements-capture, definition, and design; to development, deployment, and maintenance; to performance tuning and monitoring. +You are also expected to keep up-to-date with the latest cutting-edge developments, and/or make use of the UK’s most advanced computing facilities like Dawn, ARCHER 2, JADE 2, and Baskerville. ### What is the difference between a Junior and a Standard role? @@ -115,13 +188,42 @@ The main difference between the Junior and Standard roles is that the Junior is We consider candidates for the Standard position if they have a PhD or an equivalent working experience (meaning for instance a few years of work in a data scientist or software engineer position, in close contact with research projects). If you think you have enough experience you can apply to the Standard position and stress this in your cover letter. You can also apply to the Junior position and mention in your cover letter that you are also considering the Standard position, in case you feel your profile or working experience is in between the two. -Feel free to get in touch with the REG recruitment team ([reg-recruitment-inbox@turing.ac.uk](mailto:reg-recruitment-inbox@turing.ac.uk)) about this point. +Feel free to get in touch with the REG recruitment team ([reg-recruitment-inbox@turing.ac.uk][recruitment]) about this point. + +### What kind of projects do you work on in REG? + +The projects at the Turing largely fall into three themes, namely Environment and Sustainability; Health; and Defence and National Security. +These projects tend to revolve around the _application_ of data science and AI to solve challenges in these areas. +Apart from this, there are also projects in foundational research in data science and AI. + +You can see a list of projects we are currently working on on [our team website](https://alan-turing-institute.github.io/REG/). + +### Are working hours flexible? + +Formally, the Turing's core working hours are between 10 and 4. +Most people would work these hours plus some additional time on either side to make up a 36-hour working week. +However, in practice we are extremely flexible around working hours. +Much of our work is done asynchronously, and does not require everyone to be online at the same time. + +We are especially aware that team members may have responsibilities (e.g. childcare) which can make it difficult to work a typical 9–5 schedule. + +### What languages and technologies do you work with? + +The primary language we use in REG is Python. -### For the Junior post it states as Essential: "Fluency in one or more modern programming languages used in research in data science and artificial intelligence". In my case I am familiar with X, would my computing knowledge satisfy this criteria? +However, depending on the project, we work with different programming languages and different settings, so more than the programming languages you currently know the important aspect for us is the willingness and ability to pick up new languages along the way, based on your previous experience (especially in research and data analysis contexts). -Depending on the project, we work with different programming languages and different settings, so more than the programming languages you currently know the important aspect for us is the willingness and ability to pick up new languages along the way, based on your previous experience (especially in research and data analysis contexts). +You can see an (unscientifically generated) word cloud of the languages and technologies we use in REG here: -### Given the job profile in the REG team, what do REG members tend to transition to (for eg. Academics, or Industry, or something else)? +![wordcloud](https://raw.githubusercontent.com/alan-turing-institute/REG/main/src/assets/wordcloud.png) + +### How long do projects last for / how do you choose projects? + +The length of projects can vary significantly; some are as short as three months, and others have stayed on projects for multiple years. However, there is no requirement to stay on a project for its entire lifespan; there are always options to rotate onto other projects. + +You will be given the chance to say which projects you are interested in working on, and you will (to the best of our ability) be placed on a project that you are keen on, rather than one that only matches your prior experience. + +### Given the job profile in the REG team, what other careers do REG members tend to transition to (e.g. academia, industry, or something else)? We have only had a few members of the team who have moved on with their career trajectory so far. To read about some of their career paths you can visit our [REG alumni page](https://www.turing.ac.uk/research/research-engineering/reg-alumni). @@ -131,35 +233,114 @@ Others have progressed to more senior roles within the team. ### Would the candidate be able to bring their own projects with them and/or seek funding while in the role ? The team's role at the Turing is to collaborate with institute researchers to support their research agendas, rather than pursuing our own. -It is much, much more usual for team members to be working on other people's projects than their own. +It is much more common for team members to be working on other people's projects than their own. If you would like to prioritise pursuing your own research agenda at the Turing there are [other types of positions](https://www.turing.ac.uk/opportunities-turing) at the Institute that allow you to do this. -However, we are keen to support team members in pursuing their careers, including developing and leading projects. -We would generally expect these to be projects that would be a sufficiently good fit for the team and the Turing that we would take them on even if the particular team member was not involved. +### What else do you do as part of REG? + +80% of our time is formally allocated to project work. +Apart from this, we also have 10% of our time set aside for personal development as well as 10% for internal team responsibilities ('service areas'). +There is also a yearly budget for professional development, which all team members can draw on. + +Things done as part of personal development can include: + +- Attending conferences, workshops, or courses +- Participating in seminar series and interest groups at the Turing, including the team’s own weekly [tech talks]({{< relref "docs/regular_events/lunchtime_tech_talks.md" >}}) +- Contributing to [open source code]({{< relref "docs/regular_events/open_source_hacksessions.md" >}}) and community groups such as the [Society for Research Software Engineering]({{< relref "docs/onboarding/society_of_research_software_engineering.md" >}}). + +The team's service areas are diverse, and work can include both internal and external activities. +This list is not exhaustive, but some examples include: -We would also expect team members that do lead their own projects to continue to work collaboratively with others in REG and the Institute. We would therefore not expect people to be bought out more than 50% on their own project and would expect the project to involve other members of the team or the Institute. +- Recruitment (overseeing the entire hiring process, including writing these FAQs!) +- Equality, diversity, and inclusion (see the [EDI page]({{< relref "docs/working_at_the_turing/edi" >}}) for some info) +- Research computing support (providing members of the Turing with training and support on using high-performance computing resources) +- Communications (social media and outreach) +- Research programming support (running [drop-in sessions]({{< relref "docs/regular_events/drop-in_sessions" >}}) for people at the Turing) +- Knowledge sharing (organising our [tech talks]({{< relref "docs/regular_events/lunchtime_tech_talks.md" >}})) -Nevertheless, while a permanent role within REG is not meant for pursuing an independent research agenda, we highly encourage initiatives and are open to hear new ideas and contributions. -So, if you think your project would benefit our group and the Turing (and vice-versa) you should highlight it in your cover letter. +### Can you tell me more about what it is like working at The Alan Turing Institute? + +At The Turing, we want to make sure you feel comfortable and supported in how you work. Here’s a bit about what to expect: + +- **Hybrid Working:** + Although the Turing does require employees to come into the office (see [above](#are-you-accepting-remote-applicants)), we do our best to ensure a healthy work environment whether you are in the office or working remotely. + Some of the team work primarily remotely, while others come in every day. + We’ve set up our working style to be remote-first, ensuring that those not in the office aren’t at a disadvantage, so there’s no pressure or expectation to be in the office more than the minimum four days a month. + However, some team members have found that when they work remotely, they miss out on the informal water cooler chats or lunchtime conversations that happen in the office. + To help bridge the gap, we try to mitigate this with online randomised coffee chats and co-working sessions. + +- **Flexible Hours:** + Our core hours are 10 am to 4 pm, but you’re free to work whenever works best for you. + Whether you’re an early bird or prefer working later, we trust you to manage your time in a way that fits your life and responsibilities. + We also understand that everyone has commitments — whether it’s a doctor’s appointment, picking up kids, or running errands — so working flexibly around these activities is completely fine. + +- **Work-Life Balance:** + We value a healthy work-life balance and believe you should be able to switch off outside of work. + There is no expectation to respond to emails or messages outside your working hours! + While there may be rare occasions when deadlines lead to higher workloads and longer hours, we encourage you to ensure that you balance that, so on average you work the correct number of hours and maintain a balance that works for you. + +- **Hot Desks:** + We use hot desks, meaning you can sit wherever you like when you’re in the office, on a first-come, first-served basis. + The Research Engineering Group typically sits near one another on the first floor. + If you need a permanent or bespoke workspace (such as standing/adjustable desks or footrests), we can work with the facilities team to make it happen. + +- **Meeting Etiquette:** + We typically like to have our cameras on during Zoom meetings, but it’s absolutely fine to have your camera off if you feel more comfortable. + And, while we encourage you to take regular breaks as needed, it’s also ok to eat or snack during meetings — in fact, we host regular lunchtime tech talks or reading groups where the team can lunch and learn simultaneously. + +- **Come as You Are:** + We don’t have a written dress code; the team typically opts for smart-casual, but you can wear whatever makes you feel comfortable. + We trust you to keep it professional when needed. + +- **Office Snacks and Team Lunches:** + We love having team lunches together when we’re in. + There is also free fruit, biscuits, juice, tea, and coffee to keep you going throughout the day. + The kitchen area is great for group coffee breaks, or you can snack at your desk anytime. + +- **Location and Socials:** + Our offices are based in the British Library, right in the heart of London and just 5 minutes from King’s Cross Station. + As part of the Knowledge Quarter, there’s always something exciting happening nearby. + We also have plenty of social outings organised by and for Turing staff, including five-a-side football, tennis, climbing, Thursday pub club, French club, film club, hikes…the list goes on (although absolutely none of it is compulsory!). + +### Other benefits of the role + +Some of the benefits of working in REG have already been covered in other questions (for example, [flexible working](#are-working-hours-flexible), [having strong input into the projects you work on](#how-long-do-projects-last-for--how-do-you-choose-projects), and [time for professional development](#what-else-do-you-do-as-part-of-reg)). + +Other benefits include mental health support and private healthcare ([the wellbeing page]({{< relref "docs/working_at_the_turing/wellbeing" >}}) has a more detailed description of the support available at the Turing), as well as a 13% contribution to a defined contribution pension scheme (3% from the employee, 10% from the Turing). + More employee benefits are listed on [the Turing's website](https://www.turing.ac.uk/work-turing/why-work-turing/employee-only-benefits-guide). + +### Where can I find out more? + +Members of REG have been featured in various interviews and spotlights, where they discuss their work and team activities. Here are a few examples: + +- [Team presentation at RSECon2022](https://www.youtube.com/watch?v=Dq537Sh6ZT4): Our director and other team members discuss building and growing a research engineering team at the Alan Turing Institute. +- [Code for thought podcast](https://codeforthought.buzzsprout.com/1326658/14761258-en-building-data-science-teams-alan-turing-institute-skills-and-policy-award-part-i): Check out the "Building Data Science Teams" episode, where REG members share insights into the teams they work with. +- [Data science and AI careers series](https://www.turing.ac.uk/data-science-and-ai-careers-spotlight-series/spotlight-series): Some of our team members are featured in The Turing's spotlight video series on data science and AI careers. +- [REG spotlight series](https://www.turing.ac.uk/work-turing/research/research-engineering-group#researcher-spotlight): Several team members have been highlighted in The Turing’s spotlight series, discussing their work and career journeys. +- [Research Software Hour](https://www.youtube.com/watch?v=WIYaXzXLLY4): One of our alumni presents on workflow automation, sharing insights into efficient workflows and automation in research projects. +- [Turing podcast episodes](https://www.podbean.com/media/share/pb-vrci3-1366a21?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share): REG appear on episodes covering a range of topics, including [AI for the Skies](https://www.podbean.com/media/share/pb-zzidx-d7bb24?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [Fantasy Football AI](https://www.podbean.com/media/share/pb-5afja-df2052?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [3D printed bridges](https://www.podbean.com/media/share/pb-qekh3-dfe740?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [Reproducible data science](https://www.podbean.com/media/share/pb-wxkjp-ecfa7f?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share), [The problems of AI](https://www.podbean.com/media/share/pb-dyq36-112350b?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share) and [Living with Machines](https://www.podbean.com/media/share/pb-s9das-1275eb2?utm_campaign=w_share_ep&utm_medium=dlink&utm_source=w_share). ## Interview ### Could you describe the interview process? -As we mentioned in the job description, all interviews are currently held remotely. +As mentioned in the job description, all interviews are held remotely. +We are currently looking into the possibility of holding interviews in person; please feel free [to ask about this][recruitment] if this is something you would like. -We operate a two-stage interview process. If you are successful at the screening stage, you will be asked to attend the first interview via video call. -In this interview, you will be expected to give a ten-minute presentation on code you have written that either demonstrates an algorithm that you consider important in data science or illustrates your use of good research software engineering practices. -Existing examples of work are encouraged as long as the code was substantially written by you. -You should be prepared to answer questions about both the code and the research challenge it addresses or the algorithm it demonstrates. -Any source code shared for the interview will be treated in the strictest of confidence. +We operate a two-stage interview process. +If you are successful at the screening stage, you will be asked to attend the first interview via video call. +In this interview, you will be expected to give a ten-minute presentation on code you have written to address a specific research question. +This code should ideally illustrate your use of good research software engineering practices; however, imperfect code is totally fine as long as you can discuss what you would improve and why. -The second interview is usually held about one week later for successful candidates. This interview focusses on your previous experience and competencies for the role. +More information about this presentation can be found in the next sections. + +The second interview is usually held about one week later for successful candidates. +This interview focusses on your previous experience and competencies for the role. There will also be a problem-solving discussion with the interview panel, where you may want to use paper and pen to arrive at an understanding of a proposed data analysis challenge. In both interviews, there will be the opportunity to ask questions about the role and the team. -### Does the algorithm need to be written entirely by me? +### Can you tell me more about this code presentation? In the first interview we expect you to demonstrate your ability to write code for addressing a data science task in a reproducible manner and/or to use good software engineering practices for developing research software. This could be done by presenting a data analysis script or piece of research software written entirely by you, or by presenting a larger piece of research software you have made a significant contribution to. @@ -169,24 +350,42 @@ Using existing libraries that implement algorithms you are using is fine (and go 1. the underlying algorithms or methods your code is implementing or using, and 1. the research domain or question for which you are applying them. -### Can you give any more detail on what the panel expect from the algorithm which will be presented - does it need to meet any certain criteria, for example have a certain level of complexity? +We will not evaluate you on how complicated your algorithm is, but in your understanding of its implementation, awareness of its potential drawbacks, and its overall appropriateness to solve the problem you are trying to address. + +You can write new code specifically for the interview if you so choose, but existing examples of work are encouraged, as long as the code was substantially written by you. +You should be prepared to answer questions about both the code and the research challenge it addresses or the algorithm it demonstrates. +Any source code shared for the interview will be treated in the strictest of confidence. + +### What sort of code have previous candidates presented? + +We collected several examples of code that have been presented by current team members in their interviews. +This list is not exhaustive, and we really want to emphasise that you can present any code that you feel demonstrates your skills and experience. +Some are scripts / notebooks which were put together specifically to demonstrate a particular technique for the interview: + +- A Jupyter notebook with a data analysis pipeline to solve an old Kaggle competition +- A notebook (and module) demonstrating inference and analysis with a hidden Markov model using TensorFlow Probability, applied to synthetic healthcare data +- An R script to calculate the depth of ocean floor sediment samples ([GitHub](https://github.com/IFenton/Sediment-age-depth)) +- Notebooks and scripts to reimplement the TAGME algorithm for annotating text with Wikipedia entities ([GitHub](https://github.com/fedenanni/Reimplementing-TagMe)) + + -In the first interview we expect you to demonstrate your ability to write code for addressing a data science task and/or to use good research software engineering practices for ensuring research reproducibility. -This could be done by presenting for instance a data analysis script written by you, where you would describe us the implementation and answer some general questions. -The adopted algorithms can be ones available in existing software libraries, integrated for instance in a data analysis workflow, but they can also be written by you if you prefer. +There are also examples of fully-fledged libraries / applications that were written as part of applicants' academic work, for example: -We will not evaluate you on the complexity of the algorithm, but in your understanding of its implementation, awareness of its potential downfall and its overall appropriateness to solve the problem you are trying to address. +- An R package for statistical analysis and visualisation of biological data (primarily gene expression) ([GitHub](https://github.com/KatrionaGoldmann/volcano3D)) +- A Python library for differentiable programming in high-energy physics ([GitHub](https://github.com/gradhep/relaxed)) +- A web app (plain TypeScript) for NMR spectrometer code generation ([GitHub](https://github.com/yongrenjie/genesis)) +- A Python library for tensors with internal symmetries ([GitHub](https://github.com/mhauru/abeliantensors)) -### Will I be only explaining the algorithm / analysis / software, or running it and discussing the results? +### Will I be only explaining the code, or running it and discussing the results? Should it be accompanied by other materials (e.g. a slideshow)? -You will be presenting your chosen analysis, algorithm or software and its implementation, but you should be able to talk about the results of the analysis or the performance of the software. -It would be useful to be able to run the code to generate results, but we recognise this is not always reasonable in an interview setting. If this is not not feasible then you should bring some previously generated results so that we can have a conversation around inputs and outputs. -The discussion will likely touch on the performance of the algorithm in terms of e.g. speed, accuracy or range of applicability, but our goal is to evaluate your understanding of the algorithm, analysis or software and its implementation rather than to assess you on the performance of your particular implementation. +You should ideally able to show and run the code, using any means you are comfortable with: for example, Jupyter notebooks, Rmarkdown, an IDE, or the command line. +We recognise, though, that it is not always possible to run the code in an interview setting. +If this is not feasible, you should bring some previously generated results so that we can have a conversation around inputs and outputs. -### Should the presentation be verbal only or should I produce some materials alongside it - would the committee prefer presentation directly from an IDE, or using a presentation software? +The discussion will likely touch on the performance of your code in terms of e.g. speed, accuracy, or range of applicability. +However, our main goal is to evaluate your understanding of the code and general software engineering practices, rather than assessing the performance of your particular implementation. -You should be able to show and (potentially) run the code (this could be using Jupyter notebooks, Rmarkdown, a mix of an IDE and the command line). -You are welcome to include any other material that could be useful for supporting your presentation. +You are welcome to include any other material (such as slides) if you feel it is useful for supporting your presentation or providing context. ### What will the problem solving aspect of the second interview involve? Will I be asked about particular data science or machine learning approaches? Will I need to write code or explain the details of an algorithm's implementation? @@ -207,44 +406,26 @@ The best thing you could do to be prepared is to eat well, take some long walks ## Offer -### What are the reasons of your job offer? Is the salary negotiable? +### Is the offered salary negotiable? Fairness and transparency are key values for us and our goal is to avoid inequity by ensuring we are paying people the same salary for the same level of contribution to the team. -**Our offers are not negotiable** and set by considering the level and applicability of each candidate’s experience relative to their future peers already working in the team. +We make initial salary offers at 0/3, 1/3, and 2/3 through the advertised salary range, based on the level and applicability of each candidate’s experience relative to their future peers already working in the team. +**Our offers are not negotiable.** -We have annual pay reviews, where we actively review the performance and development of each team member against the expectations of their position within their seniority band and make salary adjustments where these expectations are being exceeded. -Additionally, the team is growing and there will be opportunities for people to progress in their career. +### What is salary progression like in the role? -Becoming a member of REG will also bring the following benefits: +Each year, there is a cost of living increase which is applied to all Turing employees. +On top of this, we also have annual pay reviews, where we actively review the performance and development of each team member against the expectations of their position within their seniority band, making salary adjustments where these expectations are being exceeded. -- Flexible working: we are currently trialling being a “remote-first” group for the entire decision-making process, but as the office is now fully re-opened members are free to choose how often they come into the office. - -- The opportunity to work and collaborate on cutting-edge data science projects with high-profile institutions, but with the benefits of working in a full-time position (better than a post-doc, better than many data science roles in industry). - -- Strong input into which projects you work on. - We value providing the experience of learning something new in a collaborative setting, and prioritise staffing people onto projects they would like to work on rather than maximising the fit to people's prior experience. - Our group is made up of people with a wide range of skills and experiences and we generally find we can put together project teams with a suitable mix of skills from those who are enthusiastic about each project. - -- Formal support for professional development via learning and development plans each team member develops with their line manager during the probation process, annual objective setting and regular 1-2-1s. - These learning plans feed into the projects people are allocated to and the roles and responsibilities they undertake within these. - -- Support to team members with their development outside of projects, providing 20% time that is split evenly between self-directed development and getting involved in one of the group's or institute's service areas. - We support team members to attend conferences, workshops and courses, and there are many seminar series and interest groups at the Turing that team members are encouraged to get involved with, including the team’s own weekly [tech talks]({{< relref "docs/regular_events/lunchtime_tech_talks.md" >}}). - We also support team members making contributions to the wider ecosystem as part of their 20% time. - Examples include contributing to external [Open Source Hacksessions]({{< relref "docs/regular_events/open_source_hacksessions.md" >}}) and contributing to community groups like the [Society for Research Software Engineering]({{< relref "docs/onboarding/society_of_research_software_engineering.md" >}}). - -- The opportunity to get involved in non-project work through one of the team's service areas, some of which support the running of the team and some of which support the wider research community at the institute (for instance Recruitment, Planning and finance, Training, EDI, Communications, Research computing support, Research programme liaison). - Some service areas require significant support and will have core team members who have chosen these service areas instead of a full project workload, but all team members have a 10% allocation to volunteer for a service area of their choice. - -- The opportunity to contribute to how the group works and grows. - We run the team in an open, consultative and collaborative manner and almost all of our decision making on how we organise ourselves and develop the team is done in the open on our group GitHub with the opportunity for anyone in the team to contribute. - -- [Other benefits](https://www.turing.ac.uk/work-turing/why-work-turing/employee-benefits) include private healthcare and a 13% contribution to a defined contribution pension scheme (3% from the employee, 10% from the Turing). +We also hold annual internal promotion rounds to allow people to move up to the next level of seniority when they are ready. +There is no cap on the number of Junior, Standard, and Senior roles, so promotion opportunities are not limited by availability. ## My question is not answered here -Please contact the REG recruitment team ([reg-recruitment-inbox@turing.ac.uk](mailto:reg-recruitment-inbox@turing.ac.uk)) with any additional questions you may have. +Please contact the REG recruitment team ([reg-recruitment-inbox@turing.ac.uk][recruitment]) with any additional questions you may have. We also run monthly drop-in sessions where you can meet some of the current team and ask them questions face to face. These sessions will be hosted by team members who won't be involved in that month's interview process, and questions you ask at these sessions will have no influence on how your application is treated. To be informed of the details for these drop-in sessions, please register for the team's [recruitment newsletter](https://forms.office.com/e/vJy48fNJXB). (You can unsubscribe at any time via [this link](https://forms.office.com/e/P22MqUT0N3).) + +[recruitment]: mailto:reg-recruitment-inbox@turing.ac.uk