roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Explain Kotlin at the depth interviews probe, from null safety and the type system to coroutines and Flow. Covers classes and functions, collections, Java interop, multiplatform, tooling and testing.
1876 of 1876 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 1876 new. 0 cut, outside your plan.
Where you are interviewing decides which part of this tree carries the conversation. Android teams treat Kotlin as the working language of the whole loop, so questions slide from the language into the screen: collecting a flow without leaking work past a lifecycle, choosing `StateFlow` or `SharedFlow` for UI state and, on teams sharing code with iOS, what `expect` and `actual` declarations buy you. Backend teams, often partway through a migration from Java, probe the seam instead: what a platform type lets through, why Spring needs final-by-default classes opened for proxying, what a `suspend` function looks like when called from Java. Both open on null safety and the class model. Preparing for the full loop rather than the language alone? The [Android Developer](/roadmaps/android) and [Kotlin Backend Developer](/roadmaps/kotlin-developer) roadmaps place this topic among the platform, framework and design questions those interviews also ask.
Work through the plan by drilling questions, not by reading it top to bottom. The [Kotlin hub's primer](/topics/lang-kotlin) maps how the parts depend on each other; read it first if the language is new to you, and return to it when an answer feels recited rather than understood. A junior should be able to defend [null safety](/topics/lang-kotlin-null-safety) under follow-up questions before anything else: the difference between `?.`, `?:` and `!!`, and where a smart cast stops working. Middle candidates are usually separated by the [functional machinery](/topics/lang-kotlin-functional), inline functions and lambdas above all, because the coroutine API is built from it. Senior loops spend their longest stretch on [coroutines](/topics/lang-kotlin-coroutines), cancellation and exception propagation in particular. With little time, narrow level to the range you are aiming for, raise importance to must know and study by frequency.
Where you are interviewing decides which part of this tree carries the conversation. Android teams treat Kotlin as the working language of the whole loop, so questions slide from the language into the screen: collecting a flow without leaking work past a lifecycle, choosing StateFlow or SharedFlow for UI state and, on teams sharing code with iOS, what expect and actual declarations buy you. Backend teams, often partway through a migration from Java, probe the seam instead: what a platform type lets through, why Spring needs final-by-default classes opened for proxying, what a suspend function looks like when called from Java. Both open on null safety and the class model.
Preparing for the full loop rather than the language alone? The Android Developer and Kotlin Backend Developer roadmaps place this topic among the platform, framework and design questions those interviews also ask.
Work through the plan by drilling questions, not by reading it top to bottom. The Kotlin hub's primer maps how the parts depend on each other; read it first if the language is new to you, and return to it when an answer feels recited rather than understood.
A junior should be able to defend null safety under follow-up questions before anything else: the difference between ?., ?: and !!, and where a smart cast stops working. Middle candidates are usually separated by the functional machinery, inline functions and lambdas above all, because the coroutine API is built from it. Senior loops spend their longest stretch on coroutines, cancellation and exception propagation in particular. With little time, narrow level to the range you are aiming for, raise importance to must know and study by frequency.