Live data from Hacker News

The Machine Learning Software Engineering Interview

eng.lyft.com

41–50 of 81 posts

Re: The Machine Learning Software Engineering Interview

#41
post #8

This blog post was so painful for me to read. This is a symptom of "bullshit" going on around in big tech companies. "bullshit" here is an economic term defined in the book "bullshit jobs". https://www.amazon.com/Bullshit-Jobs-Theory-David-Graeber/dp... Reading through the post, I was noticing So much corporate Jargon which really does not mean anything important. Dehumanizing language when describing people intervie…

[deleted]

Re: The Machine Learning Software Engineering Interview

#42
post #2

It would be great if companies would allow you to bypass the code challenge if you grant them read git access to a relevant project that you have ownership of.

On a whim I responded to a recruiter last week about a job. The first step was an online coding challenge. The company wanted a "Java developer", and I told the recruiter I have never used Java regularly, but given my experience she said it wasn't a problem. I figured the code test would be some simple filter stuff.

Instead, it was five algorithm quizzes... all in Java. I had an hour to finish it and, after spending the first fifteen minutes searching for Java standard library stuff just so I could write the code I wanted, I decided this was a waste of my time and closed the tab. This was all before I could even speak with someone who works at the company to find out if I cared to move forward.

I worked as a hiring manager for a couple of years and have had input into the hiring process for more than a decade. I've never found it difficult to screen someone out who had no place applying to begin with by taking a fifteen minute call. This at least gives them a chance to ask some questions and they don't feel like you're yanking them around.

Re: The Machine Learning Software Engineering Interview

#44

Good source of data for training a de-bullshitter. Input: A year and a half ago when we began scouting for this type of machine learning-savvy engineer —something we now call the machine learning Software Engineer (ML SWE) — it wasn’t something we knew much about. We looked at other companies’ equivalent roles but they weren’t exactly contextualized to Lyft’s business setting. This need motivated an entirely new role…

Yeah actually it would not surprise me if their article was generated by GPT2 using your "targets" as input.

Re: The Machine Learning Software Engineering Interview

#45

Good source of data for training a de-bullshitter. Input: A year and a half ago when we began scouting for this type of machine learning-savvy engineer —something we now call the machine learning Software Engineer (ML SWE) — it wasn’t something we knew much about. We looked at other companies’ equivalent roles but they weren’t exactly contextualized to Lyft’s business setting. This need motivated an entirely new role…

I have another target for your second one: We share a Google Drive full of resumes and people put their names on a spreadsheet when they like the candidate. Then we interview them!

It’s super innovative and fit to our business context!

Re: The Machine Learning Software Engineering Interview

#46
post #8

This blog post was so painful for me to read. This is a symptom of "bullshit" going on around in big tech companies. "bullshit" here is an economic term defined in the book "bullshit jobs". https://www.amazon.com/Bullshit-Jobs-Theory-David-Graeber/dp... Reading through the post, I was noticing So much corporate Jargon which really does not mean anything important. Dehumanizing language when describing people intervie…

Sometimes, lessons from the past can help to remove some of the rose-tinted glasses that people seem to associate these newer companies with. For example, it's worth reading Enron's Vision and Values statement (http://www.agsm.edu.au/bobm/teaching/BE/Cases_pdf/enron-code...) from 2000.

I don't think there have been any fundamental changes since 2000 that would incentivize make communication from large public corporate entities to be more honest or logically rigorous.

Re: The Machine Learning Software Engineering Interview

#48

Good source of data for training a de-bullshitter. Input: A year and a half ago when we began scouting for this type of machine learning-savvy engineer —something we now call the machine learning Software Engineer (ML SWE) — it wasn’t something we knew much about. We looked at other companies’ equivalent roles but they weren’t exactly contextualized to Lyft’s business setting. This need motivated an entirely new role…

See https://mourner.github.io/bullshit.js/

Re: The Machine Learning Software Engineering Interview

#49
post #8

This blog post was so painful for me to read. This is a symptom of "bullshit" going on around in big tech companies. "bullshit" here is an economic term defined in the book "bullshit jobs". https://www.amazon.com/Bullshit-Jobs-Theory-David-Graeber/dp... Reading through the post, I was noticing So much corporate Jargon which really does not mean anything important. Dehumanizing language when describing people intervie…

Yep. Taxi routing service, and not even the best one, you'd think they're launching those taxis to Mars.

That said, SpaceX interview process is even more ridiculous. The first step is to talk on the phone with a non-engineer recruiter who has to ask you highly technical questions, but doesn't understand a word of your response, and you know it. They then sort of have to correlate what you're saying with the answers they have and decide whether you know anything or not. The most uncomfortable interview situation I've ever been in. Or at least that's how it was a few years ago, maybe they've changed it. I was so thrown off by this, I totally fucked it up and never got to the second step, in spite of nominally having all the right experience. To relate, imagine trying to explain low level assembly to a five year old, over the phone.

Post reply on HN