3 ms·
I think researching the companies where you're interviewing is a good idea. Going into an interview with a list of ways to improve the product might not be beca
by brudgers 10y ago
I think researching the companies where you're interviewing is a good idea. Going into an interview with a list of ways to improve the product might not be because:
1. In most cases the detailed knowledge of the product and the customer base and the logistics and the costs are not available and an interviewee simply cannot have expertise.
2. In those cases where the product really is so bad that an interviewee could come up with feasible well structured changes, it's not unlikely that those changes will come across as "you people don't know what you are doing".
3. In cases where the people know what they are doing, an interviewee pushing changes can still come across as in item 2.
4. While every company isn't a 'We are all A players' type company, few companies want to hire someone whose world view is my coworkers are all mediocre and my current employer sucks...because that attitude tends to be portable across employers.
So my random internet advice is that next interview, mostly listen and let people talk about themselves and the company and to not offer unsolicited advice and to not slide into the role of 'the expert in the room.' Go into the interview and learn.
As a last thought, ten applications is not very many. It may simply be a case where the statistics are stacked against you.
Good luck.