Software Engineer .Net Interview Preparation Guide
Download PDF

64 Software Engineer .Net Questions and Answers:

1 :: What do you consider to be your greatest achievement so far and why?

Be proud of your achievement, discuss the results, and explain why you feel most proud of this one. Was it the extra work? Was it the leadership you exhibited? Was it the impact it had?

2 :: Tell me about a time when you successfully handled a situation?

For this question, the interviewer wants to know what you do in a situation that doesn’t have a clear answer. This will help the interviewer know how you respond to unforeseen challenges.

3 :: Give me an example of a time when you set a goal and were able to meet or achieve it?

Show that you set great goals and the process and steps you took to achieve it. Details really matter here.

4 :: What is your biggest weakness As Software Engineer .Net?

No one likes to answer this question because it requires a very delicate balance. You simply can’t lie and say you don’t have one; you can’t trick the interviewer by offering up a personal weakness As Software Engineer .Net that is really a strength (“Sometimes, I work too much and don’t maintain a work-life balance.”); and you shouldn’t be so honest that you throw yourself under the bus (“I’m not a morning person so I’m working on getting to the office on time.”)

5 :: Can you describe your ideal boss/supervisor?

During the interview As Software Engineer .Net process employers will want to find out how you respond to supervision. They want to know whether you have any problems with authority, If you can work well as part of a group (see previous question) and if you take instructions well etc.
Never ever ever, criticize a past supervisor or boss. This is a red flag for airlines and your prospective employer will likely assume you are a difficult employee, unable to work in a team or take intruction and side with your former employer.

6 :: Explain what are your strengths As Software Engineer .Net?

Bad Answer: Candidate is unprepared for question or only gives generic answers.

This is the most common job interview question - everybody should be expecting it. If they don't seem prepared, or give a fairly stock answer, it's probably a bad sign.

Good answer: The consensus is to go for quality, not quantity here. Candidates should give a short list of strengths, and back each one up with examples that illustrate the strength. Also, they should explain how these strengths will be useful in the job you’re applying for, and use this question to say something interesting about themselves.

7 :: Have you ever you have been in a position As Software Engineer .Net where you've had to fire someone? How did you feel about that experience?

Be very thoughtful about your answer. This is a very serious matter for most companies and requires a very serious answer. You need to express that you will do it when it is the right thing to do but you don't want to give the impression that you're callus to the process. Don't forget that firing is not the same as laying someone off - it typically is for the direct benefit of the company.

8 :: What experience do you have As Software Engineer .Net?

The employer would want to know that not only you can do the job but you can make the difference and bring significant contribution – Simple as that.
No doubt that this is your time to perform and present yourself – You have to introduce/sell yourself to the interviewer. Prepare your answer based on your qualification, professional experience and what you’ve already achieved in your previous jobs. This is your time to express why you think that your professional abilities fit into the job and its requirements.

Top 10 employment experience you’d want to review:
☛ Companies you worked for with dates
☛ The positions you’ve held
☛ Key projects and responsibilities
☛ Achievements
☛ Coursework & continues education
☛ Expertise
☛ Tools you used (software, hardware)
☛ Knowledge of languages
☛ Engagement with customers and key industry leaders
☛ Team work you were involved (and your contribution)

9 :: Tell us something about yourself?

Bad Answer: Candidates who ramble on about themselves without regard for information that will actually help the interviewer make a decision, or candidates who actually provide information showing they are unfit for the job.

Good answer: An answer that gives the interviewer a glimpse of the candidate's personality, without veering away from providing information that relates to the job. Answers should be positive, and not generic.

10 :: If you were given more initiatives than you could handle, what would you do?

First prioritize the important activities that impact the business most. Then discuss the issue of having too many initiatives with the boss so that it can be offloaded. Work harder to get the initiatives done.

11 :: What education or training have you had that makes you fit for this profession As Software Engineer .Net?

This would be the first question asked in any interview. Therefore, it is important that you give a proper reply to the question regarding your education. You should have all the documents and certificates pertaining to your education and/or training, although time may not allow the interviewer to review all of them.

12 :: How well do you know our company?

Well, a developed company that is gradually building their reputation in the competitive world.

13 :: What have you learned from mistakes on the job?

Candidates without specific examples often do not seem credible. However, the example shared should be fairly inconsequential, unintentional, and a learned lesson should be gleaned from it. Moving ahead without group assistance while assigned to a group project meant to be collaborative is a good example.

14 :: The change in the business industry now requires you to have a new set of skills you have to learn, how do you react to that?

First, find out which skills are the ones that you're currently lacking. Then identify what the steps would be to acquire/build those skills. Then take action to do so.

15 :: How have you made an impact on your team in the past?

I would explain and show to him or her best way possible and if they have a better way then I will encourage him or her to let me know then we can see if it works or not As Software Engineer .Net.

16 :: What motivates you at the work place?

Keep your answer simple, direct and positive. Some good answers may be the ability to achieve, recognition or challenging assignments.

17 :: What has disappointed you about a previous job?

Again, this question could get you in trouble so tread carefully. Some good answers might be that your previous job didn't provide any room for growth, that you were laid off due to a mandatory reduction in staff, that they closed their office in your state and required you to relocate, etc. Make sure not to mention anything negative about the people you worked with, the company in general or the job itself.

18 :: What is the most irritating thing you've experienced about your co-workers?

This question is designed to find out if you get along well on team, with other and whether or not you'll be a fit with the interviewer's organization. It's a trap. Think real hard but fail to come up anything that irritated you about your co-workers. A short positive response is best.

19 :: What type of people do you not work well with?

Be very careful answering this question as most organization employ professionals with an array of personalities and characteristics. You don't want to give the impression that you're going to have problems working with anyone currently employed at the organization. If you through out anything trivial you're going to look like a whiner. Only disloyalty to the organization or lawbreaking should be on your list of personal characteristics of people you can't work with.

20 :: What have you done to improve your knowledge As Software Engineer .Net in the last year?

Try to include improvement activities that relate to the job As Software Engineer .Net. A wide variety of activities can be mentioned as positive self-improvement. Have some good ones handy to mention.

21 :: Top 11 Questions to Verify Experience and Credentials As Software Engineer .Net:

Sometimes people want a job a little too bad - and they may fudge their credentials and experience a bit.

If you've run into this problem, are worried about it, or have credentials and experience that are absolutely essential, you may need to ask a few verification questions.

If you are a candidate, you should review your resume and make sure you know all the key points, and that nothing has been misconstrued.


1. What grades did you get in college?

2. What were your responsibilities when you worked in job x?

3. How many people were on your team at your last job?

4. What will your previous manager/supervisor say when I ask where you needed to improve?

5. What was your beginning and ending salary at job x?

6. What were your beginning and ending titles at job x?

7. Are you eligible for rehire at job x?

8. What tools are necessary for performing job x?

9. Describe to me how you would perform [x typical job task].

10. What was the focus of your thesis?

11. When did you leave company x?

22 :: Do you work well on a team? How would you define teamwork?

I would define team work as getting the job done As Software Engineer .Net whether that means if I have to do more then the guy next to me as long as the work gets finished.

23 :: What types of situations do you consider "unfixable"?

Most situations are "fixable" - the ones that are not are typically related to business ethics (someone is cheating the company, someone is stealing, etc)

24 :: How important is a positive attitude to you?

Incredibly important. I believe a positive attitude is the foundation of being successful - it's contagious in the workplace, with our customers, and ultimately it's the difference maker.

25 :: What do you feel you deserve to be paid?

Do your research before answering this question - first, consider what the market average is for this job. You can find that by searching on Google (title followed by salary) and globalguideline.com and other websites. Then, consider this - based on your work experience and previous results, are you above average, if yes, by what % increase from your pay today from your perspective? Also - make sure if you aim high you can back it up with facts and your previous results so that you can make a strong case.

26 :: Why were you fired?

OK, if you get the admittedly much tougher follow-up question as to why you were let go (and the truth isn't exactly pretty), your best bet is to be honest (the job-seeking world is small, after all). But it doesn't have to be a deal-breaker. Share how you’ve grown and how you approach your job and life now as a result. If you can position the learning experience as an advantage for this next job, even better.

27 :: What do you already know about our company?

Good reputation of a large home grown company that has various departments and product.

28 :: How articulate are you in expressing your ideas?

One of the best ways to answer this question is clearly articulate three points that demonstrate how articulate you are (and in a sense show that in a live setting) - for example: "I would say I'm articulate because one, I typically gather my thoughts before speaking, two, I organize my thoughts well, and three I'm concise when making a point.

29 :: What do you like to do outside of work?

Interviewers ask personal questions in an interview to “see if candidates will fit in with the culture [and] give them the opportunity to open up and display their personality, too,”. In other words, if someone asks about your hobbies outside of work, it’s totally OK to open up and share what really makes you tick. (Do keep it semi-professional, though: Saying you like to have a few beers at the local hot spot on Saturday night is fine. Telling them that Monday is usually a rough day for you because you’re always hungover is not.)

30 :: Describe your work style?

Describe the positive aspects of your work style if possible, including: work ethic, attention to detail, interpersonal skills, skill sets (analytical or otherwise), leadership abilities, communication skills.