Live data from Hacker News

What I've learned from 100s of interviews with candidates at top tech companies

observer.com

171–180 of 225 posts

Re: What I've learned from 100s of interviews with candidates at top tech companies

#172

Earlier quoted context omitted.

> On a higher level - how much of an "already seen the algorithm" crapshot are tech interviews? I'd say it is mostly that. Just do thirty to fifty leetcode medium problems (some of them on pen and paper), and you're good to go.

I really hope its not. I don't expect any of the people I interview to have ever seen my question or even the particular algorithmic solution before. Good candidates should be able to come up with efficient algorithms to transform and manipulate common data structures on the spot.

Do you believe that the solutions to "solve a sudoku" and "solve n queens" are significantly different?

Re: What I've learned from 100s of interviews with candidates at top tech companies

#174

Earlier quoted context omitted.

How on earth can you think that 300k is a basic living wage in the bay. Even with insane housing prices, this is like 10x the national median wage. Knock out 1/3 for taxes and you are left with 200k per year. How are you spending the 190k per year on rent and transportation that would be needed to knock you down to typical post-expenses income levels?

Assume a family and a couple of kids, health care, child care, and transportation and according to this: http://www.businessinsider.com/how-expensive-is-san-francisc... You're already at 91,000 for basic expenses. That puts 200k right around the mark for a livable wage and 300k pretty comfortable (and also at the high end of a senior dev wage by a fair margin).

> That puts 200k right around the mark for a livable wage

To begin with, when discussing wages most people are assuming for a single person taking care of his or herself. The wage needed to support a fully family including enough for a stay-at-home parent would be significantly higher.

Even with all of that a family of 4 with only a single adult working is estimated a living wage in SF area is deemed to be 70k.[1] Not 200k. I'm assuming you're meaning "livable wage" to be different than "living wage".

Even if we were to going with the businessinsider data, which says 90k for expenses for a family, you're claiming that a family would need to spend almost 10k in discretionary spending every month for a "livable wage"? Remember all required expenses have been paid for, this would just be for discretionary. If you've already paid for "housing, food, childcare, transportation, healthcare, taxes and other necessities, and taxes" and are still going through an additional 10k/month, you're beyond a "livable wage".

[1]. http://livingwage.mit.edu/metros/41860

Re: What I've learned from 100s of interviews with candidates at top tech companies

#175

The advice about not giving up on the question is a key point here. In a previous startup I would ask a single question that would take 30+ minutes to work through with no expectations that the candidate would ever get the answer. All I cared about was if you could break down the issues and move from one set to the next in trying to narrow down the issue. I cared deeply about how you thought, not what you knew. As pe…

[deleted]

Re: What I've learned from 100s of interviews with candidates at top tech companies

#176
post #5

Earlier quoted context omitted.

The biggest problem I have with these companies is that they feel like a cult. And the people working there are doing a lot to keep that cult spirit alive. All of these companies want you too feel and act like they are the single best entity in the entire universe and you should be honored that they even acknowledged you. This works great for young graduates that are full of dreams and hopes but it discourages experi…

> I would rather make more money in a stupid corporate job than working on more aggressive ways of making people to click on ads. Could you name a few "stupid corporate jobs" that pay better than Google or Facebook (200k - 300k for a senior engineer) ?

All you're doing is repeating the cult's mantra there. They'd better pay that much if they're going to depend so heavily on dehumanizing you.

It does take a lot of preparation for big-company clueless interviewing processes though. Next we'll see guides for how to ace your kid's application to the top-tier coding preschool.

All this sucking up to big companies with questionable morals and procedures, for the money, is so... 80s. So yuppie, so Reagan-era. Reachin' for the top! Go for it! Eye of the tiger! Pressure, pushing down on you, pushing down on me, no man ask for.

Re: What I've learned from 100s of interviews with candidates at top tech companies

#177
post #162

Earlier quoted context omitted.

I think it's well intentioned but highly flawed. 1. The time commitment issue. 2. It allows a company to give a bunch of "interviews" (assignments) even for candidates they aren't serious about. It can waste a lot of candidate time. 3. There is so much cheating on these that you really can't use it for evaluation. It can really only be a screening tool (which makes 4+ hour assignments really unfair). 4. It primarily…

#2 and #5 are issues with the company/hiring manager. #1, #4 and #7 are issues with traditional interview as well. #4 It's incredibly difficult to accurately assess potential during an interview. #1 and #7: This holds true for white-board interviewing. Most successful candidates (including myself) invested time to practice coding interview questions. I did over 150 questions on LeetCode and it dramatically increased…

#2 is not a trend we want to start in industry. With phone screens, both sides make an investment. With a pre-screened assignment, there is very little cost to the company. This gives them a much stronger incentive to throw everything on the wall and see what sticks. Or even feel that they're doing candidates a favor by 'letting' them take the 4hr assignment. Doing a phone screen aligns incentives.

You think you hate whiteboard interviews? Imagine having to to 15+ different take home assignments for different companies before you even get a chance to talk to a person.

Re: What I've learned from 100s of interviews with candidates at top tech companies

#178

I think the tide is turning against this type of interview. The industry is starting to notice how ineffective and stupid it is. The big tech companies don't care and will continue doing it because success hides all failures. When there's an endless flood of new college graduate applicants and near-monopoly positions bringing in billions of revenue, nobody cares if the hiring process is bad. They will care someday if…

So if whiteboard interviews are stupid and ineffective, what process do you think is better? I assure that the big tech companies absolutely do care, but they struggle to find something better.

For the most successful jobs I've had, they just looked at my resume and asked some general questions about prior work.

I've also had several positions where I passed whiteboard hazings. Those didn't go as well. My theory is that selecting strongly for code jam types may correlate with not selecting carefully for people who work well together.

Re: What I've learned from 100s of interviews with candidates at top tech companies

#179

Earlier quoted context omitted.

I think Hanlon's Razor applies. They have no impetus to change and think they have found an approach that works reasonable well when given absurd amounts of candidates. The problem is the ridiculous false negative rate. I struggle to think of a better system. Using experience is unfair and misleading (I worked on awesome stuff... that I can tell you nothing about, I was totally the lead on this software, etc...). Tak…

They have lots of impetus to change. It's just that they struggle to find a better system. Talking about prior experience? Flawed for the reasons you mentioned. Take home stuff? Flawed -- cheating and other issues (I discuss this in another comment). Work with us for a week? Doesn't scale. Unfair to candidates. Lots of issues here. Sit down and help me fix this bug? Flawed: 1. Huge bias based on whether they know thi…

I'd say homeworks are good. In a mix. In fact the process should be a mix. It's hard to get it right.

You can find out if they copied the homework. There should always be a follow up talk about it. They should be able to explain the details.

Ask them to add some functionality on spot. They have working code they should be familiar with and you can work with that. You want to test their approach more than anything.

Bug fixing is hard to prepare right. If you have a clear cut position, that would eliminate part of bullet one.

I'd argue that they should not be asked to find the bug. Only to fix it.

It does not have to be the same bug. I'd argue for a pool they can pick from.

You should be testing how they approach the problem and how they go about solving it. Heck you can debug and outline a fix for something you can't really code yourself, I know I did.

Pairing with someone from the team they'd work in could also provide some insight into the dynamic.

I agree there is no cookie cutter way for homework and bugs. That's why they need to be in a mix, well prepared and supervised.

Re: What I've learned from 100s of interviews with candidates at top tech companies

#180

Earlier quoted context omitted.

Assume a family and a couple of kids, health care, child care, and transportation and according to this: http://www.businessinsider.com/how-expensive-is-san-francisc... You're already at 91,000 for basic expenses. That puts 200k right around the mark for a livable wage and 300k pretty comfortable (and also at the high end of a senior dev wage by a fair margin).

> That puts 200k right around the mark for a livable wage To begin with, when discussing wages most people are assuming for a single person taking care of his or herself. The wage needed to support a fully family including enough for a stay-at-home parent would be significantly higher. Even with all of that a family of 4 with only a single adult working is estimated a living wage in SF area is deemed to be 70k.[1] No…

First of all, these are all gross income numbers and include no savings at all. If your estimated gross living wage is 70k, but you're making 200k, that means an extra 130k. About 55k of that goes towards taxes (see tax rates below), leaving 75k. That needs to cover all your savings (if you make 200k, you better be saving about 20-30k/year for retirement, plus you might want to have college savings and such if you have kids) plus discretionary spending. If you figure $10k/year for college savings for 2 kids (probably low!), that leaves 35-45k, or 3-4k/month in discretionary spending, which is still quite a bit, though nowhere close to the naive 10k/month you mention.

Looking at the sources of these various numbers, the $91k number in the busnessinsider article comes from http://www.epi.org/resources/budget/ which breaks down the annual costs as follows, annually, for the SF metro area:

* Housing: $23k (seems fairly low for a family of 4 in the Bay Area, but I guess it depends on how far out you live)

* Food: $9384 (quite reasonable)

* Child Care: $10815 (seems unrealistically low for 2 kids if both parents work; hard to tell if only one works, since I would expect that to be near-0 for a bare minimum).

* Transportation: $7300

* Health care: $12,453 (might be high depending on your employer)

* Other necessities: $15689

* Taxes: $12490

I assume that tax number is based in the actually cited $91k income, so to figure out how much more income we need for discretionary spending and savings we need to look at marginal tax rates. Looks like CA state income tax is 8 or 9.3% in the relevant income range (60k-500k for couples). Federal rates are 25-28% (75k-233k taxable income). Medicare is 1.45% until we get to 250k. Social Security is 6.2% until we hit the cap. So a marginal rate of 35% to 39% not counting Social Security.

Retirement savings should be ~15k here (15% of income is the common recommendation), and can often be done "pre-tax" (so only taxed by Social Security and Medicare); let's call this 16k gross income.

Are you saving for college for those two kids? Any other savings (e.g. for a house)? Any discretionary income at all? Multiply all those numbers by 1.6 or so to account for the taxes involved. Realistically I would expect this to come to another 20-30k easily for anything resembling a "middle class" lifestyle.

Looking at the numbers from your link, they have a much lower healthcare estimate (~6k/year), a somewhat higher housing estimate, correctly estimate childcare costs if only one parent works, but still have what look like ludicrously low numbers if both parents work. The "2 adults, both working, 2 children" number from your link is $83k and the difference between that and the $91k from the businessinsider article is all down to the health care number.

Anyway, the correct conclusion here is that in the Bay Area for a family of 4 you need an income in the 70-90k range (mostly depending on how much you pay for health insurance and whether you both work) just to barely scrape by, with no savings and no discretionary spending of any sort. At 150k you can probably do ok in terms of being able to save for retirement, college, maybe take some vacations every so often, etc. 200k should be reasonably comfortable if you have no pretensions to more than 2 bedrooms (notice that housing for 2 kids is claimed to cost the same as for one kid) and aren't trying to get into good school districts.

If you want good schools or more living space than a small 2-bedroom place way far from anywhere, the housing numbers cited above are almost certainly way too low...

Post reply on HN