Help:Technical Interview

[artsfartsyjanet]

Hello. =) now that i got your attention...

I was selected as a candidate to interview for an application development position. For those of you have been through a technical interview, what kind of questions did you encounter? What kinds of questions should I possibly expect? A friend of mine teaches ASP coding and what not, and recommended reading Ace the Technical Interview. While I'm searching that book at Borders, I want your input as to how I should prepare for it.

[tommyhtown]

What is the job description? What kind of technology your prospective employer are using?

[kboy75]

anything that you put on your resume is something they will potentially ask you about. if the job description and your skill set match up expect questions. on those skills. they may ask you to debug some code. they may ask you about common programming practices or known issues. it could be anything. i've had everything from them printing out some C++/Java functions and handing it to me on paper, and asking me to tell them what is wrong... to asking me what i thought the most important phase in the whole development cycle was... to asking me to describe to them "exactly" what happens when you compile a code... to being asked to write (on paper) a function that does blah blah blah... to writing a join in SQL... etc, etc... it usually involves a piece of paper.

there really is no "shortcut". you either know it or you don't.

however... even if you don't know the exact answer, what i usually do is use some paper or talk-out-loud during my problem solving so that they know that I at least kind of know what direction to go in. then they at least get to know my thought process. not everyone remembers syntax off the top of their head, so it's understandable. the more you talk about what you do know, the better chance they will have more confidence in you and your problem solving abilities.

good luck.

[kitty]

I dunno if this will help but when I interviewed for my lab tech position, they just busted out with "what's PCR... can you draw a diagram for me?"... I think the only thing you can do is not lie or try to BS them on your resume, but just ask how much you're supposed to know beforehand and say how comfortable you feel with giving an answer to their questions. "Like, I debugged C++ code in sophomore year, so I feel a little rusty, but looking at it right now... it looks like blahblahblah"

[SunWuKong]

i'd just review the basics. anything beyond that, the scope is too large to prepare yourself for anyway.

shameless bragging: for the job that i had in HK, because i had to fly there for the final interview and they had to make a decision, they needed to really make sure they want to hire me. so they sat me down for 3 or 4 hours and had me write a chat program, server and client. they didn't expect me to actually finish it, but i did. :)

[achtungbaby]

To piggyback on what SWK said: review the basics and act like you know what you're talking about.

[artsfartsyjanet]

ok i will be swamped in books and old coursework for the next 10 days reviewing all the basics. mock interviews are in store for me on monday. *shrug* this is war.

[golden_buns]

ok i will be swamped in books and old coursework for the next 10 days reviewing all the basics. mock interviews are in store for me on monday. *shrug* this is war.


It depends on the type of position they're looking for and on what you are expected to perform at work. I wouldn't rely so much on mock interview books because this is up to the interviewer, sometimes it's technical questions sometimes it's just personal questions. Like I said, it's depending on what they're looking for.

Like everyone says; review the basics and be try to act confident showinng that you know what you're saying but don't bluff too much, cuz they might question you more on things that you're not too sure about.


I think that you might have some extra points if the interviewer is a guy, cuz usually male interviewers in the computer industry go easy on female candidates, especially if they're cute.
maybe that's why most of the girls I knew from CS ended up getting a job right after college, whereas most of the guys I knew from CS are still jobless

[SunWuKong]

To piggyback on what SWK said: review the basics and act like you know what you're talking about.

yeah it's all about selling yourself. either act like you know what you're talking about or just be up front and say you've started learning about whatever the interviewer asked but you have no clue about. gleam what information you can from the things that the interviewer says and use it in the interview itself. it's all about selling.

[artsfartsyjanet]

I'm open to as many suggestions as possible and that includes what books have to say. Reading an entire book is not feasible for me, but I don't think it hurts to scan what the book suggests. One book is enough for me considering the time I have. I will probably just go to borders for a few hours to look over the book. A friend of mine is going to give me a mock interview (actually Wednesday now). I really don't have to work on personal questions b/c that is a cinch for me. it's just selling myself as someone who knows at least the basics of what I've learned that will pull me through. I'm not sure exactly who my interviewer is, but I think it's the same person who emailed me, and she's Indian. =) I know a lot about Indian schtuff through all my Indian friends. lol....

It depends on the type of position they're looking for and on what you are expected to perform at work. I wouldn't rely so much on mock interview books because this is up to the interviewer, sometimes it's technical questions sometimes it's just personal questions. Like I said, it's depending on what they're looking for.

Like everyone says; review the basics and be try to act confident showinng that you know what you're saying but don't bluff too much, cuz they might question you more on things that you're not too sure about.


I think that you might have some extra points if the interviewer is a guy, cuz usually male interviewers in the computer industry go easy on female candidates, especially if they're cute.
maybe that's why most of the girls I knew from CS ended up getting a job right after college, whereas most of the guys I knew from CS are still jobless

[achtungbaby]

A friend of mine is going to give me a mock interview (actually Wednesday now).That's a good idea. One thing I've noticed is that often times tech people will disdain the interview process, not taking it seriously enough and hoping to slide through. You should be able to answer the basics like you're talking about your favorite subject. That way, once your message is down pat, you can focus on delivery.

[SunWuKong]

oh and act like you're interested in what the company is doing, even if what they're doing is boring as hell. ask them some questions about it. unless the position you're applying for is highly specialised, it's understood that when a programmer comes in on a project, there will be a few weeks of a learning curb, so usually they'd only make sure that you know the basics, especially if you're not very experienced.

[AliBabaIncorporated]

The best thing to do is ask as many clarifying questions as you can think of before even attempting the problem. (If it's a programming or "solve this" kind of thing. Asking clarifying questions about basic technical stuff like "what is a stack" or "what is polymorphism" will just make you look incompetent.) It shows that when you're actually on the job, you won't make assumptions about client requirements and give them something they didn't want, but will work with them to make sure they get exactly what they need, even if they're not quite sure themselves.

Also, if your interviewer is some HR dweeb who got his technical questions from a script and only knows one right answer and doesn't really understand how to do the problem himself, asking him a clarifying question he doesn't know how to answer gives you the opportunity to watch him shift around in his chair uncomfortably, stammer, and then maybe pick a different question.

[SunWuKong]

Also, if your interviewer is some HR dweeb who got his technical questions from a script and only knows one right answer and doesn't really understand how to do the problem himself, asking him a clarifying question he doesn't know how to answer gives you the opportunity to watch him shift around in his chair uncomfortably, stammer, and then maybe pick a different question.

one of my friends was asked by a recruiter, "do you know the C?" and my friend replied, "yeah. i know the C."

[achtungbaby]

one of my friends was asked by a recruiter, "do you know the C?" and my friend replied, "yeah. i know the C."Was the recruiter a FOB or something? Like, "Are you the gay?"

[SunWuKong]

Was the recruiter a FOB or something? Like, "Are you the gay?"

hahhah i don't know. but my friend is white, and he didn't mention that the recruiter has any accents.

[artsfartsyjanet]

All of your suggestions help a lot. Thanks. Here is the job description. Maybe that will help you guys understand what I might expect at an interview.

This position is responsible for performing analysis, design, development, testing, and support of software. This includes development of software analysis skills necessary for the definition of deliverables, estimation of costs, and creation of timelines.

The candidate needs to possess adequate technical expertise necessary to learn to develop software to meet business and technical requirements. Requires use of programming languages for new development and/or support of IT applications.

Must have appropriate communication skills necessary to successfully interact with software users and other teams. This person will learn how to act as a liaison between the technical and business communities documenting the requirements necessary for software development.

[artsfartsyjanet]

I had the interview on the 23rd. The interviewer is an IT Lead for one of the departments in the company. It went well. I made her laugh a few times, but I can't remember what I said that made her laugh.... Anyway, she invited me back to the "Blitz" interview on the 3rd of November. Don't know why it's called a blitz. She emailed me and told me that she enjoyed the interview. Now, for the next interview, I believe it will be technical because two project managers or two people from one of the departments will be interviewing me. The last interview was behavioral. eeek. =)

[steakandrice]

Sup....I work for a software company...

What kinda applications? web-based, client/server, just regular apps?
What languages will they use? C, C++, Java, VB?

Typically they ask you what languages you know...what you are most comfortable.....if this is a decent interview they will ask you some basic programming questions....like write me a function, or class file, what is a pointer, what does pass by reference/value mean.....is java 0 or 1 based....

pretty much programming languages all share the same common ground just different syntax....so if you're a good programmer you should have no problem..

I like to bring in old school project with pictures and code....and to show them some of my past work. The thing in interview is to make yourself stand out from all the other applicants....you should really have everything down...be confident....and prove to them that you are a SUPER application developing P.I.M.P

hahahaha...I feel so GEEKY NOW!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[artsfartsyjanet]

Yeah, i'm brushing up on the basics in all of my classes and compiling deliverables I've done in all of them to present if they ask. I know java the most, but i'm learning more about asp and php. it's an application development position. I got a packet in the mail about the interview. they say it's behavioral and i will be interviewed by 3-5 people who are project managers, staffing specialists, and who knows.... Here is more information about the company if you're bored and interested. hehe Monsanto (http://monsanto.com/monsanto/layout/default.asp)

Here's a general description of the job:
The candidate needs to possess adequate technical expertise necessary to learn to develop software to meet business and technical requirements. Requires use of programming languages for new development and/or support of IT applications.

Must have appropriate communication skills necessary to successfully interact with software users and other teams. This person will learn how to act as a liaison between the technical and business communities providing the requirements necessary for software development.

Here are the general responsibilities, but it depends which department I'll be working.

This position is responsible for providing analysis, design and development of software. This includes development of software analysis skills necessary for the estimation of deliverables, costs, and timelines.

[artsfartsyjanet]

I GOT THE JOB!!!!!!!! Thanks everyone for all of your insights. It certainly helped throughout this grueling process. My Lead sounds like he's from Louisiana or North/South Carolina.... nice guy at voice-value. =) I will be in a team of 7 people working in asset management. I will also be using oracle, ms access, and whatever the heck else they do. i'll get a packet detailing all of the information. great,i have to pee in a cup too. =)

[artsfartsyjanet]

Was the recruiter a FOB or something? Like, "Are you the gay?"

hahahaahha

[tommyhtown]

Congrat! Way to go girl!