Hacker News new | ask | show | jobs
by supriyo-biswas 222 days ago
A few paragraphs below, the article answers that the company can't afford to pay as much as some others; I assume if you are being already being paid way over the market rate you should keep working at the place you're at.

As for the take home, I'd take it or any other kind of non-conventional question that allows me to show me my skills, rather than the usual interview where your interviewer gives you an algorithm or system design question they couldn't solve themselves, with the occasional smirk as they watch you fumble through that question.

3 comments

I might be a masochist, but I actually enjoy system design interviews and they're quite formulaic. Resources like "System design in a hurry" are great for narrowing down the formula.

Where I live (BC, Canada) actually has a law requiring all employers to list the position's salary range, which is great for cutting down on the "expected salary expectations" dance.

I don't like take homes as it's (highly likely) a one way time commitment and if you're truly looking to show off your skills it would take you hours.

If the system design interview is designed in a sane manner, which most of them are, thankfully for now.

Unfortunately, some interviewers ask questions that they themselves have not thought through properly, which leads to "interesting" discussions followed by a disqualification. While I've not had to face that issue first-hand as an interviewee, I've seen interviewers who wouldn't have been able to pass their own interview, for example.

Washington State (where this company is based) has the same law about including salary ranges in job postings
I wouldn't do a take-home unless they do an interview first, to signal they value my time and are acting in good faith. (HR people don't count).

Then, when they give me the take-home, I would ask how many other people are in the stage with me. If it's 20, with only one candidate getting hired, forget it. My expectation in such situations would be that they won't be able to trim the pipeline as much as they will need/want to by applying purely objective/rational criteria, and I'd end up getting rejected on grounds of "inability to mind-read subjective preferences".

I wonder if the people replying bothered to look at the take home question. I wish I had an interview like that, it would be the second easiest interview I’ve ever done in my life, and then task is interesting and easy to me, as someone who just started learning unity a week ago