Post

Hiring for the Ability to Learn

Why I think engineering teams should make room for candidates who can pick up unfamiliar systems.

Reading job descriptions during a search can make it feel like you’re expected to know every tool before you start. I understand why a team wants someone who can contribute quickly. I also think every new job has a learning period, including for senior engineers who’ve already worked on complicated systems.

Someone may have to learn the company’s platform, terminology, or deployment process. Experience still helps. An engineer who knows how to find good information, ask focused questions, and work through a problem can transfer that skill to an unfamiliar stack.

During my search, I spent some time learning the basics of OpenTelemetry and Kubernetes. It helped to have specific things to explore. A small project, a course, or a conversation about what you’re trying to learn can all make the next step clearer.

If I’m evaluating someone, I want to know how they’ve picked up something unfamiliar before. That tells me something a list of tools can miss.

Adapted from my original LinkedIn post. Read the original on LinkedIn

This post is licensed under CC BY 4.0 by the author.