Fresh Software Requirements Engineer Interview Questions & Answers:

1. What are the goals you've set for yourself?

You could discuss your goals with regards to these categories: Career goals, impact you want to leave on society, financial goals, academic goals, charitable goals.

2. 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.

3. Describe your management style?

Try to avoid specific classifications, whatever it may be. Organizations usually prefer managers who can adapt their skills to different situations.

4. What specific steps do you utilize in solving workplace problems?

Analyze the problem As Software Requirements Engineer. Discuss possible remedies and resulting outcomes. Decide on the remedy and track results. Re-visit problem if it's not resolved.

5. Tell me about a time when you had to think strategically?

There was a time when I was told I had to get rid of 20% of my people. I had to determine which persons I needed the most by determining who could do what. I had to put aside personal feelings so that I could keep a working crew to handle he same workload with less people.

6. 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 Requirements Engineer.

7. How did you handle meeting a tight deadline As Software Requirements Engineer?

Review every deadline you need to meet. Prioritize your projects by deadline and factor in how important each project is. Record your deadlines on a digital calendar or spreadsheet.

8. Explain what are your strengths As Software Requirements Engineer?

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.

9. What has been your biggest professional disappointment?

When discussing a professional disappointment, make sure to discuss a scenario you could not control. Be positive about the experience and accept personal responsibility where applicable.

10. What are your strengths As Software Requirements Engineer?

This is one of the most common questions you will be asked. Give an answer relevant to the skills and qualities relevant to the position you are applying to. The interviewer is trying to find if your strengths match the job. For example, if you are applying for a job As Software Requirements Engineer where accuracy is an important issue, one of your strengths could be that you have an eye for detail. It may useful to find different words to describe similar attributes and qualities in order to avoid repetition.

11. Give me an example of how you handled pressure at work As Software Requirements Engineer?

The company is looking to see if you can handle pressure well. Share with them an example where you were able to stay calm during a pressure filled situation (perhaps it was a deadline, or there was an emergency with a customer occurring). Discuss the situation, your reaction and steps you took to resolve it and the outcome.

12. Tell me a difficult situation you have overcome in the workplace?

Conflict resolution, problem solving, communication and coping under pressure are transferable skills desired by many employers As Software Requirements Engineer.
Answering this question right can help you demonstrate all of these traits.
☛ Use real-life examples from your previous roles that you are comfortable explaining
☛ Choose an example that demonstrates the role you played in resolving the situation clearly
☛ Remain professional at all times – you need to demonstrate that you can keep a cool head and know how to communicate with people

13. What do you expect from this job As Software Requirements Engineer?

Talk about the potential career development, your career aspirations, your work relationships and the learning you'll receive.

14. Who are your heroes?

Have at least one person you consider a hero or role model. Be ready to explain why they are a hero to you and how they've inspired you to be a better person.

15. What have you done to improve yourself in the last year As Software Requirements Engineer?

Discuss how you've improved yourself through work experiences, books you've read, classes, club(s) / extracurricular activities and describe the process on how it's happened. For example: I've improved my presentation skills tremendously because I've had to do 2 presentations this year for my communications class.

16. Can you describe your ideal boss/supervisor?

During the interview As Software Requirements Engineer 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.

17. Can you tell me a little about yourself?

This question seems simple, so many people fail to prepare for it, but it's crucial. Here's the deal: Don't give your complete employment (or personal) history As Software Requirements Engineer. Instead give a pitch-one that's concise and compelling and that shows exactly why you're the right fit for the job. Start off with the 2-3 specific accomplishments or experiences that you most want the interviewer to know about, then wrap up talking about how that prior experience has positioned you for this specific role.

18. Explain what are your weaknesses As Software Requirements Engineer?

Red flags: This is the peanut butter to the previous question's jelly. Again, everyone should expect it, so it's a bad sign if someone seems totally unprepared, or gives a stock answer like, "I'm a perfectionist." Also, of course, candidates crazy enough to blurt out some horrible personality trait should go in the red flagged pile.

Good answer: Candidates should talk about a real weakness they've been working on improving. For instance, they're not good at public speaking, but they've been taking a course to help them improve. Or maybe they feel that they're easily distracted when working online, but have installed software that helps them stay on task. Answers like these show a desire for improvement, self awareness and discipline.

19. How would your boss and co-workers describe you?

First of all, be honest (remember, if you get this job, the hiring manager will be calling your former bosses and co-workers!). Then, try to pull out strengths and traits you haven't discussed in other aspects of the interview As Software Requirements Engineer, such as your strong work ethic or your willingness to pitch in on other projects when needed.

20. Describe a time when you put your needs aside to help a co-worker understand a task. How did you assist them? What was the result?

The key is to show that the mentoring of a co-worker was first a higher priority than the task you had at hand (remember, you want to show that you focus on highest priority tasks first). Then, describe in detail how you helped them not only complete the task but learn to do it on their own. You want to teach them HOW to fish and not to simply fish for them.

21. Do you know anyone that works with our company?

Sometimes companies have policies relating to the hiring of individuals related to current company employees. If you are related to anyone working for the company make sure you're aware of company policies before you enter the interview. If you have a friend or acquaintance working for the company make sure have good relationship with this individual before mentioning them.

22. Top 11 Questions to Verify Experience and Credentials As Software Requirements Engineer:

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?

23. What education or training have you had that makes you fit for this profession As Software Requirements Engineer?

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.

24. Your coworker highlights your mistakes in front of everyone, how do you handle the situation?

Admit to the mistake without being emotional, but then discuss how you are being proactive in getting it fixed. Lastly, pull the co-worker aside later on to tell them that you'd appreciate it if they gave you the feedback 1:1 first before throwing you under the bus.

25. If you have multiple projects on your plate, how do you handle completing them on time?

Prioritize based on business importance. Set clear timelines for each so that you know which ones to knock out first. Get your teammates to help if necessary.

26. How many tennis balls can you fit into a limousine? 1,000? 10,000? 100,000? Seriously?

Well, seriously, you might get asked brainteaser questions like these, especially in quantitative jobs. But remember that the interviewer doesn't necessarily want an exact number-he wants to make sure that you understand what's being asked of you, and that you can set into motion a systematic and logical way to respond. So, just take a deep breath, and start thinking through the math. (Yes, it's OK to ask for a pen and paper!)

27. What is your biggest fear?

Don't try to sugarcoat the answer by listing something ambitious as a fear, unless you truly mean it (for example: I fear being a great leader) - Share your real fears but discuss how you would overcome them.

28. How well do you multi-task?

Multi-tasking is an important part of most jobs. You want to show that you're good at it but not overwhelmed with it. So discuss just a few things you can multi-task well on - for example: "I'm good at multi tasking between work email and working on projects As Software Requirements Engineer and the reason it because I'm good at prioritizing my work emails.

29. What did you major in and why?

Tell them your major and the motivations behind why you chose it and how it's helped to prep your of this potential job.

30. If you look at a clock and the time is 3:15, what's the angle between the hour and the minute hands?

Usually, if the answer to a brainteaser seems too easy, chances are the answer's wrong. And in this case, the answer is not zero degrees. The hour hand, remember, moves as well. That is, in addition to the minute hand. And so, at 3:15, the hour hand and the minute hand are not on top of each other. In fact, the hour hand has moved a quarter of the way between the 3 and 4. This means it's moved a quarter of 30 degrees (360 degrees divided by 12 equals 30). So the answer, to be exact, is seven and a half degrees (30 divided by four).