01
What is a blocker bug?
Show answer
A defect that stops testing or release of a feature because no workaround exists, so it is highest priority.
Red Hat Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Red Hat hiring for Software Testing roles
Red Hat is an open source software company, now part of IBM, known for Red Hat Enterprise Linux, OpenShift and Ansible. It provides enterprise Linux, hybrid cloud, container and automation platforms with subscription-based support. In India it has a large presence in Pune and Bengaluru, hiring software engineers, quality engineers, support engineers and consultants.
For Software Testing roles, this Red Hat practice set focuses most on Test Case Design (10), Bug Life Cycle and Jira (7), Agile, SQL and API Testing (7), STLC and Test Planning (5). It has 35 medium, 5 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Product
- Headquarters
- Raleigh, North Carolina, USA
- Main India offices
- Pune, Bengaluru
Red Hat Software Testing interview process
- Online assessment or resume screening
- Technical round 1 (Linux + programming)
- Technical round 2 (domain or open source)
- Hiring manager and HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Red HatStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
02
What is the difference between a defect and a production incident?
Show answer
A defect is a flaw in the software that makes it behave differently from the requirement, whether found in testing or production. A production incident is an event that disrupts or degrades service for users, such as an outage or a failed payment flow. An incident may be caused by a defect, but also by infrastructure, configuration or third-party failures. Incidents are handled by an incident process first, then linked to defects for the fix.
03
How do you write test cases when only wireframes are available and the UI is not ready?
Show answer
Use the wireframes and the user story as the test basis. Write test scenarios and high-level cases for the flows, field validations, navigation and error states shown in the design. Note open questions, such as missing empty states or error messages, and clarify them with the designer. Keep exact UI text and steps light so they are easy to update. Once the build arrives, refine the cases and add any missing details.
04
Write test cases for a calculator app.
Show answer
Basic operations, division by zero, decimals, large numbers, order of operations, clear and backspace, repeated operations and memory keys.
05
Write test cases for a file upload feature.
Show answer
Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.
06
Write SQL to verify an order was saved correctly.
Show answer
SELECT status, amount FROM orders WHERE order_id = 'ORD123';
-- compare with the UI, then check the matching rows in order_items
07
Your test repository has many duplicate and outdated test cases. How do you clean it up?
Show answer
Export the cases and group them by module and requirement. Mark duplicates, merge them into one well-written case, and retire cases for removed features. Check which cases have not been executed or failed in months and confirm whether they are still valid. Link the remaining cases to requirements so gaps are visible. Do it module by module with peer review, and set a rule that every story update also updates its test cases.
08
The test environment is down for two days just before release. What do you do?
Show answer
Escalate immediately with the impact on the schedule. While it is down, prepare test data, review and update test cases, and test what you can elsewhere: API tests against another environment, UI on a developer machine or a staging copy. Track the lost hours in the status report. When the environment returns, run smoke first, then the prioritised list, and ask whether the release date or scope needs to change.
09
The sprint ends tomorrow and two stories are still in testing. What do you do?
Show answer
Tell the Scrum Master and product owner today, not at the review. Focus testing on the acceptance criteria and the riskiest paths of the story with the most value, and ask a developer to help with test data or simple checks. If a story cannot be finished with quality, it should be carried over, not marked done with untested parts. Raise the cause in the retrospective, such as late handover.
10
Scrum ceremonies and the tester's role?
Show answer
Sprint planning (estimate test effort), daily stand-up (status and blockers), sprint review (demo) and retrospective (improve). Testers clarify acceptance criteria early and test within the sprint.
11
A screen reader announces 'button, button, button' on a toolbar. What is the bug and how do you report it?
Show answer
The toolbar uses icon-only buttons without accessible names, so users hear the role but not the purpose. Report it with the page, the screen reader and browser versions, the exact announcement and the expected one, such as 'Bold, toggle button, not pressed'. Reference WCAG 4.1.2 Name, Role, Value. The fix is an aria-label or visually hidden text on each button, plus a tooltip that also helps sighted users.
12
Managers say the automation test report is hard to understand. What should a useful report include?
Show answer
A useful report shows total tests run, passed, failed and skipped, the run time, the environment, build number and browser. For each failure it should show the test name, the failing step, the error message, and a screenshot, video or trace, plus logs. Trends across runs help spot flaky tests. Linking failures to Jira bugs or manual case IDs helps managers see real product risk, not just numbers.
13
SQL: find customers who placed more than three orders in the last 30 days.
Show answer
SELECT c.id, c.name, COUNT(o.id) AS order_count
FROM customers c
JOIN orders o ON o.customer_id = c.id
WHERE o.order_date >= CURRENT_DATE - INTERVAL '30' DAY
GROUP BY c.id, c.name
HAVING COUNT(o.id) > 3
ORDER BY order_count DESC;
14
Describe a time you missed a bug that reached production.
Show answer
Model answer: Situation: a discount was applied twice when users pressed the pay button quickly. Task: I had tested the feature and missed it. Action: I owned it in the retrospective, helped reproduce and verify the fix, and added double-click and slow network cases to our checklist for all payment buttons. Result: similar issues were caught in later sprints, and I learned to always test repeated actions.
15
What are suspension and resumption criteria in a test plan?
Show answer
Suspension criteria define when testing should be paused because continuing would waste effort, for example when a blocker bug stops the main flow, the build fails smoke testing or the environment is down. Resumption criteria define what must happen to restart, such as a new build that passes smoke testing or the environment restored. Writing these down avoids arguments and shows clearly why testing time was lost.
16
The build arrived three days late but the release date has not moved. How do you prioritise execution?
Show answer
Rank test cases by business risk and usage: critical flows like login, payment and data saving first, then new features, then high-risk regression from past defects, and cosmetic checks last. Run smoke testing immediately to avoid wasting time on a broken build. Share the reduced plan with the lead and product owner so they know what will not be covered, and get agreement on the remaining risk.
17
Your team wants to use an AI tool to generate test cases and automation scripts. What benefits and risks do you point out?
Show answer
AI assistants can draft test cases from requirements, suggest edge cases, generate first versions of scripts and test data, and some tools self-heal locators when the page changes. Risks are confident but wrong output, tests that assert the wrong behaviour, hidden locator changes that mask real bugs and leaking confidential data into external tools. Treat AI output like a junior's draft: review it, run it and keep human judgement on what matters.
18
What is decision table testing?
Show answer
List conditions and actions in a table and cover every combination of conditions (rules) — ideal for business rules like loan approval: salary > X AND credit score > Y → approve.
19
Write test cases for a signup form.
Show answer
Mandatory fields, email format, password rules, duplicate email, terms checkbox, captcha, confirmation email and field length limits.
20
What is performance testing and its types?
Show answer
Measuring speed and stability: load (expected users), stress (beyond limits), spike (sudden surge), endurance (long duration) and scalability testing.
21
A training portal is adding recorded video lessons and podcasts. What accessibility checks do you run?
Show answer
Check that prerecorded videos have accurate, synchronised captions, not just auto-generated ones with errors, and that audio-only content like podcasts has a transcript. Important visual information that is not spoken should have audio description or be covered in the transcript. Media should not autoplay with sound, and player controls must work by keyboard and be announced by screen readers. Also check that nothing flashes more than three times per second.
22
How do specification-based techniques differ from experience-based techniques?
Show answer
Specification-based (black box) techniques derive tests systematically from requirements: equivalence partitioning, boundary values, decision tables, state transitions and use cases. They give measurable coverage. Experience-based techniques rely on the tester's knowledge and intuition: error guessing, exploratory testing and checklist-based testing. They are good at finding defects the specification never mentioned. Strong testers use specification techniques for coverage and experience techniques to fill the gaps.
23
What are the seven principles of testing?
Show answer
Testing shows presence of defects, exhaustive testing is impossible, test early, defects cluster, the pesticide paradox, testing is context-dependent and absence-of-errors is a fallacy.
24
How do you handle a product owner who keeps adding scope in the middle of a sprint?
Show answer
Model answer: Situation: our product owner added two small changes to a story mid-sprint, which pushed testing to the last day. Task: protect quality without being rigid. Action: I showed the extra test effort in stand-up and asked the Scrum Master to help decide what to swap out. Result: one change moved to the next sprint, and the team agreed new requests go through the backlog.
25
What are the typical JIRA workflows for bugs?
Show answer
Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.
26
Write test cases for a one-to-one chat feature.
Show answer
Send and receive text messages and check order and timestamps. Test sent, delivered and read status. Send emojis, long messages, links and attachments within and over the size limit. Check messages sent while offline are queued and delivered on reconnect. Verify blocking a user stops messages. Test notifications when the app is in background. Check chat history after reinstall or on a second device, and that deleted messages disappear for both users if supported.
27
Write test cases for an OTP verification screen.
Show answer
Verify a correct OTP within validity logs the user in. Verify a wrong OTP shows an error and an expired OTP is rejected. Check the OTP length and that only digits are allowed. Test resend: it is disabled during the countdown, and the old OTP stops working after resend. Check the maximum number of wrong attempts locks verification. Verify auto-read on mobile, paste support, and behaviour when the network drops during submission.
28
How do you decide which automated tests run on every pull request and which run nightly?
Show answer
Pull request checks must be fast, usually under ten to fifteen minutes, and highly reliable, so they include unit tests, API tests for changed services and a small UI smoke set of critical flows. The full UI regression, cross-browser runs, long data-driven suites and performance checks run nightly or before release. Tag tests by suite, measure run times and flakiness, and move tests between suites based on value and speed.
29
What is cause-effect graphing?
Show answer
Cause-effect graphing is a black box technique that models input conditions (causes) and output actions (effects) with logical relations like AND, OR and NOT. The graph is converted into a decision table, and each column becomes a test case. It is useful when outputs depend on combinations of inputs, such as loan approval based on income, age and credit score. It helps find missing or contradictory rules in the requirement.
30
What is defect age?
Show answer
Defect age is how long a defect stays open, measured either in time, from the date it was logged to the date it was closed, or in phases, from the phase where it was introduced to the phase where it was found. High defect age signals slow fixing or triage. Phase-based age shows how late defects are caught; a requirement defect found in UAT has a high age and is costly.
31
How do you verify database schema changes in a new release?
Show answer
Get the migration script or change list. Compare the schema before and after: new tables and columns, data types, lengths, default values, NULL rules, indexes and constraints. Check that existing data was migrated correctly, for example a new status column filled for old rows. Run the main app flows to confirm queries still work. Finally, confirm the rollback script works on a copy, so the release can be reversed safely.
32
Write a JQL query for open high or highest priority bugs in the current sprint of project PAY.
Show answer
project = PAY
AND issuetype = Bug
AND statusCategory != Done
AND priority in (Highest, High)
AND sprint in openSprints()
ORDER BY priority DESC, created ASC
33
Your automated accessibility scan shows zero errors. Is the page accessible?
Show answer
Not necessarily. Automated tools catch only a part of WCAG issues, such as missing labels and contrast. A clean scan still needs manual checks: keyboard-only navigation, focus order, a screen reader pass, meaningful alt text and link names, error handling, zoom and reflow and dynamic content. Report the result as 'no automated violations found' and add the manual checklist outcome before claiming conformance.
34
Your backlog has 200 low-priority bugs and it is becoming unmanageable. How do you handle it?
Show answer
Run a backlog grooming session with the product owner. Close bugs that are obsolete, no longer reproducible or for retired features. Merge duplicates. Group the rest by module and user impact, and ask whether a few related bugs can be fixed together as one story. Agree to reserve a small share of each sprint for bug fixes. Set an ageing rule, for example review any bug older than 90 days.
35
The UI shows the correct order total, but the database has a different value. What do you check?
Show answer
Note the order ID and compare the UI value, the API response and the database value to find where they differ. Check if the UI calculates the total on the screen instead of using the saved value, whether taxes, discounts or rounding are applied at different layers and whether a later update job changed the record. Log the bug with all three values, because invoices and reports will use the database figure.
36
What is accessibility testing?
Show answer
Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.
37
How do you manage testing for multiple projects with competing deadlines?
Show answer
Model answer: Situation: I was supporting two products whose releases fell in the same week. Task: deliver both without dropping quality. Action: I listed tasks by release date and risk, agreed priorities with both leads, blocked focus time for each product and shared daily status. I also asked a teammate to take retesting on one project. Result: both releases went out on time with no critical escapes.
38
How do you chain requests in Postman by passing a token from login to the next call?
Show answer
// Tests tab of the Login request
const body = pm.response.json();
pm.environment.set('authToken', body.token);
// Next request header:
// Authorization: Bearer {{authToken}}
// Postman replaces {{authToken}} with the saved value
39
What is a traceability matrix?
Show answer
A grid mapping requirements to test cases and defects, proving every requirement is tested.
40
How do you run a moderated usability test session?
Show answer
Define goals and three to five realistic tasks, such as 'Book a train ticket for next Friday'. Recruit participants who match real users. In the session, explain that you are testing the product, not them, ask them to think aloud, and avoid hinting even when they struggle. Record the screen with consent, note where they hesitate or fail, and finish with a short questionnaire. Then group findings by severity and frequency.
Tips to crack the Red Hat Software Testing interview
- Get comfortable with Linux commands, shell scripting, processes, permissions and networking, which are central to many Red Hat roles.
- Contribute to an open source project or show GitHub work, since Red Hat values public collaboration and community involvement.
- Learn the basics of containers, Kubernetes and Ansible, and consider Red Hat certifications such as RHCSA for support roles.
- Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
- Practise the hard questions on this page aloud; Red Hat interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Red Hat Software Testing interview?
Candidates usually go through 4 stages: Online assessment or resume screening; Technical round 1 (Linux + programming); Technical round 2 (domain or open source); Hiring manager and HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Red Hat Software Testing interview?
This practice set leans on Test Case Design (10), Bug Life Cycle and Jira (7), Agile, SQL and API Testing (7), STLC and Test Planning (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Red Hat interviewers ask you to walk through real work.
Are these the exact questions asked at Red Hat?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Red Hat's. They are not a leaked or verified list of past questions.
Where does Red Hat hire Software Testing professionals in India?
Red Hat has large teams in Pune, Bengaluru. Openings and locations change often, so check the Red Hat careers page and filter by city and experience.
Software Testing questions for similar companies
Product
Amazon
Software Testing interview questions
Bengaluru, Hyderabad, Chennai +2
View questionsProduct
Workday
Software Testing interview questions
Pune
View questionsProduct
Software Testing interview questions
Bengaluru, Hyderabad, Gurugram +2
View questionsProduct
Autodesk
Software Testing interview questions
Bengaluru, Pune
View questionsProduct
NetApp
Software Testing interview questions
Bengaluru
View questionsProduct
ServiceNow
Software Testing interview questions
Hyderabad, Bengaluru
View questionsMore ways to practise
Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets