Internal Hiring Process:

Application Process

  • Red Hat posts opportunities on LinkedIn and its careers page.
  • Youtube channels also provide information about recent openings.
  • I applied via LinkedIn which directed me to Red Hat’s career page.
  • Then CV selection takes place.
  • Red Hat hosts a drive, the link for which is sent to the email of applicants whose CV has been shortlisted.
  • The drive is hosted on Red Hat’s conference tool, Blue Jeans.
  • First, a short Presentation by the Red Hat team takes place then a test link is sent to each participant on the conference via Google forms.
  • The test takes place on the HackerRank platform.

Round 1: Online Test

  • The test is hosted on HackerRank.
  • Duration of test: 45 mins
  • There is a negative marking of -1 for each wrong question and +5 for each right question.
  • The test mainly comprises of following sections-
    MCQs from:
  • Data Structures (Easy to Medium difficulty)
      Questions from Pointers, Linked List, Arrays, Stack, Queue, Tree algorithms, Graph algorithms.
  • Linux (Easy)
      Questions on SSH, basic commands like cat, grep, ls, cd, etc.
  • Operating System (Medium)
      Questions on job Scheduling, Deadlock, Multithreading, Types of Kernels.
  • Software Engineering (Easy)
      Questions on types of testing, SDLC, Documentation practices
  • Coding Questions:
    • No. of questions: 2
    • Language: Your choice (mine was Python)
    • Difficulty- One easy one medium
    • Question 1: Sum of prime no.s in the array (easy)
    • Question 2: Shortest repeating substring (medium)
    • I passed all test cases for both questions
  • SQL Query
    • No. of questions: 1
    • Difficulty: Easy to medium
    • My test had: Finding the youngest student among students whose names are not unique in a database of students of a class

Round 2: Technical Interview

  • Duration of test: 45 mins
  • After 10 days of the test, I got a call that I have been shortlisted for an interview.
  • About interview:
    • Brief introduction
    • Detailed discussion about my projects
    • Why did I start with C, why I shifted to python?
    • Various advantages and disadvantages of C and Python
    • Algo discussion about TSP problem
    • What do I know about Linux Kernel?
    • What are some important steps in the development of a software productWhat are various Data structures in python with their advantages and disadvantages?


Round 3: Technical Interview + Managerial Interview

  • Duration of test: 45 mins
  • After 7 days of round 2, I got a call that I have been shortlisted for the final interview.
  • About Interview:
    • Brief introduction
    • Detailed discussion on my projects.
    • What I knew about the role of SRE.
    • What is Open Source
    • My strength and weaknesses
    • My leadership qualities
    • Situational analysis, for eg: while developing a project about a topic I am totally unaware of, how will I proceed, what stages I will go through, etc.

 After 2 days, I came to know via phone call that I have been selected for an internship as Associate Site Reliability Engineer Intern for a duration of 6 months.

Full-Time Role Hiring Process:

In order to grab a full-time offer from Red Hat, I had to go through 4 different tasks which were related to my profile, that is, SRE (Site Reliability Engineer).

1. Project Development: Developing a CLI tool that will integrate the use of Pager Duty and will allow a person to acknowledge alerts, see schedules, etc via a single CLI tool. The project was built in Google Go language which was completely new to me. The project went through extensive PR reviews and made us learn various SE practices like API mocking, T-View, CLI, UI tool, etc. This was a team project consisting of me and another intern.

2. Project Presentation:  After the completion of the project, we had to deliver a complete presentation and demo of the project across various teams i.e 3 teams: NASA, APAC, EMEA (based on region)

3. Toil Reduction ticket resolution: I had to work on a toil reduction ticket and provide a proper solution and analysis with justification to mark the ticket as resolved on JIRA.

4. Oncall duties: This involved being secondary on-call (handling JIRA tickets that are part of SRE support), primary on-call (handling alerts in PagerDuty).

After the completion of my internship, I was offered a full-time role at Red Hat as an Associate Site Reliability Engineer.

The overall experience at Red Hat:

Red Hat is a great organization and I am completely in awe of it. People here are not judged on how much they know, but on their willingness to learn. Red Hat believes there is no such thing as perfection in knowledge and no such thing as the age of learning, even if you are with Red Hat for 6 years, you still are given space to ask and learn. The management is transparent across levels and a plethora of brightest minds here make you enjoy your work a lot, knowing that you are growing both as a person and as a professional.