In job interviews, what elements of your development experience/expertise do you find most challenging to articulate, prove, or demonstrate?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (5)
The design of a product and its architecture.
We can always provide useful information by following the STAR rule, and sometimes this info would even be enough for non-developers making decisions.
However, even with the STAR rule, reaching a common understanding of architecture works requires much more effort, from both sides of the interview.
The interviewee must be able to describe the work from abstract to details, from plain & simple language to developers' tongue.
On this occasion, the pyramid principle is a practical choice.
The fact that we provide a ton of open source projects, yet they still demand silly technical exercises.
I've heard this same frustration before, are you referring to showing them open source contribution but them ultimately still requiring the technical exercises despite you having demonstrated the competence in the open source project?
My background is mechanical engineering.
After graduated, I hardly pass the interview process in manufacturing area, because I;m partially color blind.
That's really frustrating! Did they accommodate this at all? Seems like something that they should account for in some way.