Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "interviewers"
Interviewer: Welcome, Mr X. Thanks for dropping by. We like to keep our interviews informal. And even though I have all the power here, and you are nothing but a cretin, let’s pretend we are going to have fun here.
Mr X: Sure, man, whatever.
I: Let’s start with the technical stuff, shall we? Do you know what a linked list is?
X: (Tells what it is).
I: Great. Can you tell me where linked lists are used?
X:: Sure. In interview questions.
X: The only time linked lists come up is in interview questions.
I:: That’s not true. They have lots of real world applications. Like, like…. (fumbles)
X:: Like to implement memory allocation in operating systems. But you don’t sell operating systems, do you?
I:: Well… moving on. Do you know what the Big O notation is?
X: Sure. It’s another thing used only in interviews.
I: What?! Not true at all. What if you want to sort a billion records a minute, like Google has to?
X: But you are not Google, are you? You are hiring me to work with 5 year old PHP code, and most of the tasks will be hacking HTML/CSS. Why don’t you ask me something I will actually be doing?
I: (Getting a bit frustrated) Fine. How would you do FooBar in version X of PHP?
X: I would, er, Google that.
I: And how do you call library ABC in PHP?
I: (shocked) OMG. You mean you don’t remember all the 97 million PHP functions, and have to actually Google stuff? What if the Internet goes down?
X: Does it? We’re in the 1st world, aren’t we?
I: Tut, tut. Kids these days. Anyway,looking at your resume, we need at least 7 years of ReactJS. You don’t have that.
X: That’s great, because React came out last year.
I: Excuses, excuses. Let’s ask some lateral thinking questions. How would you go about finding how many piano tuners there are in San Francisco?
X: 37. I googled before coming here. Also Googled other puzzle questions. You can fit 7,895,345 balls in a Boeing 747. Manholes covers are round because that is the shape that won’t fall in. You ask the guard what the other guard would say. You then take the fox across the bridge first, and eat the chicken. As for how to move Mount Fuji, you tell it a sad story.
I: Ooooooooookkkkkaaaayyyyyyy. Right, tell me a bit about yourself.
X: Everything is there in the resume.
I: I mean other than that. What sort of a person are you? What are your hobbies?
X: Japanese culture.
I: Interesting. What specifically?
I: What’s hentai?
X: It’s an televised art form.
I: Ok. Now, can you give me an example of a time when you were really challenged?
X: Well, just the other day, a few pennies from my pocket fell behind the sofa. Took me an hour to take them out. Boy was it challenging.
I: I meant technical challenge.
X: I once spent 10 hours installing Windows 10 on a Mac.
I: Why did you do that?
X: I had nothing better to do.
I: Why did you decide to apply to us?
X: The voices in my head told me.
X: You advertised a job, so I applied.
I: And why do you want to change your job?
X: Money, baby!
X: I mean, I am looking for more lateral changes in a fast moving cloud connected social media agile web 2.0 company.
I: Great. That’s the answer we were looking for. What do you feel about constant overtime?
X: I don’t know. What do you feel about overtime pay?
I: What is your biggest weakness?
X: Kryptonite. Also, ice cream.
I: What are your salary expectations?
X: A million dollars a year, three months paid vacation on the beach, stock options, the lot. Failing that, whatever you have.
I: Great. Any questions for me?
I: No? You are supposed to ask me a question, to impress me with your knowledge. I’ll ask you one. Where do you see yourself in 5 years?
X: Doing your job, minus the stupid questions.
I: Get out. Don’t call us, we’ll call you.
All Credit to:
Recently had an interview with a company. At some point an SELinux question came up and while I didn't provide the best answer ever (I'm hardly familiar with SELinux and mentioned that as well beforehand so they knew), it was technically correct and the reaction of the interviewers was funny.
TI (technical interviewer): say your php script isn't executed and after a while you find out that SELinux is blocking php script execution, how can you fix that?
Me: setenforce 0...? (essentially disabling SELinux at all)
TI: disabling it entirely for getting php execution to work?! That doesn't sound like a good solu...
HRI (HR (non technical) interviewer, also present): *turns to TI* - but, would it solve the problem?
TI: 😐 well, yes, but... That's a bad thing to do so I wouldn't count is corre..
HRI: *still aiming towards TI* but you simply asked him for a way to solve the php execution issue, would his answer work? Regardless of whether it's the best or worst solution, would it be a solution which works?
TI: well... yes...
HRI: then he answered correctly I'd say, next!
(yes, I'm aware that my answer wasn't good as for security at all but it would have solved that problem which is what was asked)21
Skype interview for CERN: done!
Interviewers were very nice and professional :) If all goes smoothly this adventure starts in September!17
One of the RH interviewers started asking about myself, personal information, etc..
He : well, let me introduce you our tech lead, he will make you some question about JS
Me : alright
Me : yes..?
Tech Lead : ok, cool. We will call you.
I got the job..11
Why are interviewers so resistant to letting people use Google while doing coding questions? It’s not like I can remember all the semantics of every language anyway, and so much of coding is learning to use Google correctly.8
I got laid off from my previous position as a Software Engineer at the end of June, and since then it was a struggle to find a new position. I have a good resume, about 4 years of professional dev experience and 5 years of experience in the tech industry all together, and great references.
As soon as I got laid off, I talked to my old manager at my previous company, and he said that he'd love to hire me back, but he just filled his last open spot.
In order to prepare, I had my resume reviewed by a specialist at the Department of Labor, and she said that it was one of the better resumes that she had seen.
There aren't a huge amount of dev jobs in my area, and I got a TON of recruiter emails. But they were all in other states, and I wasn't interested in moving.
I applied to all the remote and local positions I could find (the ones that I was qualified for,) and I just got a bunch of silence and denials from all my applications. I had a few interviews that went great, but of course, those companies decided to put the position on hold so they could use the budget for other things.
The silence and denials were really disconcerting, and make you think that something might be wrong with you or your interviewing abilities.
And then suddenly, as if the floodgates had opened, I started getting a ton of callbacks and interviews for both local and remote opportunities. I don't know if the end-of-year budget surpluses opened up more positions, but I was getting a lot of interest and it felt amazing.
Another dev position opened up at my previous company, and I got a great recommendation for that from my former manager and co-workers. I got a bunch of other interviews, and was moved onto the next rounds in most of them.
And finally, I got reached out to regarding a remote position I applied for a while ago, and the company was great about making the interview process quick and efficient. Within 2 weeks, I went from the screening call, to the tech call, and to the final call with the CTO. The CTO and I just hung out and talked about cars/boats/motorcycles for half the interview, and he was an awesome guy. AND THEN I GOT AN OFFER THE NEXT DAY!
The offer was originally for about the same amount as I made at my previous job, but I counteroffered up a good amount and they accepted my counteroffer!
It's a great company with offices all over the world, and they offer the option to travel to all those offices for visits if you want. So if you're working on a project with the France team and you think that it'd be easier to just work with them face-to-face, then the company will pay to fly you out to Paris for the week. Or you can work completely remotely. They don't mind either way.
I'm super excited to work with them and it feels great to be back in the job world.
Sorry about the long post, but I just wanted to tell my story and help encourage anybody out there who's going through the same thing right now.
Don't get discouraged, because you WILL find an awesome opportunity that's right for you. Get somebody to go over your resume and give you improvement recommendations. Brush up on your interviewing skills. Be sure to talk about all the projects you've worked on and how they positively impacted people and/or companies.
This is what I found interviewers responded the best to: Be sure to emphasize that you love learning new things and that you love passing along that knowledge to other people, and that your goal is to be an approachable and reliable source of knowledge for the company and to be as helpful as possible. It's important to be in a position that encourages both knowledge growth and knowledge sharing, and I think that companies really appreciate that mindset in a team member.
Moral of the story: YOU GOT THIS!16
I should add to my list of skills "managing to keep the interviewers entertained for 90 minutes, even though I couldn't answer like 90% of their questions".7
Ok yeahhh it’s not me.
Just got told I didn’t pass an interview that lasted 15 minutes with him talking about the company and no questions for me.
My interviewers lately have just been unfortunate3
I recently interviewed for a job at company where I had 20 minutes to code a solution in python (whose standard library I know nothing about) to a question, which also included googling certain finance-related APIs, with not one but two technical interviewers looking over my shoulder THE ENTIRE TIME.9
What the fuck is up with interviewers asking about my goddamn hobbies now? My hobby is slowly going blind while frustratedly talking to myself through an anthropomorphized rubber duck you fucking idiot, that's why I'm here in the first place. "Well we want a well rounded person". I'll give you a well-rounded asshole. It used to be, "well do you write code in your spare time too"? What the fuck do they want from us? Next time I'm answering this new "hobby" question as follows:
I DO COKE AND FUCK STRIPPERS! I'M THE ROCKSTAR DEVELOPER YOU'RE ALWAYS JERKING OFF TO, CAN YOU EVEN HANDLE THAT YOU ASTONISHING PUSSY?17
This is not an interview test just an awkward experience in general regarding interview.
This happened two years ago when I was a fresh university graduate looking for a job in UK as an immigrant (Im EU national).
Went to an interview for a web dev+tech support position. Two fat guys with tshirts met me and started interviewing me for a sysadmin position. Started asking me about disaster recovery and stuff.
Turns out recruiter messed up not only companies but positions as well. Also these two guys didnt bother to check anything.
I pulled out the job ad for which I applied originally, interviewers had a look at it and still proceeded questioning me while knowing that I prepared for completely different position interview.
Needless to say, it went terrible and I didnt get the job. I dont know if its just me or Im unlucky, but I had a lot of encounters in UK with so many incompetent recruiters.3
Why are Job interview tests so reliant on knowledge of the language's functions!
I dabble in a few languages and I don't bother learning all the basic functions of by heart...
Eg: len(str), str.length, str.Length, strlen(str)
why... because they are literally a 5 second Google. Unfortunately for us, this quick search isn't possible and I think it should be.
Another example of bad interviews is a coder with 37 years experience but was unable to get a job at Google (link: http://gwan.com/blog/20160405.html)
He was asked strict questions by someone who didn't know much about computers let alone programming. Unfortunately, since the interviewer wanted exact answers, the coder was unable to complete the interview. He answered all the questions validly and with depth but this was not written down on the interviewers sheet.
Do employers want people that have a good and broad knowledge of their field or people that know what they want them to know. It's getting ridiculous.9
Worst: The guy gave me 5 minutes to code a given assignment on paper. I did all the logic and told him I was missing a function whose name I would just Google. He told me I can't always Google. Well... I won't be coding on paper either.
Best: I was given the assignment to clone a part of a production site. Assignment was intended for 3 days and I was given 5 hours. Completition wasn't important, only structure and coding style counted. I cloned everything and even added new features.
You just can't always be in the zone. I hope more interviewers would take that into account and design better questions.4
I got my job because I've been myself. As soon as I laughed with the interviewers I knew I got it.
They choose you for a interview out of all the other CVs because they hope you know your stuff. Proof it! And most important - show your character. Don't be a blank paper! Make fun with them. Or at least leave some kind of positiv impression.
The funny part:
I applied for jobs in Austria while doing my Bachelor degree in the UK. Over Skype they had no idea I was wearing sweatpants.1
Did not expect this from Google. Seems like you're hiring real linguistic pros.
Now this is not the only thing I didn't like, they're very disorganized & the interviewer got sick & two of three interviewers were so cocky.. bad bad vibes
On the other side, a small local company is giving warm & good vibes, seems more accommodating even with lower pay.. their website sucks & the tech director was honest & smiling.
So yeah, Fuck You Google
Grr the feeling when one of your interviewers has a hard-on for trying to find ways to sink your boat.
Went to a job interview yesterday during my lunch break for a mid level dev job in central London , i have been trying to transition from a junior role.
First were two senior devs , that went quiet well...
Next up was the tech lead and a team lead, lets call the latter Mc-douche for some problem
The tech lead was fine, very relaxed and clam guy more interested in seeing the logic of my answers and questions as to why i did certain things in this or that manner....
Mc-douche, he would always try to find something wrong then smile smugly and do that sideways head waggle thing
His tech lead is like " yup that's correct"
But he would be like " yeeess but you didn't think about bla bla bla" then talk about shit not even present in the context of the question
Ah also he would ask a question then cut me off as soon as I begin to say that i didnt mention or take into account x or y even though literally my next sentence is about address those details he wanted.
let me fucking finish you dickbag 😡
Had a js question, simple stuff about dom manipulation, told not to bother with code... yet McD starts asking me to write the code for it....managed it , quite easy stuff
Then a sql and db test , again technlead was happy with the answers and the logic am approaching the question when writing my query, yet mc d Is bitching about SQL syntax....
Ok fine, i made a simple mistake, I forgot and used WHERE instead of HAVING in a group by but really?! Thats his focus ?!
Most devs I know look up syntax to do stuff , they focus on their logic first the do the impl.
Then a general question on some math and how i would code to impl a solution on paper
That was a 20 mins one, the question said they didn't expect me to finish it totally so
I approached it like an exam question.
I focussed on my general flow of my process, listing out each step.
Then elaborated each step with pseudo code showing my logic for each of the key steps.
Then went deeper and started on some of the classes and methods , was about to finish before it was time up.
Mc douch went through my solution
And grudgingly admitted my logic was "robust enough" it was like he really had to yank that deep out of his colon.
I didn't really respond to any of his rudeness throughout the whole interview,i either smiled politely or put on a keen looking poker face.
Really felt awful the rest of the day, skipped the gym and went home after work, really sucks to have a hostile interviewer.
Pretty sure i wont be hearing anything good from them even though the three other interviewers were happy with me I felt.4
Not learning data structures and algorithms. Not learning programming languages. Actually not learning anything to answer during a job interview.
I am more of a learn-while-you-do kind of guy. I never learn anything, instead just do it. Interviewers think I am useless because I know nothing. But I can get a job done, any kind of job done. I have no learning period, I can start working from first day in a all new language, in a all new IDE, in a all new OS.
I know nothing, and I learn nothing. I am a problem solver. You got a problem, I can solve it.6
I work in a contract position and reviewed the code of a senior engineer recently. Regretfully I can't provide context to preserve anonymity.
- handled a single DOM element with 2 different frontend libraries
- used the logical operator && to 'chain' two methods (it didn't work) instead of returning a boolean value,
- broke everything down into minute detail (a comment box had 7 components!),
- API calls were made for every component update instead of maintaining local component state where it made sense, which meant UI updates were slow,
- animated EVERYTHING, which made my Firefox on Xubuntu i7 64bit with 16GB RAM beg for mercy.
I had a rough couple of months with interviews, with 2nd stage technical interviewers throwing impossible tasks at me.
3. Hack a website from the browser's address bar using parameters ( what?!! ),
Obviously, the next time I meet a 'senior', I'm going to tell him talk is cheap;
'SHOW ME YOUR CODE.'3
Six or seven years ago, I worked for a large financial organization as part of a very large effort to convert server assets from physical to virtual. The consultants on site were in bed with the vendor of a terrible piece of software designed for that purpose. After a couple weeks on the job I'd had it, and sat down in between sessions of "validating" the conversion procedure, and started writing my own software for converting Linux servers. After a couple days it was working great, and they wound up adopting my software as the default method for Linux conversions.
Years later, I'm interviewing for my current job and one of the interviewers tells me he used my converter some time later and loved it. Pretty sure it's what swung the interview for me.
Alright. This is going to be long and incoherent, so buckle up. This is how I lost my motivation to program or to do anything really.
Japan is apparently experiencing a shortage of skilled IT workers. They are conducting standardized IT skill tests in 7 Asian countries including mine. Very few people apply and fewer actually pass the exam. There are exams of different levels that gives you better roles in the IT industry as you pass them. For example, the level 2 or IT Fundamental Engineering Exam makes you an IT worker, level 3 = capable of working on your own...so on.
I passed level 1 and came in 3rd in my country (there were only 78 examinees lol). Level 2 had 2 parts. The theoretical mcq type exam in the morning and the programming mcq in the afternoon. They questions describe a scenario/problem, gives you code that solves it with some parts blanked out.
I passed the morning exam and not the afternoon. As a programmer I thought I'd be good at the afternoon exam as it involves actual code. Anyway, they give you 2 more chances to pass the afternoon exam, failing that, you'll have to take both of them the next time. Someone who has passed 1 part is called a half-passer and I was one.
A local company funded by both JICA and my government does the selection and training for the Japanese companies. To get in you have to pass a written exam(write code/pseudocode on paper) and pass the final interview in which there are 2 parts - technical interview and general interview.
I went as far as the interview. Didn't do too good in the technical interview. They asked me how would I find the lightest ball from 8 identical balls using a balance only twice. You guys probably already know the solution. I don't have much theoritical knowledge. I know how to write code and solve problems but don't know formal name of the problem or the algorithm.
On to the next interview. I see 2 Japanese interviewers and immediately blurt out konichiwa! The find it funny. Asked me about my education. Say they are very impressed that self taught and working. The local HR guy is not impressed. Asks me why I left university and why never tried again. Goes on about how the dean is his friend and universites are cheap. foryou.jpg
The real part. So they tell me that Japanese companies pay 250000/month, I will have to pay 60% income tax, pay for my own accommodation, food, transportation cost etc. Hella sweet deal. Living in Japan! But I couldn't get in because the visa is only given to engineers. Btw I'm not looking to invade Japan spread my shitskin seed and white genocide the japs. Just wanted to live in another country for a while and learn stuff from them.
I'll admit I am a little salty and probably will remain salty forever. But this made me lose all interest in programming. It's like I don't belong. A dropout like me should be doing something lowly. Maybe I should sell drugs or be a pimp or something.
But sometimes I get this short lived urge to make something brilliant and show them that people like me are capable of doing good things. Fuck, do I have daddy issues?19
Can interviewers PLEASE stop asking cliche and terrible questions??
Interviewer: "Where do you see yourself in five years?"
Me: "Not with you guys obviously, you dumb piece of shit."
That's what I'd like to say to them at least... :/7
Do real interviewers (I mean those who are smart and have some experience) still ask questions like "what are your weaknesses"?
Dumbass, why the fuck should I declare, not just to you but also to myself, that I have some particular weaknesses? I know what I'm not good at, and I'll keep trying to improve. But unless my weakness is that I get a massive boner during team meetings, you don't need to know about it. I'm not telling you. Just know my strengths - that's enough. If you're just following a standard list of interview questions that you didn't even come up with, stop pretending to be an interviewer for heavens' sake.8
Had an interview with a local recruiting company for a series of jobs they posted. It started with two of their interviewers casually talking to me at a Starbucks. After a while they realized I met the criteria for one of their own job postings so they texted their boss who came down to the coffee shop about five minutes later. Which is when it got weird. She asked me regular questions about the job, then started asking me about non work stuff. She was sitting next to me at a 4 person table. We talked a little about hobbies, I'm really into biking so we talked about that. Which is when it got super weird, she felt my leg up and ran her hand around my chest. I didn't even think anything of that until the interview ended honestly, but it's freaked me out until this day. Never had an interview like that before. Ironically, I didn't get the job, and if I would have gotten the offer it would have had to have been really really good to take it. She gave me the heebie jeebies despite being attractive, who does that, in an interview none the less.4
I once interviewed for a role at Bank of America. The interview process started off well enough, the main guy asked some general questions about career history and future goals. Then it was off to the technical interviewers. The first guy was fine. Asked appropriate questions which he clearly understood the answers to.
The next guy up, however, was what I like to call an aggressive moron. After looking at my resume, he said I see you listed C++. To which I said, yes I have about 7 years of experience in it but I've mostly been using python for the past few years so I might be a bit rusty. Great he said, can you write me a function that returns an array?
After I finished he looked at my code, grinned and said that won't work. Your variable is out of scope.
(For non C programmers, returning a local variable that's not passable by value doesn't work because the local var is destroyed once the function exits. Thus I did what you're supposed to do, allocate the memory manually and then returned a pointer to it)
After a quick double take and verifying that my code did work, I asked, um can you explain why that doesn't work as I'm pretty sure it does.
The guy then attempted to explain the concept of variable scope to me. After he finished I said, yes which is why I allocated the memory manually using the new operator, which persists after the function exits.
Einstein then stared really hard at my code for maybe 10 to 15 seconds. Then finally looked up said ok fine, but now you have a memory leak so your code is still wrong.
Considering a memory leak is by definition an application level bug, I just said fine, any more questions?4
ok, well, I have a list of worst interview experiences. here is one. This was my very first job interview.
[Things differ with places, but where I live, we give a lot of respect to teachers, interviewers etc]
It was my turn for the interview and I forgot to knock the door. The interviewer didn't like that. But I guess he ignored.
I also forgot to ask to get in. So, instead of pointing out my mistake, he taunted me. When I was already in, in front of him, he looked at me and said "Yh, come in!" as in, you forgot to ask that. But I was already more then, just in.
I felt sorry, quietly sat down on the chair. when I was well settled on my chair, he looked at me and said "Yh! sit down please!". Again reminding me I forgot to ask him to sit down.
Should I have apologized atleast? I forgot to do so! So he reminded me again, "Oh that's okay! don't say sorry."
It was enough embarrassing for me already when I hadn't even utter a word. I don't give a damn about interviews anymore, but well, that was my first one! You must know that feel.
Well, he was quite happy with the rest of the interview, so at the end of it he told me "it's okay it usually happens initially. You'll get used to it pretty soon." I ignored that later but could never forget how it all started. 😂🎃2
@Owenvii made a post over at (https://devrant.com/rants/2359774/...) and I want to write a proper response.
The biggest thing you have to look out for as a new dev is the jobs which you accept to begin with.
This isn't minimum wage no more, this is "big league", well, maybe not apple or google big league, but it's not $9.25 an hour either.
Basically you don't want to work anywhere where 1. your labor will be treated as a highly disposable commodity. 2. where the hiring manager doesn't know how to do the job themselves.
The best thing you can do is, if you're new, and just breaking through (and even if you're not), is ask them common questions and problems/solutions that crop up doing the work. If they can answer intelligently that tells you the company values competence (maybe), enough to put someone in place who will know ability from bullshit, merit from mediocrity, and who understands the process of progressing from junior dev to a more involved role.
It also means they are incentivized to hire people who know what they're doing because the training cost of new hires is lowered when they hire people who are actually competent or capable of learning.
Remember, an interview isn't just them learning about you, it's your opportunity to interview *them* and boy, you'll be making a BIG mistake if you don't.
Ideally you want them to ask you to pair program a problem. If your solution is better than theirs then they aren't sending their best to do interviews, and it tells you the company doesn't fire incompetents. The interviewers response can tell you a lot too, if they critique your work, or suggest improvements, and especially if they explain their thinking, that is an amazing response to look for, it says the company values mentorship and *actual* teamwork (not the corporate lingo-bingo 'teamwork' that we sometimes see idolized on posters like so much common dogma).
Most importantly, get them to talk about their work and their team. If they're a professional, it'll be really difficult to pry anything negative about their co-workers out of them, but if they're loose-lipped and gossipy thats a VERY bad sign, regardless of what they have to say.
Ask to take a tour and do a meet n' greet of who you will be working with. If they say no, then it's no thank you to a job offer. You want to take every opportunity to get to know everyone there, everyone you'll be working with, as much as possible--because you'll be spending a LOT of time with these people and you want to rule out any place that employs 'unfireable' toxic assholes, sociopath executives, manipulative ladder climbing narcissists, and vicious misery-loving psychopathic coworkers as quick as possible. This isn't just one warning flag to look out for, it's the essential one. You're looking for the proper *workplace culture*, not the cheesy startup phrase of "workplace culture", but the actual attitudes of the team and the interpersonal dynamics.
Life is really short, and a heart attack at 25 from dipshit coworkers and workplace grief can and will destroy your health, if not your sanity, the older you get.
Trust and believe me when I say no paycheck is too grand to deal with some useless, smarmy, manipulative, or borderline motherfuckers at work constantly. You'll regret it if you do. Don't do it. Do you fucking do it. Just don't.
Take my words to heart and be weary of easy job offers. I'm not saying don't take a good offer that lands in your lap, I AM saying do some investigating and due diligence or the consequences are on you.1
I was in the last stage of a 12 hour interview process (over 3 days), meeting with the CEO/founder of the company. His final conclusion was (and he said this directly to me) that he felt I would do really well, and that my skill set was perfect and all the feedback from the interviewers was top notch...but he asked if I was published or had any patents. I said “no”. So, he paused and then said “well, without a full 4 year degree or either having been published or having any patents, I think we would be taking too great a risk. I mean, there’s a chance you would work out. I have taken that chance before, and he’s now our CTO. But I’m just not sure about this”.
I was not offered the position.5
Had an interview last week set up by a recruiter. Interview went well, aced the tech part, got on well with the interviewers, etc. They had one more interview the next day and would make the decision. Got feedback from recruiter the next day. I was in the top 2. Was told I had the best experience and skills. Thought I had this. Later that day got told they went with the other candidate because my recruiters presented me for $5000 more than the employer's posted upper limit. The employer just felt my salary requirements would push their budget too much so they went with the cheaper, less qualified candidate.
Not happy with my recruiter at all!
Heard a job position opened through a friend. Passed him my CV since we don't know his email (lol how?)
Got called for an interview + technical test. Came and they were expecting my CV. They somehow misplaced my CV (lol again how?)
Told the interviewers that I made a couple of apps for fun and informative. Tested me by doing a value switch between 2 variables without introducing a third variable. Done and dusted.
A month later, the company that interviewed me disappeared.
That's my definition of the worst interview rejection. Company pulled a Houdini without telling all of their candidates that we're rejected.14
What do you tell interviewers as a "Senior developer" when they ask you what you do at your current job.
I've been with my current for almost 8 years, since graduating... Few different time but not very well managed (semi/barely agile). Hasn't really provided any skill growth opportunities. Mostly fixing production issues, chasing other teams.
The projects I've worked on are in many different languages either enhancements or some standalone stuff. But nothing that's huge and I don't think I've learned anything from them. I usually apply what I learn and practice outside of work to work.
So to me I can probably list a whole lot of projects but to me their not that amazing, I didn't learn anything from them.
Also about those algorithm questions. I've never used any of this stuff actually at work. Concepts yes but not how do you implement ... And honestly I've never once had a situation that required algorithmic thinking other than maybe writing recursive functions in rare occasions...
But to me I've never once done anything harder or new which I haven't already done on my own....
Sorry for the disorderly rambling this turned into... which is sorta a problem too.
Everytime I think about interviews, I want to give rants about we technical questions are BS, how I probably have enough real experience to tackle any problem and come up with a good plan/solution (in a realistic timeframe, not 20 minutes from design to implementation)2
just got rejected after interview because I just cracked on with the coding exercise and didn't ask for the interviewers help (trying to create a collaborative environment) even though I smashed out the solution.... maybe dodged a bullet there5
Just got interviewed for a project today.The interviewers knows i am a fresher and the last thing that they told me after the entire interview was that the job requires a 4 yr experience!!! I was standing there and wondering why am i being interviewed then and how was my profile selected for the job 😂2
Adobe labs released one new component, I played with it after two days. Went to an interview with huge company after two weeks for a developer position, the interviewers was from different departments, they asked about one technical challenge they have, then I suggest the new component as solution, they gave me small task to implement using the component, I delivered it next day... Then they hired me in R&D department. It was great days.
I would like to present you the story that I tell everyone who is afraid of expectations, stressed to impress interviewers etc. Story about how I got my first job.
A little of backstory:
I always was good with computers, not like expert, but good. Of course parents were against giving me admin rights, so I just played games or such. When time came to choose my path throgh life, I've chosen to go medicine-related way, and chosen high school with such profile. I did my exams terribly, cause I never cared about marks, so I applied to uni for Information and Communication Technology course. I've learned basics of coding there, much stuff I don't really need right now, but in the end it was the best choice I've made.
With that way too long prologue...
I had to do internship for my uni and decided to try and find some year earlier. There was a lecture about multiplatform coding held by company my uni had partnership with. I've filled a questionare and few weeks later they invited me for assessment - event where they will choose who is good enough.
Of course I didn't believe in my chances to win an internship (1st place got full time job). There were 3 stages:
- solo coding (C/C++ own implementation of list)
- group designing (UML and presentation according to specification)
- interview (talking about code from stage 1, some questions, theory)
I failed 1st stage miserably... so I decided to don't give a shit and bravely presented our group project. A guy asked why we did not included a thing on UML, so I told him that it was not in specification - he was suprised but took it as big +. We "won" that part. When it came to interview... I was myself, cool headed, admited when I don't know things.
I thought that was it.
Few weeks later I received email - they invited me for internship.
They put me into Python project, language that noone in our trainee team knew. Told us 2/4 will be hired. At first I was not interested, wanted to finish my degree. But they convinced me. Now I'm here +2 years.
I am aware there are not many companies like that. Here, the people matters - you don't have to know everything, as long as you are getting along with others.
My tip for you though is: BE YOURSELF, NO MATTER WHAT THEY SAY 🎶
And I wish us more companies like that.😉1
Had my 2nd job interview.
Two of the interviewers were great, but the third interviewer was like an asshole.
Always tried to make me stuck somewhere haha9
I've never been to a job interview yet (most of the cunts here in Belgium work with Windows Server 🤮, and I'm still studying electronics), but given most of the submissions on this group rant, I think that I might very well have seriously overestimated interviewers! 😄2
I landed myself an interview with a really great company for a DevOps intern position tomorrow.
Im really hopeful about this. The company truly seems like a great place to work with incredible opportunity to grow, and I desperately want to pursue a career in DevOps, but Im worried that Im underqualified. I lack true professional experience, and have really had no adequate time working with CI/CD tools, but I am very interested, excited and willing to work hard to become proficient.
Ive been prepping myself as much as I can in this last week (trying to gain familiarity with tools like jenkins, artifactory, chef etc), and so I ask to you, my fellow ranters (particularly DevOps), are there any final tips or bits of advice that I can take to really impress my interviewers and better my chances of getting this position?
Also, hello again to my old devRant pals~ I miss hanging around here and conversing with you great people13
I asked at an interview if they documented their code with class diagrams.
One of the interviewers told me: "Good code doesn't need a class diagram"
Why do technical interviewers expect and force you to know a made-up word such as SOLID and treat it as if it's a gospel?
Is this "SOLID" a technical standard now that should be taught in schools?
I'm not against learning and using the principles in SOLID. I just find it funny (and weird) that if I didn't watch the talk by the guy who came up with SOILD, I wouldn't be able to answer the interviewer.17
How to respond to the "How do you rank yourself in technology X on a scale from 1 - 10"?
What is 10? Why are recruiters and interviewers asking such questions?7
Don't understand why interviewers ask such stupid questions like where do you see yourself in 5 years?
If I goddamn knew why the hell would I be applying here.
Also why do you want to join our company?
The obvious answer is money. end of story. Why do you expect me to say the work environment blah blah blah22
Know your shit and don't give a fuck.
Sometimes interviewers are just idiots or monkeys.
I dunno, I've had a few interviews where it just doesn't click. While I'm sitting there, I say to myself: this is nothing like what you said on your job description.. and I've seen all your "technical questions" on Google
I had a coding interview with Amazon. I had to implement a depth-first search algorithm with no prior experience while 2 devs watched me code on a collaborative IDE. To make it worse, the connection was terrible on the conference call and one of the interviewers had a very thick accent. I barely understood what they wanted me to do until I typed out:
Breadth-first search || Depth-first search?
// Sorry, phone keeps cutting off and I can barely hear you
Yeah, I didn't make it to the next round. :(2
4 really basic questions. Things you can't get through 1st year undergrad without knowing. One was testing you understand references, one testing understanding of inheritance, then exception handling... Then a bit of a tricky one: what happens when you query 2 tables in sql without a join. That took me a second because it's just not something I'm used to doing.
So yeah it's pretty basic stuff. At this point I was used to writing fairly long code snippets and quizzes with lots of gotchas that make the interviewers feel really smart. I think "ok they basically want to make sure I'm not totally useless and they're fine with training me". But noooooo. Being able to answer all that correctly is really impressive. That's never happened before. I'm a fucking prodigy.
So I got the job and I alternate between thinking I'm in Idiocracy and thinking the reception I get is some sort of elaborate joke
My class team picks me for a competition.
My team tells me to do everything and doesn't give me an outline of what they want for the code or design.
They have 7 members. + me, 8.
I have to design and code the whole app on android.
Furthermore it was my first time with library stuff.
I had to develop from 10pm to 6 am with short rests in between. Almost no sleep.
It's impossible sht. I continue with it.
When it was time for school, I just went to school as per usual.
When it was the interview someone just had to roast the judges.
Our idea was very sophisticated; was to help track down elderly or child with a gps tracker and the app.
Didnt got in the qualifiers because of the leader being an asshole to the interviewers.
Heard nothing back from an interview I attended 3 weeks ago. I'm sure this sort of thing is common, but it's never happened to me before.
It's so shitty and unprofessional.
The interview was a joke anyway, bouncing between business questions (strictly non-technical, as I learned that one of the interviewers thought Bootstrap and JS were the same), a written test for a Junior (testing to see if you knew arrays started at 0), then random technical questions which didn't allow me to prove what I could actually do.
So what the fuck are you recruiting for here, a business person, Junior, Mid or Senior developer?!
Total fucking bullshit.
Surely the best way to test a candidate is to let them try to fix a recent bug from your app?
Annoying because I know I can do the job.
Fuck you and your shitty fucking questions.
So is it just a standard thing, now, where interviewers get you to do a coding problem remotely on a shared notepad while they watch you over video chat? For me at least, it is the most uncomfortable style of interview I've experienced. I don't think I'll ever get through one :(4
Spent most of my time studying algorithms, data structures and other theoretical stuffs in college. But tried to do some web development with heavy frontend for course projects and for fun (beautify my cv as well)
Interviewers: wow, you'r experience quite focused on frontend and graphics
Me: (poker face…)2
I might be wrong but all the interviewers I’ve had lately have been duds and didn’t know how to interview
Like. I can’t tell if I sucked or they had no personality and energy for me to work off of
This not a rant, but I want to ask you some advice from you the community.
Before that I want to tell you about me. I have an invisible handicap. I'm half-deaf. I have some moderately severe loss between ~500 - 3000 Hz. To give you some idea, its in the range of clock ticking, whispering, piano notes, pronounced letters (m, n, p, h, g, ch and sh sounds), leaves crushing or waving in the wind.
I use hearing aids, however I can't always count on those because if it's too loud (ex: airplane flying over the building), I can't hear the voices that are speaking in that moment. Or sometimes the tubes where the augmented sounds are passing to my ear are repleted because of humidity. So I don't hear 100% better but rather in the range of ~70 - 80%.
I'm going to need to do an internship next year to finish my studies. Since I will take interviews, I want to ask you if I should mention those details to my interviewer or keep it very simple and tell him that I use hearing aids?
I ask you this because I know people with hearing aids had problems to find a workplace because the interviewers feared the "unknown". Some needed to sign up for help for handicapped people to receive a workplace. For them it is a downside because they are tagged as "handicapped" in society.
I know here are some interviewers and I wanted to know some advice from them as well from you guys of the community.
If you want to know more about hearing loss, feel free to ask questions.3
What's wrong with interviewers who never call or send an email?
It's not like it was a bad date you want to get out of. It's a fucking interview!!3
So there was this position in our college for part time programming/building a project. Being university students looking for part time work a lot of us applied there.
Finally the person that was selected among all of us was the person who does no work and is completely useless. If you ask her to do something she despite taking a long time doesn't produce any output.
So my question is what did the interviewers see in her that they selected her despite multiple way better people applying.4
For a class we had to get an internship, the interviewers where quite enthousiastic. "So, when can you guys let us know whether you would like to join us?"
Why the fuck do I have to complete situational strength tests related to commercial shit when I'm applying for a Software Developer role? What the fuck is up with companies nowadays? This is why it's a good idea to be your own boss and either do freelance or make your own brand, because these interviewers know jack shit about technology and software and you cannot express your passion nor your knowledge. I'm sick of how bad the employment process is for software developers who are looking for jobs after graduation.
The following piece of advice will be for those aspiring for an IT service desk position:
When companies are looking to hire service desk agents, they're primarily looking for socially skilled people with strong communicative skills, rather than primarily technically skilled people. When I first joined the IT world, I went on different interviews for that position and across all of them there was one truth: all the interviewers were eyeballs-focused on my social and communication skills and a mere thin layer of technical skills was required (depending on how technical the service desk). In fact, I immediately got aggressively dismissed twice for two of those when I filled in a Myers-Briggs personality test according to my Sheldon-type personality (selfish, condescending etc). Conversely, when I applied for a new position and I faked that test into answering everything focused positively on the social aspect, I was an immediate top candidate.
Here's a definition from the ITIL Foundation course, chapter Service Management: Because of how lateral the function of the service desk has become today (not only used to solve technical issues, but also company-wide issues), the most important and valued skills when hiring a service desk agent are fully focused on empathy and soft skills and none of those are technical skills. This is because the service desk has people that are the front window of your company and thus you can't make social mistakes as to protect your company's reputation. That risk has to be minimized and you need the ideal people. The people who in fact solve the technical problems are behind a back-office and they are contacted by the service desk agents.
In the beginning, when I did my first service desk job, I also thought: "Oh, I'm going to have to convince them I'm this technical wizard". In the end I got hired for being able to explain technology in human language and because in the interview I successfully communicated and explained ideas to both the team manager and the CEO, not because I knew what goes on inside a computer. This is a very important distinction.
My friends have also been in service desk positions and ironically they were the most successful when they were empathetic slimeballs (saying: "of course, anything for you" while not meaning it, constantly making jokes), rather than people with integrity (those got fired for telling the customer they were wrong while being unfriendly).
I hope this helps.8
I have attended some interviews and have solved problems related to tree, queue and what not. But after joining bo matter what never worked on any of them as such. The only place I have worked on them is open source. Not really sure why the interviewers go through the process of asking them. And in lots cases as they have just copied these from net they even don't know any alternative answers or understand them. Quite shitty.
Went for an internship interview today
Interviewers= tell us a little about yourself
Me thinking haha I can mention the time I took a 300 level course in my freshman year (have ranted about this) and show them I can take up a challenge = I'm known in my batch for not making smart decisions
Interviewers = sarcastic clap
What the actual fuck,no why why would I even start off like this fucking shit what even am I stupid what even. Great job man great job.3
I’ve seen a lot of Linked In posts lately about interviewers doing tests on candidates. What’s your thoughts on it? A lot of developers are saying they hate them and many feel they would fail under test conditions. I’ve not looked for a new job for years, but wondered how common they are?7
I think here the CS degree/experience just gives you training basically to pass this technical interviews which has been a constant problem because 99% of the work you actually do, you ain't gonna need it. (I don't work at big tech companies but pretty sure it's the same, have to be very Senior and leading a project before you really need to think about this stuff?)
I don't have a CS degree unfortunately, completely self taught, but that experience while "impressive" to interviewers doesn't seem to matter much when do how do you implement a red black tree or quick-sort.
I may know the difference in general but I don't fucking care to remember the details as YAGNI... If rather remember the things I need every day