Well, first of all, you must understand that there is no specific tell me about yourself answer . Everything that you tell, you tell it so that it is what the employer wants to hear, organically interweaving your real merits in your words. Difficult, I agree. I recommend practicing this with Mr Simon's AI .

with patience, experience and successful negotiation.

I used to do some generic preparation tactics like trying to guess and prepare the HR questions, mirror talks, glassdoor research and so on before applying a company and they were rejecting me. Those jobs were my dream jobs and I was ready to do anything to get hired :)

One day, I had a chance to meet and talk with a manager from one of those companies. We drunk coffees and chit chat mostly. But one moment in that conversation, she told a big clue to get hired by the biggest companies around the world. That clue seemed like a non-important thing at that time but it changed my career and helped me to do my dream work.

She told me that "the key to success for software developers is not just being good at coding. That's important though. But not the whole thing. The key is being good at communication skills."

She was absolutely right. Because as a technical person, in general, we are not good at communication skills. At least I wasn't :) But, who improve himself/herself about it, that person can differentiate himself/herself from all the other good coders.

You can see that all amazing coders have a good command of English and they are proficient at world's language to tell their ideas to the world.

So I recommend you to improve your communications skills to get your dream job. I used SudoSpeak to improve my Business English and Business Skills with their unique curriculum.

You may check it or you can find another way to do it. But at the end of the day, the only barrier in front of your dreams might be just your communication skills.

By the way, I'm working as a freelancer nowadays and I have customers from 25 different countries.

I did these when I was searching for a job. It was a painful journey of rejections. But I finally got it.

For interviews I would first start practicing HR interview questions. Then when I get comfortable about answering those questions I move to participating in coding competitions.

Then I set up a mock interview in a website called Pramp. It's really good for people who want to practice coding for interviews and the questions are really good.

In Pramp you have to attend 5 mock interviews then after that, a person from Pramp will contact you.They will help you to search for a job. It's really helpful.

At this stage you should actually be very efficient at coding in any language of preference. Next you need is interview calls. For that you would need to change your resume to see which gets a better response. You need to play trial and error game for some time until you get a good response from all types of companies big and small.

So I recommend you first finish setting up the resume then move on to the next step. These were the very few of my experiences preparing for interviews.

Just Keep you head up always because in the journey to get a job you will face a lot of rejections.

Some generic things I did before my interviews:

• Tried to find out more about the company and the field they are in.
• Reviewed Glassdoor for employee feedback.
• Looked at who's working there on LinkedIn, so I can get a better idea of who I'm going to talk to.
• Looked for articles about the company, any official statements, and updates.

I did all of these because I've already worked for one corporation and swore never to make the same mistake again. I love smaller and friendlier environments.

Then,

I review the job ad once again. A single job title can represent two different job roles in two different companies. I outline the areas I expect to help out and make sure I'm up to date with whatever is going on in that field.

Also:

I prepare a list of questions about the company and the team.

It's all about the right fit. I may have the skills the company needs, but if I don't like the team or the hiring manager, that's it, I'm gone.

I could never do my job right if it weren't for the support of my team, so I'm always concerned about working with kind and helpful people. It's best when you and your coworkers are working towards the same goal, and not stressing about who did or didn't do what. Bad culture fit is what causes true damage to a company.

I have a notepad and I’ve written down some little snippets about things that are more likely for me to be questioned about. Things like design patterns, SOLID principles, a couple of common magic methods etc. and whenever I’m about to have a job interview, I take a short glance on it and I’m ready to go.