Are these the exact questions LinkedIn asks?

No. These are problems that commonly appear in LinkedIn coding interviews as reported across public community sources, chosen to match the patterns LinkedIn tends to favour. Interview content varies by team, role, and time, so treat this as a focused practice set rather than a question leak.

How should I practise these?

Open each problem, attempt it cold for twenty to thirty minutes, and run it against the test cases. If you get stuck, work out the optimal approach, then close the editor and re-solve from scratch the next day. Being able to reproduce a solution unaided is what carries into the interview.

Which language should I use?

Use the language you will interview in. The editor runs JavaScript, TypeScript, and Python in your browser, and Java, C, and C++ in a sandbox, so you can rehearse in your real stack.

Practice in the browser

LinkedIn coding interview problems

LinkedIn favours trees, graphs, and design-leaning questions, often with a follow-up that pushes on scale or an alternative data structure.

Commonly emphasisedTrees and graphsDesign follow-upsHash maps

These problems commonly appear in LinkedIn coding interviews based on widely shared public reports. They are not an official list and not leaked questions, and interview content varies by team and level. Use the set to focus your practice on the patterns LinkedIn tends to favour, then solve each one in the live editor.

easy

2 problems

medium

4 problems

Frequently asked questions

Are these the exact questions LinkedIn asks?: No. These are problems that commonly appear in LinkedIn coding interviews as reported across public community sources, chosen to match the patterns LinkedIn tends to favour. Interview content varies by team, role, and time, so treat this as a focused practice set rather than a question leak.
How should I practise these?: Open each problem, attempt it cold for twenty to thirty minutes, and run it against the test cases. If you get stuck, work out the optimal approach, then close the editor and re-solve from scratch the next day. Being able to reproduce a solution unaided is what carries into the interview.
Which language should I use?: Use the language you will interview in. The editor runs JavaScript, TypeScript, and Python in your browser, and Java, C, and C++ in a sandbox, so you can rehearse in your real stack.

Keep going

LinkedIn interview questions and process

All coding problems in the live editor

The NeetCode 150 roadmap and tracker

Guide: coding interview patterns

More companies

Google Meta Amazon Microsoft Apple Netflix