3 ms·

I had a pretty similar experience while going through a series of interviews at the beginning of last year. The way to really get your compensation up is to do

I had a pretty similar experience while going through a series of interviews at the beginning of last year. The way to really get your compensation up is to do as the article suggests and interview many places in parallel. Then negotiate offers to get what you want. I found I don't actually like take home interviews, I work as a mobile engineer so it's often the same take home, a list of stuff retrieved a back-end and then rendered in a list on screen. Selecting a list item should open up a details page. While the take home is never particularly difficult, the boundaries of the task are often not set clearly. So it's easy for that 4 hours to extend to a whole weekend to make sure all the latest patterns, and trendy libraries are used. Annoyingly on a few occasions after sinking a weekend into a project, I have had an auto-reject with no feedback. That soured me on them. I have put a few hundred leetcode practice problems over the years and can discuss mobile system design pretty extensively, i'd rather interview that way in future.

etblg 5y ago
> So it's easy for that 4 hours to extend to a whole weekend to make sure all the latest patterns, and trendy libraries are used. And including those could potentially be a liability. I had a take-home assignment (a front-end application) where I decided to use Typescript, because I would like to use it and I figured it would reflect nicely. One of the items of feedback given (I still passed) was that there was an implicit "any" in the code. If I hadn't included Typescript would I have gotten feedback that I wasn't using Typescript? If you're using Typescript but not going the full 10 yards and making sure it's set up in a perfect way you'd use it in production? Could including it harm your chances over not including it because you're not using it in a way the reviewer likes? Ultimately you'd think it wouldn't matter and that just including it was good enough (and I think it was for this specific reviewer), but it's a tricky game of hoping your choices line up with the unknown opinions and biases of the person reviewing in order for it to work out.

etblg 5y ago

> So it's easy for that 4 hours to extend to a whole weekend to make sure all the latest patterns, and trendy libraries are used. And including those could potentially be a liability. I had a take-home assignment (a front-end application) where I decided to use Typescript, because I would like to use it and I figured it would reflect nicely. One of the items of feedback given (I still passed) was that there was an implicit "any" in the code. If I hadn't included Typescript would I have gotten feedback that I wasn't using Typescript? If you're using Typescript but not going the full 10 yards and making sure it's set up in a perfect way you'd use it in production? Could including it harm your chances over not including it because you're not using it in a way the reviewer likes? Ultimately you'd think it wouldn't matter and that just including it was good enough (and I think it was for this specific reviewer), but it's a tricky game of hoping your choices line up with the unknown opinions and biases of the person reviewing in order for it to work out.