🇬🇧 Elevate Your Interview Skills: Communicate Your Successes Effectively
Summary:
In this video, I discuss why developers often undervalue themselves in interviews and how we can change that perception. I emphasize the importance of articulating our successes and skills confidently, rather than just answering questions with a simple ‘yes’ or a skill ranking. I encourage you to write down your victories and practice presenting them in various timeframes to adapt to different interviewers, whether HR, technical, or management. By doing this, you can elevate your self-presentation from a 2 to a 10, showcasing your true expertise. Remember, effective communication is key to demonstrating your value!
Transcript:
0:00: Why developers are underrider in interviews? And you know what? It’s our fault. Yes! One of the biggest problems developers have is that we don’t talk.
0:14: And because of that, we are seeing us two instead of ten. Yes, let me tell you, when we are in an HR interview process, we are asking many questions.
0:28: Do you know the JavaScript? script, you know, this technology, you know, these exercises, etc. We just, we just say, yes, yes, yes, or rank your skill number, okay, five, six, oh gosh.
0:40: Forget about that, you know, you have to say 10, 10, 10, 10, 10, 10, 10, 10, of course, you know what you have been doing, you know, about your strengths.
0:49: But when you have a weakness, okay, you will see and you will say, okay, seven. But that’s not the point.
0:55: Hey, wait, the point is the following, the point is when they ask you hey can you please tell me one of your biggest success in a project oh yeah I work on this project I was able to implement the following feature oh you know what sounds boring you have to speak okay you have to sync your victory.
1:26: Hey, in that project, I was able to knock out not just a five tickets, but also 15 tickets. Of course, when you’re playing with that, you have more energy.
1:36: And okay, the other person will say, oh, okay, that person knows how to tackle tickets, knows how to, you know, bring that value.
1:45: But that is not enough. You could say the following, Oh, for that project, I was able to implement that EPIC, and that EPIC corresponds to the following critical process in that project.
2:01: And it was very key. And because of that, I was able to bring the following results 10% more in sales.
2:08: Wow, because of this implementation. And you know what? I brought that implementation. Yeah, because I work on previous projects, and because of that, I was able to implement and bring this new implementation.
2:22: Oh, amazing. So you are bringing your expertise, it had results. You told a quick story, and then you did a person who said, oh, wow.
2:33: If the other person is a technical interview, OK, tell me more, what challenges you faced. Yeah, one of the challenges that I faced is that I need to grab all the files and documents in order to migrate, you know.
2:48: So for that, I use a defensive, recursive programming in order to grab all the files and all the folders. Instead of doing a big queue process, I just did a trash, a commands with no time out.
3:03: With that, then it was just a less effort. Ooh, the other person would say, oh wow, the person knows a lot.
3:10: And you say this is very confident. Mm-hmm. Now you don’t sound like a tool. you sound like a 10. I’m more than a 10, 11 or 12.
3:18: In their mind, they would say, oh, let’s hire Eduardo. Eduardo knows everything right there. He is the expert. Awesome, right?
3:26: But for that, in order to go to that point, of course, one of the things that you have to do is you have to first write your victory.
3:36: Write it down. Write down your victory. Use to it twice and repeat every time, practice, practice at pitch, but that doesn’t have to sound like a script.
3:53: Okay, practice and make it sound like three minutes, two minutes, one minute, thirty seconds, ten seconds, it’s going to sound like very natural, okay?
4:05: And then you will just speak in front and then you’re going to see the camera, like again doing right now.
4:13: And then I just started speaking, and then, but of course, you have already your structure, you have already written down, you have already practiced, not memorized, but practiced different periods of time, three minutes, two minutes, one minute, 30 seconds, 15 seconds, five seconds, and then you know
4:32: when you have the interview process, you have a HR right there. Okay, she wants to know, he wants to know quickly in 30 seconds or 20 seconds, if there is a technical interviewer, then he will want, or she will want, like, a one-minute or two-minute explanation, then boom, you basically start explaining
4:56: all of your great victory. Does that make sense? And then when you talk to a general a man a year.
5:03: Okay, he just is speaking in 30 seconds, your victory. What did you did? How many team members were there? Did you take a leadership role?
5:17: What was the consequence? What results you bring to the parade? Boom. And then the person we love that. Of course, that kind of pitch, you have to make sure you put it into different time friends and also have versions in order to adapt for HR, for a technical interviewer, for your general manager.
5:40: You see? And with that, you see the victory. And then you’re not at two. You are at ten because you’re communicating very well.
5:47: You know who is your audience. You know who you are talking to. You’re talking to HR. Are you talking to a technical interviewer?
5:56: Now, you’re talking to a general manager. And then you know, because you know your story and then you have full time friends and also adaptions variations If you want to call it like that, okay So instances, okay, because it’s like I’m talking to you my friend they developed from my friend Instances,
6:15: okay, and different with different variations, and then there you go. You see you flew it Okay, so that’s how one of the biggest problems is that we don’t talk we don’t sink our victories But with these tips that I have already told you, you’re not gonna be looking as a 2, but instead a 10.
6:35: I’m more than a 10, a big higher. Ta-da!
