3 ms·
If you’re interviewing for a junior position that would be fine. If you’re interviewing for something higher level that answer would definitely raise some red f
by sarchertech 4y ago
If you’re interviewing for a junior position that would be fine. If you’re interviewing for something higher level that answer would definitely raise some red flags.
The point is to see if the experience you claim matches what you have actually done.
- giantg2 4y agoThat's the condensed version of the answer for here. Obviously id go into the technical details in an interview. I work for a finance company. The vast majority of the devs, including seniors, haven't released any software outside of work. Maybe 10% have. It seems this is true for other non-tech industries too. Even on here, do you think more than 50% have released something they made by themself, that is more advanced than a simple Android app? Obviously there's a lot of talent here. I would be surprised if the number is higher than that.
- sarchertech 4y agoWhat about “what is the coolest thing you have ever built” makes you think it has to be by yourself, or outside of work? If you’re been working 5-10 years or more and you’ve never built anything at all that you’re excited about, that’s a red flag.
- giantg2 4y ago"What do you do for fun when not at work? … dig into to questions from here." Made me think the other questions are follow-ups to these. Eh, when you work on large systems in a large and highly regulated company, it's not very exciting. There have been some interesting components to those systems, but in general they have been mundane business topics with tight guiderails and little freedom. I mean, the majority of people in the world don't get "excited" about work - it's just the means of survival.