Extras

***************************   How to approach task   ********************* Understand the problem Objective - what are we solving (core issue) What already exists in system and what we can't do or limitations  Define how much we have to improve and what is "good" If too large, break problem into sub tasks and ask questions for each sub task → then move on to aggregate those answers Whenever putting your POV, try to frame it as question like "my idea is .... What's your opinion?"  Connect the conversation better  Make flowchart (HLD) on how you will be approaching what columns to be added in DB what functions to be made Confirm it with seniors on validity of approach Always think all aspects first before asking or connecting with seniors Make adjustments accordingly Think from your perspective also → if things seem off → think & question it If solving A, creates new task B → first tell situation to seniors and ask how to proceed → maybe B can be assigned ...

Past Mistakes Never show ki you don't know something (Media.net) keep asking and clarifying + explain slowly (if needed start summarising) (GS) Take time to give OA (Google) If stuck or missing something  - >  khud se testcases bna and analyse  →  more you do better you improve => DO NOT stop and keep thinking Lead technical discussion forward, try to s olve question with close to minimal hints Try to independently find solution instead of asking interviewer for advice Integrate any hints/suggestions by the interviewer in your solution Web Development Keep in mind, there is a difference between DSA and Dev.  In Dev round  -->  do not focus more on the DSA implementations of the online judge.  Focus on system design, implementation part, custom  isolation &  API using  containerisation and Docker , authentication page Focus on DRY, docker best practice (keeping less changed to most changed + docker compose), code-editor ...