5 ms·
> Anyone can glamorize and exaggerate the work they have done, and make it sound a lot more impressive than it actually was My personal experience interviewing
by dahart 7y ago
> Anyone can glamorize and exaggerate the work they have done, and make it sound a lot more impressive than it actually was
My personal experience interviewing is that people cannot easily glamorize their past projects when pressed for details. It might be easy to make it look good on a resume, but hard in person during a discussion with follow up questions.
I think asking about past projects is a fantastic interview question, and it’s very easy to get a good sense of what they did, what they were trying to do, how much was their leadership versus others, how successful it was, how much effort it took. All you have to do is ask questions about it, and not take the resume item at face value.
Personally, I find the open ended nature of the past projects question to be a better predictor of future performance than almost everything else on that list.
- username90 7y agoOr they could just lie and tell you from the perspective of another dev on their team, or even combining the achievements from several of them at once. Of course most people wont lie a lot but this style heavily favors those who do so you will get a disproportionate amount of liars on your team.
- dahart 7y agoI think your assumption is incorrect, based on my own experience. I’ve never hired a liar, and I’ve hired a lot of people. I have, however, declined to hire people who failed to answer follow up questions honestly or appeared to not be able to explain their success. Anyone who wants a job knows it’s a bad idea to lie because you find out immediately once you hire someone whether they are lying, and it would be grounds for immediate firing. Also follow-up questions weed out lies & half-truths very quickly. You should try it, see how long you can answer probing questions about someone else’s experience. I agree that most people won’t lie, and what does happen is almost always not lying but just spin, trying to glamorize rather than outright fabricate. My experience is that people get honest about their glamorizing very quickly if I keep asking more questions.
- username90 7y ago> you find out immediately once you hire someone whether they are lying Do you really believe this? Lets say we have a mediocre person on a team who tells the story of him being a star performer. How would you catch that? He went on the design meetings, he know why every decision was made, he has worked on the project for years. There is no way you would catch it, and the halo effect would likely mean that you still think he is doing decent work but that the environment might have made him a bit worse but you wouldn't believe that he lied.
- aantix 7y agoNuance comes from experiencing constraints from implementing the solution. Eventually the liar runs out of those details when pressed.
- dahart 7y ago> Do you really believe this? Yes, absolutely. I’m not lying. :) Like I said, I have lots of experience with it. I’ve interviewed people who tried to inflate their contributions, and it’s easy to tell over the course of a 5-10 minute conversation. > How would you catch that? Easily, they would fail to be a star performer, and fail to match the abilities they advertised. You can’t lie your way into good programming. However, it’s bigger than lie or not. Seasoned programmers have mature philosophies, and you can tell by talking to them. And honestly, I don’t mean this judgementally, but your question does sound like it comes from a lack of experience. You will find out what I’m talking about in time; big lies are not in the least bit easy to pull off, and almost nobody tries that kind of thing because the probability they’ll get caught and have serious consequences is very high. Being present in design meetings and knowing why decisions are made does not make you able to talk about it fluently. BTW, while I believe this myself absolutely, I don’t know for absolute certainty that I’m right. So if it’s easy to do and the payoff is large then you should do it and write about it! If you could easily lie your way into a job, then it should be easy to work your way into one of those super high paying jobs, making robots or neural networks, and get away with it for years.
- 7y ago
- wslh 7y agoYou can discover the lie asking very technical questions on how the solved some issue. They will answer at the greatest level of detail if they did it themselves.
- username90 7y agoNote that we aren't talking about people who can't code, we are talking about mediocre performers who know what they are doing but are still far from top talent. Knowing how to explain a coworkers thought process is not very hard when you have reviewed their design documents and been on every meeting.
- marktangotango 7y agoProvided you or the arbitrary interviewer have the technical background to evaluate the answers! I once had reason to view the resume of a former colleague who took all credit for a major project I implemented. This project involved parsing and a particular parser generator. He worked on it after I implemented it, but he claimed it all. And he was knowledgeable enough to back that claim up!
- smsm42 7y ago> And he was knowledgeable enough to back that claim up! If he worked on it and could convincingly fake it, I - as a recruiter - wouldn't care too much if he embellishes a bit and claims he also did it from the start. Maybe he factually didn't, but if he's good enough to make me think he did, there's a decent chance he would be good enough to actually do it for me. Not a certainty, there's never certainty, but a good chance. Of course, given the choice, I'd prefer the one who actually created it, but one who worked on it and knows it well enough is not bad either.
- palerdot 7y agoThe point is the hiring method attracts people who are both not genuine , to admit that they just jumped in on an impressive project and insecure enough , that they think they should claim everything as their own ... It doesn't matter if they actually possess the technical skill as there might be behavioural issues between this person and the rest of the team.
- smsm42 7y agoThat is a very dangerous gamble though because the next question would be "you did all that? How cool! Tell me more details!" and my experience shows that faking the details, unless you've done at least something very close to what you claim you did, is not very easy. And generic bullshit is rather easy to detect - usually you can see when the person is genuinely talking about something they did and are excited to share and when they're just stalling because they have no idea. Of course, once in a while you can get a bullshit artist of high caliber - but those very quickly reveal themselves when you ask them to actually do something.
- ozim 7y agoYeah... or I have been working on that cool project six months ago and by the time we just have this talk I had a 100 other things on my plate which are not that cool. Then maybe I want to change job because we got new boss that was stressing me out for 3 months and I gave up. So I am rusty on the details and I am also intimidated when you bring in 3 people to have talk about it. I would say it is OK if it works for you but it still might be that you drop off some good guys. Because it is environment that creates good employees, and if someone was working for months or years in a bad environment, he can be perfectly capable of doing work, but not being confident and feeling good about talking about his last job.
- lubesGordi 7y agoYeah it's pretty easy to tell where a senior engineer is at if you're in the same domain as them. Just discussing projects really provides much more insight than leetcoding them to death. It's shocking to me how many places are leetcoding senior engineers before talking to them about their past work or discussing design. Is it because we want to have hiring automated? Is it because of discrimination? Why is the leetcode interview process so widely adopted?
- closeparen 7y agoBehavioral, system design, coding, and problem solving interviews are AND gated. It's not a question of one being more important, but which ordering optimizes the funnel and employee time. There are many more calendar slots belonging to tech ICs than to hiring managers; you can run a higher velocity pipeline if you start with a technical phone screen. The coding interview itself is an immune system against the surprisingly large population of candidates who have long resumes and can talk a big game but not actually perform. (I didn't believe these people existed either, until I started doing phone screens). It's also a way to recognize smart people who will do well with whatever they're given, even if they're underutilized or in a different domain at their current job. Tech companies are typically hiring more for this than for tech stack or business domain similarity.
- monksy 7y ago> but not actually perform You're trying to measure how they'll perform on your work before you hire them? That sounds like you're trying to get free work from them. (Just a note.. this is on the words you used) > recognize smart people who will do well with whatever they're given, How does a take home coding test that is limited on time, and their own time + stress indicate that they are in that category?
- dahart 7y ago> You’re trying to measure how they’ll perform on your work before you hire them? That sounds like you’re trying to get free work from them. I wish the hyperbole about trying to get free work during an interview would just die already. Nobody is getting free work by interviewing applicants, interviews are costly to most companies, but necessary to grow the team. Just because interviews take time and are difficult and scary doesn’t mean someone is taking advantage of you. Try to put yourself in the company’s shoes — they have to evaluate you one way or the other. How would you do it? A time limited stress test is extremely effective at identifying certain kinds of performers. Obviously being able to solve problems fast is an indicator of a certain kind of smart. This doesn’t identify all smart people, and nobody claimed it did, that’s why a coding test is almost always one part of many in the interview process, and people routinely get hired when passing some parts without passing all the parts.
- golemiprague 7y agoI agree, I don't even bother doing code testing, it is much better to talk to someone about past projects and get a gut feeling if they are good or not. It is the common thing to do in most other professions, people don't sit for tests, sometimes you can ask a bit more difficult questions like how would you do this or that or whatever but nobody expect people to sit and fill up pages in most professions and rightfully so. There is no advantage predicting the future from those tests over a simple gut feeling.