Archive for December, 2011
There has been a recent discussion on resumes on Twitter and the Midnight DBA blog/show. In January the Colorado Springs SQL User Group will also be hosting SQL Saturday #104 and will have resume writers and mock interviews as part of the activities.
Inspired by this I decided to dust off and update my own resume using some of the tips I’ve heard mentioned.
In this short blog post I’d like to mention some of the things (as someone who has been in a few hiring circumstances) in my immediate disqualification list:
- Misspelling. This is a resume and should have been put together with great forethought and editing. If you misspell something I assume you do not have good attention to detail right off the bat. Use spell check, read, re-read, etc.
- Don’t make it more than two pages. I don’t have time to wade through fifty 10 page resumes. If you feel like you need more detail put a link to another document I can read online if I’m interested. This is really an exercise in how well you distill information.
- Don’t list obvious skills. If you can write code I’m pretty sure you know or can figure out how to use Microsoft Word.
- It’s beneficial to you to tailor your resume towards the job. In other words don’t list your experience in construction, but if you do, show how it might be relevant. This is not required, but shows initiative and may get you put into the consideration pile.
- Be consistent in font/style. ‘Nuf said.
- Follow up with a phone call or e-mail to make sure I received your application. This insures I know your name. It may even give you a second read.
- Show up 15 minutes early. This not only looks good, but also gives you time if you can’t find a place to park (speaking from experience).
- Dress up. Now I know some place will penalize you for this (game design firms for one), but my opinion is that this thinking is flawed. It’s an interview. It shouldn’t matter if the dress code lets you go pants-less in your cubicle. This, to me, says that I took the time to look good and make a good impression.
- Be personable but to the point. Try not to stray off topic.
- It’s ok to be nervous, some of us are for you (sometimes I feel like I’m more nervous that the interviewee is).
- Be prepared. Something that is helpful for me is to have a 1 page cheat sheet that I can take notes with. This cheat sheet contains pointers to the questions I might anticipate (“where do you see yourself in 5 years”, “why do you want this job”, “what was your most difficult customer experience and how did you handle it”, “do you have any questions for us”, etc). Nobody is going to see your sheet, plus you can take notes as well.
There are tons more tips out there. These are just the ones I’ve compiled over the years.
Hopefully these tips help you land that next fat salary.
Share and Enjoy
Wanted to put this post out there in hopes of helping the unfortunate soul who may be trying to get this working as well.
Disclaimer: this solution has only been tested with the latest version of Nginx and OWA 2007. Your mileage may vary.
First off I would like to reference a very good example of getting Nginx set up with talking to OWA via a reverse proxy here: http://planetit.ws/linux/debian/configuring-nginx-based-reverse-proxy-for-owa.html
This example works perfectly for most mobile devices (Android, WebOS, etc). However, iPhones and iPads do NOT cooperate and simply fail their requests to the back-end.
After much searching apparently the problem is iOS devices do not work well (or at all) with GZip compression. To turn this off simply add the following to your nginx.conf and it will disable it upstream (the empty string disables):
proxy_set_header Accept-Encoding “”;
Once you restart Nginx with this added your iOS devices should work with ActiveSync with no issues.
Share and Enjoy