It is tee time with your host attack lead.

The tack lied now, as an ex Google tack lied.

I wanted to talk to you about the potential career path that you could be taking as a software engineer.

You know, I've seen some people going around learning machine learning and JavaScript.

And just so you know, that's just a combination that is unheard of in tech.

There is no row for something like that.

You generally aren't running machine learning in JavaScript on client side Web browsers.

So I would encourage you that if you really want to fast track your career that you signed up for my program.

Daily interview pro dot com.

So Daily Interview Pro is a website in which I will send you a free white board.

They interview question every day.

Check it out.

Daily interview pro dot com So what we're going to do here today is we're going to cover some of the top career paths and also go over why some of these may not actually be good choices for you.

Some of these are really only for senior people, and you need to start building your based off of something simpler.

For entry level people, there are certain career paths that are far simpler to get into than others.

If we take a look at the beginning, when you start off most computer science students and even if you didn't go through a computer science school a lot people start off learning, say, Java or C C plus plus, and this gets you a standard role as a back and Web engineer say another problem is, if all you know is Java or C, then that really limits the scope of work that you can do and you'll be competing with everybody.

For a few Java based the Web back, an engineer rose.

The fact is that most companies are not running their back ends in Java these days.

A lot.

The company's maybe running python or PHP under beckons.

You know, we're talking about YouTube, instagram, Pinterest, Cooper and more, so that's our first role here.

Webb back an engineer and this one of the most common types, and it's a pretty good, decent road against Started in is very traditional, and somewhere you really want to hear is pick up some coming languages like, say, python or PHP.

Maybe pick up no Js.

And if you know Java or C, then all the better.

That's just going to make your stronger candidate and more fleshed out and where you want to be focusing in on Here are Web projects, the rest a p I contract between client and server and what that a p I looks like what the inputs and outputs are.

Are you using Jason Protocol buffers?

If you're looking to be a ***, an engineer and then you suddenly start mixing a little bit of graphics development game development that's just going to end up kind of wasting your time.

You know, all learning.

That's good.

That's great.

But it's not really as focus and going to land your job as quickly as if you had just really focus in on that *** and engineering rope.

Now the other type of role we have here, the 2nd 1 is Web front and engineer, and this is an especially easy entry point.

I think if you're just looking to land a job in tech, you pick up a wet front and technologies we're talking about JavaScript.

CSS html learned some new frameworks like, say, angular react view Js.

And these are going to get you set up to be a wet front and engineer, and that's really all you need.

You don't really need to touch the back in cook, which generally requires a little bit more theory on the computer science site.

If you take a look at many boot camps out there that are aimed at people who have no programming experience, you may know this that a lot of them they kind of trained you towards being a friend and engineer.

And maybe they give you a little bit of full stack experience as well, so you can get prepared for that.

But I've seen plenty of Rose and companies.

Start ups where people really want is somebody working on the front end building up those user experiences buttons you eye color funds, graphics positioning layout, hooking up AP eyes onto the back end.

But the front and usually does not do much more than simple rendering.

And if all you did was no javascript, very well then I think that this could be an excellent entry point for you to start getting your foot into the door in tech.

Now, If you were to actually combine, say some of the back and front end and learn both of these, then you would be considered a Web full stack engineer, which is excellent.

For a long time I have been the Web for stack engineer and then the way I still am.

The reason for Stack engineer is so good is because Webb is here to stay, and especially as mobile phones have been getting more powerful lot cos they don't really see the need to create native applications, they just create a very good, responsive website.

And that's really all they need.

And it is also perhaps the most entrepreneurial form, right, if you are able to develop in the entire website back in through front and that you're able to pretty much launch your own companies.

So this is one big appeal for me.

You know, I didn't really want to be just a pure back, an engineer writing a bunch of Python scripts because that would not be sufficient for me to be entrepreneurial in that sense.

So I think that the Web a full stack engineer is an excellent goal for many people.

And it's a road that is in high demand by many startups, people who just want you to do kind of a little of everything, put a whole future together, front and threw back and start to finish.

And for this sort of roll, you're going to want some of that front and experience like JavaScript C sssh!

Demo, maybe angular or react and that on the back.

And you're going to want to know, maybe, like python PHP ruby on rails.

Django, Java know Js go laying some back in language like that.

If you know some day the basis like my sequel and then some Windex to just glue everything together, then that's really going to get you all set up there.

And so that brings us to our fourth category here, which is mobile engineering.

It turns out that mobile engineers are one of the biggest categories of engineers, which may come as a surprise to some people.

Mobile is big and has surpassed that stop usage.

Many software engineers, including myself, have built their entire careers on being the mobile engineer IOS or android.

Those are the two big ones, and you can pick one to specialize in.

This is also an excellent entry point.

By the way, if you're trying to get into tech, if all you knew was Iowa's engineering and you decided to get good at that or android engineering, then that's pretty much all you need for a road you don't need.

JavaScript.

You don't need databases or python.

All you need is to know how to build an android app using, say, Coughlin or Java or for IOS would be swift or objective.

C.

So this is a very clean and easy path, right?

Because all you have to do is just learn one single language and you're set.

And the other great thing about this is that it can actually help you be somewhat entrepreneurial as well, right?

It's pretty fun to be able to put together an entire AP front through back.

Launch it and you can have some results there, too.

You could put together a game and try your luck at the APP store.

Maybe it will become popular.

Maybe you can build a useful service or something like Twitter, and that could be quite useful as well.

If you were to mix some of that client side code experience with a little bit off the back end coat back in the day.

Used to be that IOS was the far better platform.

But these days, Android is big.

In fact, 100 has surpassed Iowa's a long time ago.

You know the number of Android users is probably 4 to 1 or 5 to 1.

Maybe more than that.

By now, Android has been growing very quickly and even though Eilis is very popular in the United States and it is by far the biggest global market share another career path here that we've talked about somewhere is game development or graphics development.

And this was something that I have been doing straight out of college and a lot of people.

I would say I tried to get into game development because that's really the first interaction people have with computers.

Maybe they play a computer game when their kid I played one and then I was inspired by that, and I want to make my own games and really get into graphics because it's so visual.

But the funny thing is that, you know, faint cos they don't build games and the game industry.

If you're to get into it.

It's pretty notorious for low pay and hard working conditions, and they just don't treat you with the same level of respect as a top tier tech companies in Silicon Valley.

That's why it's a little unfortunate that companies like Google aren't making games.

They're not in that game business.

If they were, I think game development would be an excellent field to get into it.

So fun you and they're often working in c++ under type performance limitations, memory requirements and performance requirements.

They have to stay at 60 frames per second, and then the graphics programming portion as well often requires a lot of knowledge about physics.

Shade er's GP use Ah ho set of skills over there.

Luckily, because of virtual reality and augmented reality starting to gain traction graphics engineering is actually becoming a viable field here.

You know, it used to be that you could only do graphics engineering if you're building like a game engine, and that was pretty much about it.

But now you know you could be working as a Google under V R or Air next gen hardware, or maybe simply on some camera app or on creating YouTube video filters.

Now, another area that we haven't talked so much about and I don't hear that much about but it turns out, is pretty popular is data engineering.

Now, what I did here was I went to H and hiring got me.

And you can do this too.

This is a list of job postings from hacker news.

They just scrape the whole website and then format it nicely for you.

And you can see that if I were to look up data engineer, there's at least 80 matches for this.

And so that's pretty much a lot of people are looking for data engineers here.

Data engineering is really about organizing data.

You may have tons of data logging coming in, and then you need to build data pipelines in which you write scripts and save python or something like that, and you consume a bunch of day that you write sequel quarries and then you out.

Put that into a nice, pretty table that is fast.

Cory and then, like a data scientist, may quarry that and just present some data in the nice way.

So that's data engineering.

And then there's a whole bunch of other specialty fields, one of which is machine learning, which seems to be all the rage now.

It's very popular.

I would encourage you that if you are interested in machine learning, and it is a very popular thing that you take a look at some of the job requirements out there.

I don't think it's the easiest thing for entry level people to start getting into.

It requires quite a bit of math and experience in this area to really be effective at machine learning.

And oftentimes it's funny that if I were to ask the new college scratch what they're interested in, 90% of them will say machine learning.

The thing is, we don't need 90% of people to be machine learning engineers, right?

We need, like, maybe say, 10% to be machine learning engineers, and then for the rest you're building like, say, some android app.

I was Epsom back in some front end, and then there's really a whole host of other interesting engineering types.

You have cybersecurity Dev ops, right?

That's like site reliability engineering, And this is one thing to think about.

If you dig yourself into Lynn Nix and Pearl and scripting and bash you next commence.

That's not quite the same thing as software engineering.

It's actually closer to Cite Reliability, Engineering or DEV Ops.

So just understand that there is a distinction between two.

They're both fine careers, right?

Any career is actually fine.

You can just pick whichever one that's exciting for you.

And then there's Que es engineer as well.

And that really has to do with the writing test automation software and coming up with the test sweets to test programs and systems.

Front to back integration, testing unit testing, automated His thing, all sorts of stuff like that, if that's your interest than other more power to you.

As far as that goes, I know that some people they get into Q A engineering, and then they hope that from there they will be able to springboard into actual software engineering, which is a path that I've seen some people, too.

But I would just warn you that if you do take this route, there's a chance that Number one you could be digging yourself deeper into Curie engineering, and it would probably require you to actually be good at that job.

Could be able to transfer out right like you would have to have enough sufficient passion in tests, automation engineering to really be doing that for, say, six months to a year, and you may not be able to transfer.

It may just dig you deeper into that area, whichever path you choose.

I would recommend that you be passionate about the work that you're doing, not just so that you could be in there for, like, a show in my own time and search out because I've heard stories about people who get trapped in these roles, and then they realize that they didn't really want to do this from the first place.

And then that's a whole other messes up.

So overall, I would recommend that you think about the career path that you're taking him.

Position yourself correctly and navigate that focus.

You're learning.

And yeah, I mention this because this seems to happen.

So many attempts.

I've been reviewing a lot of resumes, and here's a quick pluck for tech Interview pro dot com where ex Facebook engineer Joma and I, ex Google engineer, we prepare you for the technical interviews, and that's part of this.

We've also been reviewing resumes, so check it out.

Check interview pro dot com World When the fast track your career, I've been reviewing resumes and I just see some people.

They're all over the place.

They seem to be doing a loop of everything or they may be have been billed the ample skill in something that just doesn't seem very useful.

You Maybe they've been learning some thought net java and then a little bit of JavaScript and ish Timo.

And when look at that profile set, it's just not clear what type of person this is, right?

What is that profile?

Is that a back and engineer Web front and engineer?