CODING PLAN
Since I am not a beginner I will start solving problems topic wise and make
and maintain docs for each topic for revision purposes.
I have made a total of 15 docs on various topics .
Maintain google docs for each question for every topic and paste code links
along with 2-3 lines solutions and revise them daily . Revision will help you to
remember concepts and you can apply them in OAs or contests in future.
Revision is the key!
INTERVIEW SESSION
Make sure to tell your coding language before the start of the
interview.
[Link]'t act like a robot.
Little bit of informal connection is needed because if some hectic task is
given by the interviewer you can convince him to give some relaxation.
[Link] use good variable names which describe their work in the code this
will increase code readability and create a good impression in front of the
interviewer.
[Link] write properly structured code and proper function names along with
these always follow indentation.
[Link] writing the code, always explain each line of your code. This will help
the interviewer understand your thinking process which will create a good
impression.
[Link] your approach and idea before implementation.
[Link] for doubts,assumptions,constraints etc. as soon as the interviewer gives
you a problem.
a) Don't be silent, ask questions related to the problem . It will make the
interviewer realise that I am a good listener, observer and good fit for
their team.
b) Ask about range of numbers, sign of numbers if your question consists
of numbers, you can ask about null conditions in questions of tree and
linked list.
c) Make sure you and the interviewer are on the same page.
d) Write your approaches on screen along with explaining your approach
to the interviewer.
e) Now your explanation part is over and don't forget input output
explanation.
[Link] submitting, tell the interviewer that sir I want to check every thing
where my code could be wrong like spelling mistakes, edge cases etc.
[Link] there is time do dry run because dry run is considered as an actual test of
code.
9. Always discuss corner cases.
10. Questions to ask after interview:
a). How did you join xyz and how did you reach your current position?
b). What tech stack you worked on and what were the teams you worked
on?
Non Technical Aspects
Resume should be very good, such that my resume gets selected for MAANG level
companies.
[Link] of connections on LinkedIn should be high.(Make at least 2000-3000
connections
and make sure your connections are currently working in top MNCs)
[Link] visibility.(Make your LinkedIn profile formal and presentable. It will make
a good
impact when you will ask people for referrals or any other favour. They will take
you [Link] should know you exist.)
[Link] Applications.(Probability will work in your favour if you apply for more
companies.
Be active on all job sharing [Link] 5 times a day ,this will increase your
chances of being selected for interviews.)
[Link] profile improving/enhancement.(Show Off your skills on LinkedIn
because HRs generally visit your LinkedIn profile, so when they will see various
achievements mentioned in the featured section it will be a plus point for [Link]
mention all your achievements,leetcode, codechef profile etc in featured section.)
[Link] Algorithm(Whatever your connections like that posts will only be shown
in your feed,so make more connections because many people will like more such
post which are inviting people for referrals)
[Link]/Job/Intern
[Link] Skills
a). Clarity and depth of explanation.(Understand Interviewer is not a robot, Use
technical words in between your explanations. This will create a good impression of
you on the interviewer, and explain your explanation with confidence.)
b).Psychological Trick(Give details only which you know well so that interviewer
will know the boundaries from where questions can be asked, so present yourself
like this I am xyz and I have done my Btech from xyz college and during my four
years I have explored DSA and DEV. In DSA these topics and in DEV I have made
4-5 projects using xyz tech stack on these features then tell I have done internship in
this tech stack and at last ask interviewer Sir! Do you want me to explain my
project in more detail? This is a very good psychological trick and I can explain my
project for 15-20 minutes which will create a good impact/impression of you. This is
called pulling the interview on your side. If you don't know the answer of any
question, tell the interviewer something like this “Sorry Sir, this thing is not currently
in top of my head but I have explored DSA, OOPS and DEV very well.)
What things I have to tell you about the project?
[Link] starting tell name of project,tech stack, what does the project does and what are
the different features of project, what languages are used in different features.
[Link] a summary of 5 pages of each individual project.
[Link] 50-50 questions of each tech stack used in the project
[Link] all loopholes and write all cross-questions related to the project and prepare
the answers.
[Link] the problems that came during project making. Tell the interviewer that
I along with my team did a lot of brainstorming and searched for possible solutions
on stackoverflow to implement the feature.
Never tell non technical [Link] solving brute force solution or half solution
[Link](Revision should be strong, read questions and formulate answers in
[Link] revise 2 docs in the morning. If you work hard you will get solutions.
Mindset will be growth and solution based. If I try here and there , do hard work
,search things then I will get solutions. A guy can do anything if his mind is in his
control . I will put questions which I cant solve in backlog doc)
[Link](Number 1 priority should be GOD, number 2 priority should be health)
Resume Trick-> Make 2 resumes, one resume should have one email, phone
number and another should have another. It will increase your getting test link.
How to take referral?
I am done with xyz and done engineering from xyz college then explain
whatever you explained at the time of your explanation and at last write If you
find me suitable please refer.
OFF CAMPUS AND ON CAMPUS JOBS
Technical
Part1:DSA preparation for interview
Part2: DSA preparation for OA
[Link] the interview, the top 500 questions on the sheet are good enough. DSA for
interview is board preparation and DSA for OA is jee preparation.
[Link] roadmap of kumar k sir.
[Link] and mindset (Solve quality problems and do revision, don't try do
questions anyhow)
a)How to do revision?
Step1)Make 15 DSA docs and include links of all questions you did on any
topic
When you wake up in morning revise daily 2 docs
[Link] Interview(You have to do a lot of things apart from explaining questions to
the interviewer.)
[Link] Preparation(People think OA is very hard because they never studied OA
because some topics are asked in OA which are not asked in an interview. Topics
which are asked in OA: Array Manipulation/Sliding Window/Hashing/Two
Pointer/Greedy/Binary Search and BIT/Segment Tree/General DP/General DP on
Tree/General Graphs/Bit Manipulation(XOR,OR,AND.)
50% OA are easy and 50% OA are hard in the current Indian Job market.
[Link] 3 contests every week (One codechef starters and two leetcode weekly and
biweekly.)
Make leetcode contest documents separate and codechef starters document
separate.
RESUME GUIDANCE
[Link] template given in homework document.
[Link] details according to your details.
[Link] paste the code of doc1 to [Link] and doc2 in page1 [Link]
WEB DEVELOPMENT GUIDANCE
[Link] is a basic structure of a webpage.
[Link] helps to make websites attractive and user friendly.
[Link] libraries already have few codes written which can be reused instead of again
and again.
[Link] Frameworks are used to make single page web applications.
What is a single page web application?
If we use only HTML,CSS,JS we have to make multiple pages. When you click a
button, the server will get a request and it will reload the site and take you to that
page. In single page applications what happens is that in spite of making so many
web pages we make one web page
and it will contain everything so the reloading time is eliminated.
[Link] Management Library : Till every thread of a process is executed the state of
every element in that particular process must be the same.
[Link] Control System: Used when a number of developers are working on a
project so there may be version contradictions which are handled by Version Control
System.
[Link]: One must have some knowledge of testing.
[Link] your projects.
[Link] Concepts like APIs
Take a project from links.
Tutorial 2 for backend.
Make summary of your project
Make a self descriptive heading and summary should be a max of four points
including tech stack as well it will help you to pass ATS checker.
Have three projects in your resume.
Now interviewer will ask questions so->
You should be clear about why you made this project.
Tell what your project does.
What features does your project have?
What tech stack did you use? Why did you use that tech stack?