Coding Plan
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.
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.
2.Always 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.
3.Always write properly structured code and proper function names along with
these always follow indentation.
4.While 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.
7.Before submitting, tell the interviewer that sir I want to check every thing
where my code could be wrong like spelling mistakes, edge cases etc.
8.If there is time do dry run because dry run is considered as an actual test of
code.
Resume should be very good, such that my resume gets selected for MAANG level
companies.
2.LinkedIn 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 seriously.People should know you exist.)
3.LinkedIn Applications.(Probability will work in your favour if you apply for more
companies.
Be active on all job sharing channels.Apply 5 times a day ,this will increase your
chances of being selected for interviews.)
5.LinkedIn 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)
6.Dev/Job/Intern
7.Communication 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.)
Never tell non technical things.Try solving brute force solution or half solution
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.
Technical
Part1:DSA preparation for interview
Part2: DSA preparation for OA
1.For 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.
3.Revision 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
6.Give 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
3.CSS libraries already have few codes written which can be reused instead of again
and again.
4.State Management Library : Till every thread of a process is executed the state of
every element in that particular process must be the same.