After you've sent out your proposal or your job application and you've heard back from the client,
now it's time to nail the interview.
The first type of question you want to get comfortable with are technical questions.
This is also known as coding related questions, and this may be asking you to do a whiteboard coding
assignment or do some coding on a computer.
These technical questions are designed to find a freelancer who can help the client solve their problem
and who has the current skill needed for their project.
That does not mean, however, you will need to know every single answer, but it's all about you asking
questions when needed and showing that you are adaptable and you're always willing to learn and to find
a solution as quickly as possible.
A great example of technical questions you may get asked as a developer is on 30 seconds of interviews
dot org.
This is arguably the most important thing in passing a coding interview because you have to be well
prepared and the best way to do that is to practice the common interview, coding questions over and
over again until you know them by memory.
If you can practice enough and you really work at it, you'll be able to handle a question you've never
seen before based on the problem solving that you've learned.
Now you will have to gain confidence here, but once you do, you'll be able to relate it to something
else that you've probably done in the past, and that will help you stand out and nail the interview.
So if you go to this website, you can start to scroll down and once you see these questions, all you
have to do is click show the answer and it will give you the in-depth answer to that question.
And you can also sort it by different categories, by expertise, etc..
So let's say you want to have some JavaScript questions here, and let's say you you look at some of
these and you can also see the different difficulty of them easy, easy, intermediate, etc. And from
there, this is where you can get some good practice.
You can click, show the answer, and then you can also hide it and test yourself again.
And there's a lot of practice that can get done on this website.
The next type of question you want to get comfortable with for nailing the interviews are non-technical
questions.
So these are questions that are more on the side of tell me about a problem you solved or why do you
want to work for us?
Or tell me about yourself and what you're interested in.
You want to get comfortable with these type of questions and have a general response ready for each
of the most commonly asked questions.
So you're not just making it up on the spot, but you have a framework for which you are working from.
You also want to do your research before the interview.
So do as much research as you can about the company that you are interviewing for and as well as the
people who are going to be interviewing you.
Now, if you don't know who will be interviewing you, you can ask the person who has been arranging
the interviews, who will be doing that.
And then you can use this information to prepare a thoughtful and specific question to demonstrate that
you have curiosity, and you can also prepare additional questions ahead of time so that you were not
the only one getting asked the questions.
But now you're also going to ask the client questions, which shows that you are interested and that
you are a problem solver.
Now let's discuss what is important to focus on during the actual interview itself.
The first is mindset.
So during the interview you always want to focus on the mindset that you have because it's not a do
or die thing.
You are going to have many different opportunities and that will help take some of the edge off of it
if you are nervous.
And also it's important to remember that it's a huge learning opportunity every interview you go on.
So if you show up with a positive attitude, you're excited about the potential project.
Just let that shine through.
Next is to be prepared for all of the questions that are going to be asked, as well as the questions
that you want to ask the interviewer.
And lastly, during the interview, you should have at least two stories that you can tell that showcase
that you are a great fit for the job.
Now, these stories should focus on how you got started in your field, what inspired you to learn the
skills and basically anything that's relevant to the type of job that you are applying to.
Another story could explain a past project or a job you've worked on in your portfolio where you can
highlight the process of the project, the value that you delivered, and ultimately the problem that
you solve for the client.
Remember during the interview.
You do not want to ever show any negativity.
Always keeping positive and never be a Debbie Downer.
Don't talk down on past projects or jobs that you have because all this does is shed a bad light on
you.
It makes you seem difficult to work with, and it will likely push the client to hire someone else because
they may not see you as the best fit for your job.
So even if they ask you what your biggest weakness is, find a way to answer it honestly.
But then describe how you work on improving it.
This shows that you are a problem solver and not just a complainer, and that's the type of freelancer
that any client wants to work with.
At the end of the interview always ask questions because like we said, that shows them that you are
interested in the project and you're eager to find out more about specific questions that you have or
next steps of the process.
Now, of course, you always want to tailor your questions based on what you need clarified about the
project.
For example, a question you can ask that shows you are interested in the longevity of the company is
Where do you see your company going in 5 to 10 years with the implementation of this website?
This will show the client that you're not just in it for that short term money opportunity, but you're
actually looking at the long term goals of the company, and that's what's in the client's mind.
So if you can connect with them on that higher level, they will be much more likely to not only remember
you, but also consider hiring you for the project.
Next, once a client is interested and they start talking about pricing and things of that nature,
it's up to you to negotiate and to close the deal.
So if the project is a good fit for you and for the client, you have to negotiate the payment terms,
the scope of work and everything of that nature so you can get the ball rolling.
Now you want to give reasons for everything and you also can mention industry averages and always be
on a positive and an open note.
Once again, if you found out more information about the scope of work or anything that changes during
your initial proposal, let the client know that you're going to revise your offer and get it back to
them as soon as possible in writing.
Usually you want to do that within an hour or two of that call because then you nail the interview and
from there you're already sending them an updated proposal and it makes it as seamless as possible for
the client to hire you and you to get started on that project.
Remember, at the end of the day, the entire process is all about showing that you have the skills,
the knowledge, and most importantly, you have the desire and the emphasis needed to focus on the problems
that are there and to solve the problems that the client has so they can reach their goals.
Because if you were able to solve the problem, you are ultimately very valuable to the client.
It's all about your thought process as a developer and showcasing this to the client, even if you don't
know the answer to every single question.
Don't let that discourage you.
And remember, it's all about solving problems.
I look forward to seeing you in the next lesson.