Question lists, and what we actually answer

Real Java question sets — some from a named interview loop with the company, role and date, some curated revision lists — with every question pointing at wherever this site answers it. The coverage number is the point: you can see the gaps instead of guessing at them.

Reported, not verified

These are shared by candidates, not verified by us, and not endorsed or confirmed by the companies named. Everything else on this site is checked on every build; this section is reported rather than verified, and it is kept separate for exactly that reason. Process varies by team, by interviewer and by year, so treat a list as one loop that happened, not as a syllabus you can expect to be repeated.

41 of 102 questions across every list are answered somewhere on this site. The rest are gaps, and they are marked as gaps.

How to use a list like this

Not as a syllabus. A loop is one team on one day, and the same company runs a different interview next quarter; a curated list is one person’s judgement. What either is genuinely good for is calibration — the shape of the questions at a given level, and how much depth a single question is expected to carry.

The coverage numbers are here because they are the honest version. 40% of the questions across these lists have a deep-dive answer here; the rest do not yet, and pretending otherwise would waste your time. A list whose coverage is low is not a bad list — it is a list pointing at something unwritten, which is how the writing order here gets decided. For the planned curriculum and what is written against it, see the question bank and the company-type breakdowns, which describe patterns rather than single loops.