Sunday, June 26, 2022

SOFTWARE ENGINEERING CAREER | SDE 1 Vs SDE 2 VS SDE 3 | Salary | Roles | Work | Expectation

What does a software engineering career look like what are the different levels that are present in the software engineer's career and what comes after sd3 what are the different roles responsibilities work and salary at each of these levels and how does one get promoted in their career if you are ever so slightly interested in software.

Engineering as a career then this video is absolutely right for you this is your host swamiji bhattacharya and welcome back to another video in my channel before starting i must say the like target of today's video is 1.5 000 likes so go ahead and smash the like button subscribe to the channel if you have not already hit the notification bell and.

Share this video among each and every one of your friends and peers that you know now without further ado let's get started before starting i have a very special message from cryo trio is one of the leading edtech platforms in the country.

Which focuses on project-based learning rather than video based learning they have two amazing software development tracks one is back-end development track the other one is full stack development track both of these tracks have amazing amazing industry great projects which you will be building hands on and you can add them in your resume as well.

Not only this you will get support from industry leading mentors teaching assistants as well as you will also get exposure to a lot of amazing latest technologies including aws react java spring boot mokito and much more to get a glimpse of how projects are made in the industry you can get a 10 percent discount using the code show magic i.

Have given the link in the description below so go there and definitely check out the courses you can even avail a free week completely to see if it is for you and then definitely use the code so magic to get a 10 percent off software engineering just like any other profession has multiple different levels in it as and when you progress through.

These levels your salary changes by quite a lot as well as the work that is expected out of you the roles and responsibilities also shift by a huge margin obviously as you move from one company to another company the name of the levels might be different the years of experience that is required to be at one particular level might be different.

As well as the number of levels might be different but in general the essence remains the same typically speaking these are the levels that are present in most of the tech companies as soon as you join any company as a college hire as a fresher you start from sd1 slowly and slowly you progress to becoming an sd2 then you get promoted to an sd3.

Which is also known as the senior software engineer after sd3 comes star software engineer which is followed by principal software engineer and ultimately you can become a distinguished engineer now the question might arise like how many people actually end up becoming a principal software engineer or a distinguished.

Software engineer to answer your question it really depends from one company to another company for example it's relatively easier to become a principal software engineer in oracle however it's relatively difficult to become principal software engineer in amazon to be honest the principles of the engineer that i have worked with in.

My previous team had 46 patents to his name and 80 more in process so yes it is definitely not everyone's cup of tea generally speaking if you see staff software engineer is normally the terminal level of a software engineering career at big tech companies now let's dive a bit deeper into all of these.

Levels and try to understand how the salary changes how the core work expectations responsibilities as well as your day-to-day activities change as you progress through these levels one after the other we will start from sd1 as soon as you graduate and enter the workforce you start at the level of sd1 also known as software development engineer one huh.

For example in some of the companies it is known as member technical staff and some of the companies that is known as associate member technical staff some of the company that is also known as software engineer too for example in case of google and walmart the levels start at software engineer too but the expectation from a fresher is that.

Of nsd2 the expectation is still same as that of an sd one so that humlog opening mental sanity maintains video we will only stick to the standard definition of the rules hence we start with sd1 the years of experience generally required to crack the role of sd1 is greater than equals to zero years of experience this role is also geared.

Towards fetches apart from industry hires with one to two years of experience typically speaking if you are working in a company at the role of sd1 then you should expect to get promoted to the next level in around 20 months of experience in that particular company obviously speaking the promotion does not happen on the basis of how much time.

You have spent in one particular role but mostly happens on the basis of your own performance hence if you are spending more time in a role but you are not performing up to the expectations then more likely you will not get promoted just because you have spent x number of months in that particular role generally speaking as an sd1 most of.

Your work will revolve around coding hence the interviews if you see the interviews of sd1s across different companies they are more focused around bsa coding as well as problem solving because these are the major things that you will be responsible for in your to day work you must have heard about low level design high level design and so on.

And so forth but as an sd1 your primary responsibility is to take the design that is given to you and convert the city design converts the set algorithm into production ready code and hence the stress in all of the sd1 interviews on coding and problem solving does this mean as an sd1 you will never be doing it low level design and high level.

Design in your day-to-day work the answer is no that's not the case as i said your promotion will depend upon your performance and typically speaking in the industry you only get promoted once you start working consistently at the next level which means once you start consistently working to at the level of an sd2 for a period of let's.

Say six months is only when you get promoted and to work at the level of an sd2 obviously you would have to take on all the challenges all the things that nhd2 generally performs in the day-to-day work in order to get promoted your day-to-day work as an sd1 will generally revolve around supporting the application that is already present in.

Production that is of paramount importance apart from that you will be responsible for researching about different technologies writing production ready and optimize code for the products that you are working on as well as interacting with different people that are responsible and related to the product that you are working on.

So that you can learn and grow in order to get promoted from sde one to the next level which is sd e2 apart from doing all the responsibilities that are expected out of an sd1 you should also take on more design based challenges you should be actively contributing towards the design reviews that happen in the team you should be doing design both low.

Level as well as high level design with all the design principles to build products apart from that you are also expected to actively contribute towards food reviews and mentoring new hires and intern if you showcase these responsibilities properly for a period of let's say five to six months then you can definitely expect to get promoted.

Generally in many of the companies you are the driver of your career so if you want to get promoted then you have to have that conversation with your manager and showcase all the data points that you have collected that showcases that you are already working at the next level as a new higher sd1 the expectation is that you will make.

Mistakes the expectation is that you will require some amount of hand holding as well as you will not know things in depth in detail and that is okay because that is something that is already expected out of an sd1 that these things will happen now coming to the level of sd2 the expectation out of any new higher sd2 level is drastically.

Different than what we just heard for an sd1 in case of an sd2 you are expected to be independent as well as it is expected that you will not require any hand holding now this does not mean that you cannot reach out for help you can definitely reach out for help but if there is a solution available it is expected that more often than not you.

Yourself should be able to reach to the solution from a technical competency perspective it is expected that you will be super good in low level design as well as high level design this is because right from the start right from d1 you will be entrusted with building products at scale by employing all the techniques and all the skills that you.

Have learned in your past experience with respect to system design you are expected to perform all the roles and responsibilities that an sd1 performs flawlessly which means you will be supporting production applications you will be researching about the code that you will be writing you will be contributing by writing meaningful.

Optimized codes you will be consistently doing code reviews design reviews as well as you will be responsible for making architectural decisions for your team as an sd2 you typically become owners of different products that your team is building which doesn't necessarily mean that you will be developing each and everything in those.

Products that you own however it certainly means that you will be knowing everything that is going on with respect to the products that your team is building as well as you will be knowing what all things and improvements that you can do in order to make the product better day in and day out you will be interested.

With ambiguous problems to solve what do i mean by ambiguous problems these are those problems just a straightforward solution and you will be interested to talk with the different senior engineers that are present in the team to talk with the business of the team get the requirements understand the requirements.

Properly and correspondingly propose solutions to solve it generally speaking the years of experience for an sd2 role is somewhere greater than two years of experience this particular upper limit i have seen people with even more than 10 years of experience as well working as an sd2 similar to an sd1 to get.

Promoted as an sd2 you have to show that you are working at the level of an sda3 for at the very least six months as an sd3 the expectation out of that role is remarkably different than that of an sd2 and sd1 as an sd3 you are generally the senior member of the team all of the people in the team including your managers look up to you your work no.

Longer is limited to the scope of your team but in general gets expanded to the scope of your organization you will be responsible for making architectural decisions for influencing architectural decisions all across your org your scope of the level increases drastically once you start taking up those challenges which are not only just impacting your.

Team but also your org as an sd2 you tend to get promoted to an sd3 generally speaking as an sd3 the years of experience required to start at this particular role is somewhere around six years of experience and there is no upper limit to the edge cap i have definitely seen people with 15 and 20 years of experience as well working as.

An sd3 and it is perfectly normal as an sd3 you will be always given the most ambiguous problems to solve and deal with as an sd1 and sd2 typically you are given some form of business requirement document on the basis of which you create your solutions however as an hd3 you will be involved in problems which you have never seen before you will be.

Involved in problems where the problem space in itself is not defined properly properly and you will be responsible for defining the problem space creating a meaningful problem out of all the information that is presented to you and come up with a solution you definitely will be regarded as a technology leader not only in your team but also your.

Organization you will be owning key technology components across your organization and will have good amount of influence and impact on them from your day-to-day work perspective there are some teams in which as an sd3 you are still expected to support applications in production and there are certain teams in which you are not.

Expected to support applications in production so it completely depends from one thing to another as an sd3 you are expected to be a force multiplier which essentially means that not only you will be doing your work absolutely that's the case but apart from that as well you should have enough influence across your team so that you can make other people.

As well to meaningfully contribute towards the work that you are doing yes because that's how you will be able to drive meaningful changes across teams from a compensation perspective as an sd1 generally speaking in most of the product-based companies the compensation range varies between somewhere around 15-17 lakhs per year to around 30-35.

Lakhs per year as an sd-2 in most of the product based companies the compensation range varies around 40-45 lakhs per year to around 80 lakhs per year as an sd3 the compensation varies from somewhere around the 1 crore per year to around 1.7 crores per year all of the compensations that i have talked about here they are yearly compensations which.

Is the yearly salary that you will be getting in one year as and when you progress through different levels right from an sd1 to hd2 to sd3 the salary also increases exponentially so much so that the principal engineer salary can even cross 2.7 crores per year in india and as a result the work the responsibilities the type of work the.

Expectations the roles everything drastically changes i really hope that i was able to put some light around the entire software engineering career now you might say that after becoming an sd3 after becoming a staff software engineer what does one do in their careers now it is an extremely personal opinion and definitely speaking it will.

Change from one person to another uh what i have seen typically is that many times people do end up taking uh positions like chief technology officer positions like director of engineering and smaller startups in order to progress their careers based upon individuals interests sometimes people do end up staying in their company.

Itself sometimes people do end up getting to the role of principal software engineer and so on and so forth there are a lot of ways in which a particular person can progress not only this in most of the companies as well there are parallel tracks with respect to engineering and management so certain times people also.

Transition from an engineer to becoming an engineering manager and then grow in that particular level as well i really hope that you found this video extremely meaningful if you did then smash the like button the like target of this video is 1.5 000 likes subscribe to the channel if you have not already share it among your friends and peers as much as.

Possible it will definitely help each and every one a lot do comment down below what different kinds of videos you would want me to make i'll gladly make them this is amazing building goodbye that's with dania you're a superhero

RELATED ARTICLES

Most Popular