Get hired as a software developer in FAANG like companies

Programming, Html, Css, Javascript, Php

Resources to get hired in one of the best IT companies :-

    Topics you need to cover before applying for the roles:

  • Data-structures and Algorithms: 

    Start solving questions on platforms like GeeksForGeeks and Leetcode as only way to get hired in MNC's is through practice. Mine goto place for interview prep is Leetcode's inteview questions https://leetcode.com/problemset/all/?listId=wpwgkgt&page=1.

    And I'll suggest if you are starting early then you should follow the questions from this repository  https://github.com/AkashSingh3031/The-Complete-FAANG-Preparation , it has almost everything that you need to cover for interview.

    You can also follow SDE sheet provided by Youtuber Love Babbar the link for the same you can find here. I would suggest you to keep track of questions you solved and also make notes for certain concepts of important questions, now how you'll know which is important, then for that visit must do interview questions from GFG.

    GFG and Leetcode should be your goto place for interview prep according to me.

    There are various video lectures out there but I'll say follow editorials more and for videos Abdul Bari Sir's lectures are more than sufficient.



  •  System Design: 

    A proper pathway along with courses to follow and books to be read, all of it is available in this repository, the admin of this repository has curated a great study plan of 100 days for system design. Finally for final revision you can visit this repository for interview specific questions and how to answer them.


    Gaurav Sen has also curated a great video tutorials for system design resources.


    Here are some insights that would help you become a better developer. 

  • Keep reminding yourself that you are there to learn: A major mistake that most developers do is that they tend to skip some concepts which they feel that they already have an idea on. Doing so makes you miss some essential concepts which might cause a problem for you in the future. Learn everything with the mindset that this is the first time you are learning it. Never be overconfident.
  • Start writing code every day: It may sound obvious, but you've got to start writing code every day. You might be busy, but trust me there's a reason we all keep telling you to write code every day. It's because it works. Writing code every day keeps your skills sharp. Each day you will be learning something new by applying the things you learned into a code.
  • Don’t be afraid to make mistakes: Mistakes happen. Especially when you are coding, encountering an error is very common. You can see the number of developers asking for someone to solve their error in stack overflow every day. Try to have a positive mind and approach the problem with confidence regardless of how many errors you counter while solving the problem.
  • Try to build your own projects: This one can be easier said than done because finding time to do this can be tricky unless you are super disciplined or have lots of spare time in your week (which I doubt). Only when you apply the things you learned in your own project, you will understand things deeply. You will have the experience to start a program from start to catch. It gives you some specific goals and targets which are easy to measure. This helps you see your progress, and it quickly lets you know what kind of skills/tools/technologies are missing from your toolbox. Then when the time comes later on, when they become relevant in a real-world project, they won't be as unfamiliar as everything else around them
  • Learn the logic, not the syntax: Programming languages, tools, and methodologies come and go. That’s why it pays to get as much experience as you can with as many languages and frameworks as possible. Focus on the programming fundamentals, because the basics never change; pay more attention to architecture than to programming. Try to understand how things work. When you are given a problem, do not directly try to solve it. Think which approach would be the better one and why. Try to understand the concepts of any language rather than blindly getting it inside your head.
  • “The code works” isn’t where you stop; it’s where you start: Yes, your first step is always to write quality software that fulfills the spec. Average programmers quit at that point and move on to the next thing. Keep trying until you optimize the runtime and the memory occupied.

Post a Comment

0 Comments