I have not used recursion in backend code till now. Maybe I thought all these things in college,
that life would be chill and relaxed later. We wrote what just works. Which works. In fact, we would declare a variable as anything. It would work on any of them. Let's see unique How much is it helping anyway? Is anyone using AI right now? I, honestly, use it in my work. So it was so highly sought, that
you just know what you have to do. . Later it would be a trend, they would talk so much. When I open the comments section, out of 100, 10-15
comments would be about, should I learn Java or C++. There's a lot of C++ vs. Java. You tell Nishant, have you used any language in the industry? No. Everyone college does that. They even give cash prizes. Yeah, there are good prizes given. Now it's 45, let's study from 6. Then 6 become 6:30 and the cycle continues. There are many companies who are paying more than that, but students don't think about them. Because it is not highlighted. People consider working in a startup more
cool than working in a FAANG company. When I go in a meetup, I wonder whether
I should say I work in Microsoft or not. I used to apply in like 40 companies. Just opened Internshala and keep applying. There wouldn't be even one reply. So I thought it would be quick, in Sprinkler, out in the first round. Honestly, I even left. For a few days I was like, I would do a startup. All this is illusion and all these things. Hi guys, I am Nishant Chahar, welcome back to the channel. In today's video, we are going to
talk about a lot of interesting things. First the common question, whether I should do Java or C++. That is answered in a lot of detail. After that we discussed, when you join a job. The expectations you have, the things
you've thought about what will happen. Whether that actually happens or not. When you join, then how is work done, how things work, what things you have to keep upskilling. Or is it just join once and then chill. If you are joining at 5-6 LPA. Then how can you increase that in the coming years. There are many examples, examples of many
friends, people around that have been told. So its gonna be a very motivational and interesting video. So watch it carefully to the end. Along that we've discussed how important hackathons are. How to make projects. DSA vs. development, what to do. When to do what. When to code from, first or second year. We've discussed a lot of things. How to face rejections. And lot of things, its a very interesting podcast. So if you're liking this format and if you like
these discussions of sitting with 3-4 people. Then like this video, comment and tell which
other people you want this type of video with. And we'll try to get this done. And along that, let's keep the like aim to 5000. You had got it done in the last few videos. Thank you so much for that. So if you want to become a software engineer. If you want to learn Data Structures and Algorithms. Our Algoprep elite batch is going to start today. Quickly enrol if you haven't done yet. There's a coupon code available, 'FIRST250',
using that you can get extra 250 off. The ones who teach here are the ones
currently working in Google, Amazon. So you get industry experience, industry exposure as well. Along that, everything is taught from scratch. If you don't know any language, don't worry. It will be taught with Java, if you already know C++ or Python even then don't worry. Because all the programs, questions done will
have their code available in Python as well C++. DSA is mostly concept based so
you are taught concepts properly. And its gonna be a very good journey. So yeah, do enrol in the Algoprep batch now. I'll see you in the first class. Let's start the video now. So hi guys welcome back to the channel. Today we have three amazing guests with us. We are going to dicuss a lot of things with them. So first, we'll take an introduction from each
one of them and then we'll start the video. Okay, let's start with Siddharth first. So, myself Siddharth Singh Bhawa. And I am currently a software engineer at Wells Fargo. And I passed out in DTU in 2022 in Information Technology. And that's it. I have an Instagram channel and a YouTube channel. I run both of them side by side. So there's that. And make good videos, recently doing a DSA challenge. Yeah we've taken a challenge. How many days has it been? I uploaded a video today of 58. Now he'll add the 59th day. See for today's, what it will be. Great. So next we have Urvi. Urvi can you please introduce yourself. Yeah, hi I am Urvi. I also graduated in 2022. From IGDTUW. And right now I'm working as a software engineer at Microsoft. And I also teach coding, DSA to students. Great. So next we have Vanshika. Hi everybody, my name is Vanshika. I'm currently working as software developer at JP Morgan. I graduated in 2022 batch from MIT Pune. And I'm currently working on React. Nice. So please tell your Instagram handle. Maybe they don't know you by your name. Yeah so my Instagram channel is CodeCrookShanks. Right, so you might have seen her on Instagram. But she generally doesn't use the name Vanshika. Uses it sometimes, even I didn't know for a long time. So that's normal. I think it's also that we came here after studying DSA in college. And DSA is used very less, the recursion we've studied. I haven't used recursion yet writing my backend code. So you also have to learn a lot of things coming here. So I feel that the end goal thing that I thought in college. There will be relaxation and chill in life after getting out. But its not easy. When you start your job, you have to put in the
effort that you had put in time of preparation. To excel at your job, if you want to
become a good software engineer. You have to keep on learning new things. If you are given a new task, its not
necessary that you've already learnt that. You have to, like, given in time to learn a new thing. If your project changes, team changes, then new thing comes. But if you get a new feature in the team. There will be a new problem. And you have to solve that particular problem. So you have to learn. Also the designing principles, when we made projects in college. We never thought about scale. We never thought about writing efficient code. We wrote what just works. Which works. In fact, we would declare any
variable, int a is going in every thing. It was just that the code should run and it should work. The app should work and all. But you can't do that here. Here you have to write good code. Efficient code. And code that scales. So these things are also new for someone
who comes straight out of college. People say that DSA is not used. DSA is not directly used. Not used directly. But it's like that you learn how to solve a problem. Its about solving a problem, not about, like, everyone
knows what queue, stack is from the childhood. Everyone knows binary search. Its just how and when to use it
which is the main thing that you learn. That binary search is used in this problem. That is the thing that you learn when you do DSA. Basically, yeah, what my perspective
is that companies ask DSA because I mean I don't have a company. But they ask because DSA is a thing that
you can see a person's problem solving. Basically like we are, we are working on different tech stacks. So the companies don't know which person they'll align with what. And plus if they know it, they don't know
how long that project is going to be for. You get recruited and it is going to end in 6 months, so they basically recruit a generic software engineer. To see that, the best is to see how good
your problem solving and learning curve is. You are studying data structure and they know that its a thing
that is difficult to understand, to study, to solve questions. So with that like a marksheet, they have
your track record of being a good learner. So the day you get in a company. Like we know we have to learn new things. So we will be able to learn new things,
that's what they check from us. So in a way, I think DSA is used. Otherwise, what happens in stack, how
it is implemented is no matter to us. You can just use libraries directly. That's what coders do. Exactly, so that is not used, but that tells how much in
dept computer you know, how many concepts you know. So in a way, I think that's why DSA is asked. So generally it depends on which
type of role you are applying for. If you are applying for a SDE role, then SDE is generic. They can get you to do devops, android, front end, back end. So how will they judge for it. That's why they ask DSA, right. From DSA you judge the problem solving ability of the person. So if a new thing comes, they will learn that. If they can learn this. So that's why people ask DSA. Still ask DSA, even though you know
that many things have come, AI and all. But, see, if you don't know concepts, don't know how to
learn things, then even ChatGPT won't be able to help you. Because you have to tell ChatGPT what you want. If you don't know, like how to write architecture, scalable code, you can ask ChatGPT to write that code. But you have to tell what to give. Exactly, we are ones who have to give prompts. It'll write code but if there's an error,
you should have the knowledge of it. So in the current scenario, AI is helping you out. That you can do your work fast. See unique How much is it helping? Is anyone using AI right now? I do use it in my work, honeslty. I use it scarcily. To write unit tests, I give it the code
because Microsft has its internal ChatGPT. So yeah, you can give it internal data and you can use it. Apart from it, Copilot is integrated in VS Code. Then integrated in Visual Studio. So they have the whole access to the codebase. So we can do things by asking questions. We can't do ChatGPT. But ogloop, which we can use, you can
add the whole file in it and its allowed. So there, you can just give it the
function, it can write a unit test for you. And I've used it a lot. Its not allowed in ours but my friends use it on the next level. My friends are in a startup, so they do it so
much that you just have to know what to do. Give it prompt, keep collecting it. Even if there's an error you can do a rectification. But the basic, the labour work of
a software engineer have reduced. Now a few prompts and the work is done. But still the designing part. You need that smartness about exactly what you want. What you want to give in that unit test and what it should do. What the expected output is and how you want to give it. Even writing prompt is a work. You should've the knowledge, it
will just get your work done fast. This doubt about, AI is here it will do
everything, it is not able to do everything. At least not yet, can't say if it will do after a few years. But not for now. Later it will be trend that see they used to talk so much. We are telling according to the present, if
it can think later then even we are not good. Exactly. But yeah, there's still time. But you have to learn the principles. Earlier I had an IOS team. Now I had to learn React, JavaScript. So that has changed. So you will have to learn new things. They just give you a week or two. In college we would take months, a year to learn. We would first set the mood to learn later. Here they give you two months to learn, then the work will start. You'll get bugs, after bugs they'll give features. So the ramp up time here is less. They ask you common things so that
they know you are smart, you'll cope. So that factor remains. Also doubling on what Siddharth said, that tells that DS is only for problem
solving, but the students learning DSA sometimes they take syntax so
seriously that which language to do. And are they just skimming it or do
they understand how to implement it. Or have they memorised the solutions
to problems, this is how it will be solved. But understanding that thing is very important
that companies don't want you to write solutions. They just want whether you are able
to think about the solution or not. That's the point. This doubt does come. Which language to learn. When you are in college, which language should I learn. When I open the comments section, out of 100,
10-15 are about whether I should learn Java or C++. There's a lot of issue about C++ vs. Java. Its a lot. And everyone has answered that question. Yeah everyone knows but they ask me that in the next video. I said, just watch the previous one. No, they want you to comment on this one. I mean you have to tell in every video
regardless of whatever topic is going on choose this between C++ and Java. So which one did you do in college? I did C++, I will tell the login behind that. Basically in our college, in the first year C is asked. In everyone's college. The latest C. So when I read C, I thought C++ must be close to this. Its just '++'. Yeah. So I did ++ and learnt C++ and that's what I continued for DSA. But when you do Java, then also its good. And I say, if your college doesn't do C, then do Java
because many companies have work on Java springboot. And in general, Java is comparatively
easier because there are no pointers. When you do C++, people get stuck the most on pointers. They don't understand. Java is comparatively easier because all these things are not there. Now we've answered, still it will be asked in next video. So even I did C++ but I basically did all
the languages because my course had them. That's why I did C++, Java, Pro level. And Python, I mean I knew basic. Now converting code from one to another is done with Google. That is different. Now Nishant you tell whether you've
used any language in the industry. No. . So, earlier I worked on Swift. So Swift is similar to Python and JavaScript. So the code is very mixed of Python and JavaScript. Syntax is comparable to both. So that was completely different,
there's no relation of C++ to Java. Objective C is also, is used in IOS
development that too before Swift. So, some old code is in that. So C, C++ concepts are used there, pointers are used, just as C. So when I needed to change anything in that, I used it. Apart from that, I have not used anything else. What about you guys? I started with C++. But in the end, I started focusing more on the development side. Front end development side. It is visible what you are doing. Its fun to see that the colour of the button is changing. So most of the people have this question, whether to use DSA or go to development. What to do So I believe that DSA and development
both are important in applying for jobs. Basically DSA tells the learning curve like we discussed. Development shows that you are
able to implement things practically. Basically company wants you to do development after coming. They won't give you DSA questions. So development is basically you show that
I've done this and I've created a project. So in a way, development is used
to show how good your projects are. And then if projects are naive, that somebody is using. Then you are considered at another
level, they've done something practical. So in a sense, I think DSA and development both are important. But which one first? First I think do DSA. DSA is basically your qualifying thing. Now 100 out of 100 people have done DSA sheets. The 400 questions in the market. Now tell what's the difference,
then knowledge and all that matters. How good you are. The more good your development is Two people of DSA, ofcourse who has the
better projects will have the upper hand. A lot of things come into it. Sometimes it depends if you have added
projects in your resume, then they can ask it. If your ratings are very good, then
maybe they'll ask you questions. One more thing, for me, you know what
the biggest benefit of making project is. Suppose you are in an interview, and
you don't have projects in your resume. Then I don't have any option, DSA questions, competitive
programming, whatever you've added in the resume. I'll ask according to that. But if you have projects in resume, project is a part
where basically you drive how the interview is going to be. If I say that I've created this project, I used React and this. Now the person will ask about React. I've already studied React and saw
the most asked interview questions. Now in this, you'll give a direction that, you'll say
that I've done this, then it will be asked from there. So here you drive the whole interview. For the 15-20 minutes. Otherwise if you don't have project, then they'll
ask you DSA question that you don't know. If you are a fresher, your main point to showcase is project. Exactly. What work is in this, that only interviewer will see. Put a GitHub link. That will help. That you have the knowledge of this thing. And hackathons help a lot. They do help a lot. Because, first, you have projects, then if you've
won some hackathon, it becomes an achievement. Plus team work and you are not
doing everything yourself in hackathon. If you are going with four people, then one is doing front-end, one is
back-end, or two front-end or back-end and one is something else. So you have multiple people doing things. So it shows collaboration. Everything is seen so. Hackathon is a very good thing. I made one project in the first year, that
too when I went to SIH in the grand finale. So that was very reluctantly on why to make projects. Like Vansika likes to make projects. I used to feel like, what is all this hashtags and all that. I used to just understand int. I didn't understand all of that. But due to that hackathon. And I am telling honestly, we just gave that for fun. The idea is there and we gave it. Later we get to know that we got selected for the grand finale. Then we really had to do it. That made us our project and also got an achievement. And everything got done. Also learnt. Learnt too, because of that. So that's what happens, you learn a lot by going in hackathons. Plus networking is done, you get to meet people. It is a very new experience. You get exposure of doing things. Not just hackathon, I think even taking
part in coding contests is really beneficial. And almost every college today are doing tech fests. So if you go in those, I don't why students don't do it They think someone is doing sophisticated coding there. But in this, there are chances of winning
because it is done on a local level. And even the prizes are very good. And it boosts confidence. Hackathon is for development and
coding contest is for DSA, basically. If you do DSA then you can give and go coding contest. There are many of them. Every college does that. Even give cash prizes. Yeah, they give very good prizes. So definitely if you don't participate, then you should. There is a scare factor that if you
participate and nothing happens, then what. So they don't apply because they're
scared, or just don't participate. But they should, as you'll network, you'll grow, you'll learn. Exactly, nothing will happen there, nobody judges. The judges there don't care. If they meet you again, they'll say
they've seen you in the hackathon. Not that you didn't make any project. You get to network with people and its good. Basically, if you put yourself in uncomfortable position. Then you'll be able to do it. If you don't, and just think that you've
become perfect, college's best web developer. Then only will I go, then you can
just sit for 4 years, you'll do nothing. But think like, you don't know web development. We made an app named shopper worm, names it anything. We didn't know any app development,
but we gave the idea, now we have to go. So we had to made it, then in pressure,
being an engineer you have to do it. So we would do it. Don't think like the best time Don't wait for the best time. Yeah, that then only will you give hackathon. You should not wait for the best time for anything. Best time is right now, just after this video. Just go and do it. I want to learn development, DSA, anything,
I will start from tomorrow or from 1st January. Or 1st of this month, or sit on 5 o' clock. It used to be like this. Now its 5:45, I will start from 6. Then that 6 becomes 6:30 and it keeps going on. Everyone does that. So don't do it, we've done this mistake, you don't do it. There's another thing. This 15 LPA, 20 LPA, 30 LPA, 40 LPA thing. So, people's success metric has changed a lot. Earlier, we used to be like that we've got placement, its good. When I joined college, my success
metric was that if I get a job of 12 lakh. 1 lakh per month. Then I'm happy. That was with me because I used to see seniors. Everyone was like and average college placement would be that. And like time goes on, everyone was like, no I want 50. What is your take on that? So, according to me, what's happening right
now is we don't know who is wrong here. But as you are seeing on YouTube, this guy got
in FAANG, Microsoft, this achievement and all. So when a college student in first year, they
automatically think that Google, Microsoft is the target if they don't get in it that means they didn't do much in college. Its practical that these companies will only take limited people. After that, people go in other great companies. But in that, assume if a person gets 5 LPA,
then they think that my friend got 20-25 LPA. Their life is set. But think that in a way, you got 5
LPA, you are starting your career. When you are starting your career with
5 LPA, basically everything is long term. If your friend has gotten a 20 lakh
package, does nothing in the company. Then maybe his 20 will become 30 in two years. But if you are from 5 LPA, I am
telling about my friend as an example. He started from a Tier-3 college last year. And he started from 5 LPA, now just
one year later, he has come to 13-14 LPA. So you can see, the Tier-1 college,
if you see their base salary pay, then it is 13-14 LPA. It is around 12-15. Now that person came from Tier-3 infact without doing DSA. So don't think that you are a fool for starting from 5 lakhs. Think that, that is your start. And many students who are coming from Tier-2, 3 colleges. They are already demotivated that the
companies don't come in their college. So we don't have a chance. But there are many people in my
team that are from Tier-2, 3 colleges. They went to some other company. They worked there for a year. And then they joined Microsoft. Because after that companies don't
care from which college you are from. The work. Yeah, they focus on your skills then. Industry experience is important. Right, if you can't get your dream, FAANG company directly. Then you can work somewhere else for a year. Learn there and then you can switch a year later. And then you have endless opportunities. Right. See, this is also somewhat our fault. The video that we've made and showed them. Basically, I will tell you something honestly. A content creator is doing what people want to see. So, if people are seeing that they've used
Google, Microsoft from their childhood. Then they want to see it. If I do, how to become a software
engineer at JP Morgan, Wells Fargo. Then they won't see it. So basically content creator use the
psychology of what the people want to see. Now due to that, a lot of hype was
created that that is the only success. But that is not the metric of success. You just start, from 5 LPA, 3 LPA, whatever. You have your own journey, so
what if someone start from 20 lakhs. Basically, if he doesn't continue that
hard work in the long term ethics then you will surely surpass him if
you are hardworking in the long term. And we've discussed that end game is not getting a job, end game is surviving for a longer
time and learning, keep on learning. Becoming a better software engineer. Keep upskilling yourself, keep learning new things. Many Tier-2, 3 colleges don't even have DSA. Like, they don't know that DSA is also important. I've talked to a lot of people. When they graduate, after that. We had a meetup in Algoprep, in Bangalore. So a lot of students came there that
were already graduated in 2022. In 2023, or '22. So they are doing the course now and told that
they didn't even know that DSA is important. We saw your video later, someone's
video that we got to know about this. So people don't know about it. And the awareness. At least if they see any of my video, they
are benefitting that they have to do DSA. So they get to know what to study. And its going to the mass audience
that, yes these are the things to do. Awareness is coming. Basically but don't make that as a metric. That someone's in Micrsoft. That doesn't matter. Just start from anywhere. Just start. And even I did a lot of podcasts,
they reach 15, 20, 50 from 2.5, 3, 5. Its more about improving your problem solving ability. And keep on learning. See SDE-II, III from Amazon. Amazon doesn't judge anything. They just want that you have experiene of three years. And just clear the interview. They don't care if you are from Tier-2, 3,or 1. Infosys, TCS, it doesn't matter. So just focus on that, fix your problem solving ability. Also, more than FAANG, Microsft, there are
companies who are paying more than them. But students don't think about them. Because it is not highlighted. They don't have that powerful brand name. When I came to Bangalore, I've noticed that people consider
working in a startup more cool than working in a FAANG. Learning opportunities. Yeah. So when I go to a meetup, I'm like
should I tell I work in Microsoft or not. That is normal now. Earlier this was considered that, wow
you are working Microsoft, Google. Now, everyone's doing it. Now it is more interesting that if someone's working in a startup. That is more interesting. I mean, that also has its own benefits. Startup vs. MNC has a different We'll do this with someone from startup. It has its own benefits. Both have their own benefits. MNC's benefit is that you have multiple teams. So in every company there will be
team which is working as a startup. If you want such team in Microsoft that has
just started now, a year and a few months. Then startup type work is done there. So, you are there to choose it. But what's happening in startup is as it is. You can't change there. You don't have the option. And then it comes to security, it will shut anytime. You will have to leave then, there are XYZ reasons. But yeah, it is cool. You do things quickly, getting funding rounds. Your ESOPS value can go upto 100x. I think there's a lot of learning in startups, basically, my friends were from Tier-3 so they went to a startup. But, comparing my knowledge to them
now, its a difference of day and night. Because they implemented so many things, so quickly. Because you have to regress a lot in startup. And they have to do things end to end. Yeah, exactly. That is, we people touch a little part of a very big codebase. They are making things end to end,
their knowledge gets killer, is what I think. In fourth year, the person who was same dumb as me. Now, you can see him. He has become different. They handle front end, back end, everything. So, its just that no one is dumb, honestly. Like, no one is dumb, everyone is smart. Its just that, how much effort you put into certain things. The more effort you put, the more you practice things. You will get better at it. Its not that, you won't get it tomorrow if you can't get it now. Its not like that. Just give it time. Even we were not able to do it in first go. Even I was not able to write the code for recursion. Even I used to write it wrong. Its not like I did not face any rejections. Or Siddharth hasn't. You didn't learn to walk in first go. It takes time. You first stumble, then you walk, its the same. And everyone faces rejection from companies. Like I did. At the time of intern, I sat for like 15, 20 companies. And I got rejected in two after getting into the final round. Reached the HR round and got told
that we are taking them not you. So everyone faces rejection. Everyone does mistakes. They learn from mistakes. So, you will do it after getting rejected from 2, 3, 10, companies. When I was in second year, at the time of
internship, I used to apply like 40 companies. Just opened Internshala and just applied. There wouldn't be even one replies. To get demotivated and shut it, that's not the right thing. Keep applying, at least you'll get one reply, sometime. And there's also a difference
between on-campus and off-campus. Like, Vanshika you must have applied
to multiple companies off-campus. You were from MIT. MIT, Pune. Right. So, not many companies must have come
on-campus, there would be but less comparatively. Yeah, comparatively if you are talking about FAANG. Then they don't come. So in the end, its not like just don't go in on-campus. And just focus on off-campus. Both are important, if you are sitting in
off-campus, do sit in on-campus too. But yeah, if you have too big of an
aim and you want to fast forward. Then off-campus will be a better
way if you are from Tier-3 college. Off-campus is difficult. But its just that keep doing. If you apply in 100 companies. 10 will revert back to you. There will be interviews for 3-4. So, its just increase the no. of applications. That if you were doing 50, 5 interviews are coming. Then make it 100, then you'll get 10. Success chances increase. Basically, don't attach your ego to your rejection. Don't think that you are the fault because you got rejected. You have to see why you got rejected and improve. But don't think that why am I dumb. I mean, I'm telling you, I mentioned DSA, 450
questions, hackathon, projects and everything, and in my mind it was like, now
I'll get an internship in just 5 days. So basically I thought that I will quickly
get internship but then as companies came. In the first 10 companies, there wasn't much on coding round. Then came sprinkler. It has the most respect in our college. Directly 30 base. So have to get this one. And in that I got shortlisted in the coding round. For me, I was doing each of their coding rounds, was able to do everything because my CGPA was above 9. So I was able to sit in each of them. So I thought it would be quick, then I got in sprinkler. Out in the first round. But I thought, alright no big deal,
I didn't get in the 10 companies. I would be an intern in the next 15 companies. Now a month got passes, 25 days, didn't get in
one company and I'm sitting in all of the companies. All of the companies in college. So I got rejected in 34, 36 companies in college. I don't know why I'm not getting shortlisted in the coding round. How people are shortlisted. You are not given any reason, you are just rejected, simple. So at a time, I took it to my ego. Maybe I am not that smart because
people around me are getting internships. But in way, I even left it honestly. For a few days I was like, let's do a startup, all this is illusion. Don't get into these things. But then, my friend has a guy in IIT,
friend from coaching, he phoned him. Then he asked how its going, he had gotten into Microsoft. He had gotten good, what's with me that's what I could do. So he said, the no. of times you've talked to me. Everytime you're saying I won't get it, I won't get in. For once think that the ones coming, the 15-20 companies. You are the one getting placed in it. First think that. Manifest. So I honestly manifested that the
companies coming now, I'll crack them. That is, I was doing in them but I wasn't able to. Then next came Wells. Wells interview directly came, first
coding round, it got done quickly. I sat in the interview, quickly got done and out. Then you can think that I was in a sad state for 35 days. I won't get in And in a day I started getting respect. See he got his internship. That's how you code. In that, one important factor is of self confidence. Until you don't think that I can do it, then you won't. And you will be beat down, your self
confidence will be lowered repeatedly. When you get rejected, you'll feel that I was in a different space. There's nothing like that. But you have to understand, keep doing. You will see that people around you
will have already started to be miserable. Leave coding and all, there's nothing in it. Only these people get in, not everyone gets in. Now you have to think that, just study yourself. So you will go over them because they are already miserable. So they've already given up. So, it is not over until it is over. Positive mindset. Yeah, this is really helpful because
everyone tells to do coding in placement. You'll everything coding, DSA, project. But if you are good, have good luck you will get in the first time. But either you will have to go through this phase. And this phase, not everyone discusses it so everyone feels like all these people, Nishant, everyone got in, there
was a placement buffet and took whichever company. Nothing like that happens. Everyone has worked hard. Everyone has faced rejections. And this, what you said now. That is very important right now because students
are very demotivated because the hiring freeze also. That is currently going on. And that is something which is out of control. Nobody can do anything about it. It is what it is. There is one thing about it. See, there are a lot of startups in India. And many new startups keep emerging then and now. Like even his friend started with a startup, a lot of them. So start applying to startups. If MNC's are not hiring, you have the
target of Google, Microsoft, don't worry. Why that's the target, leave it. But start with a startup. At least get a job, start getting experience. Learn new things and then apply after one year. Microsoft is not going anywhere. It won't be any trouble even if you join after 2 years. If you just want to join it. And when you join 2 years later, you will be
earning better because you would've experience. There will be more skills than people who are starting. One hack is that, generally those in
the company before you are paid less. And the new hire get more. So keep that in mind. Freshers joining Google, Microsoft have generally less salary. If you go in after a year or two,
then your salary is generally more. Base salary is, can't say about the rest. CTC and all. But yeah, you get more. That factor is also there. And after coming in startups, companies
recognize that this person knows things. Even I started with a startup. Interviewer knows that this person is from
a startup so he is already knowledgeable. I have seen that this is not true vice-versa. They think that someone coming from MNC is a mild guy. I mean, I've seen a college friend works there. So he said they don't respect MNC guys much. Because we know they come after relaxing in the office. They are used to it. They get spoiled. So startup ones are trained. They know how to do it. That's the thing. So, first of all, tell about what do you work. The first doubt of any student, currently in college,
what people work as a software engineer, what do they do. When they go in a company, join it. What is done? People say 9-5, but what do you do in 9-5. We also used to get this doubt, I used to have that. I have seen a lot of videos, even made them. So A lot. So, that is a doubt. So like, what do you do? So basically, we do coding, but it is a chill life. If I talk about chill life, software engineer's
life is, you can manage time yourself. Its not like exactly 9-5 as it is told. You'll see that in very few companies. You are given a task and basically you
have to complete that task in a sprint. This is our target, sprint is basically giving a task in two weeks. So there's that. Now talking about work, for me,
our work is majorly of two types. One is either you develop a new thing. Or second, you are maintaining an existing application. So basically my work as a software
engineer is to maintain an exisiting application. If we have to add any new feature, we are
adding all those feature for new clients. So basically this is my work. Other than that, what are your works? And one other thing, sprint depends
upon company to company, team to team. Like his is two weeks. Mine is of a month. For some people, it can be 6 months, 3 months, it depends. It changes product to product. Day to day tasks change according to that. For example, his is two weeks. So it will be tightly packed. What to do in 10 days. Two weeks mean 10 working days. So you have to tell these things I'll do in 10
days, all this will be shipping in tihs sprint. So it depends. Now, if its of a month, it will be a little chill. It will be more chill. Then you are managing it according to yourself. But then, people can also be lazy,
they are doing it at the last minute. So there's also that. That's why we don't follow it. Generally that's what happens. Guess they recognized Siddharth so they kept it for 2 weeks. I think all of the engineers do this. They wait at the end of the deadline to complete. That's what they learnt in the college. Studying two weeks before exams. That's how engineering is trained. And what do you do? So, I think initially when I started working, at that
time, mostly my seniors were giving me tasks And they were very defined tasks. You have to code this thing and write these unit tests. But after one year, its shifted to now they tell me this is the
work to do and I have to decide myself how to design this. From whom to get approvals, to get reviewed,
how to write tests for it, how many tests to write. So that is slowly changing and I
think, its as you progress in this field you won't get told exactly what to do. You have to figure out yourself, so along your coding,
your designing, collaboration part slowly increases. With time. Right, true. Initally, you are spoon fed for a while. Absolutely. This is the task, managers or senior member or
team leads, whatever tell you this is task to be done. Write unit tests in this, do this and that. After some point of time, you have to
take up a task and drive it all yourself. So that comes after around 1-1.5 years. And yeah, what do you do? My sprint is also of two weeks. Do finance companies have sprint of two weeks? Yeah, we do. Tight budget. So basically, when I started they explained everything what exactly is the structure, architecture and everything. Then slowly you will learn how to build small features. And then they'll give you the whole feature. Build it completely end to end. So, you learn basically. And the main thing I observed is you get very collaborative. You have to talk with product managers, with everyone. And which is a very good thing, I believe. Interacting with anyone. We don't know initally what to do. Then when you start working, you have multiple things. Like with one team, designers are
working, along with product managers. Product managers will define you to make X Y Z things. And designers will design it for you. Now more than half the time it is not feasible. They design anything. And when you code, it becomes a problem. I mean it happens in front end. In back end teams, it mostly won't happen. Yeah, it is already defined clearly in back end. And if you get a story in sprint, story is the task we have to do. So it is reviewed, project managers review it. These are the changes to do, they have analysed. Then you have to see those changes and review it. Where to change, how to change. Which files have to be changed, we have to decide that. And then we do changes. But you don't have to do it with designers. Yeah, we don't have collaboration with design. But still with project managers. Project managers basically take business decisions. They have to see how many users,
what users want, what to add, delete. So that is important. Now the next thing is, when we were in
college, the end goal was to get a job. But after that, we thought now there's
a job, nothing to do after the job. Just port code for a while, work is done. But what do you feel. Is it different after joining a job? Or how different is the expectations and reality. Expected is that we'll go, everything will
be wonderful, there will be work to do. And then copy paste from stack. Just code it. And now ChatGPT is there. Ask ChatGPT and everything will be done. But does it happen See it is half true and half false. In a way, the dream life that we think, we will code and just go. That in a way is happening. You have a lot of flexibility. You can work anytime. So that is true. But what happens is it depends on your situtation. If you are given the same thing again and again. Then basically, your excitement of joining,
learning new things, you will get stuck in that. I am doing the same tasks again. But if you get opportunity to work in various works. Then your journey after becoming a
software engineer seems more interesting. Wow now you are doing new things. So that is a factor and it depends
on the type of work you're getting. Makes sense. So there's a last part. One suggestion for people who are in their college. Who are trying to get a job. Any suggestion that may be coming in your head. And we'll wind it up. You start, I've talked a lot. Okay, I'll start. I mean I always say, I'll repeat here as well. I would say, don't make your end goal of just getting a job. Make an end goal of becoming a good software engineer. And when you start carrying for a job. When you start studying DSA. Then only make that aim in your mind. Because when you are aiming to become a good software
engineer, then you will learn problem solving skills. And when you learn that, the job will be easier to get. So yeah, that's what I would say. I'll say just, you do have to study, that's there. But you have to be, networking is very important. So, okay you're in college, study,
but networking is also very important. Be active on LinkedIn. Job opportunities are mostly on LinkedIn. So this is very important. Then, hackathon as mentioned, participate in them. Join communities. Because there are a lot of inner discussions in the communities. And you get job opportunities in them, internships. So these things are important, I believe. Generally, from communities to hackathons
can also get you direct job opportunities. There's Flipkart's hackathon. Various companies, Myntra has it. So do participate in challenges. Doesn't matter if you win or lose. At least your data will go to that company. You'll get entry into the database. When you apply again, by chance if they need
that tech skill later, then they might contact you. So try to apply to these companies. Apply to as many hackathons, opportunities there are. And keep giving coding contests. Exactly. Do you have anything in your mind? You all said very good things. From me, basically, if you are in
college, I'm telling a generic way. Keep things balanced. There should be a fun element in
college, and the coding element. Because you have to do good career
wise and there should also be memories. Not like, I was just sitting in front of my laptop, terminal. So basically, keep everything balanced. And always, don't think that how does Nishant
manages all this, YouTube channel, software engineer. Everyone, in a way, focused majorly on one thing. Then when it got sorted, they started another thing. So if you're also in college, now DSA vs. development. Everyone has that they'll manage both. So first do DSA once. Now start development after that, just continue doing DSA. So the person in front will think, man
he does DSA and development both. But actually you focused on one thing. So if you're learning anything in college. If you have to work in your passion. Then pick one and do that, then build up on it. Priority. Yeah, if you do multiple things once. You can see it will be problematic. Sorting priority is very important. Like he said, start development and keep doing DSA. That means keep giving contests. Do one questions a day. Just keep it in touch. Give contests on weekend on Leetcode. So that will keep you in touch, won't forget it. You did 6 months of development
and you can't even write syntax. You don't know how to write DP, how to make graph. So that is not right. That should be in continuation along with it. So yeah. Thank you so much, thank you everyone for taking out time. It was a lot of fun with you all. And thank you very much for coming on such a short notice. Siddharth has a meeting right now. So he'll join the meeting. A meeting with US team. Have to run quickly. Yeah, so thank you so much. Do like the video. You can follow them on all the social media platforms. Link is in the description. I'll see you in the next one. Bye!
