Job Hunt: Interviews

Overview

My goal for job hunting is to secure a position in a company that fosters a positive work environment and values my passion for coding. While job hunting can be challenging, the interview process is particularly difficult. In this blog, I will share my general approach to tackling common interview questions, preparing for interviews, and negotiating salaries. Although there is no one-size-fits-all solution to interview success, I hope that my strategies will help you improve your own interview experience.

Interviews

As a self-taught developer with 5 and a half months of coding experience, I found it incredibly difficult to land interviews. On average, only 1 out of 100+ resumes resulted in an interview, making employment opportunities few and far between. Unfortunately, my first two interviews didn't go well. I struggled with nervousness, and I lacked a clear understanding of my strengths. Imposter syndrome and other factors only compounded my struggles. It was disheartening to put in so much work just to fail at the early stages. Additionally, I felt that I couldn't compete with developers who had CS degrees, boot camp certifications, or more experience. This limited mindset only added to the pressure.

Common interview questions

I struggled to answer common interview questions like "Tell me about yourself," "What are your strengths and weaknesses," and "Why should we hire you?" However, I changed my approach when I stopped comparing myself to other candidates and instead focused on my strengths. After researching common interview questions, I realized that they were all essentially asking the same thing: "What value do you bring that makes you perfect for this role?" Drawing from my real-world experience in the restaurant industry, I identified transferable skills such as customer service, teamwork, and working well under pressure as valuable characteristics employers were looking for. This self-awareness gave me confidence and provided better clarity to approach interview questions.

To discuss my coding experience, I focused on my portfolio. Rather than attempting to create more complex applications, I doubled down on understanding the three projects I had already completed. These projects became the focal point of my experience, allowing me to discuss the challenges I faced and how I overcame them during the application development process. Keeping in mind my target employers were those that valued my passion and curiosity for coding.

During job interviews, I informed hiring managers that I was transitioning to a new career and highlighted the transferable skills I had acquired from my previous employment. As a self-taught developer with limited experience, I elaborated on my responses when asked common interview questions like "Tell me about yourself". I drew connections from my culinary/hospitality skills and how they could be valuable in software development. For example, I explained how my previous experience working in a team environment could translate into effective collaboration with other developers. As a result, my answers tended to be more in-depth, detailed, and personal compared to other candidates.

Write a script

I always experience a high level of anxiety during interviews, which often caused me to forget essential information. To help organize my thoughts, I created a script that outlined my transitional skills and projects. I practiced and revised this script daily, by reciting this in the car, in the shower, and any time I had a spare moment.

I found the script to be incredibly helpful, as it acted as a guide for my ideas and stories. Even when my anxiety was at its peak, a single word could help me transition from one topic to the next. After a few interviews, I became more adept at selecting the right stories to match the moment. This not only saved me time but also allowed me to focus more on preparing for technical interviews.

Two-way communication

One of my primary goals during the job hunt was to find a company with a positive learning environment. Unfortunately, many companies take advantage of junior developers, seeking experienced individuals while offering only junior-level salaries.

For many years, I believed that interviews were simply a one-sided conversation, with the hiring manager asking questions and the candidate responding. However, I was surprised to discover that interviews are a two-way conversation. While the potential employer is evaluating candidates, candidates should also be evaluating the potential employer.

To learn more about the companies, I began asking questions such as "Why is this position open?", "How does the company handle project delays?", and "What happens if an employee falls behind?". These questions were appropriate and respectful, and I eventually began asking as many questions as the hiring manager. This approach helped me avoid undesirable situations and allowed me to save time by identifying potential red flags early in the process.

Salary

Discussing salary was not something I felt comfortable doing during interviews. I found some hiring managers would compare salary expectations between candidates, which could eliminate my application at any stage of the interview process. To remove the focus from money and shift it towards my passion, skills, and value, I refused to discuss salary unless it was for the contract at the very last stage. Focusing on compensation early on could detract from the effort I put into daily practicing and preparation, and could lead to misinterpretation about my interest in the company. When asked about salary expectations, I would respond with "I don't have enough information at this time to give an accurate amount, I would prefer to answer this question at a later time." This gave me more time to learn about the role and the company. It also gave the employer time to evaluate me reasonably based on my passion and skills, rather than solely on salary.

When it came time to negotiate salary, I researched how much junior developers were typically paid in the region, considering the cost of living and responsibilities of the role. After determining my desired salary, I added a few extra dollars to give room for negotiation. Rather than suggesting a salary range, I would tell the hiring managers exactly what I wanted, and I found that I would often receive an offer near the amount I asked for. I strongly believe in doing your research, knowing your worth, and trusting in your abilities to negotiate a fair salary.

Be Kind

It's important to remember that job interviews can be stressful for both the interviewer and the interviewee, and not to take any negative outcomes personally. Instead, I approach every opportunity as a chance to learn and grow. Regardless of the outcome, I try to be kind and respectful to everyone in the process. Demonstrating kindness and a positive attitude could be easily overlooked, but it makes a significant difference in the hiring decision. In fact, between two highly skilled candidates, the one who is easy to work with and has a great attitude will be remembered more fondly. Therefore, I treat everyone with respect and kindness, it will make a lasting impression on the people I meet during the interview process.

Lesson

"It is better to be prepared for an opportunity and not have one than to have an opportunity and not be prepared." - Whitney M. Young

Preparation is key to increasing your chances of success. Remember that opportunities are limited, so make the most of them by dedicating yourself to preparing and practicing. By taking the time to prepare, you will feel more confident and increase your chances of success. Believe in yourself and your abilities, and you will be one step closer to achieving your goals.

Thank you for reading. If you believe my story will benefit someone who's attempting to make a change please share this post. Feel free to contact me, I would love to hear from you. Please subscribe if you'd like to stay up to date and receive emails when new content is published.