Name: ソフトウェアエンジニアのキャリアパスとそのナビゲート方法 (Career Paths for Software Engineers and how to navigate it.)
Uploaded: 2021-01-14T10:17:38.000Z
Duration: 13 min 15 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

Hey, tackling terror and welcome back to another episode of the attack lead.

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.

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.

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

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.

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.

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.

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.

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 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.

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.

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.

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.

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 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.

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.

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.

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.

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.