So, I’ve been promoted to Senior Engineer in the last couple of months and that felt really good because I felt that people recognized my efforts to progress and that my dedication paid off. The problem is that, as a senior, I am supposed to become more part of the recruitment processes, through code review candidates applications, interviewing, etc. All fine by me, but sometimes I get haunted by the too familiar Imposter Syndrome when looking at the code submissions of some candidates for some of the challenges we ask them, I am supposed to be evaluating people that in some cases have (at my eyes) solutions that I would not be able to implement in such detail or finesse and some times I end up spending some hours going through some solutions just to grasp everything that a candidate has done. Am I an imposter or is this just another phase of the process?
Just a slightly different angle. The best managers and team builders are people that aren’t afraid to get people in with skills far out pacing their own. Maybe some one can program this task better than you but the company has trust in you to find those people and put them in the best environment to leaverage that skill. The best skill you can have is using other people’s skills together. No body wants a manager who can only program. They want a leader and some one who is knowledgeable in their peticular code base. A programming test shows they can program but doesn’t mean they’ll have the years of knowledge of your code base that you do
The best managers and team builders are people that aren’t afraid to get people in with skills far out pacing their own.
This is the most important thing when hiring. If staff only hire new employees that are less experienced/talented than themselves then the skill level of the team reduces over time. If you give hiring staff the target of finding someone better than they are, the skill of the team increases over time.
I see it as a different skillset. You possess skills to cut maintainable code, work through issues (technical and people), and whatever other traits the organisation sees you doing well in, or have the potential to. That is quite different from interviewing, which is often just about impressing people enough to let you in the door. I say this having gone through the same process. If you’re that worried, study the code as you’re already doing, grind leetcode, or my preference - pick up harder problems and run with them. You’ll learn some new stuff, maybe build something cool and feel a bit less like an imposter.
