Skip to main content

What to do: Practical Tips for a job interview

Like I said in a previous post Practical Resume Don'ts, I sometimes have to interview potential candidates for open positions are my job. Here are some tips for that elusive job interview:

  • Don't be afraid to say you don't know. It's better than cooking up wrong answers. Or saying "I can easily google that"
  • Talking about Google, don't use "I can easily google that" as your answer to every question or even to most questions. 
  • Please please don't disparage your current/previous job. It just doesn't look good. 
  • Don't make me an accomplice to you cheating on your timesheet at your current job. One candidate told me he "just left work" and will "go back whenever. Or maybe not even go back at all". 
  • Don't ask me how you did, whether you'll be hired or what your pay will be. For one, I don't control all that. And if I did, I wouldn't even tell you. So why even ask?
  • No begging!
  • Do ask questions about the company, what I work on. Doesn't matter if you don't care about the answer or if you've already done your research, it still helps to ask questions.
  • Do speak English. No offense. English is not my first language either but if I can't understand you I simply can't recommend that you be hired. Just can't do it. 
  • Know your stuff. Nothing, absolutely nothing, counts more than this.

Comments

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply