Microsoft Interview Question for Software Engineer / Developers






Comment hidden because of low score. Click to expand.
1
of 1 vote

Functions often used by the users

Complex functions

Functions that have a lot of updates or bug fixes

Functions that require high availability

Functions that require a consistent level of performance

Functions that are developed with new tools

Functions that require interfacing with external systems

Functions with requirements with a low level of quality

Functions developed by more programmers at the same time

New functions

Functions developed under extreme time pressure

Functions that are most important to the stakeholders

Functions that reflect a complex business process

- Anonymous June 24, 2010 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

This is a software engineering question...

If you run out of time, you should prioritize functional reqs by severity/rate combo. Testing, anyhow, only shows that bugs may exist.

- Jack May 03, 2006 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

Hmm ... Nice ... So in ur opinion, was my answer right or wrong ?

- Altaf Al-Amin Najwani May 03, 2006 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

Short on time means avoiding thorough testing and priortizing testing. So the things you should test for should be limited to for example:

1-Critical features: most used by customers, critical to the application
2-History: components that had failed in past

- Neo May 04, 2006 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

Testing components with high rate of failures isn't actually a good factor for prioritizing. A test case either passes/fails. As you fix the software, these failures go away. Rate of occurances/failures applies more toward Risk Management.

- Jack May 05, 2006 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

I think...the most important thing is to test the most critical features of the application. Also Security testing is very important issue which should definitely be tested for.

- Div June 24, 2006 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

Answer : First of all i will find out all the most commonly use case scenerios and will come up with the list of operations which are most commonly used. For eg. Login is used in every case. Then will test for all inputs and outputs. Will Check performance, throughput and response time. Will check for the Boundary Conditions. Will check that whether the functionality is giving desired result. Will do walk through of whole application to test the integration among different modules.

- Altaf Al-Amin December 04, 2006 | Flag Reply
Comment hidden because of low score. Click to expand.
0
of 0 vote

Testing should be prioritized for most critical features if you run short of time

- Anonymous March 29, 2008 | Flag Reply


Add a Comment
Name:

Writing Code? Surround your code with {{{ and }}} to preserve whitespace.

Books

is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.

Learn More

Videos

CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.

Learn More

Resume Review

Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.

Learn More

Mock Interviews

Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.

Learn More