30+ years of tech, retired from an identity intelligence company, now part-time with an insurance broker.
Dev community mod - mostly light gardening & weeding out spam :)
Thank you for sharing your experience and the assessment of some useful resources :)
Last interview I was in, because the candidates were internal staff, we went though a shared design challenge together, working /with/ each candidate on a /real/ challenge for the business. This was coupled with the pre-prepared PBI starting points, and of course existing knowledge of their work within the company.
This gave both parties a good feel for what it might be like working together, and provided an opportunity for each candidate to explore a new challenge and widen our understanding of their personal motivations, career aspirations and desires for the business itself.
Experienced software and UX guy. Over 20 years making professional software. Lots of tech/tools/languages. Father of 7. Armchair philosopher. Currently focused on full stack dev with React, Node..
I agree collaborative design challenges are another useful tool. When I was leading Design at one company, that was a key component of the process because collaborative design and critique are essential to the Design process. It's a great way to see how people interact on the team in that way. That's one reason why I like to include the code review as part of the process above--it helps get a sense for those dynamics.
Thanks for sharing!
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.
Thank you for sharing your experience and the assessment of some useful resources :)
Last interview I was in, because the candidates were internal staff, we went though a shared design challenge together, working /with/ each candidate on a /real/ challenge for the business. This was coupled with the pre-prepared PBI starting points, and of course existing knowledge of their work within the company.
This gave both parties a good feel for what it might be like working together, and provided an opportunity for each candidate to explore a new challenge and widen our understanding of their personal motivations, career aspirations and desires for the business itself.
Hi Phil,
I agree collaborative design challenges are another useful tool. When I was leading Design at one company, that was a key component of the process because collaborative design and critique are essential to the Design process. It's a great way to see how people interact on the team in that way. That's one reason why I like to include the code review as part of the process above--it helps get a sense for those dynamics.
Thanks for sharing!