One of the most feared moments for every developer is THE INTERVIEW!

I'm here to help you with some insights and knowledge based on my own experience from being on both sides of the table.

We will tackle the 9 main categories 1 by 1.

1_ Current Role & Project

Thread

The first thing you need to know and be comfortable explaining is your current role.

Basically, what do you do? How many people do you work with? How do you help them? How do they help you?

If this is your first job, talk about projects you did with friends or OS collabs

Be HONEST! Don't overstate your current responsibilities because it will bite you in the back if they see through it, and trust me, they will ask questions.

But... sell yourself. Focus on telling about your strengths and the value you add to a team

Real examples >>> Words

Let's move to the project.

Study EVERYTHING about your current project. From the business perspective, motivations for it, why the client needed it, what problem it solves.
To the whole technical aspect of it. Macro & micro. Structure, tech stack, scalability, extensibility

You have to be comfortable explaining how it works, how is it organized, which frameworks does it use, and why?

Be ready to answer why those technologies were picked or which advantages they present compared to others.
If you don't know ask your team now!

Lets put a full example:

- On one of my last projects the web app purpose was: handling payments, different types of them, adjustments, repetitive, etc.

The stakeholder needed an easy way for their users to generate payments and validate them in the system

I was the lead dev with 2 colleagues. There was already a legacy backend in place.

I designed a brand new UI, added new functionality to the backend and DB which was huge for the Business team and new validations are in place in an easy manner thanks to the UX designed

That way I quickly summarized some scope of the project, my role in it, and how I added value. Now the interviewer has an idea of my skills and a frame to ask questions.

Lets see an example of the proj structure without much details of architec, we will cover that tomorrow.

The project has an existing backend on old WCF that we couldn't migrate because of time constraints.

The new UI was built using Angular 9 and we used .netcore 3.1 for the web APIs and services that process before calling the existing WCF. All with Azure services.

I covered briefly the new stack we used, how we adapted to legacy code, and maintained existing stuff focusing the effort on delivering the project on time for the Business team.

Demonstrates versatility, up to date knowledge, and focus on client value.

Then I would be ready for some more qs regarding tech choices, team dynamics, and my role in those areas. But the frame is established and I showed I know where I'm standing. Be assertive!

That's it for the 1st thread of this series

I will see you tomorrow with more tips!

Find the next thread of the series in here: https://twitter.com/MattCodeJourney/status/1308939387741372419