# So frustrated - damn those interviews!

This topic is 2059 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Need to blow off some steam... Here we go:

I'm the goto guy, been the goto guy my entire professional career. I'm the one they come to when need to solve something - design, bugs, algorithms, whatever you need - I always have the answer. And I'm getting paid a lot to do that, which probably means something.

Then there's interviews. I've done a number in the past year, just because, to keep in shape. And they all sucked. No real reason for that - they ask me questions I should have answered without hesitation, but nothing - blank mind. And whenever the interview ends - I go out and the answer immediately pops in my head.

Last one was 2 days ago. Sucked big time. And now I'm frustrated. The problem is I'm over-confident. I'm used to being the smartest guy in the room, I forget that I actually have to make people who don't know me see that. I'm too smug at interviews, like I'm doing them a favor I'm coming. Not really know why I'm frustrated, given that I'm an idiot.

I have interview for a job I actually want in 2 days, so frustration is bad. And here's why I'm going to own it:

- I never really cared about the other jobs, so didn't really bother with interviews.

- I will not be smug for an interview I actually care about.

- I will not be a smart-ass for an interview I actually care about.

- I'm the goto guy.

Feel much better now...

And BTW, I like the forums here because they make me feel humble. A lot of smart people hanging here, a lot of things to learn. I don't get it in my day job anymore.

[EDIT] Just re-read it. Hope I'm not coming off as an ass. I'm really not.

[EDIT2] re-re-reading it, that's the problem. I'm not going to own the interview just because. I need to prepare, do some exercise, sleep-well the night before, come focused. I knew you guys would help

Edited by N.I.B.

##### Share on other sites

Can you give an example of a question you were asked?

##### Share on other sites

Here's a bunch:

- Define an architecture for immediate messaging system that minimizes server load (I actually think my solution was better than the answer suggested by the interviewer).

- Reverse the order of a singly-linked-list. Easy, expect when I they asked me to write the code my brain decided to shut-down. Completely shut-down.

- Efficient algorithm for updating file-indexing service when files change. I actually got that right pretty fast.

##### Share on other sites

goto is evil

goto is nostalgic. I started learning BASIC on Amstrad CPC64 when I was 8 - the most beautiful spaghetti code I ever saw.

##### Share on other sites

- Reverse the order of a singly-linked-list. Easy, expect when I they asked me to write the code my brain decided to shut-down. Completely shut-down.

The only one I could answer. My solution requires a printer and a mirror.

##### Share on other sites

- Reverse the order of a singly-linked-list. Easy, expect when I they asked me to write the code my brain decided to shut-down. Completely shut-down.

The only one I could answer. My solution requires a printer and a mirror.

SNode* pPrev = NULL;
SNode* pCurr = pRoot;
while(pCurr)
{
SNode* pNext = pCurr->pNext;
pCurr->pNext = pPrev;
pPrev = pCurr;
pCurr = pNext;
}
pRoot = pPrev;


10 lines of code. I knew the algorithm, had a writers block when needed to write it down.

##### Share on other sites
I'm guessing from context that these interviews are job interviews (very different from what I initially assumed).
Since this is about job interviews, I think it would be a useful addition to the Job Advice forum (so I'm moving this there).

##### Share on other sites

You seem to be finally realizing that job interviewing in the IT industry is a completely separate skill. Totally unrelated to the technical prowess you possess.

Since it's a skill, this means you can get better at it. You just need to work on it (as on any other skill).

As you already figured out, sitting in your chair at work, writing the code in your IDE, under the daily routine (coffee + music) is anything but even remotely comparable to the stress of having to "code" while standing in front of the person you never saw before, on the paperboard using a highlighter (or pen&paper).

It's great you realized something is wrong and it's even better that you figured it out while still having the old job. Trust me, you don't want to find that out when you're out of the job and doing the interviews (and waiting days/weeks till they schedule another round).

Now, I recommend doing a search and spending an evening or two with researching for what kind of questions are usually given at interviews (or just grab a book - plenty of those out there).

Then, grab a piece of paper and a pencil, and start coding on a paper. No IDE. No google. No music and no coffee.

This may take anywhere between 10-40 hrs of raw hand-writing, but you will get better at it.

What was the last time you spent a full hour writing just using your hand ? I found out my hand hurts like hell. Better to be prepared for things like that, than figuring them out when being stressed out at the IW.

Now, coding on paper is still way, way easier than on a big board with the highlighter. On a paper, you see easily 20-50 lines of a code. Not so much on a big board, where you gotta use bigger letters so that the interviewer can see it from distance.

There's no delete / enter on a paper with a highlighter.  It truly sucks doing a typo during an interview, but you just gotta embrace the feeling and go with it, completely ignoring it.

To improve the skill further, there must be someone in your room, could be from your family or a friend. It's ok they don't know sh*t about IT. During an interview, you will be given lots of "why" questions  anyway, so it's best to be prepared to be constantly interrupted, while you're trying to figure out how to insert a damn line between two lines already written on the big board.

10 months ago, when I was changing jobs, I did insane amount of interviewing (it's practically like two full-time jobs) and had a chance to really up the skills of interviewing, since some companies had 5-8 rounds of technical phone/online/on-site interviews.

In this world, no one really cares if you have the skills. But can you sell the skills you don't even have ? That's what really matters, regardless how crazy it sounds at first...

##### Share on other sites

Whenever asked to talk through your thought process......DON'T.  Solve the problem quickly and then go over and expalin it.  Much quicker and much more flawless.

• 18
• 29
• 11
• 23
• 16