Land Your Next Web Development Job: The Interview Process

Advertisement

During my career as a software developer and manager, I have been involved in many interviews. Whether the interviewer or interviewee, I have always paid special attention to the interview process.

In my current role, I spend a lot of time interviewing potential employees, so I’ve seen my fair share of good and bad interviews. Some candidates stand out from the crowd immediately, while others are just another face in a million. In this article, I’ll give you a few tips and a head start on your next interview. Whether your next interview is your first or twenty-first, hopefully these tips will help you along the way.

Interviews can be scary, especially when you attend your first few or haven’t attended any for a while. Preparation is the key to success and can take the stress out of the dreaded process. You can do a few things before even walking through the door. If you are prepared and your mind is ready, then the whole process should be a breeze. I like to break the interview process into three steps: preparation, interview and post-interview.

Preparation

This is the most important stage in the process and could determine whether you appeal to the recruiter. A CV won’t even make it past the review stage if it doesn’t meet certain criteria, but by preparing beforehand, you can maximize your chances of making it to the interview stage.

Update Your CV

Spend time creating a great CV. Some great templates are on Guardian Jobs. If you have never created a CV, try to mirror the layouts of some of the people who inspire you. I drew some inspiration from both Scott Hanselman and Paul Irish. For example, Paul’s CV contains testimonials from other popular developers in the community, and Scott’s CV contains highlights from his presentations, qualifications and open-source contributions. You might not have the same experience or work history as the people who inspire you, but you can always get new ideas from their CVs. Who are the leaders in your field?

I follow a few rules when creating a CV:

  • Don’t lie.
    Never claim anything on your CV that you can’t do, because if an employer questions you and you don’t have the answers, you could lose the job and look like a fool in the process.
  • Steer clear of buzzwords.
    I have noticed a trend of candidates adding a load of buzzwords to their CVs to help recruitment agents find them. Only add a skill if you have used it before and feel competent enough to answer questions about it. Also, steer clear of buzzwords such as “dynamic,” “synergy” and “creative.”
  • Have your CV reviewed.
    Get your mother, sibling or friend to review your CV before submitting it. The extra pair of eyes might spot a few areas for improvement and help you finely hone the document into the perfect CV. Remember that your CV is the first point of contact before you walk in the door. You may be the greatest programmer in the world, but if your CV isn’t up to snuff, no one will want to interview you!
  • Spellcheck.
    And then spellcheck again!

Put Your CV Online

If you haven’t done so, create a LinkedIn profile. It’s a great way to get your profile out there and to get potential employers looking at your CV. Simply upload a copy of the CV that you created earlier, and, with a little tweaking, LinkedIn will format it for you. I often use LinkedIn to see whether a candidate knows someone I know or have worked with in the past. Professional connections are a good indication of a person’s working background. You might have a friend who works at the company — a referral always helps.

Another great website for developers is StackOverflow’s Careers 2.0.

StackOverflow Careers 2.0

Much like LinkedIn, Careers 2.0 lets you post your CV, but it is more developer-focused, allowing you to link to your open-source projects and any technical books you may be reading. Once you have created your online profile, both LinkedIn and StackOverflow will let you export a PDF of your profile, which could serve as a CV. So, if you like the format and layout, simply download and use it for your next job application.

Get Some Code Out There

If you are a Web developer or designer, then an online presence is vital. If you have any side projects or even snippets of code, get them onto a social collaboration platform, such as GitHub. Seeing that a candidate builds things in their spare time or even contributes to open-source projects instantly piques my interest. It’s a great indicator that they are passionate about what they do. Include your highest-quality work in your online portfolio. Tinkering with projects in your spare time also helps you to learn and grow, and hopefully you will be able to bring that knowledge into the company.

Github

A few great code-hosting services are GitHub, Bitbucket and CodePlex. Once you have uploaded your code, put it on your CV! It could help you to stand out from the crowd.

If working on an open-source project isn’t for you, then you could always contribute on StackOverflow. The community is great, and the more questions you answer, the higher your score, or “reputation.” While this doesn’t necessarily indicate that a candidate is qualified, it does show that they have an active interest in the community and are willing to learn.

Get a Blog Up and Running

If you have the time, writing a blog can be a rewarding experience. It will teach you the ins and outs of SEO, website deployment and social promotion. You could go down the route of writing your own blog engine (which would give you something to deploy on GitHub!), or you could use one of the awesome blog engines out there that are ready to roll. I quite like Tumblr, SquareSpace and even WordPress.

Tumblr

Again, don’t forget to add the blog’s URL to your CV! Blogging isn’t for everyone, and it takes time, so if you feel you might not be able to commit or update it regularly, get yourself onto Twitter and start following people who inspire you. As an employer, I always like to see what a candidate is interested in, talking about, etc.

Do Your Homework

Before going to the interview, learn as much about the company as you can. How long has it been operating? What products does it sell? What is its culture like? Think about the challenges it faces and how you can use your experiences and know-how to help it build great tools. Nothing is worse than interviewing someone who has no idea about our company or what we do. You don’t need to spend hours learning the history of the company, but a basic understanding of what it does and its ethos is important. If you haven’t done your research, then an automatic “No” is almost guaranteed!

Technical Test

If the job entails writing code, then certain companies will require you to complete a technical test. It could be a simple exercise that you complete at home, or it could be a test that you come into the office and complete then and there. If you are asked to complete the test at home, put as much effort into it as possible. I have received many tests from candidates that have a lot of JavaScript errors or that don’t compile. Make sure yours has no errors and that it works on platforms other than the one you develop on! If you get the chance, review the code briefly with someone you know. You might just find a few areas to improve on.

Site44 dropbox websites

Another great idea is to deploy the test to a live server. You can sign up for a free starter plan on Site44, which enables you to create and deploy HTML websites from your Dropbox account for free. Both Amazon EC2 and Windows Azure let you set up free cloud websites in a matter of minutes and delete them when completed.

By deploying your application and showing a working version, you demonstrate an understanding of how to deploy software, which could give you an advantage over other candidates. In fact, I hire most developers who show me a live, deployed, working version of their code!

Technical Test

By taking that extra time to make sure your technical test is outstanding, you give yourself a clear advantage over other candidates.

The Interview

If you’ve made it this far, congratulate yourself. Your hard work and preparation have secured an interview, and the employer thinks you might be the right candidate. It’s time to nail the interview and finish the whole process in style.

Questions

Before going into the office for the interview, write down a few of your own questions about the position. This is your chance to learn as much about the role as possible. Having learned a little more about the company, you might even find that it’s not the place for you!

Ask about the working environment, the development stack you will be working on, and anything else related to the job. Interviewers love to answer questions, and it shows you have taken the time to think about the position. Going into an interview without any of your own questions is a bad thing! Remember that you are also interviewing the employer in this stage!

Don’ts

There are a few definite no-no’s in the interview process. Follow these simple rules to avoid any awkward moments:

  • Don’t ask about the salary.
    Bringing this up during the interview is not the best timing. Other members of the staff will often sit in on the interview, and your potential salary might not be intended for their ears. If you do need to ask at this point, do it privately with the hiring manager.
  • Don’t ask how you did.
    This is important because the people in the room will be discussing you after the interview. Other candidates might be interviewing before or after you, and the team will need a chance to compare you to them.
  • Don’t badmouth your former employer.
    No matter how mistreated you feel or how bad the job was, keep your thoughts about your former employer to yourself. Be as diplomatic as possible, because disparaging other people won’t win you points with the interviewer. Your attitude towards and description of your former employer is a good indication of the kind of employee you will be. If asked about your last position and why you left, explain the situation but save the ranting — you would only make yourself look bad!
  • Don’t lie.
    If you don’t know the answer to a question, just say so! The interviewer will respect you for answering honestly and will understand that you don’t know the answer to every question.

Last-Minute Details

Whether you are applying for the job directly or through an agency, check a few last things before going to the office for the interview:

  • What is the dress code?
  • What will the format of the interview be?
  • How long will the interview last?
  • When and where will the interview be held?
  • Who will be present in the interview?

Find out the address and time of the interview, and arrive at least 15 minutes early. This will give you a chance to relax and to avoid the stress of rushing about. By arriving early, you will also observe the staff coming and going through the reception area. Those 15 minutes could give you a good feel for the company.

Finding out these simple things before going for the interview takes some of the stress out of the situation. Preparation is the key to success!

Relax

The interview process is as much about you finding out whether the job and company are right for you. Feeling nervous is natural, but try to relax and enjoy the process. If you are relaxed, you will interview that much better and will come across as more confident. You’ve done all the hard work to get through the door — now, just keep up the good work.

Post-Interview

The interview is over, and you are eagerly awaiting the result. Depending on the company, it could take a few days to a week to get back to you. Rest easy, knowing that you have done all the hard work and given it your best shot.

If you wind up not being chosen, don’t be disheartened. The timing might not have been right, or you might need to brush up on a few areas. There could be any number of reasons why you weren’t offered the position, many being outside of your control. Interviewers will often give you feedback on the process and your performance; if you would like more detail, don’t be afraid to ask. Whenever I have been turned down for a position, I have asked the interviewer for areas to improve upon. It is an opportunity to learn and grow. Practice makes perfect, and the more you interview, the better you will become at the process. Once a few interviews are under your belt, it starts to become a piece of cake.

If you do get the job, well done! You’ve nailed your first interview and are on your way to starting the new job. You should be extremely proud of your achievement.

Remember

Interviewing is difficult! No matter how hard you try, you will not always be successful, and sometimes it just doesn’t work out. By following the steps in this article, hopefully you will become more effective at the process and seem a more attractive candidate. Finally, remember that the interview process is as much about you learning about the employer as it is about them learning about you!

(al, il)

↑ Back to top

Dean Hume is a software developer and blogger based in London, U.K. A passionate techie, he created the ASP.NET HTML5 toolkit and blogs regularly about web performance at deanhume.com. He is the recent author of Fast ASP.NET Websites.

  1. 1

    Thanks for the article! Really helpful!

    0
  2. 2

    I think a thank you note should be added to the Post-Interview list.

    0
    • 3

      I’d like to know if employers still think so and appreciate a note. The whole hiring process is so automated now, I question the value.

      0
      • 4

        My experience has been that it depends on the company, the industry it is in, and how big it is. For instance, if you’re applying as a developer for a company who’s focus is in a different industry than web, sometimes it gives the in-house recruiter (who is normally the only person you have contact info for) warm and fuzzies but doesn’t really get to the right people. For smaller web shops, and even some of the larger ones, you’re normally dealing directly with a web person (owner, project manager, senior developer, whathaveyou) and it does leave a positive impression.

        Unfortunately, the same applies to the point made above about asking how you can improve. If it’s a company who’s focus is not web, the in-house recruiter won’t know because they didn’t interview you. And even with smaller agencies, sometimes you won’t get a response because they’re… well just too busy (hence looking for more developers!).

        There are always exceptions of course and this is not a hard and fast rule (nothing really is in this industry). I always send a follow up thank you note, as well as ask how I could improve, and if I don’t hear back from them I just accept they’re busy.

        0
    • 5

      Only a very simple note to the recruiting agent or HR staff member… I have seen 2 instances recently where someone had a job locked down but lost it at the very end because of overly wordy thank you notes.

      0
    • 6

      YES! A “Thank You” note is VERY important.

      Not sending one means “I’m not really interested in this job.”

      0
    • 7

      Never write a thank you note. It makes you appear needy/stalker like desperate and it will lead to an instant rejection!

      0
      • 8

        That’s simply not true, Matt. Last year I applied for a job I was really interested in and after the interview I wrote very short and simple thank you notes to all the interviewers. I got the job.

        I think the important thing is to be sincere, concise and to avoid the copy-paste approach.

        0
  3. 9

    I would add, use antiperspirant instead of deodorant. I get super sweaty when I’m nervous.

    0
  4. 12

    Excellent article!

    Two things I’d add.

    Small talk and light humour
    Often, before an interview, there’s a moment where everything is being setup, or someone still has to join the process. You may be nervous, your interviewers may be nervous too, or jaded – this may be the third or fourth interview they’ve done on that day. If you can lighten the mood with small talk and an appropriate light joke, half the battle is won. Just getting a smile or a laugh from your interviewer/s has a massive impact on your chances.
    That small talk can start out as simple as the weather, your commute, the football scores.

    Do you have any questions?
    Every interview I’ve had that comes up – “do you have any questions about us?” – usually at the end of the process.
    You *HAVE* to answer this with a “Yes I do”, it shows enthusiasm and the fact you’ve prepared. Try to have two to three key questions to ask, as often, if you’ve just got a single question, it may have been covered already during the interview process. Keep it pertinent to the role. “How do you guys handle XYZ?” “Do you have external XYZ resources?” “There’s this great piece of XYZ tech, do you use it?”

    0
    • 13

      Hi Matthew

      I totally agree with you, and you raise two very good points!

      A potential candidate should always come ready with a few questions to ask the interviewer – it shows interest in the company and it looks like they have taken the time to research.

      Cheers
      Dean

      0
  5. 14

    Ugh. It didn’t take my other post… Not rewriting it but essentially it’s be yourself.

    Don’t put on airs and act like someone you’re not. Obviously even if you talk like a sailor on a day-to-day basis, don’t throw the f-bomb around during the interview but don’t come across as all prim and proper (or “professional” in the classic sense of the word) when you’re not.

    Be honest about who you are. I’ve replaced too many developers because they impressed the interviewing team with their “professionalism” during the interview but were let go a month later because they came across as deceitful (seriously, I’ve had interviewers say that to me more than a few times).

    Relax, be yourself, focus on showing them how you can help them grow.

    0
  6. 15

    As a front end developer, something I always try to do with my CV is create an HTML version. This is a good opportunity to demonstrate what you are capable of, in a way that should be useful to the person reviewing your CV.

    0
    • 16

      Hi Ben

      Yup, definitely agree with that. An HTML version of your CV is a great idea, especially if you are a front end developer!

      0
  7. 17

    “It could be a simple exercise that you complete at home, or it could be a test that you come into the office and complete then and there.”

    At home tests are a fair test of a developers skills. The developer will have their tool stack in front of them and they can show off their skills with the final product. And yes, deploy it to an external server and provide a URL to the employer.

    That being said, in office tests raise a HUGE red flag in my books, it signifies a weak interviewing process by the employer. Many developers have used numerous syntax over their careers and committing all of the rulesets to memory is unrealistic at best. In office tests DO NOT provide an accurate gauge of a developers abilities, especially if its pencil and paper.

    As an employer I want someone that can show me solid work from the past and that indicates a willingness to learn new tech quickly and efficiently. An in office test will not be a determinate of these attributes.

    The only other comment I have is about arriving 15 minutes early. I would bring that down to 5 minutes early. Arriving too early means that the manger gets a call in his/her office and now they feel rushed to make the interview. Meanwhile you get to sit in reception oddly staring at everyone that walks by thinking that they might be the person interviewing you. Every reception area is the same, you won’t get an idea of the working environment there. Show up ON-TIME, not uncomfortably early and NEVER late.

    0
    • 18

      Thank you! In almost 20 years, I’ve only had one in-office test and it was on a whiteboard. What. The. Crap.

      I get that’s the new (“new” as in the past few years) thing to do but that’s definitely more for an engineer than a developer (and NO they are not the same thing).

      I truly don’t see how any developer could write accurate code (or even pseudo-code) on a white board (or paper) that will give the the interviewer what they’re looking for, primarily because of what you said: we have used numerous syntax and formatting and whathaveyou over the years and, unless we’re an engineer, we should be able to adapt to the syntax/format/style of the company we’re interviewing with.

      At least in my experience, every company I’ve worked for or with has done those things different enough from one position to another.

      0
      • 19

        I agree! I’ve actually turned down interviews because they wanted a whiteboard presentation in front of a group. I’m an engineer and developer (yup, there is a difference) and not a performer. I don’t think you can really show your best skills with that kind of approach. Speaking in general about how you would approach a problem is fine, but requiring someone to solve a problem without their usual resources doesn’t give the opportunity to show their best work. Yes, it can indicate how good someone is at thinking on their feet or responding to a crisis, but as an overall measure of quality, it’s really lacking.

        I actually work well under pressure, but not so much if I have to “perform.” I’m an engineer, not an entertainer. If I wanted to be in front of an audience I’d be in a different career. That’s not to say I’m antisocial or unable to speak in front of people, but having to solve a problem with a bunch of people literally looking over your shoulder is really uncomfortable. Not everyone can focus as well in that circumstance and not being able to do so is not an indication of a poor developer. It’s similar to how some people are better with a book and theory, but not as good when it comes to applying that knowledge. Different strokes and all.

        I also dislike some of the online tests. I was asked to do one recently and it was very heavy with computer science theory, talking about things like Big O notation (which I’d never heard of) and using algorithms I haven’t seen since college. As an engineer, I’m very hands-on and am mostly self-taught in my coding skills, learning by doing and applying the formal training I’ve had in other languages to learning new ones. I didn’t come through the more theoretical computer science path, so that aspect of things tends to be lost on me. Most of those tests are very computer-science-like in their approach, so it doesn’t give an accurate representation of real world skills for those of us who aren’t recent computer science graduates.

        0
    • 20

      Yes and yes.
      With respect to time, I have heard a few employers complain about about interviewees who show up too early. Five to 10 minutes really, otherwise sit in your car, go for a walk, go to the restroom and make sure there’s no spinach between your teeth…

      0
      • 21

        I was reading the comments before leaving mine on the exact same subject. Punctuality is being ON TIME, not before, and of course not after. 15 minutes early is way too much from my point of view, I don’t want to be interrupt in that thing I was finishing before the interview just because the applicant couldn’t wait another 15 minutes anywhere else…

        0
    • 22

      +1 insightful

      0
  8. 23

    Hola, estas recomendaciones son excelentes, lo voy a tomar muy en cuenta.
    gracias!

    This recommendation are very good, I go implement in my resume. thanks a lot.

    0
  9. 24

    I will share one of my experience. Our HR had hire a web developer and he cleared all test from technical to group discussion. He joined the company but when he was ask to do simple task he was not able to create a simple html page with the form.

    So we ask our hr manager how you select the candidate who as a zero working knowledge. HR manager said we asked him all the technical question and he was good at everything. After some days we found he was friend of a employee who was working with our company so he was aware about all the technical question and test. So he prepared everything about interview process. But we didnt got a answer why did he applied for position in our company. hahahahahaha

    I agree with the below person::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

    Deborah
    September 18th, 2013 7:27 pm

    I’d like to know if employers still think so and appreciate a note. The whole hiring process is so automated now, I question the value.

    0
  10. 25

    15 minutes early seems excessive. I usually find the office half an hour before I’m due, then take a walk around the surrounding area for a while, clear my head, find a bathroom, then enter the reception with no more than 10 minutes to spare.

    I’m not sure about thank you notes either. This is actually a custom I hadn’t heard of until recently and I’m not convinced it’s entirely appropriate, especially if a recruiter/agency is involved.

    0
  11. 26

    Great article Dean, keep them coming!

    0
  12. 27

    Look, there are standard do’s and don’ts in this world of job hunting and the hiring process but it truly is based on you as a person and who you are interviewing for. I’m going to come at this from a different point of view though. What if we look at the individual who is being interviewed as being their very own company, wanting to partner with another company that would allow each of them to grow. I think individuals in this vast job marketplace should be just as important as any other partnership. Post-interview notes given should not be tossed aside or forgotten. An acknowledgement that it has been received along with a “Thank You” from the company should be given out to the interviewer. You just never know whether it be in the near future or perhaps later, you as a recruiter might want to rethink about who’s note you don’t respond to. Perhaps there are individuals who just want a job and a higher salary that goes with it, but that is just equal to a company just wanting a worker to do that job with self interested benefits. When an interviewee takes the time to write a Thank You note, it is only out of courtesy that the HR person responds because you just might meet this very same individual, working with another company who you might want to work with. Never diss people because you don’t have the time. We all have time to say Thank You.

    0
  13. 28

    I have been applying for many jobs in middle east through many portals, Got once to Interview via stackoverflow career. Never got a call from any other website..

    0
  14. 29

    Hey, thanks for the article. Eerie timing for me as my first-ever interview for a job as a front-end developer is tomorrow. These tips will help solidify how I come across.

    0
  15. 30

    There’s a lot of things I would disagree with in this article.

    1. A Thank-You note… first of all, you’re not really thanking them. It’s not just the employers decision – it’s YOUR decision. You’re interviewing the company/client as well to see if it’s a good fit for YOU. A better thing would be a “follow-up” note. Provide any additional information that you said you would deliver or follow-up on, follow up on a timeline, etc.

    Aside, I’ve never sent a thank-you note or a follow-up, especially when dealing with recruiters or contracting companies; they do the follow up with you. I’ve also never been rejected for a position, and I consider myself professionally “new” – I’ve withdrawn my candidacy, but never been turned down.

    2. Salary discussions – don’t waste anyone’s time. If there’s more than one interview, yeah, wait til the later interviews if you can. Otherwise, if the salary is a deal breaker, you should mention that upfront. Ideally, the employer will give a range first of what they are willing to pay for this position. This doesn’t always happen. When dealing with a recruiter or contracting company, since they handle your payroll anyway, definitely discuss it with them. They should already know how much the client is expecting to offer a candidate before even interviewing.

    3. 15 minutes is waaaay early. A lot of reception areas (especially smaller businesses) aren’t set up to accommodate guests. I agree that you should plan your travel so that you’re not late; however, if you’re more than 5 minutes early, take a walk outside.

    0
  16. 31

    What about interviewing for contract roles vs. permanent? Do you recommend a different approach? I don’t usually send thank you notes for after interviews for contracts, since there’s usually an agency as the middle-man. I do politely thank them for their time when I leave. A lot of times, I don’t get any feedback at all, not even an indication of rejection. I call that the recruiter “black hole.” It’s annoying, but seems to be the norm for some recruiters.

    0
  17. 32

    Great article, especially the part about being prepared to ask questions. Some examples of appropriate questions or questions that impresses the interviewers would have been helpful as well.
    Some developers worry about “fitting in” with the future team or about getting a boss who is very controlling; nit picking on every line of code, but feel awkward asking about the “team culture” during the interview process. What would be a good way to bring this up during the interview process or is it even appropriate at that point?
    Many developers I know see the coding tests during the interview process as one big red flag about a “backwards” team culture, since these tests don’t accurately gauge the developer skills.

    0
  18. 33

    It’s very likely that the person interviewing you has zero knowledge about what you do. The technical people who join the interview are on your side, they need help.
    If HR people didn’t exist would there still be a job for you ? YES !

    It’s unfortunate that you have to jump through a bunch of hoops, but you do….

    Just keep in mind the reason you are at the interview in the first place is because this company needs people who have actual knowledge and can produce actual work. (Not everyone can send emails and ask stupid questions for a living.) Keep your head up, sweat down, and remember you are valuable.

    0
  19. 34

    I’ve often been told that dress code for the interview is suit and tie. As a mature candidate I’ve lost count of how many times I’ve been interviewed by someone in shorts and tshirt and felt them observing that this guys in a suit isn’t really going to fit in. I’ve often felt that smart casual or losing the tie would have been more appropriate dress.

    0
  20. 35

    I find that the biggest problem is getting past the recruiter. Often this role is outsourced to someone who is matching skills without really knowing what they mean or what level of expertise is required. These days the word javascript is mandatory for almost every role from £20K to £100k yet the recruiter has very little idea of what level of expertise is actually required. Advertised job roles are often very brief and candidates have little chance to tailor their application/cv to roles and so ensure that they offer what the recruiter is looking for.

    0
  21. 36

    Not mentioning salary – in every interview I’ve ever had the interviewer has asked me what slary I expect. I’ve always tried to avoid answering this with vague responses such as ‘a salary commensurate with the role’ or ‘salary is not my primary concern, I’m sure we can agree something’ but they’ve always pushed for at least a small range. I’ve often felt that a candidates salary expectation is used as part of the decision process; everyone considers price when purchasing and hiring is no different. Personally I wish hirerers would be more upfront about what the role pays as it allows candidates to better judge the expectations of the role. There’s also nothing worse than going through a round of tests and interviews just to get an offer thats way below your current salary.

    0
    • 37

      there is a very old adage when it comes to really any financial negotiation, and that is…

      “the side that mentions a number first always loses”

      ..I find this to be true…sooooooo…always ask “well, you must have a number in mind, what would that be?” or something along those lines.

      0
  22. 38

    In other words be a kiss ass, waste your time and get manipulated. Why in this country (USA) everyone teaches you to be indirect, and passive. A salary is what we need the most that is why we work. If you don’t agree you are full of it. Salary is not your concern because your trying to manipulate your potential employee to get to pay them the least amount as possible. NO.

    0
  23. 39

    Mark Petherbridge

    February 5, 2014 7:18 pm

    One thing I always tell me friends who smoke (if they ask for advice), is DO NOT have a cigarette before your interview. This means, the moment after you have showered, prepared and fragranced yourself do not light up a cigarette.

    0
  24. 40

    I enjoyed this! My first interview is tomorrow, and I am a recent graduate. I know about 3/4 of what’s involved/expected due to inexperience and lack of thorough job description – I really hate that. But as a Junior, that’s ok right?

    0

Leave a Comment

Yay! You've decided to leave a comment. That's fantastic! Please keep in mind that comments are moderated and rel="nofollow" is in use. So, please do not use a spammy keyword or a domain as your name, or else it will be deleted. Let's have a personal and meaningful conversation instead. Thanks for dropping by!

↑ Back to top