Leonard was a very promising C ++ coder, three years out of college, with a solid career path
and an impressive skill set. He proved on the phone screen that he was above the technological medium.
That's just why he was invited to an interview. We needed a safe C ++ to work
a centerpiece that was interconnected cracking the coding interview pdf 8th edition with our database, and Leonard seemed to fit in for sure.
But once we started talking to him, things fell apart. He spent most of the
an interview criticizing every tool and platform that we question. We use SQL Server
like our database? Puhleease. We were planning to move to Oracle soon, right? What is that?
Did our team use Tool A to do all of our coding? Unacceptable. Used Tool B and Tool one
B, and after they hired it, we all had to switch to tool B. And we had to switch to Java,
because I really wanted to work with Java, despite having 75 percent of the code
would have to be rewritten. We would like to thank you later. And oh, by the way, I wouldn't
there are no meetings before ten.
That was not the case
the ideas were bad; in fact, he was "technically" right on many things, and his (strong) opinion
there were solid facts and a good reason for all the ions (except the ten o'clock thing - we
I think he was just doing a "power play."
He was not going to play well with the others: he would have toxic kryptonite for the chemical team.
istry. In fact, he managed to convict two members of the team during the forty-five minutes
for your interview. Leonard also made the mistake of assuming the purity code and algorithm
Beauty has always been more important than a business deadline.
In real life, there are always commitments to make and knowing how to work with them.
Business analysts are as important as knowing how to reactivate a code blob. Ma Leon¬
high wouldn't be caught with other IT people, certainly not with
together with businessmen. Maybe you can stop hiring Leonard if he's one of those
the top ten codes of the world (it wasn't). But it was the classic example of failure of "
Do you have a beer with this guy? "proof.
a mid-level Java developer with a strong history of middleware and JSP working on it
restart. Because she was local, we invited her for interviews without a phone screen. When
We started asking her questions, it quickly became clear that Trisha was a small woman
words. Their responses were brief and often consisted of "yes / no" answers, even to questions.
It was meant to start a dialogue. When it started to open, she still wasn't sure it was
really talking. I saw her lips move, and heard whispering sounds coming out, but she didn't
anything that sounded like English.
I'm not sure if Trisha was nervous or just shy, but either way, I had to ask her a question often.
repeating itself. Now I was the one getting nervous! I didn't want to be the type to "destroy"
the interview, so I withdrew my questions. The other people in the room and I exchanged
restless looks. We feel like we're on an episode of Seinfeld. It was almost impossible to be scarce
Trisha stood up and when she spoke, her speech patterns stopped, uncertain, confused.
made us feel more like code breakers than interviewers. I am not exaggerating when I say that I am
did not understand an answer she gave during the interview.
Not many know it, alone. You will be talking to other technicians,
and will speak to customers, sales reps, and Betty from Marketing. Your
Eventually you will write something, be it documentation, a project plan, or a need.
ment document. The word processor can correct your spelling, but it will not correct yours.
lousy writing. The ability to express thoughts and ideas, clearly and concisely.
an invaluable skill that employers seek.
The same goes for verbal communication. I used to work with a collaborator who did the
the length of each meeting I was in, because I couldn't answer a question in less than ten
minutes. "Hey Dennis, what time is it?" " Well that's interesting, because I've only happened
I thought I would read an article on cesium clocks and skip seconds and the history of
Gregorian calendar and ... "