Timeline for Is it right to ask candidate why he is applying for developer while he was a leader?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2020 at 22:12 | history | edited | Joe | CC BY-SA 4.0 |
fixing typo
|
| Jan 12, 2017 at 18:52 | history | edited | Joe | CC BY-SA 3.0 |
added 65 characters in body
|
| Jan 12, 2017 at 18:44 | comment | added | iheanyi | @joe Agreed. I think perhaps the phrasing of the paragraph with "are you hiring a developer who won't grow" was what threw me - it is contrasted with growing into a leadership position but doesn't suggest an alternative of continual growth as a developer. | |
| Jan 12, 2017 at 17:34 | comment | added | Joe | @iheanyi Leadership != management. You're certainly right that being a developer and being a leader are not entirely identical, but I think that's important to understand during the interview: are you hiring a developer that you'd happy with staying a developer, or are you hiring a developer who you want to see some leadership skills from? I've hired for both positions, and it is always important to know which you're looking for. | |
| Jan 12, 2017 at 16:33 | comment | added | iheanyi | There is a difference between growing as a developer and growing into a leadership position. If management is so simple, that someone can learn it by osmosis, why waste a great developer when you could just hire a great manager when you need it (given that after all, you are interviewing for a developer now). | |
| Jan 12, 2017 at 8:51 | comment | added | Mawg | "all about finding red flags"? :-) but +1 for an otherwise good answer | |
| Jan 11, 2017 at 12:54 | history | answered | Joe | CC BY-SA 3.0 |