Microsoft Interview preparation and CV Preparation - Suggested by Masud Karim Khan Sir

Videos:

1. https://www.facebook.com/ndcins/videos/727021087448808/

Some tips on writing good resume

1. One page resume is the best. Up to two page it’s good. Too big resume  they will think – “It’s going to take too much time, I will read the shorter ones first and come back to this later”. That "later" unfortunately hardly happen, they get lots of resume.
2. Format is very important. There are several good way to organize the information. One example:
   • Header – Your name, phone number, email address and physical address. Don’t mention your date of birth or Father’s name kind of info. I have seen people doing it!
   •  
   • Objective – What are you looking for? Full time/part time, what kind of role (dev/PM/test etc.). Make it one liner.
   •  
   • Highlights – Few bullet points that tells your skills. Try to make them quantifiable. Bad example: “Strong C++ coding skill”. Good example: “3 years of experience writing codes in C++”.
   • Work Experience (Only if you worked in industry) – One section for each job you held. Write the job title, company name and start-end date. Few bullet points explaining your role. Don’t disclose any non-public info such as you working on a feature that’s nobody outside of your org supposed to know yet. This is important, they don’t want same to happen to their company either. If you have completed any professional training as part of your job, mention that too. In this section, while writing about your role, highlight what your achievements were, or how your your work helped the product/team/clients/overall quality and try to add some numbers and technical info (not jargons) about the work. Example: "Worked on the web service to handle customer requests" might be written as "Designed and implemented a distributed web service in Java that can serve x requests/per sec to handle customer requests from legacy systems". Another example "Implemented a multi threaded data access layer in C# that increased performance by 60%".
   • School projects (Only if you are a fresh grad, skip this if you have a reasonable amount of industry experience to write a good section on “Work Experience”) – Mention several team projects you have worked on. Write a line or two summarizing each projects, what was your role in the team etc. Individual projects are not that important to mention but you can mention couple of challenging ones if you have. Your thesis goes in this section too.
   • Education – This is important. You don’t need to mention your SSC or HSC information. Start from first professional degree, which would be Bachelor’s degree. One line per degree – name of the degree & major, university name, GPA and year graduated.
   •  
   • Skills – This is different from Highlights. Totally non descriptive section, just mention the keywords. One line per skill set. Example skills: OS, Programming Languages, Test tools, Applications, Any version control tools etc.
   •  
   • Activity/Honor – One line per activity/honor. Here you can mention if you won any scholarship, competed in a programming contest etc. It’s not necessary to have all activities related to programming/CS. If you have organized a picnic, led a debating club, president of student organization, this is the place to brag about it. Recruiters want to see a leader in you, not a back office programmer.
   •  
   • References – This is optional. You might put couple of names who might recommend you if contacted by recruiters. You can skip this in resume, they have their way to verify if you provided any false info.
   •  
3. If you don’t have a particular skill, don’t mention it in the resume just to make it look good. For example you don’t know perl but mentioning it might end up they will ask a question on it during interview even though that company doesn’t do any perl scripting. Bottom line, don’t try to oversell yourself by putting a lie in the resume.
4. In big orgs they get 100s of resume daily. First level of review is done by recruiters in that case, who may not have enough technical knowledge. They will just look for matching keywords, such as C++, Java, Embedded software etc. and forward the resume to appropriate team. That’s why “Highlights” and “Skill” section is important.
5. Have the resume ready in both Word/PDF version and also in simple text version. Many companies ask to copy the content of the resume in their online application. Text version helps in that case, copying from word doc most likely will mess up all the alignments.

 Books for data structure and algorithm:

Introduction to Algorithm - by Thomas H. Cormen is one good book. Also, for quick preparation for software developer interview, Programming Interview Exposed - by John Mongan is very effective.

5 years details in microsoft life of Masud Karim Khan Sir: here 

মাইক্রোসফট - ইন্টারভিউ পর্ব