Bhaiya I have two offers one is graduate engineer trainee at MBRDI bengluru and second is SDE1 at peoplestrong gurgaon which on should I choose? And what is role of get at MBRDI is it sde an what is future of GET at MBRDI
Most of the time the problem lies around coding snippets if you are able to answer all the conceptual and scenario based questions, but not able to do coding questions then you were simply rejected, doesn't matter how good you are in theoretical part.
Yes right here Eg if they tell you that you need to find some missing elements from the Collection or duplicates or top 5 or sum then you can write code using Stream api
@@rexsam3134 But coding questions shouldn't be asked as majority of the junior or experienced developers googling syntax and logic from articles and stackoverflow, so it is obvious that no one can remember the correct syntax or logic
@@experience_share6836 whatever code you write must get compiled and should run. If not then they will not be satisfied Never argue but always ask for suggestions Flatter them Google for mistakes and move on
@@jacknjill8096 I am from the opinion that let them ask for the approach at a high level. But for freshers coding is more important as they must know what is the actual Java 1.8 syntax. For experienced it is not expected to know the code but the pattern and approach should be clear. Guys like us have never been taught the algorithms in enginnering before 1998 cos we were trained on Fortran Pascal Basic Cobol and Dbase
@@rexsam3134 for freshers it is very difficult to memorize the syntax at one glance and hence they were ended no jobs in hand. For freshers concepts and fundamentals are most important because most of the time they will give you bookish answers and bookish examples, so it is clearly understood that they don't have much hands on. Coding shouldn't be asked whether it is fresher or experienced, rather than asking during technical rounds, there should be proctored assesments or live coding round of 1 hour just like MAANG does before appearing for technical. So one can be prepared well enough for conceptual and fundamentals without bothering for writing codes. Yes approaches can be asked, because approach can be made within 3-5 mins, but if one wants an entire optimised snippet within a window of 10 mins, it is very difficult and challenging.
Bro you are amazing. Thank you so much for making this video. please keep up the good work.
bro , the humbele thing in you that u mention everything ,either you select or reject . Thank you so much for making videos
Thanks bro
Thank You for Letting Us Share Your Experience
U r doing a great work to the community. Please keep doing !
Thanks a lot bro 👍
Hey man. Amazing work
Thanks bro for sharing interview experience
Bhaiya I have two offers one is graduate engineer trainee at MBRDI bengluru and second is SDE1 at peoplestrong gurgaon which on should I choose?
And what is role of get at MBRDI is it sde an what is future of GET at MBRDI
Bro can you tell me the eligibility criteria for benz R and D for btech students
Waiting for more interview experience
What is your total experience now
Thanks for sharing bro
what is CTC bro
Most of the time the problem lies around coding snippets if you are able to answer all the conceptual and scenario based questions, but not able to do coding questions then you were simply rejected, doesn't matter how good you are in theoretical part.
Yes right here
Eg if they tell you that you need to find some missing elements from the Collection or duplicates or top 5 or sum then you can write code using Stream api
@@rexsam3134 But coding questions shouldn't be asked as majority of the junior or experienced developers googling syntax and logic from articles and stackoverflow, so it is obvious that no one can remember the correct syntax or logic
please share your questions with answers also. it will be more helpful
Sure, will do
i feel bad for this freeze hiring senario , i hope to better day to come soon
Thank you
Thankyou so much for sharing
Ur honest.
Where did you go wrong? Which version have you used?
U need to practice a lot
I didn't have much hands-on at that time
@@experience_share6836 whatever code you write must get compiled and should run. If not then they will not be satisfied
Never argue but always ask for suggestions
Flatter them
Google for mistakes and move on
@@rexsam3134 I do believe that coding questions shouldn't be asked because it can be nullify your entire theoretical knowledge
@@jacknjill8096 I am from the opinion that let them ask for the approach at a high level. But for freshers coding is more important as they must know what is the actual Java 1.8 syntax. For experienced it is not expected to know the code but the pattern and approach should be clear. Guys like us have never been taught the algorithms in enginnering before 1998 cos we were trained on Fortran Pascal Basic Cobol and Dbase
@@rexsam3134 for freshers it is very difficult to memorize the syntax at one glance and hence they were ended no jobs in hand. For freshers concepts and fundamentals are most important because most of the time they will give you bookish answers and bookish examples, so it is clearly understood that they don't have much hands on.
Coding shouldn't be asked whether it is fresher or experienced, rather than asking during technical rounds, there should be proctored assesments or live coding round of 1 hour just like MAANG does before appearing for technical. So one can be prepared well enough for conceptual and fundamentals without bothering for writing codes.
Yes approaches can be asked, because approach can be made within 3-5 mins, but if one wants an entire optimised snippet within a window of 10 mins, it is very difficult and challenging.
Thanks for sharing ur experience.
Could u please share ur resume?
Sure, ping me in LinkedIn