Hire developers
Most Kotlin hiring is really Android hiring, so the pool skews toward mobile engineers who also carry years of legacy Java. That is a strength when you need someone who can navigate an old codebase, and a trap when you assume modern Kotlin idioms come standard. Server-side Kotlin (Ktor, Spring) and Kotlin Multiplatform are much thinner pools, so if that is the job, screen for it directly instead of trusting the keyword. The real risk is hiring someone who writes Java in Kotlin syntax and never touches coroutines, null safety, or the type system in a way that earns the language.
Look for a working grasp of coroutines and structured concurrency: what a scope is, when a job gets cancelled, and why launching work off the wrong dispatcher freezes the UI. Strong Android candidates can talk about the lifecycle honestly, configuration changes, process death, and where they lost state because they trusted the framework too much. Ask for a real story about an ANR or a memory leak they tracked down, ideally one where the coroutine or a leaked context was the culprit. Anyone can list Jetpack Compose on a resume, so probe whether they understand recomposition and why an unstable parameter tanks their frame times.
Describe the role in one chat and it goes live after a quick review. Kotlin developers apply straight to your inbox.
Post a roleFrontend Engineer
Senior Software Engineer | Backend-first | Distributed Systems & Applied AI
Looking for work? See Kotlin developer jobs.