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

Python at Mozy.com

At my day job, I write code for a company called Berkeley Data Systems. (They found me through this blog, actually. It's been a good place to work.) Our first product is free online backup at mozy.com . Our second beta release was yesterday; the obvious problems have been fixed, so I feel reasonably good about blogging about it. Our back end, which is the most algorithmically complex part -- as opposed to fighting-Microsoft-APIs complex, as we have to in our desktop client -- is 90% in python with one C extension for speed. We (well, they, since I wasn't at the company at that point) initially chose Python for speed of development, and it's definitely fulfilled that expectation. (It's also lived up to its reputation for readability, in that the Python code has had 3 different developers -- in serial -- with very quick ramp-ups in each case. Python's succinctness and and one-obvious-way-to-do-it philosophy played a big part in this.) If you try it out, pleas...

A week of Windows Subsystem for Linux

I first experimented with WSL2 as a daily development environment two years ago. Things were still pretty rough around the edges, especially with JetBrains' IDEs, and I ended up buying a dedicated Linux workstation so I wouldn't have to deal with the pain.  Unfortunately, the Linux box developed a heat management problem, and simultaneously I found myself needing a beefier GPU than it had for working on multi-vector encoding , so I decided to give WSL2 another try. Here's some of the highlights and lowlights. TLDR, it's working well enough that I'm probably going to continue using it as my primary development machine going forward. The Good NVIDIA CUDA drivers just work. I was blown away that I ran conda install cuda -c nvidia and it worked the first try. No farting around with Linux kernel header versions or arcane errors from nvidia-smi. It just worked, including with PyTorch. JetBrains products work a lot better now in remote development mod...

A review of 6 Python IDEs

(March 2006: you may also be interested the updated review I did for PyCon -- http://spyced.blogspot.com/2006/02/pycon-python-ide-review.html .) For September's meeting, the Utah Python User Group hosted an IDE shootout. 5 presenters reviewed 6 IDEs: PyDev 0.9.8.1 Eric3 3.7.1 Boa Constructor 0.4.4 BlackAdder 1.1 Komodo 3.1 Wing IDE 2.0.3 (The windows version was tested for all but Eric3, which was tested on Linux. Eric3 is based on Qt, which basically means you can't run it on Windows unless you've shelled out $$$ for a commerical Qt license, since there is no GPL version of Qt for Windows. Yes, there's Qt Free , but that's not exactly production-ready software.) Perhaps the most notable IDEs not included are SPE and DrPython. Alas, nobody had time to review these, but if you're looking for a free IDE perhaps you should include these in your search, because PyDev was the only one of the 3 free ones that we'd consider using. And if you aren...