Earlier quoted context omitted.
What, you couldn't derive a solution in a vacuum from first principles? I bet you think referring to API documentation isn't cheating, too!
Hmmm hard decipher your comment. But, that interviewer is the type of developer I don't want to work with. A know it all who only acts like he knows it all and uses Google secretly. Who puts others down to make themselves look good. AKA an insecure P word I want nothing to do with.
Harder programming questions do a worse job of predicting outcomes
321–330 of 540 posts
Re: Harder programming questions do a worse job of predicting outcomes
#322Earlier quoted context omitted.
They have kids. Developing a sentient being is a higher priority and more difficult than developing React Redux.
> They have kids. Developing a sentient being is a higher priority and more difficult than developing React Redux. This is like saying: "I have a time-intense hobby that I prefer over working too much for you.".
Re: Harder programming questions do a worse job of predicting outcomes
#323Earlier quoted context omitted.
I suggest you read up on the effects of market friction. 300k/year could very well be a bargain for these people even if it sounds like a lot to you.
You might want to re-read your own post because whether 300k/year is a lot of money or not is a non sequitor. You claimed that companies ask hard interview questions to depress salaries, which is a trivially falsifiable claim when you note that companies that don't ask hard interview questions can get away with paying less money than companies that do because they are less picky about who they hire.
Your assertion that low paying positions don't also cargo cult these test-as-interview processes is pure speculation.
Re: Harder programming questions do a worse job of predicting outcomes
#324Earlier quoted context omitted.
> They have kids. Developing a sentient being is a higher priority and more difficult than developing React Redux. This is like saying: "I have a time-intense hobby that I prefer over working too much for you.".
No, it's called having a life and a sense of proportion. The sooner tech companies learn to embrace and work with this very basic fact, the better.
Re: Harder programming questions do a worse job of predicting outcomes
#325Earlier quoted context omitted.
> They have kids. Developing a sentient being is a higher priority and more difficult than developing React Redux. This is like saying: "I have a time-intense hobby that I prefer over working too much for you.".
A person can choose to spend less time on a hobby at any point, but once a child is born their parents have an ethical obligation to their children.
Indeed - and that is why you should be very cautious to give birth to children; in particular if you have career plans.
Re: Harder programming questions do a worse job of predicting outcomes
#326Earlier quoted context omitted.
>This is kind off strange for a non US resident to grasp. I've worked for two non-technical companies as a software developer and one highly technical company, and interviewed at a few Silicon Valley companies. The difference between the interview processes is staggering; my current job's interview was two hours of conversation, no code tests, just a general assessment of "do you know what you're doing" by the hiring…
It's quite frustrating, I've submitted my portfolio of open source projects on GitHub for interviews. I specifically told the recruiters, HR personnel, hiring managers and some of the developers that the projects contain a large enough body of work to see examples of my code. These projects are quite comprehensive and not one person looked at them or mentioned them during the interviews. Unfortunately, people in gene…
Re: Harder programming questions do a worse job of predicting outcomes
#327Earlier quoted context omitted.
I dunno.. flip side to this is that you could name your own price basically.
Not really though. If your price is working in a quiet, private office with a door that shuts, or having humane treatment when you’re being interviewed, then it seems nobody would pay it. Let’s take their word for it that they are desperate for a machine learning engineer. Then it suggests they care more about mandating workspace conditions (since financial cost even to provide thousands of workers with private offic…
Re: Harder programming questions do a worse job of predicting outcomes
#328Re: Harder programming questions do a worse job of predicting outcomes
#329Google recruiters call me a lot. I think I'd do a good if not stellar job working there. I've passed multiple FAANG interviews and been very successful as a senior developer. In my email I have an "interview prep packet" from them that essentially tells me to brush up on algorithms and read Cracking the Coding Interview to prepare for their interview process. I'm fairly happy in my job. If they offered more money or…
I'm a big fan of not wasting time, which I why I get stuff done at work and have been promoted twice at my current company in the past 3 years. As a sibling commenter suggests, if Google wants employees who blindly do what they're told, then I wouldn't be a good culture fit. I was taught critical thinking skills in school. Respectfully questioning my superiors' plans from time to time has been a valuable skill.
Re: Harder programming questions do a worse job of predicting outcomes
#330Earlier quoted context omitted.
So much this. I've been programming for 30+ years. My brain only has so much cache space and it dumps frequently. Asking me questions that clearly are testing my ability to hold large amounts of data in my meat computer isn't testing my ability to design and write computer programs. Sure, I'd love to have a "mind palace" like Sherlock. Alas, I do not. I often admit this as early in the interview process as possible t…
If anything, it's testing your ability to mis design computer programs. I hate working on software that was written to be read by an audience with perfect recall, because, as a human, I just don't have that. Give me code that assumes I have the memory of a goldfish, and can't keep track of anything that isn't right in front of my face. I'm pretty sure that's what half of Dijkstra's papers were trying to say, weren't…