AMD Business Analytics Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About AMD hiring for Business Analytics roles
AMD is an American semiconductor company that designs CPUs, GPUs, adaptive chips and data centre accelerators, including Ryzen, EPYC, Radeon and Instinct products. It acquired Xilinx, adding FPGA and adaptive computing products. In India it has large design centres that hire chip design, verification, physical design, software and firmware engineers.
For Business Analytics roles, this AMD practice set focuses most on Business Metrics and KPIs (9), Requirements and Agile (6), Financial and Business Analysis (4), SQL for Business Analysis (4). It has 3 easy, 35 medium, 2 hard questions, so you can start easy and work up to the harder ones.
Company type
Hardware & semiconductors
Headquarters
Santa Clara, California, USA
Main India offices
Bengaluru, Hyderabad
AMD Business Analytics interview process
Online assessment or resume screening
Technical round 1 (digital design or programming)
Technical round 2 (domain depth)
Hiring manager round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for AMDStart 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.
A balanced scorecard is a strategic performance framework that tracks objectives and KPIs across four perspectives: financial (revenue growth, margin), customer (NPS, retention), internal processes (cycle time, defect rate) and learning and growth (training hours, employee engagement). The idea is that financial results are lagging, so leaders also need leading measures of what drives future performance. A strategy map links the objectives with cause-and-effect arrows from people to processes to customers to financial outcomes.
02
An order has a value of 600 rupees, product cost 360, delivery 60, payment fee 12 and a discount of 50. What is the contribution margin?
Net revenue after discount is 600 minus 50, which is 550 rupees. Variable costs are 360 plus 60 plus 12, totalling 432. Contribution margin is 550 minus 432, so 118 rupees per order, or about 21 percent of net revenue. This is what each order contributes towards fixed costs such as salaries and rent. If the discount were raised to 150, the order would contribute only 18 rupees.
03
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.
04
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.
05
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.
The product owner owns the product vision and the backlog order, makes final priority decisions and accepts completed work on behalf of the business. The business analyst works on understanding problems in depth: eliciting and analysing requirements, modelling processes and data, writing detailed stories and acceptance criteria and supporting the team and testers. In smaller teams one person may do both, but the PO decides what, while the BA clarifies how it should work.
08
What is the difference between a task and a sub-process in BPMN?
A task is an atomic unit of work that you do not break down further in the diagram, such as Verify PAN details. A sub-process is a compound activity that contains its own flow of tasks, events and gateways, shown with a small plus sign when collapsed. Sub-processes keep high-level diagrams readable: the main map shows Credit Check as one box, and a separate detailed view explains its internal steps.
09
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;
A use case describes the full interaction between an actor and the system (main and alternate flows). A user story is a short statement of need from the user's point of view, refined with acceptance criteria.
Check whether the extra sign-ups are lower-intent users who would naturally retain less. Compare Day-7 retention for comparable users in both versions and count retained users in absolute terms, not just rates. If the new flow skips a step that led users to the aha moment, retention per user may truly fall. The decision depends on whether total retained, valuable users went up or down.
13
Guesstimate: how many new two-wheeler helmets are sold in India each year?
Drive it from vehicles. Assume about 2 crore new two-wheelers are sold a year, each with an average of 1.5 helmets bought (rider plus pillion), giving 3 crore. The existing fleet is around 25 crore vehicles; assume 60 percent are active and each active vehicle replaces one helmet every 3 years: 15 crore / 3 = 5 crore. Total is about 8 crore helmets a year. Sanity check: enforcement varies by state, so give a range of 6 to 9 crore.
Title: Invoice applies 12 percent GST instead of 18 percent for service items. Environment: UAT, build 2.4.1. Steps: create an order with service item SRV-101 at 1,000 rupees for a customer in Maharashtra and generate the invoice. Expected: CGST 90 and SGST 90, total 1,180. Actual: CGST 60 and SGST 60, total 1,120. Severity: high, as it affects tax compliance. Attachments: invoice PDF and screenshot. Linked requirement: FR-TAX-07.
16
How do you validate that a report's numbers are correct?
A UAT test plan defines how acceptance testing will be run. It covers scope and out-of-scope items, business processes to be tested, entry and exit criteria, roles such as testers, UAT lead and sign-off authority, test environment and test data, schedule and cycles, defect management process with severity definitions, communication and reporting, and risks. The BA usually drafts it with business owners so testers know exactly what they are accepting and when.
Horizontal analysis compares line items across periods, showing growth, for example revenue up 18 percent year on year while employee costs grew 30 percent. Vertical analysis expresses each item as a percentage of a base within one period, such as each expense as a percentage of revenue, or each asset as a percentage of total assets. Together they show both trends and structure, and vertical analysis also makes companies of different size comparable.
A data object (page shape with a folded corner) represents information that an activity needs or produces during one process instance, such as an invoice or an application form. It is linked with dotted associations. A data store (cylinder) represents information that persists beyond the process instance, such as the customer database or ERP. Showing them helps developers see which systems are read or updated at each step and helps spot missing integrations.
22
What is Average Order Value and how can a business increase it?
Average Order Value is total revenue divided by number of orders. If an online store earns 9 lakh from 1,500 orders, AOV is 600 rupees. Businesses increase it with bundles, cross-sell and upsell recommendations, free delivery above a threshold, volume discounts and premium options. Watch margin and conversion while doing so, because a high free-delivery threshold can raise AOV but reduce the number of orders.
23
A ride-hailing app's ride cancellation rate rose from 8 to 14 percent. How would you structure the problem?
First split by who cancels: riders or drivers. For rider cancellations, check wait times, pickup accuracy, price surges and changes in ETA. For driver cancellations, check trip distance, payment mode, low fares, destination visibility and incentive changes. Then segment by city, time of day and area. Link to recent changes like a new pricing rule. Recommend fixes for the largest driver, such as better matching or adjusted incentives.
24
What are leading and lagging indicators? Give examples.
Lagging indicators measure outcomes after they happen, such as monthly revenue, profit or churn. They confirm results but are hard to influence directly. Leading indicators move earlier and predict outcomes, such as demo bookings, trial activations, cart additions or support ticket backlog. A good KPI set pairs them: a sales team tracks qualified pipeline (leading) along with closed revenue (lagging) so it can act before the quarter ends.
25
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.
Waterfall runs fixed phases one after another with requirements frozen early. Agile delivers in short sprints with continuous feedback, so requirements can change. In Agile, BAs maintain the backlog and user stories.
30
What is a change request and how does change control work?
A change request is a formal proposal to modify agreed scope, requirements, timeline or budget. In change control, the request is logged, the BA analyses impact on effort, cost, schedule, risk and other requirements, and a decision body such as the sponsor or change board approves, rejects or defers it. Approved changes update the requirements, plan and traceability. In Agile, most changes go through backlog reprioritisation instead.
31
After joining orders to a payments table, your total revenue doubled. What went wrong?
The join created a fan-out: some orders have more than one payment row, such as split payments or retries, so each order amount is repeated. Check the grain by counting rows per order_id on both sides. Fix it by aggregating payments to one row per order in a CTE before joining, joining on the full key, or summing from the table whose grain matches the metric. Always compare row counts before and after a join.
32
Your process diagram has grown to 80 shapes on one page and stakeholders say they cannot read it. What do you do?
Restructure it into levels. Create a high-level map with 7 to 10 main steps, then collapse detailed parts into sub-processes with their own diagrams. Move complex decision logic into a decision table rather than chains of gateways. Show the happy path first and handle exceptions in separate views. Use consistent naming in verb-noun form and remove duplicated steps. Finally, test readability by asking a stakeholder to explain the diagram back to you.
33
In UAT cycle 2, a feature that passed in cycle 1 is now broken after a defect fix. What does this tell you and what should change?
It is a regression: the fix for one defect broke existing functionality, which usually means changes were not impact-analysed and there is no regression suite. Log it as a new high-priority defect linked to the fix. Agree with the team that every UAT build comes with release notes listing the changes, and that QA runs an automated or core manual regression pack before handing the build to business testers. Also add the broken flow to the UAT regression checklist.
34
What is the difference between zero-based budgeting and incremental budgeting?
Incremental budgeting takes last year's budget and adjusts it by a percentage, which is quick but carries forward old inefficiencies. Zero-based budgeting starts every cost line from zero, and each activity must be justified by its value each cycle. ZBB uncovers waste and suits cost-reduction programmes, but takes much more effort and can create friction. Many companies apply ZBB to discretionary costs such as marketing and travel and use incremental methods elsewhere.
35
A KPI on your dashboard dropped 40 percent overnight. What are your first steps?
Assume a data problem until proven otherwise, because real businesses rarely move 40 percent in a day. Check whether the refresh completed, whether source row counts look normal, and whether any tracking, pipeline or definition changed. Compare with a raw source query and a related metric, such as orders versus payments. If the data is fine, segment by channel, region and platform to locate the drop, then alert the owners quickly.
36
Guesstimate: how many cups of tea are sold in Delhi per day?
Population about 20 million, adult tea drinkers about 50%, cups bought outside per person around 1 on average. This gives roughly 10 million cups, then adjust for offices and stalls.
37
How would you measure the success of a new feature?
Define a goal metric, a baseline and guardrail metrics, run an experiment or before-after comparison and review adoption, retention and revenue impact.
38
Describe a time you had to present disappointing numbers to leadership.
Situation: a new city launch was 30 percent below its order target after two months. Task: present the review to the leadership team. Action: I opened with the number directly, then broke the gap into traffic, conversion and repeat rate, showing repeat rate was the main problem. I came with three options with estimated impact and cost. Result: leadership approved a focused retention campaign instead of more ad spend, and repeat rate rose over the next quarter.
Situation: my manager asked why customer complaints were rising, but complaints were stored as free text with no categories. Task: give an answer within a week. Action: I sampled 300 complaints, created categories, tagged them manually and used keyword rules in Excel to classify the rest, then validated with the support lead. Result: late refunds were 40 percent of complaints, the refund process was fixed, and categorised tagging was added to the support tool.
Tips to crack the AMD Business Analytics interview
Revise digital electronics, computer architecture, Verilog and verification basics for silicon roles, with clear explanations of timing concepts.
For software and driver roles, revise C, C++, operating systems and parallel computing basics, including GPU programming concepts.
Prepare detailed explanations of VLSI or embedded projects, including tools used, problems faced and how you solved them.
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; AMD interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the AMD Business Analytics interview?
Candidates usually go through 4 stages: Online assessment or resume screening; Technical round 1 (digital design or programming); Technical round 2 (domain depth); Hiring manager 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 AMD Business Analytics interview?
This practice set leans on Business Metrics and KPIs (9), Requirements and Agile (6), Financial and Business Analysis (4), SQL for Business Analysis (4). Revise those first, then practise explaining one or two of your own projects end to end, because most AMD interviewers ask you to walk through real work.
Are these the exact questions asked at AMD?
No. These are curated practice questions that match the skills and difficulty usually tested in hardware & semiconductors interviews like AMD's. They are not a leaked or verified list of past questions.
Where does AMD hire Business Analytics professionals in India?
AMD has large teams in Bengaluru, Hyderabad. Openings and locations change often, so check the AMD careers page and filter by city and experience.
Business Analytics questions for similar companies