DEV Community

Cover image for Interview Tips for  Developers  Part 1
Olanrewaju Alaba
Olanrewaju Alaba

Posted on

Interview Tips for Developers Part 1

I am writing this to address the common issue of getting a job as pertaining being developer, hardly will you find a developer who has not passed and experienced this process. So, in order to prevent and correct your mistakes and mindset towards interview, you've got to read this

Firstly, what is an interview?

Primarily, an interview is essentially a structured conversation where one participant asks questions, and the other provides answers. You would be asked questions based on your field for the intended job.

So, to get jobs easily without less stress and mistakes, let's journey down through the lines of this blog.


    The interviewing process of companies varies from each other. Typically an initial screening interview goes thus;

    • On phone (call)
    • A social media call (Skype) or zoom maybe
    • On sight interview

    Interview is a skill some people are naturally better at it than others but like anything else practice makes perfect.


    • Google "top 40 interview questions" based on your field and read through them.
    • Make sure you have stories you can easily talk about that demonstrate situations when you did some thing related to your field.
    • Maybe a class project or personal project.
    • A job assigned by maybe a former boss.
    • Check out the company online and know stuffs more about them.
    • Sample interviews questions and information about interviewing processes. Glassdoor is a great resources!
    • Information about what's like to work wherever you wish
    • Go to practice interviews with friends, families, campuses maybe, this will be of great help

This can be very hard for programmers especially, I feel we can check this book out for more knowledge "Cracking the coding interview".

Please kindly comment below for feedback and you can also link up with me on Twitter and follow me on this platform for more engagement, motivations, interactions and support as a developer.

Discussion (2)

greggomatic profile image
Greg Thomas

I've given a ton of interviews over the years and written about this subject. And the one thing, especially when it's a junior position, that always sets candidates apart is one question - what have you done outside of work.

This doesn't mean what is your side hustle or how much have you made or what projects you have finished. Just what have you done?

Have you tried learning new languages outside of your current job?

Have you played around with SDKs?

Have you built a game (though maybe not a games developer)?

Anything is on the table, if it involves technology, that's the main thing I want to know above all technology answers. How interested are you in this profession?

From there, we can chat about what you did, how you did it, what worked, what would you change next time, what works, what doesn't, etc, etc and I can figure out how your brain works, how you solve problems and where you go for help.

If you can do that, if you can show what you do, rather than what you've been told/asked to do - you are miles ahead of everyone else.

chryz_codez profile image
Olanrewaju Alaba Author

Thanks Greg