Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
My questions for candidates are designed explicitly to show me how they think.
They are often open-ended and highly subjective. My goal is not to determine what the correct answer is, but to evaluate how they arrive at any answer.
Most recently, that might mean asking them how they would prepare for a new freelance project with no background information.
I'd be looking for things like how they read documentation, how they test and scale, how they interact with clients, and how they keep themselves organized.
I mostly just want to hear them talk. I want to measure their confidence in themselves and what they know.
Every now and then I'll throw a curveball, but the idea is to never force a "gotcha" moment, but to instead work through with them how they might rectify their mistake.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My questions for candidates are designed explicitly to show me how they think.
They are often open-ended and highly subjective. My goal is not to determine what the correct answer is, but to evaluate how they arrive at any answer.
Most recently, that might mean asking them how they would prepare for a new freelance project with no background information.
I'd be looking for things like how they read documentation, how they test and scale, how they interact with clients, and how they keep themselves organized.
I mostly just want to hear them talk. I want to measure their confidence in themselves and what they know.
Every now and then I'll throw a curveball, but the idea is to never force a "gotcha" moment, but to instead work through with them how they might rectify their mistake.