Live data from Hacker News

Becoming a dungeon master for an interview

propelauth.com

171–180 of 181 posts

Re: Becoming a dungeon master for an interview

#171

Earlier quoted context omitted.

You really need two in physically different locations (ideally ASes) with some form of failover, assuming you want a reasonable guaranteed uptime

We've run 375,000 self-service employees ERP system (so much heavier single transaction than HN) on a single (large:) db2/aix box with no downtime over last 8 years. That's well within published specs for that hardware / software combo. Yes we do have a DR box in another data centre now, in case of meteorite or fire. This used to be the norm . A single hardware / software box CAN be engineered for high uptime. It's p…

I’m paranoid about environmental situations so always have a failover, but then my DR plans include events such as “Thames barrier fails”.

Re: Becoming a dungeon master for an interview

#172
post #167
post #139

Earlier quoted context omitted.

> Does 99.995% [1] of hackernews sound reasonable enough to you? How did you come up with that number? I looked at the link and just one of the outages listed on January 10 was 59 minutes. That alone makes the uptime worse than 99.99% for the entire year before it was halfway through January. (99.995% means at most 26.3 minutes of downtime per year. See https://en.wikipedia.org/wiki/High_availability#Percentage_c...…

it's the 30 day uptime statistic displayed on the website I linked. if you click the history it says 98.452% over 365 days.

That’s a pretty low level. That’s lower than my pi hole. But I wouldn’t consider my pihole to be anything other than best endeavours (99.1%). Two would be fine, but there are common points of failure which would limit the solution

Re: Becoming a dungeon master for an interview

#173
post #37

Earlier quoted context omitted.

> I'm curious what changed around 2015-2016 that led to the current interview process. In the before times the interview was more of a technical conversation, sure they had some gotcha questions, but nothing too brutal. If you had real experience that you co... Places just copied big tech companies that were already doing that for many years prior to 2015. I had leetcode style interviews well before 2010 even.

Part of the problem is people just memorize things for interviews. We interviewed three candidates that were almost exact copies of each other in their responses. Maybe they all read the same interview book? I also witnessed someone give a completely wrong (algorithm) whiteboard answer to a problem. Obviously they weren't thinking about the problem as they did it.

Algorithm that were solved over decades and centuries are asked during the 15-20 minute demonstration asks it to be memorized

The problem is the sheer dumbness of those who believe it is important in the interview process

Re: Becoming a dungeon master for an interview

#174
post #37

Earlier quoted context omitted.

> I'm curious what changed around 2015-2016 that led to the current interview process. In the before times the interview was more of a technical conversation, sure they had some gotcha questions, but nothing too brutal. If you had real experience that you co... Places just copied big tech companies that were already doing that for many years prior to 2015. I had leetcode style interviews well before 2010 even.

Pretty much this. Companies needed software engineers, looked at what Google was doing, and copied. And they call themselves innovative for doing it.

A company whose smart engineers threw their hands up claiming no moat while they were the pioneer of AI

Re: Becoming a dungeon master for an interview

#175
post #97

Earlier quoted context omitted.

You really need two in physically different locations (ideally ASes) with some form of failover, assuming you want a reasonable guaranteed uptime

Does 99.995% [1] of hackernews sound reasonable enough to you? The reality is a lot of systems (especially simple ones) run perfectly fine on a single server with next to no downtime and all the additional redundancies we introduce also add additional points of failures and without the scale that makes these necessary you might actually end up reducing your availability. [1] https://hn.hund.io/

This so much this! Experience is such a wonderful thing.

Re: Becoming a dungeon master for an interview

#176

Earlier quoted context omitted.

One of their hiring criteria is cognitive ability. If it correlates with strong proficiency in CS algorithms, then this might have been why they focus on it when hiring engineers. (I am not saying that this strong correlation exists.)

The correlation doesn't exist. A large segment of the Leetcode-uber-alles practitioners are also the ones that are obsessed with total compensation as the ultimate measure. It was a mistake by google and others to focus purely on this , but we are where we are. Many of the leetcode fanatics can't deal with real world issues in software or operations.

[deleted]

Re: Becoming a dungeon master for an interview

#177

Earlier quoted context omitted.

One of their hiring criteria is cognitive ability. If it correlates with strong proficiency in CS algorithms, then this might have been why they focus on it when hiring engineers. (I am not saying that this strong correlation exists.)

The correlation doesn't exist. A large segment of the Leetcode-uber-alles practitioners are also the ones that are obsessed with total compensation as the ultimate measure. It was a mistake by google and others to focus purely on this , but we are where we are. Many of the leetcode fanatics can't deal with real world issues in software or operations.

These companies look for people who write software to handle real-world issues on software and operations.

The mistake is in refusing to have a separate job and hiring rubric for sysadmins

Re: Becoming a dungeon master for an interview

#178
post #25

Earlier quoted context omitted.

I doubt it? My willingness to practice leetcode isn't correlated with my interest in new work or the work any given job post describes. It's also not correlated with my willingness to invest time in exploring the position. 6 hours of leetcode practice teach me nothing about a position, the work it entails, the problems the company is grappling with, and the people I'd be in the trenches with. 6 hours in conversation…

Same, I'd rather spend 3 hours working with the potential team than spend 12 hours practicing leetcode. If you want to see my code, I have plenty of public domain projects freely available.

I also have plenty of your public domain projects freely available!

Re: Becoming a dungeon master for an interview

#179

Earlier quoted context omitted.

Don't forget about the people who don't have to spend weeks or months focused just on interview prep to do well on the average leetcode question... That's who interviewers are looking for. Now, a case can be made that there aren't that many of those people and you might not need them anyway, but... if you can spend a few weeks to catch up that's not all bad compared to what high-end job offers in other professions de…

If you want to receive top compensation, and work at the Meta/Roblox/AirBnBs etc, you will need to be able to solve 2 Leetcode medium questions in 45 minutes, correctly and optimally. I work for a big tech company where people smell their own farts and think they are geniuses even though they work on CRUD interfaces for admin portals for Cloud. The interview process is well known. I have seen wrong solutions made by…

I'm sure they exist, which is great, but I have never had a non-STEM shot on my dev team at any job.

I'm sure you met a few flawed people like you describe. But they are not a large fraction.

Re: Becoming a dungeon master for an interview

#180

Earlier quoted context omitted.

That seems like an interview that you passed (the company learned that you know a lot more than them about the resources available for debugging).

More likely the interviewer was some internal recruiter type who had been given some example questions to ask but didn't know about development themselves.

They were an engineer on the team I would have led, not a recruiter.
Post reply on HN