Skip to main content

On applying for jobs

A friend asks,
If [I see a] job I could do, even though I don't meet the stated requirements, should I apply anyway?
Short answer: yes.

Longer answer: companies are all over the map here, although in general the less layers of bureaucracy there are between the team that the candidate will work with and the hiring process, the more likely the list of requirements is to be actual requirements.

How can you tell?

HR paper pushers like to think in terms of checklists because that lets them go through hundreds of resumes without any real understanding of the position, so they write ads like this one -- lots of really specific "5+ years of X," not much about what the position actually involves.

But if it's the team lead himself writing the description, which you will see at smaller companies, then you get much more about what the position involves and less checklist items, because the lead is comfortable determining competence based on skill instead of pattern matching. For a software development position, I don't care if you have a degree in CS if you can code. (Open-source contributions are a better signal for ability and passion than a degree, anyway.) My team has people with no degree, to people with PhDs.

Even when dealing with large companies, you have to factor in that people are terrible at distinguishing "want" from "need." A lot of "requirements" are really "nice-to-haves." It can be tough to tell the difference, but the better idea you have of what the job actually involves, the better you can tell which are hard requirements.

For instance: without knowing anything else about a position, my guess is that "native French speaker" really would be a hard requirement. That's not the sort of thing people tend to put down on a whim. But even then, there are shades of grey. For instance, if I were looking for a job and found a "distributed databases developer position, must know Java, be familiar with open source and be a native French speaker" then I might see if they'd give me a pass on the last part because I'm a really good fit for the rest -- and I know they're unlikely to find a lot of candidates with an exact match.

In short, you have little to lose by trying, but don't just shotgun out resumes; include a cover letter that highlights the best matches from your experience to what they are looking for. Follow up with the hiring manager if possible to ask (a) "I sent in my resume a few days ago, and I wanted to see where you are in the hiring process for this position," and if they reply that they got it but you're not a good fit, ask (b) what specifically they were looking for, so you can flesh out your intuition that much more for next time.

Good luck!

Comments

1. Do your research
Knowing as much as possible before the interview about the company is very important. It’s not enough just to study the company’s website. Gather information from various open sources, use the search on the Internet and vivsit company website. You can also find people who work or have worked in this organization and clarify their details. Your awareness will play into your hands during the interview and will make an impression.

2. Be sure to get ready
80% of success in an interview depends on preparation. Prepare detailed answers with examples of the three main questions at the interview: Can you do this job? Will you like your work? Can we work together?

3. Examine the position
You must accurately represent and understand the essence of the position you are applying for. Get ready for the “Tell us about yourself” question so that your story matches the vacant place as closely as possible.

4. Prove your competency
To understand what exactly you are suitable for the vacancy, the interviewer must evaluate your competence to perform the necessary tasks. To do this, be prepared to give examples of situations that you have encountered and talk about ways to solve them, describe your skills and experience.

5. Know Your Importance
You must not only know why you need this work, but also know why you need this work. And, of course, you should bring this to the interviewer.

6. Rehearse the answers
Carefully read the job description and requirements for the candidate. For each requirement, draw up suggested questions and prepare answers for them. Rehearse with yourself, opposite the mirror, or ask a friend to help you.

7. Be honest
There is nothing worse than lying at an interview. Be prepared that you will have to refine the details of the resume and ask complex questions such as “Why did you leave your previous job”. Your answers must be honest. If unpleasant situations have occurred, then it is worth considering in advance how to carefully comment on them.

8. Try to win time
If a question is too complicated or unexpected, do not hesitate to ask for a little time to answer it. You can ask a clarifying question or ask for an example - this will allow you to buy a little time to think things through.

9. Ask questions
Not only the interviewer can ask questions. Be sure to prepare a series of questions that interest you. After all, not only you must approach the company, but the company to you. In addition, it will show you who are interested in work and oriented in the industry.

10. Good conversation ending
Be sure to thank the interviewer for the interview. And do not be afraid to ask about the next steps in the selection for the position.

Popular posts from this blog

PyCon Python IDE review

I presented an IDE review at PyCon last Friday. It was basically a re-review of what I thought were the 3 most promising IDEs from the Utah Python User Group IDE review , to which I added SPE, which was by far the most popular of the ones we left out that time. The versions reviewed are: PyDev 1.0.2 SPE 0.8.2.a Komodo 3.5.2 Wing IDE 2.1 beta 1 I'd intended to base my presentation around a comparison of writing a smallish program in each of the IDEs, but the more I tried to make this not suck, the more I realized it was a losing proposition. Instead, I decided to try to focus on the features in each that most set them apart from the others (both positive and negative); this seemed more likely be useful. (I did a new feature matrix for this review, which is included after my comments. The slides I used are also up, at http://utahpython.org/jellis/pycon-ides.pdf , but aren't very useful absent video of the presentation itself. Hence this post.) PyDev PyDev has g...

Why PHP sucks

(July 8 2005) Apparently I got linked by some PHP sites, and while there were a few well-reasoned comments here I mostly just got people who only knew PHP reacting like I told them their firstborn was ugly. These people tended to give variants on one or more themes: All environments have warts, so PHP is no worse than anything else in this respect I can work around PHP's problems, ergo they are not really problems You aren't experienced enough in PHP to judge it yet As to the first, it is true that PHP is not alone in having warts. However, the lack of qualitative difference does not mean that the quantitative difference is insignificant. Similarly, problems can be worked around, but languages/environments designed by people with more foresight and, to put it bluntly, clue, simply don't make the kind of really boneheaded architecture mistakes that you can't help but run into on a daily baisis in PHP. Finally, as I noted in my original introduction, with PHP, ...

Troubleshooting the ps3 wireless network connection, including error 80130128

My father got a ps3 for Christmas, but ran into some problems getting it on his wireless network. The first one was "connection error 80130128" after configuring it to use DHCP. I couldn't google anything useful about this; just a few other hapless victims asking if anyone had any ideas. Fortunately Dad had his laptop there too and noticed Windows complaining that two machines on the network were both using the same IP. So, over the phone, I walked him through setting up the ps3 with a static address: on his laptop, run -> cmd ipconfig Read the "gateway" ip. Put that into his browser to go to his router's admin page Find the DHCP settings for his router to see what range of IPs it hands out; pick one outside that range Set up the ps3 with that IP, the router IP as primary dns, and an opendns server as secondary This made the connection test happy. But when he tried to go to the playstation store, it gave a DNS error. If he repeated the connection te...