Readit News logoReadit News
Posted by u/daenney 4 years ago
Ask HN: A job interview you enjoyed?
There's a lot of material out there about terrible job interviews and interview processes. So let us flip the script: is there a job interview you enjoyed or fondly think back on?

Everything is fair game here, whether it was the process, the setting, the people, the format, a particular question that was asked or anything else that made this interview stand out to you in a positive manner. It doesn't have to be limited to getting a job in tech either.

umbs · 4 years ago
Arista Networks, in Santa Clara.

First round, I had to do 2 coding questions in an hour, 30 mins for each question. I had to go to their campus. They would give me a laptop/environment of my choice and then time starts. Questions were very easy, so the expectation was reasonable.

Second round on On-site was two interviews: Director of engineering asked me why certain piece of C code was behaving in a certain way. I could not answer, but we compiled the code into Assembly and tried to understand the behavior. An hour later, the CTO of the company, Ken Duda, walked in and he asked me an Object Oriented question and some of my past projects. Really drilled me. He gave very simple design of same projects. Very educative and amazed to see a brilliant mind at work. The interview was in no way condescending.

They took a decision right there and it was a no hire. But I loved the experience. It was no BS interview.

unmole · 4 years ago
I had a similar experience with Arista Networks in Bangalore. Only I managed to get an offer and I've been with the company for a little over 2.5 years. And it's not just the interviews, we're a no-BS company in general.

P.S. We are hiring.

0xedd · 4 years ago
Debug code behavior using assembly? And deep OOP knowledge? And architecture? They better pay in gold bricks.
duiker101 · 4 years ago
Years ago, I interviewed at redgate (an interview I actually got via HN!). I will never forget it, I was very junior, but I never felt looked down upon, I had nice conversation with the interviewers, and it always felt natural. The technical part was looking at a small game code and just walking through it what it does, how it could be tested, improved or fixed.

It all felt comfortable and not "quizzy". I didn't get the job, but I got back a lot of very specific and encouraging feedback that really inspired me in my career, and I will be forever grateful.

My takeaway was, treat candidates as people that deserve respect and time, rather than churning through them.

cjdoc29 · 4 years ago
GitLab. I didn't get the job. But the experience was great. The take home was reasonable (~1hr). The technical screening was based on talking about the take home and creating unit tests. And we had a Zoom meeting to talk about feedback on what they thought I could work on to improve.
sph · 4 years ago
My first interview, as a self taught 19 year old high school dropout. I got asked what "ifconfig" did, how Ethernet works at a very high level, which languages I knew, and got hired.

Then I got put on a crash course of Solaris and vim (with the mentorship of a literal UNIX greybeard) and sent fixing bugs at customers' sites. One month later another young colleague and I were sent to teach the basics of Linux networking to a class of enlisted recruits in the Italian Army. Quite the experience, and highly reckless strategy for a consulting company, but you tend to learn pretty quickly if you're eager to.

The hoops I gotta go through 16 years later to get a consulting gig are just ridiculous.

natpalmer1776 · 4 years ago
Honesty if they vetted the candidates correctly and that greybeard was available for "trial period" damage control of new employee fuckups, I think it's a great method of running a consulting firm.

Trial by fire with the appropriate subject matter experts standing by is a great way to quickly broaden the broader talent pool in a sustainable way, while turning a profit on the free hands-on training being afforded to the new blood.

In a traditional organization you aren't afforded the sheer variability in deployments or pace of work afforded by consulting, so hiring someone completely green usually isn't the best exchange, even if the in-house expertise is available to provide the proper mentorship.

Maybe this is just me wishing I had a similar opportunity (or even just mentorship) but I would love to see this as more commonplace.

playing_colours · 4 years ago
A few months ago I had a pleasant technical interview with Snowflake.

First, the interviewer was very supportive and cooperative, it felt almost like a friendly talk between two colleagues. He did not try to outsmart me or catch on some tricky detail.

Also, the questions were very good - we discussed how to build a distributed data processing system, a very relevant and on the right level for the position I applied (Engineering Manager).

sandymcmurray · 4 years ago
When I interviewed for my current job, I asked the HR rep and the hiring manager if they were happy working at the company. The question seemed to surprise them. Both smiled, thought for a moment, then responded positively, with some details about why they enjoyed their jobs and this company. That was 11 years ago and we're all still here.
trevorde · 4 years ago
In a previous life, I was a mechanical engineer and interviewed at an engine research company. I know a lot about engines but the three engineers interviewing me were world experts. Format was me standing in front of a whiteboard and the panel firing questions at me, picking apart my answers and bottoming out my knowledge.

It was all very high stress with questions and answers going back and forth. There was a long pause which was broken by one of the engineers asking: "Do you drink beer?"

I didn't get the job.

eindiran · 4 years ago
The interviews I've enjoyed most were the ones where the interviewer and I got to chat about some technical project in depth. For my last job switch, one of the interview rounds was specifically about a project I had worked on and the interviewer that round just asked me to go into how things worked, why design decisions were made the way they were, what the constraints were, etc. Implicit in the whole whiteboarding thing is a subtle accusation that you can't actually do what you claim you can do; this interview instead hinged on the idea that I had done this and that there would be better insight into my work if it was specific and historical, rather than palely rehashing an algorithms class. It also helped a ton that the interviewer seemed genuinely interested in talking about the project, so the whole thing felt much closer to a conversation than a performance.