Hacker News Reader

Comment by opportune | Hacker News Reader

I guess if you don't like the company's interviewing process you don't have to work there. Unemployment rate for software engineers is pretty low these days so just go with somewhere else. I'll keep working at places that ask programming questions because basically all the highest-paying places do that these days. And as snobby as it sounds, I want to keep working with other people who can pass algorithms teasers

Also, yeah probably no dev-ops position really requires knowledge of DP. But they generally do require programming knowledge and probably an algorithm here and there so it's not entirely inappropriate

View on HN

> they generally do require programming knowledge

Yes

> probably an algorithm here and there

Even Amazon doesn't ask about algorithms for DevOps. When I interviewed with them for a DevOps position, they asked me to write a Python script to parse logs files. They also asked about various linux commands that you would use to work with those same logs. Pretty relevant. But the interviewer never once asked about algorithms or anything like that.

My current company gave me a take-home test to build out a solution that deploys a code package. Best interview question/task I've ever had. It was hard, but I got to show off my real skills.

Companies that ask leet coding questions for DevOps probably have no idea what they're looking for and probably don't know what they're doing.

Hm. I spoke with Amazon (AWS) recently (haven't interviewed yet), and they made the express point that if I were to accept an interview that I should brush up on my algos and HackerRank questions because they loved HackerRank and would surely use a series of those-style problems throughout the interview process.

My last in-depth interview was a take-home/collaborative project (paid) for a smaller company here in Canada. It was a great experience. So good on you.

I think you are talking about something different. The parent poster was referring to a Devops position. Were you looking at a software engineer position?

I wasn't really actively looking for anything—they contacted me about a range of positions that centred around special projects that ranged in subject matter/disciplines.

It's probably per-team, someone on here mentioned that's how Google works at least.

Someone I know did an AWS interview round during business school, and they do this thing called "bar raising" (IIRC) that involves one of the interviewers literally doing something unpleasant to see how you react (e.g. picking their teeth in the camera, cutting you off when you speak). Very odd.

That is not what bar raising is intended to be. There's always a bar raiser in an Amazon interview loop who is not affiliated with the hiring team. They ask the same kinds of questions as the rest of the interviewers in the same way, but they're not influenced by how much the team needs to make the hire, which in theory prevents the team from lowering the bar just to get a warm body in.

I'm not saying your friend didn't get a bad interviewer. It's just an interesting demonstration of how risky it is to generalize from anecdotes.

It was a generally accepted practice based on talking to the folks who interviewed with Amazon during my wife's time at Kellogg that one interview would be conducted by someone (an interviewer who had done 100+ interviews) who would be unpleasant in some way.

I'm guessing the way Amazon interview for business roles is somehow different than how they interview for specific team positions. As I understand it, MBA hires aren't filling specific gaps on teams, since the hiring process is so long and involves an internship. There wouldn't be a "team" to lower the bar for, in other words.

I have worked at Amazon, and can categorically say that this description of their interview process is false.

Like false as in I made it up or false as in it's not your experience?

False as in not true. Amazon does not have a policy of interviewers intentionally making candidates uncomfortable.

Ah, well then what was I being told? I got these independent reports form literally every single person I spoke to who interviewed with Amazon.

I also just spoke with my wife and she re-confirmed it. So I guess I'm wondering what these people who I respect are experiencing...

That is not what "bar-raising" round is. It's a difficult question (often algorithmic) that 50% of the employees wouldn't be able to solve. Its designed to raise the bar of employees.

Why would Amazon ask an algorithmic question for a non-engineering role?

>Companies that ask leet coding questions for DevOps probably have no idea what they're looking for and probably don't know what they're doing.

I think it's a more a case of cargo culting rather than not necessarily knowing what they are doing, although that might also be the case in some instances.

If you’re cargo culting do you really know what you’re doing though? I’d think the two situations are mutually exclusive. Or were cargo cults actually effective at getting supplies dropped from the sky?

Cargo-culting is literally not knowing what you're doing.

What i meant is that they are cargo culting in their interviewing method but this does not necessarily mean that they don't know what they are doing day to day.

Cargo culting is knowing exactly what you are doing, but having a completely incorrect understanding of the potential result.

I'd be frustrated for wasting my time. The recruiter should have better explained the review process.

Palantir is pretty well known for giving algorithms problems so it would have likely been solved by a cursory google "palantir software engineering interview"

Why would I search for software engineering interviews if I'm applying to be an IT systems engineer?

I guess there is a disconnect where some people don't think dev-ops people are software engineers and others do. I fall in the latter camp and have never worked with devops people who weren't also software engineers

Fair enough. I think it is the responsibility of the recruiter or the company to clarify which they expect for a particular position, though.

Because these days "IT Systems Manager" are expected to know basics of coding.

To me, there is a pretty large gap between "interview questions to test the basics of coding" and "software engineer interview questions". Searching for the latter to find the former is like search for copywriter interviews to study for questions on basic English proficiency.

Wouldn't "the basics of coding" be something like knowing how to read/write a short python/bash script to automate a task? Algorithms questions ala leetcode are far higher level than the basics.

> Because these days "IT Systems Manager" are expected to know basics of coding.

LeetCode questions test for other things than "basics of coding".

Check glassdoor for this company/position, looks like most people think it is a difficult interview process:

https://www.glassdoor.com/Interview/Palantir-Technologies-De...

Can you or anyone cite where you have read that the unemployment rate for software engineers is low? I'd love to see it but I'm not able to find much trying to search for a citation on this point. I'm not sure that it is actually low, but this seems to be a common parlance amongst recruiters.

Reply on news.ycombinator.com