How to interview for a job I do not feel qualified for

Question

I'm currently preparing for a job interview for an entry-level web developer position. Although the job is entry level, I have really only just started learning the skills required for this job, and can not say with confidence that I could immediately start being productive.

I know job interviews are all about convincing the interviewer you are confident you could do the job, but I genuinely feel under-qualified for the position. I'm having a hard time finding advice on how to deal with a situation like this. I want the best chance possible to get the job, but to still give the interviewer a realistic view of my current abilities.

I haven't been able to find any advice on how I should approach an interview like this without embarrassing myself

Edit - I did not apply to this job, I was contacted by a employee of the company who found me through the college I attended.

Answer 1

Since you have got the interview opportunity, go for it and explain your experience level, noting that you know you are not exactly qualified for this position but you are a quick learner.

Most interviews are (at least ones I have been to) about getting a feel about your personality. Especially at entry level jobs, anything can be taught to the right person, if they are willing to learn. But personality can not be changed. If you are a good team player, have easy-going personality, are a go-getter, and somehow remotely aware of the technology that you are interviewing for, you are ahead of the curve compared to the whiz kid, who do not have any social skills or one who screams bloody murder when things don't go his or her way.

So, don't sell yourself short, unless of course, if you are one of those hard-to-deal-with personalities.

Answer 2

Junior web developer here who went through similar situations recently. If there's one thing I can recommend, it's learning the fundamentals of Object Oriented Programming. HTML and CSS are important for visual aspects of Web development, but the truly important stuff happens behind the scenes. I would recommend learning the basics of C# (or Java, or some other OO language, but C# is my favorite for web development), gaining an understanding of the MVC pattern (Model, View, Controller), and maybe learning one or two other patterns.

If you can talk semi-intelligently about a few of these things and have a personality that fits the company culture, I think you'll stand a decent chance at getting the job. Entry-level development jobs typically come with the expectation that you'll be learning a lot on the job, but a basic understanding of the principals of programming is typically expected.

Answer 3

No worries. I got hired as a full-stack web developer for a Ruby on Rails project. I was an experienced developer with many platforms and languages but knew nothing about web development. I didn't know Ruby, Rails, HTML, CSS, the DOM, or Javascript. I read: Programming Ruby, Agile Web Development with Rails, plus O'Reilly books on HTML, CSS, and Javascript. After a couple of weeks I realized that the other developers hadn't read any of those things and were just copy-pasting their way to creating a huge mess.

Answer 4

The proper question is -- How qualified are you to learn the job well and quickly enough to make hiring you a positive experience?

Assume the person who contacted you is not stupid; he has read your resume and still thinks the company should hire you. Why? Try to find out what he sees in you, and emphasize that in the interview.

Maybe the company is not looking for someone who "has written HTML" and "knows CSS". Maybe they are looking for a good employee. I have a really good feeling about this.

Please post here and let us know how it works out.

Answer 5

From my experience entry level/junior developer positions don't expect you to know a great deal and they are more interested in your willingness and ability to learn.

My advice is don't try and bluff your way through the interview, be straight up, if you don't understand or know what they are asking about say just that. Make sure they know you are very able and willing to learn and will learn in your own time if required.

I interviewed for 2 web developer jobs straight out of college and felt the same as you and both interviews they asked me questions I didn't have a clue about and I remember looking completely blank at the interviewers. Eventually I admitted I didn't have a clue what they were talking about. I got offered both jobs.

It will be a steep learning curve if you get it, but don't get disheartened if you don't.

Answer 6

The wrong way to deal with a failed interview is to lose confidence and let it negatively effect your job search.

The right way to deal with a failed interview is to see it as a learning experience. Interviewers asked you their questions for a reason. Those questions cover topics that are important to them and likely important to other interviewers at other companies. During the interview, remember the questions that stumped you. Write them down. Try to remember your answers too. Afterwards, do your research to fill in gaps in your knowledge. This will help you for the next interview.

For instance: suppose that during the interview, the interviewer asked you to implement QuickSort. If you forgot QuickSort, or worse, don't know it at all, make a note to yourself. (You should bring a small notepad with you (with copies of your resume in it)). When you get home, Google "QuickSort". Learn about what problem it solves. Implement it in some language. Actually use it. Hope that the next interviewer asks you about QuickSort, because the sting of the last, failed interview should still be fresh in your mind. (Don't go back to the first interviewer with your new-found knowledge. You won't get a second chance.)

Interviewing is a skill. The best way to get better at interviewing is to interview.

Answer 7

If there is a technical screen, you either pass or you don't. Let that be your guide.

If there isn't a tech screen, you might want to give a hard look at the job. If it is salaried or paid hourly, I would not be too worried about the legitimacy of the job itself, but if you will be paid by assignment, be on the lookout for a scam. Even if the job is legit (and it probably is) if there is no tech screen, how do you know who to learn from? It's good that you know your limitations, but Dunning-Kruger syndrome runs rampant in the software industry and people who do not really know what they are doing are strongly attracted to no-screen shops. What you want from this first job is experience more than money, and when you want experience you want to be careful about working with clowns.

Otherwise, just be candid. There is a lot more to a job than raw programming skills. Most entry level programmers need to learn software engineering tools (source control, build systems, etc) and willingness and ability to learn is critical. Do you work hard? Can you communicate with co-workers, supervisors? Can you manage your own time? Do you show up? Do you have the tiniest iota of common sense? Are you gonna complain about language/tools/platform every time you read some blog post about another system? (The people who think people should be hired on pure programming skills tend to have real problems in those other areas.) It is a real problem for a manager to hire somebody who can't actually get stuff done or who other people hate. Focus on your strengths, all of your strengths.

Answer 8

It is not your job to decide if you are qualified, once the interview is scheduled.

I assume there was a phone interview first, to talk a little about your background (academic and professional) and your experiences.

If they still want to meet with you, it means they think you look like a potential match.

No one wants to lose time, so interviews are usually not given to people obviously under-qualified.

During the interview, be clear about your experiences, what you've learned so far, what you expect you'll have to learn then. Don't try to hide what you don't know, but don't throw it at them. Answer the questions, and don't sell yourself short.

Since you are preparing the interview, learn about the current state of the art, find out what kind of technologies they are using (in terms of architecture, frameworks, methods, tools) and at least know what those are about. As a junior, you are not expected to know everything, but you are expected to know about a lot of things.

Answer 9

I think my experience here can help also shed some light onto this. Currently, I'm a Principle Consultant for a pretty prominent firm. Never had really any formal training aside from 3 OO programming classes in C and JAVA in college. Self taught everything else I know. My first programming job, I wasn't anywhere near qualified for it. So, I simply put in the hours and took some extra time to actually learn the languages and area's I was going to be working in. Jumped around every couple of years and kept up with various Microsoft Certs(their MVC/C# classes/Cert is pretty good). Eventually got up to team lead, and management levels. Now doing software, architecture and cyber security work. So to speak, I was never actually qualified for any of the positions I've held. The phrase "fake it until you make it" is quite true.

With my background aside, the best advice I can give you for interviewing is be prepared. Go into the interview and have the following written down on a pad of paper: 5 Strengths, 5 Weaknesses(this is more a trick question as if you identify weaknesses you should be working to fix them or explain how you identified and fixed a couple of weaknesses), 5 questions to ask (3 about the company/job and 2 about anything else you want to know) and 5 topics of conversation that you can tell a story about should certain questions come up(problem solving, working in a team, overcoming adversity, overcoming unforeseen problems, etc). Companies are looking for intelligent, problem solvers that can work independently and in a team. Additionally, always ask at the end of the interview, "Do you have any questions or concerns about anything we have talked about today?" This gives the interviewer an opportunity to bring up anything so you can give further explanation or clear up any misunderstandings.

Lastly, always dress professionally unless specifically told otherwise. Always bring at least 5 copies of your Resume/CV with you. Listen and respond, that pad of paper you brought? It's only for the answers to the questions you ask. After all, an interview is to simply determine if you are the right fit for the company, as well as, if the company is right for you.