Intel Software Engineer, Full Stack | Second Round
Question Details
I had second round which was based on front-end question Problem statement: 1. Create the table as shown in the image, you can divide the components into 2 parts, one for the...
Full Details
I had second round which was based on front-end question
![image](<a href="https://assets.leetcode.com/users/images/9dc3459f-f802-4da6-a60e-bb5547e47743_1659370818.2770276.png" target="_blank" rel="noopener" class="text-emerald-400 hover:text-emerald-300 underline">https://assets.leetcode.com/users/images/9dc3459f-f802-4da6-a60e-bb5547e47743_1659370818.2770276.png</a>)
Problem statement:
1. Create the table as shown in the image, you can divide the components into 2 parts, one for the dropdown and one for the table itself.
2. The table should show all unique processes in a sorted order.
3. Every process has some defined nodes. Each node should be color coded as per their status, approved should be green,
rejected should be red, in evaluation should be white and pending should be grey.
4. Each node should also display its name and efficiency, where efficiency is calculated by the amount of workday/number of unique managers.
5. Each node should be displayed in their appropriate position defined by the month
6. If 2022 is selected in the dropdown, then only nodes with the year 2022 should be displayed and if 2021 is selected nodes with year 2021 should be displayed.
7. The total nodes per quarter should be displayed at the bottom, Ex: Q1 has 3 nodes Projects/Qtr, Q2 has 2 nodes Projects/Qtr
8. As a bonus question, you can add a delete icon next to the nodes that will delete the nodes from the table.
9. You can style the table however you like but please note nodes should follow point 3.
About This Question
This is a reported interview question from a intel interview for a frontend role reported in 2022.
More Intel Interview Questions
About Intel Interview Reports
This question was reported by a candidate who interviewed at Intel. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Intel are the higher-signal extractions to take from this report.
For broader preparation context, the Intel interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Intel reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Intel Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Intel reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.