tag:blogger.com,1999:blog-9109010163420737861.post9121880152018503126..comments2023-09-17T01:22:52.860-07:00Comments on An Obsession With Programming: Hiring Online EngineersDerrickhttp://www.blogger.com/profile/05974720556627635894noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-9109010163420737861.post-45477493307474002572011-08-25T08:02:46.288-07:002011-08-25T08:02:46.288-07:00Hi Derek,
We worked together in the past. I was o...Hi Derek,<br /><br />We worked together in the past. I was one of the first guiders. Your post is very timely for my own experience. I recently went up for an interview and could have used many of these lessons. It is was a programmer/analyst opportunity to lead a tough integration project for a medium-size start up.<br /><br />What I did Right:<br /><br />1. I prepared well in terms of esthetics. Crisp suit leather portfolio, fancy resume paper, plenty of things in to show: code example, documentation example, 2 letters of reference. By the way what is your view on ties, I been going open color.<br /><br />2. I researched the company and the people I was going to be talking to using the "About Us" page of the company's website. I got a sense for the culture using their facebook page and twitter feed.<br /><br />What I did Wrong:<br /><br />1. I did not brush up on all the technical terms I put on my resume. Although I did not lie, that is just stupid, I currently hold a higher level organizational position that deals with these things on a more conceptual level. Questions to keep it specific from a "make him cry" programmer did catch me off guard and showed the dust on my technical knowledge.<br /><br />2. I started many of my answers in a self depreciating manner, such as "Although I do not have a full-time developers understanding of [a technical area in question] I can tell you what I do know [dusty answer]". I have done this before professionally and been made aware that it is not the best way to communicate. Perhaps my answer is exactly what they were looking for but I just put a dark shadow on it.<br /><br />3. Was I actually Overly prepared in terms of esthetic polish? Is there such a thing? For example my brother refuses to wear a suit to an interview but I always do. This time I turned it up a notch with more polish. Was it too much for that type of company, an aggressive start up?<br /><br />4. I actually got the interview using nothing but a resume generated from my LinkedIn profile. I did bring a classic format (2 pages, [cringe]) to the meeting but I felt it was a weird way to start each one of three conversations.<br /><br />5. I got a late start and had to run to BART and stress out. I was lucky and got there on time though.<br /><br />6. I forgot a writing utensil due to above. <br /><br />7. I was shy to keep a solid eye contact. Problem I have in general. How do I deal with it? I don't want to stare them down in arrogance ether.<br /><br />8. I was very clear how happy I am at my current position. Perhaps this is a mistake... <br /><br />speaking of which, I better get ready and head out to a job that IS willing to pay me. Hoping to hear back ether way from the place I interviewed with. Will update thread if I hear back. I don't expect it as I feel that I bombed hard on the technical aspects of the interview. However it was great experience to freshen up for the next interview.<br /><br />Thank you for the post, I hope to run into you at a Farmer's Market again sometime.<br /><br />-An Appreciative Past ColleagueAnonymousnoreply@blogger.com