The interview takes the form of a panel discussion. Three to five team leaders first introduce themselves and then present the project or team they're working on or with, day-to-day tasks, project goals, what problems the project is trying to address and why. If the project is just a stepping stone, base, or building block (typically a library), then which products from the portfolio use it and how these interact with it (only briefly, though).
The interviewers then approach the candidate with questions targeting the candidate's technical skills. This follows the technical skill and knowledge base on-site test, the results of which had served the decision process of further interviewing a candidate.
Lastly, the interviewers ask the candidate whether there's any intersection between the candidate's interests and any of the presented projects, thus indirectly asking them about any preferences.
What is a core dump, and how can it be of any use to us?
What is the difference between a process and a thread?
How does list comprehension work in Python, and would you classify it as a command or an expression?
The following metrics were computed from 4 interview experiences for the Red Hat Software Engineer (Internship) role in Brno.
Red Hat's interview process for their Software Engineer (Internship) roles in Brno is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Red Hat's Software Engineer (Internship) interview process in Brno.