I've had a total of seven formal jobs in my life (not counting occasional contract-based security or under the table bouncing). This is a bit long so I'm labeling the sections if you want to skip bits:
My actual interview history:
The first was at an office supply company working in the computer department. I was 16 at the time and was referred by an employee I had met, and I don't remember the interview being particularly stressful or painful. I just went in there, talked to the store manager, we liked each other and he thought that I knew enough about the topic area, and I got the job. I worked there part time for two years during high school.
My next job was an easy one to get, because it was a "mom and pop" used computer shop where the owner had met me while I shopped in his store. I took that job after high school and after the office supply store and worked there for almost exactly a year. The owner didn't want to worry about the day to day operation of the story so after I'd been there for a while I basically ran the place from open to close on the days that I worked. It was a pretty cool job for an 18 year old, but over the course of the year I watched our margins slowly erode as the industry changed and PC compatible parts got cheaper and cheaper, so when the owner offered me a minority partnership in the business I declined and looked for employment elsewhere.
I joined another "mom and pop" shop run by some buddies of mine from high school. It was fun, more innovative, and I was working with friends and people closer to my own age, but through a series of missteps they eventually ran that place into the ground hard and I had to look for a new job. No real formal interview here.
I took a job at Egghead Software back when they had brick and mortar stores. I don't remember the interview being particularly stressful but Egghead wasn't exactly "high stakes". I was there for less than a year before I had to leave for a family emergency.
Fast forward a year or two later and I took a new job at a different "mom and pop". Again, I was referred by work friends so they had an idea of my work history and who I was. I worked there for years before they eventually decided to fold the business.
I don't remember the exact timeline at this point, but I remember there were exactly two jobs that I actually got to the interview process for that I didn't get. The first was to work at IBM as a contractor. I took a technical aptitude test which I did okay on but they pointed out a couple questions I missed. This was back in the DOS and Windows 3.1 days, and I pointed out that there were actually multiple correct answers to a few of the questions because of how you could use the utilities listed (Format, Fdisk, Scandisk, etc) and that some of the questions were just simple "UI memorization" which weren't really a great test of knowledge. They were happy with the results and subsequent conversation and said that I was their first choice to hire but unfortunately IBM just went on a hiring freeze so there were no positions available at that time.
The second interview where I didn't get the job was for a different local "mom and pop" shop. I didn't know anyone there, but I needed a job and it was close to my house. I had a corporate contact from my previous job but I knew from past work that their office was 45 to an hour from my house, so it wasn't exactly my first choice. I took the interview, but the manager seemed very disorganized. Even though he had given me the interview time, he got the resumes mixed up and thought I was a different applicant. We cleared it up and he said that I should come back and try a "trail" day of work to see how I did. I showed up the next week with my toolbag in hand to find him puzzled because he had apparently forgotten he told me to come back and he explained that they decided to fill the technician position internally with one of their sales people. This was even more annoying than the last situation, but I politey thanked him for his time and left. This company folded less than a year later. No real surprise there.
Eventually, I called the corporate contact I had and asked him if he still had a job for me. He was thrilled that I called and I came out to the office for an interview/work day. Basically they were just confirming that their impression of me from when I worked for them as a contractor was still accurate and they hired me to start the following week. I worked there for four years before a friend from my previous job invited me to join him at a premier consulting firm doing large scale corporate IT consulting. I decided to interview with this new company because I was starting to feel pretty unfulfilled at my current job. I basically ran IT for this company for the whole state, and the place was a mess when I got there. But after two years I had things in pretty good shape, so I spent most of my days doing very little besides desktop support. I did IT in a non-IT company so I just supported the people who did what the company did. I didn't help the company directly.
So I took the interview at this new company, which twelve years later is still where I work. Even though this was another referral, that doesn't get you much besides the opportunity to interview to prove your chops because this company is highly technical. I took two(?) technical phone interviews to verify my ability, which at the time focused on stuff like OSI model, DNS, DHCP, networking/IP, Windows troubleshooting/administration, etc. This was followed by a series of in-person interviews with two directors for the company. They asked me questions about how I would deal with architectural questions for large scale enterprises, which was something I didn't have much experience with yet but I did my best. For the technical screenings they were looking to get an idea of how good I was at what I did. For the in person interviews, they were looking for how I could interact with people and for the larger questions they didn't figure I'd know the answer, but they wanted to see how I tried to figure out the answer. To see if I'd approach the situation I had little experience with logically and with confidence, even if I didn't yet have the tools to get to the answer myself.
My actual interview advice based on that history and experience:
These days I'm on the other side of that interview process and I can tell you what we/I look for. For technical chops, don't tell me you're an expert in something that you aren't. Be honest about your abilities, because if the interviewer knows what they are doing you won't be able to bullshit them and even if you could, getting your foot in the door into a position that you aren't qualified for won't really do you any good. When I ask people questions, I don't grill them for getting something wrong. I'll try to "lead them to water" to see if they have the knowledge but maybe didn't understand the question. I'm not trying to trip them up on technical minutia, I'm trying to gauge what they actually know.
Some of the things that are important for interviews would be to to present yourself well. Be formal, but relate-able. Part of an interview is to see not only if you can do the job well but if you'd be a good fit for where you are going work. You need to be able to articulate yourself well. This is critically important. If you can't string a coherent sentence together because of language skills or nerves, that's a big problem because even if you are the best candidate in the world if you can't show people that then nobody will ever know. Remember, at the end of the day it's still just a conversation with another human being. Don't psyche yourself out over the fact that it's an interview.
Honestly, I could even make a "Matrix" analogy with the "There is no spoon" bit. The way I always explained that part to people was I'd ask them to think of a balance beam. Anyone with even a bit of coordination can probably walk across a 6" balance beam that's a foot off the ground. It's pretty easy for most. Now take that same balance beam and put it 50' above concrete. Could you walk across it so easily then? Assuming no modifiers like wind, the answer (whether you believe it or not) is "yes". The task is no more difficult, the beam is the same width as it was, but you psyche yourself out because the stakes are higher. If you believe that it's harder, then it actually becomes harder. You can to truly understand and believe that the task is no harder or easier than it was before. It's the same with an interview. At the end of the day, it's a conversation with another human being. If you're qualified and they like you, you'll get it, but worrying like crazy about that then you only make it harder on yourself. A good interviewer can see through bullshit. I can't tell you the number of phone interviews where I rejected the candidate because it was obvious that they were Googling answers as we spoke.
-Byshop
Log in to comment