Red Hat Business Analytics 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 Business Analytics 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 Business Analytics roles, this Red Hat practice set focuses most on Power BI and Tableau (7), Financial and Business Analysis (6), Requirements and Agile (5), SQL for Business Analysis (5). It has 34 medium, 6 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 Business Analytics 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.
Use one pool for the company with lanes for Employee, Manager and HR system. Start event: leave request submitted. Task: system checks leave balance. Exclusive gateway: balance sufficient? If no, end event that notifies the employee. If yes, user task: manager reviews. Add an interrupting timer boundary event of 3 days that escalates to the skip-level manager. Gateway: approved or rejected. Approved path updates the leave balance and calendar, then both paths notify the employee and end.
03
What are process levels such as L0 to L4 in a process architecture?
Process levels organise models from broad to detailed. L0 shows the value chain or main process areas, such as Order to Cash. L1 and L2 break these into process groups and end-to-end processes, such as Credit Management. L3 shows the detailed BPMN flow with roles and decisions. L4 covers work instructions or system steps. A level structure keeps hundreds of diagrams consistent, avoids duplicates and lets executives and operators each read the right depth.
04
A project's business case promised 30 percent cost savings, but after go-live only 10 percent is realised. What do you do?
Run a benefits review against the original baseline and assumptions. Check whether savings depended on actions that did not happen, such as reducing manual roles, retiring the old system or full user adoption. Check whether the baseline or volumes changed. Separate delayed benefits from lost ones. Then produce a recovery plan with owners, for example decommissioning the legacy licence or driving adoption. Also feed the lessons into how future business cases estimate benefits.
05
A business head wants 25 charts on one dashboard page. How do you respond?
Ask what decisions they make weekly and which three to five KPIs drive them. Propose a summary page with those KPIs, trends and one breakdown, then drill-through or separate pages for detail. Show a quick mock-up of both versions so they see the clutter and the load time. Use bookmarks or a field parameter to let them switch views without adding charts. Agree on the layout before building.
06
How would you prioritise 10 features with a limited budget?
Score them with RICE or value-vs-effort, align with goals, consider dependencies and risks, validate with stakeholders, then use MoSCoW for the release plan.
07
What steps would you follow to run a process discovery workshop?
Before: agree scope and process boundaries, invite people who actually do the work, not only managers, and collect existing documents and sample cases. During: state the goal, map the happy path first on a wall or digital board, then add exceptions, pain points, handoffs and volumes, and park off-topic issues. Keep timing visible. After: convert the output to a clean BPMN diagram within two days, circulate it for validation, and record open questions with owners and dates.
08
Write a SQL query that shows revenue, cost and gross margin percent by product category.
SELECT
p.category,
SUM(oi.quantity * oi.unit_price) AS revenue,
SUM(oi.quantity * p.unit_cost) AS cost,
ROUND(100.0 * (SUM(oi.quantity * oi.unit_price)
- SUM(oi.quantity * p.unit_cost))
/ NULLIF(SUM(oi.quantity * oi.unit_price), 0), 2) AS gross_margin_pct
FROM order_items oi
JOIN products p ON p.product_id = oi.product_id
GROUP BY p.category
ORDER BY gross_margin_pct DESC;
09
What is the answer-first or pyramid principle approach to presenting analysis?
Start with the main conclusion or recommendation, then give the two or three supporting reasons, and only then the detailed data. Senior stakeholders have little time, so a summary like 'Churn rose because of payment failures; fixing retries can save 4 lakh a month' should come first. Detail goes in the appendix. It is the opposite of a chronological walk through every step of the analysis.
10
A manager says the dashboard total does not match the finance team's Excel sheet. What do you do?
First agree on the definition: date range, gross or net, tax, returns, currency and which date (order or invoice) is used. Then reconcile at a small grain, such as one month and one region, comparing row counts and sums between the source query and the sheet. Common causes are filters on the page, missing relationships, duplicate rows after a join or a late refresh. Document the agreed definition in the report tooltip.
11
Write a DAX measure that shows each category's percent share of total sales.
Put both queries side by side and compare definitions: which events count as active, time zone, calendar versus rolling month, test and internal accounts, deleted users, and DISTINCT on user ID versus device ID. Run both on a single day to find where they diverge. Agree on one definition with the metric owner, document it, and publish it as a shared view or metric so everyone queries the same logic.
13
How would you decide whether to launch a new product?
Assess market size and demand, customer need, competition, unit economics, capabilities, risks and strategic fit, then test with a pilot before scale-up.
14
Write DAX measures for Total Sales, Sales Last Year and Year-over-Year growth percent.
Demand: population density, smartphone and digital payment penetration, average basket size and how often people buy groceries. Supply: dark store rent, rider availability and local sourcing. Unit economics: orders per store per day needed to break even, given lower average order values. Competition: local kirana delivery and other apps. Then propose a pilot in two or three cities with clear success metrics such as orders per day, contribution margin per order and repeat rate before scaling.
17
After many sprints, project documentation is out of date and new team members are confused. What do you do?
Identify which documents are actually used: usually a product overview, process maps, business rules, data dictionary and integration details. Update those first rather than everything. Make documentation part of the Definition of Done, so a story is not complete until related docs are updated. Keep living documents in a shared wiki with owners and last-reviewed dates, and archive outdated files clearly. Test the result by having a new joiner use it during onboarding.
18
A company reports a profit every quarter but is running out of cash. How do you explain and investigate it?
Profit is an accrual figure, while cash depends on timing. Check working capital first: receivables may be growing because customers pay late, inventory may be piling up, or suppliers may be demanding faster payment. Then look at large capex, loan repayments, and dividends. Review the cash flow statement and compute days sales outstanding and inventory days over time. Fixes include tighter credit terms, collection drives, inventory reduction and renegotiating supplier terms.
19
How do you calculate monthly revenue growth in SQL?
Compare total cost of ownership over the same period, usually 3 to 5 years. Include licence or subscription fees, implementation, data migration, integration, training, internal staff time, infrastructure, support and upgrade costs, and exit costs. Discount the yearly totals to present value if the timing differs. Then weigh the result against non-cost factors such as fit to requirements, scalability and vendor stability. Often the cheaper licence ends up costlier once customisation and support are added.
22
Tell me about a time poor or outdated documentation caused a problem. How did you fix it?
Situation: a new developer built a GST calculation from an old FRD version, and the error was caught only in UAT. Task: fix the defect and prevent repeats. Action: I moved all requirement documents into one shared space with version history, added a change log and status labels such as draft or approved, and linked each user story to the latest approved section. Result: in the next two releases we had no defects caused by outdated specifications.
Define the scope: where the process starts, such as a refund request, and where it ends, such as money credited. Identify the roles involved and draw swimlanes. Interview and observe each role, capturing steps, decisions, systems used, handoffs and time taken. Draw the flow in BPMN, mark pain points like rework loops and waiting time, and add measures such as average refund time. Validate the map with the people who do the work.
25
Write a SQL query for the top 3 products by revenue in each category.
WITH ranked AS (
SELECT category, product_id, SUM(amount) AS revenue,
DENSE_RANK() OVER (PARTITION BY category
ORDER BY SUM(amount) DESC) AS rk
FROM sales
GROUP BY category, product_id
)
SELECT category, product_id, revenue
FROM ranked
WHERE rk <= 3
ORDER BY category, rk;
26
Five departments each build their own Power BI reports with different revenue numbers. How would you design a better BI setup?
Create a shared, certified semantic model with one definition per KPI, built on a governed warehouse layer. Departments build thin reports on top of it through live connection instead of copying data. Set up workspaces by environment (dev, test, prod), deployment pipelines, naming standards, a KPI glossary and owners for each measure. Keep a small central team for the core model and let departments self-serve on top, which balances control and speed.
27
Describe a time you led the requirements phase of a large project.
Situation: our company was replacing its loan origination system across five business units. Task: lead requirements with two other BAs in three months. Action: I set up a stakeholder map, ran structured workshops per unit, used shared templates and a traceability matrix, and held weekly review checkpoints with the sponsor to resolve conflicts quickly. Result: requirements were signed off on time, change requests in build stayed low, and the template was reused for later projects.
28
A mid-size manufacturer must choose between building and buying a warehouse management system. How do you advise?
Compare options on fit, cost, time and risk. Buying a proven product is faster with lower risk and includes upgrades, but may need process changes and has recurring licence fees. Building fits unique processes exactly but needs a strong tech team, longer time and ongoing maintenance. Estimate five-year total cost of ownership, check whether processes are truly unique, and usually recommend buying and configuring unless warehousing is a core differentiator.
29
Your measure shows the same value on every row of a matrix. Why might that happen?
The filter from the row field is not reaching the fact table. Usually there is no relationship between that dimension and the fact, the relationship is inactive, or it filters in the wrong direction. It can also happen when the measure uses ALL or REMOVEFILTERS on that column, or when the row field comes from the fact table of a different grain. Check the model view and test the measure with a simple SUM.
30
Developers and testers interpret the same user story differently. How do you fix this?
The story is ambiguous, so bring the three amigos together: BA or product owner, a developer and a tester. Walk through concrete examples, including edge cases and error cases, and write them as acceptance criteria, ideally in Given-When-Then format. Add business rules, sample data and mock-ups where needed. Update the story and use the same practice in refinement for future stories, so gaps are found before coding starts.
Row-level security restricts which rows a user can see in the same report. In Desktop you create roles under Manage Roles with a DAX filter, such as 'Region'[Manager Email] = USERPRINCIPALNAME() for dynamic RLS. You test with View as Role, publish, and then map users or groups to roles in the Service. Dynamic RLS with a mapping table scales better than creating one static role per region.
33
Tell me about a time a SQL query you wrote gave wrong results. How did you catch it?
Situation: my weekly sales report showed a 12 percent jump that no one could explain. Task: verify the number before it reached leadership. Action: I compared row counts before and after each join and found a new promotions table had multiple rows per order, duplicating revenue. I aggregated promotions per order first and added a test comparing totals with the source. Result: the corrected report went out the same day, and I now check grain on every new join.
34
Split the epic 'Customers can track their order online' into user stories.
Possible stories: As a customer, I want to see my order status (placed, packed, shipped, delivered) so that I know its progress. As a customer, I want an SMS or email when the status changes so that I do not have to check. As a customer, I want the expected delivery date so that I can plan. As a customer, I want a courier tracking link once shipped. As support staff, I want to see the same timeline so that I can answer queries.
35
Describe a time your analysis found a cost-saving opportunity.
Situation: monthly cloud and software subscription costs had grown 35 percent in a year without anyone tracking why. Task: my manager asked me to review them. Action: I combined invoices with user login data in Excel and found 140 licences unused for over 90 days and two tools doing the same job. Result: we cancelled unused licences and consolidated tools, saving about 18 lakh rupees a year, and I set up a quarterly licence review report.
36
Write Excel formulas for IRR with yearly cash flows and XIRR with irregular dates.
# Yearly cash flows in B2:B7, year 0 investment negative
=IRR(B2:B7)
# Irregular dates: cash flows in B2:B7, dates in C2:C7
=XIRR(B2:B7, C2:C7)
# XIRR returns an annualised rate based on actual dates,
# which suits SIP returns or projects with uneven payments.
37
What steps do you follow to plan and run a UAT cycle?
Plan: agree scope, entry and exit criteria, testers and schedule with the business owner. Prepare: write scenarios and test cases from requirements, set up the environment and test data, and brief testers. Execute: run test cases in daily sessions, log defects with evidence and hold a daily triage. Monitor: report progress, pass rate and open defects by severity. Close: check exit criteria, get the business sign-off with known issues documented, and hold a short lessons-learned review.
38
The totals in your Excel report differ from the finance system by a few rupees. What could cause this?
Usually rounding. Excel may display rounded values while summing the full-precision numbers, or line items were rounded individually in the source system and the total was computed differently. Check whether finance rounds each invoice line before summing, and apply ROUND at the same level in Excel. Other causes include floating-point artifacts, values stored as text being skipped by SUM, or hidden filtered rows. Agree and document one rounding rule with finance.
39
An A/B test shows a 5 percent higher conversion rate, but revenue per user is lower. Should you ship it?
Not automatically. Find out why: the variant may push cheaper products, bigger discounts or smaller orders, so more people buy but each spends less. Check average order value, margin and long-term metrics like repeat purchase. Decide based on the metric tied to the business goal, usually revenue or contribution per user, which should have been the primary metric or a guardrail. Consider iterating to keep the conversion gain without lowering order value.
40
Write a SQL query to show cumulative revenue by month.
WITH monthly AS (
SELECT DATE_TRUNC('month', order_date) AS month,
SUM(amount) AS revenue
FROM orders
GROUP BY 1
)
SELECT month, revenue,
SUM(revenue) OVER (ORDER BY month) AS cumulative_revenue
FROM monthly
ORDER BY month;
-- add PARTITION BY EXTRACT(YEAR FROM month) to reset each year
Tips to crack the Red Hat Business Analytics 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 Business Analytics 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 Business Analytics interview?
This practice set leans on Power BI and Tableau (7), Financial and Business Analysis (6), Requirements and Agile (5), SQL for Business Analysis (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 Business Analytics 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.
Business Analytics questions for similar companies