General discussion
-
Topic
-
Oooold way of conducting Software Engineer interviews (dev, test,…)
LockedI often meet practitioner saying, i learnt more and different things in one month while on project then in 4years of Engineering. Obvious pointer to outdated ways of teaching methodologies and curriculum.
I feel same with interviews of Software Engineers (freshers or experienced)… all starts with tell me about yourselves (despite reading it all in resume!!), more about projects done, problem solving etc. Do you think these freely inherited ways of conducting is correct way or there can be dramatically different way to evaluate candidate for best fitment to job? (thinkig aloud here, say expecting 20% new inducts contribution to innovations/patents, 20% should fall in category of followers, 20% should take lead in things and get things done, 20% should be ready to slog and so on…)