52 karma · joined December 25, 2019
I've adopted a mindset where each persona is just a tool for a specific situation or setting, but I always try to be aware that it is just the self using the persona, not the other way around. I had fallen into the trap of strongly identifying with a persona and was wondering why I was feeling so confused, so stepping back a bit helped a lot.
Reading about Jung's map of the psyche has been quite interesting and useful.
In my opinion, "years of experience" should not be disqualified as one of multiple evaluation tools for skill. I think it signifies that you have had the opportunity to go through a variety of situations, challenges, projects etc. and you have accumulated knowledge and experience that cannot be learned by reading tutorials or working on side projects.
From personal experience and by talking to and working with other much more experienced engineers than me, I have noticed that some of the most important knowledge is obtained just by working on something for a longer amount of time.
Obviously, there are many exceptions to this rule, there are engineers with years and years of experience that are just bad at what they do. What I am trying to say is that this tool for evaluation should not be discarded.
I've had a couple of situations where I go in an interview and the interviews ask me questions that show to me that they have not even looked at my CV and the cover letter they asked me to write. They were just reading off a list of generic tech interview questions.
To me that feels like if I went to interview at a company and told them I have no idea who they are or what they do, I just know their name and that they are looking for a coder. That's just counterproductive.
But I totally agree with you that there is no single solution. I just think there are different "good" questions for different people, interviewers and interviewees need to adapt to that.
I have always wondered why this isn't more common, it makes so much sense to me. When you submit an application you usually submit links to your blog, GitHub, projects etc. When I attend an interview I expect us to talk about those things. This is what the person is supposed to be good at. Instead you are met with a predefined set of puzzle questions.
I think the purpose of the interview is to allow the candidate to show what they are good at and what they are excited about and to see if this fits well with what your company is doing.
The main focus is the content of the document and the other content it leads to. Not the style, the features, the tech that it uses to load the content. I compare it to books. Most books are the same, predictable. They will have text and some images on pages. When turning a page it will show another page. It wont suddenly ask you to log in or go buy another book in the middle of this one. The covers of the books are slightly different but the basic function is the same. That's it.