Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "wk197"
-
For myself, I choked on the following:
- "Why do you want to work for us?"
- "Why us, specifically?"
- That stupid logic test with the guys wearing the red and white caps
- "Convince us how you're not overqualified. We're simple people."
- "Convince us how you're not going to leave us in the long run."
- Stupid db test: here is a scenario. You have 15 minutes to write an entire relational db with 20 tables, keys, relationships..
- "Why would we want to hire you?"6 -
So I did make a few website, they kinda worked well, but they really were ugly as fuck in terms of UI and UX.
So everytime a company was asking "have you got any website to show"
"NO, ABSOLUTELY FUCKING NOT, BUT YOU CAN TRUST ME I'M A REALLY GOOD DEVELOPER"5 -
DO NOT LIE ON YOUR RESUMÉ!
I don't understand why people do this. I understand that some shady recruiters like to "gin up" the occasional resumé, but I'm talking about the people who write that they're familiar with MySQL and can't even write a SELECT, or the people who write that they're familiar with Python and can't describe the differences between v2 and v3.
And the interviews are awkward as *fuck*.
I: "So it says you're good at MySQL, could you answer a few questions about it?"
C: "Uhh... okay"
I (sensing danger): "Why would you add an index to table that already exists?"
C: "I.. don't know"
I (oh jesus I see where this is going): "Okay, we'll skip that. How would you query across a couple of tables?"
C: "Uh...."
I ([internally screaming]): "How about a single query on a single table?"
C: "I don't know that, sorry..."
I (desperately wanting to ask why the FUCK is MySQL on your resumé?): "Thank you for your time, we'll call you."
You almost feel sorry for the guy, but come the fuck on, did you think nobody would check?19 -
For skilled mid-career engineers, dynamic programming problems, np-complete bar raisers.
For new engineers, simple questions that can't be taught in school (questions that require business prioritization)
For older engineers, questions they haven't done since college (big-O, writing algorithms from memory)12 -
Interviewer: Implement Binary Search on a Linked List
Me: * did so on the whiteboard *
Interviewer: *irritated* This is complete BS
Me: Yes, a complete Binary Search 🙂6 -
A colleague of mine was assigned to do a manual testing of application. It involved testing application in no-network / offline conditions.
While doing this he disconnected the virtual ethernet of Remote desktop thus crashing the VM forever....
Dear Elon Musk, send him to Mars right away.2 -
More or less all questions related to socially adequate behaviour (hope I got the wording right)
To be honest, it makes me choke, too.
Especially when HR starts to throw bananas at the new chimp eh sorry dev ( WE do XY every week ... Oh and in christmas... Bla bla bla)
It feels like a huge privacy invasion... And very forced. Me no like.2 -
We have a notorious question in one of our coding interviews, designed to weed out people who've slapped 'Postgres' on their CV (because that's what we're looking for) when what they really mean is "I've used MySQL a lot, and it's basically the same, right?". People get choked on that about 70% of the time.
If you put something technical on your CV, be prepared to be tested on it in a coding interview!1 -
Whenever the test is to see what clarifying questions they'll ask.
Give a dev in an interview setting a vague task that needs refining before it can be meaningfully attempted, and 95% of them will just plough in and start designing / writing code.
FWIW, I don't personally like these sorts of questions in interviews, as the situation is very different to reality (and therefore I don't believe it's a true reflection of what questions a user may ask in a work environment.) They are *very* common however, and a lot of devs don't seem to be aware.