Why is this topic the interview process overlooked?

Everybody's focused on the amount of money you can make A software developer.

The type of cos you can work for is a software developer.

The frameworks of technologies, languages that you need to know to become X y Z developer.

Ensure those things are important.

But nor to get from the learning process to the job lies the interview process.

And that's very important.

So we're going to discuss in this video to get started, we need to set up a proper narrative.

So you've been learning Iowa's development.

You want to become a nihilist engineer at some corporate companies?

Some big company, maybe Fortune 500 company Not gonna list of specific company because all interview process is air a little bit different, and I don't want to beginning anything wrong.

So let's kind of just say whatever corporate company, you have it in your local city.

The first thing that you should be thinking is what is your first impression to this company?

Is it how you look?

You know, you dress nice is your hair nice.

Maybe it's how you're talking, how you smile.

Well, I'm here to tell you it's It's none of those because none of those things the attributes will see the light of day.

If your resume doesn't make it through, your first impression is your resume.

And there's so many different ways to go about creating your resume.

But the main point that you need to take home from this video when it comes to how you structure your resume is to cater it to that job listing.

Of course, you're going to be employing two jobs that you know how to do so you're not gonna be lying on your resume.

Don't lie on your resume cause that'll come back to bite you in the butt.

You want to make sure you cater that Resonate to that job listening, though, as in Iowa's engineering job listing, of course, you're gonna list the basics.

Swift X code.

Maybe this a p I that a p I and so on and so forth.

However, if that Iowa's engineering job listing that you know you're qualified for lists swift and objective, see, you want to make sure you say on your resume proficient in swift and objective.

See if it says you need to know.

Scripting language is where you need to know Python.

You know, XML.

You want to make sure you list on your resume those languages.

Those frameworks specifically because you want to make it past that first filter and get that phone interview.

Because keep in mind the person who is reviewing these resumes to see who's the best fit is generally a human resource person or an HR person.

They are looking at the job listing, looking at the skills swift, objective.

See Python XML, and then they're looking at your resume.

And if your resume essentially matches that job listing, you're gonna make it through.

You're gonna get email to schedule for an interview or they'll call you and kind of do a phone interview on this spot as long as you're available.

So Step one is catering your resume to the job listing.

We just discussed that Step two is making it past this next filter in the interview process, which is a phone interview Now.

In my experience, this phone interview is with the same HR person who went through and shows your resume for the phone interviews to remember, no development skills or minimal development skills.

But they're gonna ask you every little question about your resume about projects you've created in the past using swift using, objective see using python, you get the idea they're gonna ask you about you, and they're going also feel you out to see if you're a good fit for the company.

See, if you're nice, they're gonna understand you're nervous, sure, but they're going to just see how you interact.

This step in the process is generally pretty easy, so let's just say you made it past.

The next step is maybe a phone interview with the panel of people like other IOSE developers and project manager.

Or and more so in my experience is to go in for an in person interview with a panel of people.

So this could range from the person who was on the phone interview that HR person as well as IOS engineers, the project manager, so on and so forth.

You get the idea.

This is when you want to make sure your appearances on point because this is their first impression of you as a person and not just you on paper.

And I understand ah lot of this, you know, new tech culture.

You see Mark Zuckerberg wearing a T shirt and blue jeans or whatever he wears all the time.

But in my experience, you want to make sure you go in.

You wearing a nice suit, a nice tie, Unless they explicitly say to dress business casual, which is more like a collard long sleeve button up.

And then, you know, nice khakis or nice dress pants, something like that.

So unless they explicitly say business casual, always wear a suit and always wear a tie, this will let them know that you are serious about the job.

And you're not just kind of going through the motions.

And on top of that, make sure that you have a nice fresh haircut and generally clean shaven.

Yeah, I understand.

I had this beard I've kind of been debating on and off, But hold up, hold up.

This isn't about me.

This is about you.

So let's get back to it.

Just make sure you're looking nice, *** and span.

And if they say anything about you being overdressed, which is this happened to me in one interview.

All I said was, I want to make sure I was being respectable.

And that's generally good enough.

Because remember, it's always better to be overdressed than underdressed.

I've been to events where I am underdressed and I feel out of place.

But if I'm overdressed, I feel like the King.

You know what I mean?

You're just like these.

These peasants, they don't even know how to dress.

Well, you over here wearing this nice suit this night is Ty.

I don't to be overdressed at an event that under dressage event without a doubt.

So keep that in mind, however, is nice.

And you may look your suits your nice fresh cut will not get you the job alone.

It helps, but you need to make sure that you ace this interview.

And now this part of the interview congee go different ways.

It can go from questions all the way down to, you know, just getting the feel of you.

What are your hobbies all the way up to technical questions and people bringing out the whiteboard?

Luckily, no one's ever brought out the White board for me in order to say all right.

I want you to do the, uh what is that?

One common flub job has my buddies gamer tag on Xbox.

What is that?

Ah ah, that common question.

Hold on.

Let me look this up.

I said I met Fizz buzz the fizz bus tests.

They say that, like filters out 99% of programmers.

So questions like that are many other questions when it comes to binary trees or linked lists, things like that.

You want to make sure that you study for those, especially if you know that they'll be asking those types of questions in the interview.

So if you're going to Facebook Google, you can read stories about what they kind of doing the interview process for a nihilist developer.

What have you So just make sure you know how to do those things.

However, if you're like me most the time, these people just ask you questions based on the job position and based on your resume, you want to make sure that you know your resume and what you put on your resume better than any of these technical questions from my experience.

Because if it sounds like you B s and lied on your resume.

You're gonna be cut straight from the git.

They're going to see that you lied and you're screwed.

Basically, that's kind of how it works.

Nobody likes a lie, so make sure everything you put on your resume.

You know, if you say that you used Objective C and Swift and one IOST application and that's kind of personal interest, they're gonna ask you about it.

You need to make sure that you remember it well enough that you can kind of tell them what it's all about.

So when it comes to this interview, sure study technical questions.

If you know that's a common theme among whatever company you're applying for.

But most of all, make sure you know everything you say when it comes to your resume, which is another reason why you don't want to lie when your resume.

But don't worry.

I have faith in you.

I know you know your stuff when it comes to Iose development that you're the perfect fit for this IOS engineering position because I can tell you're smart person because you're watching this video and you're probably a really smart person since you're most likely subscribe to the channel down there that gives you extra smart points in my book, to say the least.

Just make sure when it comes to your resume, although it is your past, and you generally know a lot about it, that you go through it and that you have a talking point for each topic.

So if you list a project, have a talking point on that.

If you say something about SQL, have a talking point on that, and something I forgot to mention is when you're going into this in person interview having a Manila folder with you with five or 10 copies of your resume to distribute to each person in the panel, it's more than likely that each person on the panel will already have a copy of your resume printed out in front of them.

But it'll show them that you're coming to this interview prepared.

But inside this Manila folder is also a good place to have a list of questions that you're wanting to ask at the end of the interview, because this is also another crucial point of this interview that will always ask you, Do you have any questions for us always have questions for them.

Make sure you come prepared with those questions and make sure you don't try to memorize them.

Because I've been in there and I, like, forget a lot of these questions.

I'm like, No, you guys basically answered all my questions in this interview process.

That may be the case in all honesty, but you want to make sure that you have questions that you're pretty sure won't be answered in the interview process.

And it's best to have those written down.

Now.

This brings us to the end of the interview, and this could go a few different ways.

One way could be them saying, All right, thank you.

We will be in contact with you and we'll let you know if you got the job.

We'll let you know if you get to the next step in the interview process or what could happen.

Is they kind of situ aside with an HR person or someone of the like who discusses your salary range, they will want to get to know kind of what you're expecting to make in this position.

Talk to you maybe about benefits, kind of give you the whole HR run down of the perks of the job.

What they have to offer you, after all the interview process essentially what you have to offer them.

So it's a nice balance with the interview when companies do this.

So when it comes to them asking about your expected salary for this job position, make sure you've done research on this job.

Position the salary of it in your location.

Don't look at the national average for this job.

Look it like your city or a cities around you for this job.

What I generally do is I kind of like overshoot it in order to give a little bit more room for negotiation because negotiating is fun.

This could bite me in the butt every now and then.

But, I mean, I'm not going to take less than what I'm worth, so make sure you know your worth in that you are confident in that worth.

So I know I just got a little confusing for you right there.

Well, at least it got confusing for me because there's so many different directions that it could go after this in person interview.

If it goes to the next step of the interview process.

It may be more technical questions, or maybe essentially this same exact interview.

But instead of with IOS engineers and HR people, it goes up to the project managers, the managers of those Iowa's engineers to see if they want you in their team.

Otherwise, what you're doing is you're sitting back at home, applying to other jobs, trying to go through other interviews and waiting for the job offer from this company, which you're probably going to get considering.

You know, you watch this video you're prepared for, but as you're sitting there waiting for the job offer going through, all these other interview process is that's round one.

In this video, I'm going to step back because anything beyond that is your personal preference.

If you take this job offer, you take that job offer.

If you're lucky enough to have multiple or if you decide to negotiate, maybe you want to negotiate the salary of the purse yada, yada, yada.

So that's where this video is going to end.

Hope you guys took something away from it.

I know I didn't get into technical questions.

I have been thinking about making a serious based on common technical questions like flood job e Mean fizz Bus it, maybe some other binary trees is linked list.

Things like that.

Common coding.

Interview questions.

If you're interested in that, Siri's let me know in the comments section below, because if nobody is interested, there's no point making them.

But if you are interested, make sure you subscribe to the channel with that little bell icon turned on.

So you're notified upon me uploading those interview question videos.

So tonight, some guys haven't going piece.