Академический Документы
Профессиональный Документы
Культура Документы
careers.microsoft.com
Overview
If youre like most students we talk to, you want to know what to expect during your
interviews and what were looking for in you. At Microsoft, interviews are a two-way
street. We want to get to know you, but we also want to be sure you walk away
knowing us too.
Youll meet with your potential coworkers and team; youll typically meet for up
to an hour each with three to six people during your interviews.
In most cases, youll interview with people on two teams within a single product
group or two different teams working on entirely different products. We try to find
the best fit based on the team's business needs and your own skills and interests.
Youll have a chance to look around. We'll make sure you have time to see
campus and get a feel for the area that may soon become your home.
Be open about your skills. Be upfront about what you do know and what you do
not. If you dont have the exact skill that an interviewer asks you about, dont
panic: part of the interview process is learning and dealing with ambiguity.
Were interested in how your mind works. Be ready to show your thinking and
explain how you came up with a solution to a technical issue, design question, or
problem-solving puzzle; the process you use to arrive at an answer is even more
important to us than the answer itself.
What to expect
afraid to stand up and write code on the whiteboard, draw your solution, or ask
questions for clarification.
Process thinking questions: These invite you to verbalize your thought process as you
work through a technical issue, design question, or problem-solving puzzle.
Remember, its not always the end result were looking for, but the process you took to
get there and your ability to clearly articulate it to others.
Project questions: Be prepared to talk about the technical and soft skills you
demonstrated in previous internships and school projects. Anything you list on your
resume is fair game.
Your natural curiosity is one of your biggest assets as a potential hire. Thoughtful,
insightful questions will show that youre serious about making an impact at Microsoft.
And if you dont understand a question, dont be afraid to ask the interviewer to clarify.
Likewise, ask your interviewer about the nature of their work and projects you could
potentially work on. We know candidates of your caliber have a lot of career
opportunities, so we want you to be sure that a position with us is a great fit for you.
Recommended resources
How to prepare
You dont need to dress up to impress us. Wear whatever makes you most
comfortable. The people interviewing you are likely to be casually dressed, but
we understand if you feel more confident in your power suit.
Make sure you have the fuel and rest you need to stay relaxed and quick on your
feet. You may be nervous when you arrive, so while we have food on-site,
consider eating a meal beforehand when youre not quite so nervous.
Be ready to tell your story and to discuss your strengths, expertise and any
experience that appears on your resume.
Resume tips
Summarize your relevant education, experience, and projects. Skip the things that
are outdated or irrelevant.
Highlight your accomplishments in previous jobs or projects, not just your duties
or responsibilities. Everyone has job duties; its how you approached them and
what you accomplished in carrying them out that makes you stand out.
Show progression. Whether its in school, leadership roles or your work, highlight
how your experience has helped you grow.
Talk about related extracurricular or volunteer work. Just because you werent
paid for it, that doesnt mean its not important!
Include links to projects youve worked on. This gives the recruiter a better idea
of how you put your skills into practice.
Its okay to use more than one page. That said, be sure your summaries are
succinct and relevantand your most important information appears on the first
page.
graduation.
Be honest. Paint the best possible picture of yourself, but dont exaggerate. And
proofread for typos and errorsmore than once!
If you send your resume in Microsoft Word format (.doc or .docx), make sure to
turn off "track changes".
Best practices
When answering your questions, use frameworks, so you can structure your
answer in a cohesive manner.
Yes, we want to know how you think and what are you passionate about, but we
also want to see your personality.
Some interviewers like to interrupt and ask questionsgo with the flow and dont
panic.
Know the dress code. A lot of candidates ask whether they should be in their
formal interview clothes or dress like Microsofties, so that they can show they
know our culture. While very few people at Microsoft wear suits, its better to be
safe than sorry and dress more conservatively.
Development (engineering)
There are two primary roles within this job family: Software engineering and program
management. Read on to find out more.
Software engineering
Software engineering (SWE) roles require coding. Be ready to code, a lot! Brush up on
your object oriented languages, as our interviewers love to ask questions related to
linked lists, loops, arrays, and pointers, etc. Weve found the best coders ask a ton of
questions before writing code and consider the consequences of every line. Think of
the pros and cons of each solution, and once you decide to move ahead with a solution,
be ready to explain why you chose that approach. And most importantly, be sure to test
your code before you say youre done!
Review data structures and algorithms and make sure you know the characteristics
of data structures, e.g., when to use them, their time and space complexity,
trade-offs, etc.
Practice working through some coding problems that you havent seen before, as
this is similar to the technical parts of the interview.
Think about how you would test mundane items, like calculators or staplers. Be
sure to classify your tests (i.e., border cases, common functionality, stress,
security, error checking, etc.).
Look at some code youve written in the past, then write a tool to test your code.
Discuss the most challenging project you completed in specific terms, including:
project scope (goals, customers, accomplishments, and complexity), technical
skills you applied (gathered customer requirements, designed, programmed, or
tested), technical tools you employed (C, C++, C#, VB, SQL, Assembly), and
what you learned from your experience.
Dont try to optimize your code before its finished. Get a working solution, then
go back and improve it.
Your ability to categorize the various test cases you come up with is key, so
structure really helps.
Try to come up with as many cases as possible. Even when you think youre done,
push a bit harder and think of a couple more. And please get creativethere are
no cases too extreme!
Recommended resources
Box, Don. Essential .Net, Volume I: The Common Language Runtime. Addison-Wesley
Professional, 2003.
Cormen, T.h., Leiserson, C.E., Reivert, R.L., & Stein, Cliff. Introduction to Algorithms.
McGraw-Hill, 1990.
Gallagher, T., Jeffries, B., and Landauer, L. Hunting Security Bugs. 2006.
Howard, Michael & LeBlanc, David, eds. Writing Secure Code. Microsoft Press, 2001.
Kaner, C., Bach, J., and Pettichor, B. Lessons Learned in Software Testing. John Wiley
& Sons, 2002.
Kaner, C., Falk, J., and Nguyen, H.Q. Computer Software. 2nd ed. International
ThomsonComputer Press, 1993.
Maguire, Steve. Writing Solid Code: Microsofts Techniques for Developing Bug-Free
C Programs. Microsoft Press, 1993.
Myers, Glenford. The Art of Software Testing. John Wiley and Sons, 1979.
Tanenbaum, Andrew. Modern Operating Systems. 2nd ed. Prentice Hall, 2011.
Viega, J. and McGraw, G. Building Secure Software: How to Avoid Security Problems
the Right Way. Addison-Wesley, 2001.
Web resources
Program management
A Microsoft program manager (PM) has the rare ability to balance strong design skills
with a talent for planning and organization. That said, PM interviews can include an
abundance of challenging design questions.
The customer
For the improvements/additions you suggest, why do you think it hasn't been
done already?
What would you do if you suddenly had your deadline moved up 3 months/or
your project's budget was trimmed?
What features would you decide to keep and which would you decide to cut?
How would you communicate to the developer that spent 2 months working on
a feature that their feature was not going to be included?
Expect problem-solving questions, so be sure you understand the question and the
clues; and feel free to take a minute to think about the problem.
You can also expect a few coding questions, like linked list reversal.
Strong PMs are great communicators, can collaborate and influence across
groups, and have great interpersonal awareness.
Recommended resources
Emotional Design: Why We Love (or Hate) Everyday Things (Donald Norman)
Explore the opportunities within MSIT and learn how you can launch your career
straight out of college.
Understand the Information Technology space, review key business cases and be
familiar with the latest technologies.
Think of new problems and imagine design challenges you may face.
Explore strategies for analyzing client and partner business needs, and for
translating these into requirements for a solution.
If you are applying for an IT SWE position, be prepared to code and provide an
efficient solution to the problem at hand. Be ready to come up with interesting
testing scenarios, test cases and creative approaches to problems.
Ask clarifying questions and, when presented with a design challenge, consider:
How would you improve the design of a product? How will you tackle a complex
scenario in a timely manner? How will you manage multiple projects while
keeping momentum?
For IT SM jobs, be sure to analyze cases from different angles: What is the vision
and scope of a project? Is there any risk involved?
Marketing and Finance interviews are a bit different than developer or technology
interviews.
Do your research. We are looking for people who want to work at Microsoft and
are passionate about technology.
Read tech blogs such as Engadget, TechCrunch, and others so youre up on the
latest trends and events in technology and Microsofts latest news.
Connect with alumni at Microsoft to learn more about our culture and life at
Microsoft. Be prepared to talk about a Microsoft product or your favorite
technology product.
Recount an occasion in which you had to deal with a difficult person or team.
For University Recruiter Anthony Rotoli, its the key details that people seem to forget
most often: "Its simple really, but leaving your graduation date, or other important
information (phone number, email) off of your resume. Graduation date is very
important for us to get a sense of about how far along you should be in school. Contact
information is important forwellus contacting you!"
Beyond the initial application process, Anthony notes that candidates can sometimes
block their own path to success. His advice to avoid this? Be yourself: "Applicants will
sometimes approach the interview process with what they think an interviewer wants to
hear, and theyll try to make sure they fit the mold theyve imagined were looking for.
Bad mistake! The best thing you can show us during interviews is the real you. I
always encourage folks to approach each interview like a discussion with a current
co-worker or teammate. Dont try to demonstrate some skill you have only a
rudimentary understanding oftalk about what you know, and let your passion shine
through!"
Youll meet with several different people throughout the interview process. They all
work together to make the experience a great one for you, but each has a unique role to
play.
have questions youd like answered, just check out our Find a Recruiter page to
connect directly.
Interview scheduler: Your interview scheduler, who works for our vendor,
SourceRight, will contact you via e-mail about your travel arrangements,
interview date, and expense reimbursements. He or she is your go-to person for
questions about your interview logistics.
Your campus recruiter will let you know which group(s) youll be interviewing with on
your interview day. Dont worry if you havent heard of the specific teams youll be
meeting with. You wont be evaluated on how much you know about the groups.
Positions fill quickly, so its good to make plans as early as possible. Your interview
scheduler will email to confirm an interview date and send you instructions on how to
book your travel arrangements. Please respond to them as soon as you can.
The maximum length of your interview trip is three days and two nights. If youd like
more time, just email your interview scheduler and let him or her know your
circumstances so we can look into extending your stay.
Youre more than welcome to bring a companion, but we can only reimburse travel
expenses for you.
After your interview date is confirmed and your travel has been booked, we prefer not
to change your schedule unless there is an emergency.
In most cases, you should hear back from your campus recruiter within one to two
weeks of your interview. Please let us know if you have other offers with deadlines
pending; were flexible and are always happy to work around your schedule.
Your campus recruiter will work with you to determine a reasonable timeframe, but
typically youll be asked to make a decision within a week (internship candidates) or
two (full-time candidates).