Software Thug Tech

Functional Programming in Kotlin: What Interviewers Mean by It, and Where It Stops Being Pragmatic on the JVM

The functional programming question in a Kotlin interview is not about lambdas. It is about immutability that is real, domain models where illegal states cannot exist, errors as values with the right channel for each kind, laziness with a cost model, and knowing where the JVM makes the pure approach expensive. Every snippet compiled and run on Kotlin 2.0.

JVM Runtime Questions for Kotlin Candidates: Memory Model, Garbage Collection, JIT, and the Traps Underneath the Language

Senior loops go one layer below the language: what @Volatile actually guarantees, what happens-before means, how synchronized and a coroutine Mutex differ under the hood, why GC pauses happen and what fixes them, why the first call is slow, and the Kotlin-specific runtime traps around boxing, lazy, object initialization, and inner classes. With compiled snippets where behavior can be shown.

"Find the Bug in This Function": Ten Planted Kotlin Bugs and How to Find Each One in Under a Minute

The debugging round hands you working-looking code and asks what is wrong. Here are ten Kotlin functions, each with one bug drawn from the gotchas in the earlier posts, the input that exposes it, the fix, and the method that finds bugs like these in under a minute. Every buggy and fixed version was compiled and run to prove the bug reproduces and the fix works.

Concurrency in Kotlin: The Coroutine Questions Senior Loops Ask, and the Answers That Hold Up

Kotlin candidates get asked about coroutines specifically: structured concurrency, cooperative cancellation, dispatchers, exception propagation, shared mutable state, and Flow versus Channel. Here are the questions, the mental model, ten compiled snippets, and the gotchas that separate people who have run coroutines in production from people who have read the guide.