Design a Table Component (Frontend)
A front-end developer interviewing in Singapore in August 2026, who went on to accept an offer, was asked for "a solution for a table component." The same interview asked how they manage complex side effects within custom hooks, and what they do to keep large component trees fast. Two more 2026 interviews point the same way. A Custom Software Engineering Specialist in Chennai (July) got scenario questions on component design, debugging and code optimization. A Custom Software Engineer in Pune got core JavaScript, React concepts (hooks, reconciliation, higher-order components and performance patterns) and some architecture discussion.
So the table is a vehicle. The interviewer wants to see where you put state and how you fetch without bugs. Then they want to know what happens when the screen has ten thousand rows. The prompt gives you almost nothing, so spend the first few minutes asking questions. How many rows can there be? Does the data live on a server? Do several screens reuse this table, or is it one page? The answers change the design more than any library choice.
AccenturePremium lesson · System design round
The Accenture design, worked end to end.
- Requirements and scopeSystem design · Frequently asked
- The API and data model
- The design, drawn out1 diagram
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports
Accenture interview guideKnow what Accenture asks before you walk in.
23 coding · 5 system design · 34 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.