1. How well do you perform under pressure?

This is a fair question, as potential employers want to know if you're going to be able to get the job done even when things get a little bit stressful. You may say that you thrive under pressure or that you're able to get the job done even when things get a little bit stressful, just make sure to provide some real world examples of your ability to work under pressure in a prior job.

2. If you were interviewing someone for this position In RDBMS, what traits would you look for?

This is where the interviewer tries to turn the tables on you. Answer confidently by stating 3 specific traits that are applicable to that job role. For example, a consulting job would likely look for someone who can think outside of the box.

After answering, ask them, "Am I spot on here and if not, what traits would you look for?"

3. What critical component of this position In RDBMS makes the work challenging?

Heading information: This should include job title, pay grade or range, reporting relationship (by position, not individual), hours or shifts, and the likelihood of overtime or weekend work.
Summary objective of the job: List the general responsibilities and descriptions of key tasks and their purpose, relationships with customers, coworkers, and others, and the results expected of incumbent employees.
Qualifications: State the education, experience, training, and technical skills necessary for entry into this job.
Special demands: This should include any extraordinary conditions applicable to the job In RDBMS (for example, heavy lifting, exposure to temperature extremes, prolonged standing, or travel).
Job duties and responsibilities: Only two features of job responsibility are important: identifying tasks that comprise about 90 to 95 percent of the work done and listing tasks in order of the time consumed (or, sometimes, in order of importance).

4. What did you dislike about your old job?

Try to avoid any pin point , like never say “I did not like my manager or I did not like environment or I did not like team” Never use negative terminology. Try to keep focus on every thing was good In RDBMS , I just wanted to make change for proper growth.

5. Explain yourself in one line?

When you respond, keep in mind the type of position you are interviewing for like RDBMS based job, the company culture, and the work environment. Your answer should help show the interviewer why you're a match for the job and for the company.
Sample answers are:
☛ I'm a people person. I really enjoy meeting and working with a lot of different people.
☛ I'm a perfectionist. I pay attention to all the details, and like to be sure that everything is just right.
☛ I'm a creative thinker. I like to explore alternative solutions to problems and have an open mind about what will work best.
☛ I'm efficient and highly organized. This enables me to be as productive as possible on the job.
☛ I enjoy solving problems, troubleshooting issues, and coming up with solutions in a timely manner.

6. Tell me about a time when you had to make a decision without all the information you needed. How did you handle it In RDBMS? Why? Were you happy with the outcome?

In many scenarios, you will not have all the information needed. The key is to make the best possible decision based on what you deem to be a sufficient amount of information.

7. Name five characteristics that describe you?

Here are a few you could choose from:
Hard working, strong willed, persistent, intelligent, adept, amicable, friendly, collaborative, eager, humble.

8. What is your greatest achievement outside of work In RDBMS?

This is a great opportunity for you to discuss how you've given back to the community, how you've achieved in a competitive extracurricular activity (think sports or clubs), how you've mentored others, and so forth.

9. What kind of car do you drive?

The only time this might matter is if the job requires a certain type of car because of the responsibilities. For example, if you need to load a lot of construction materials into your car, you'll probably need a truck.

10. You have a project due in one hour but a more important emergency that affects business needs to be fixed immediately, what do you do?

Focus on the issue that impacts the business most first.

11. What do you consider ethical spending on an expense account?

It depends on the role - but the better way to answer this is to ask the interviewer what their expectations are with regards to what the role can expense and then simply state that you'll stay within those parameters

12. What is the difference between a big ego and a healthy ego?

"Ego" should be replaced by confidence. It's good to be confident as it shows that you know what you're doing. However, a big ego is when confidence spirals out of control and you become arrogant.

13. Top 13 Situational Interview Questions In RDBMS:

Situational interviews In RDBMS are similar to behavioral interview questions - but they are focused on the future, and ask hypothetical questions, whereas behavioral interview questions look at the past.

The advantage is that employers can put all candidates in the same hypothetical situations, and compare their answers.


1. What would you do if you made a strong recommendation in a meeting, but your colleagues decided against it?

2. How you would handle it if your team resisted a new idea or policy you introduced?

3. How would you handle it if the priorities for a project you were working on were suddenly changed?

4. What would you do if the work of an employee you managed didn't meet expectations?

5. What would you do if an important task was not up to standard, but the deadline to complete it had passed?

6. What steps would you take to make an important decision on the job In RDBMS?

7. How would you handle a colleague you were unable to form a positive relationship with?

8. What would you do if you disagreed with the way a manager wanted you to handle a problem?

9. What would you do if you were assigned to work with a difficult client In RDBMS?

10. What would you do if you worked hard on a solution to a problem, and your solution was criticized by your team?

11. How would you handle working closely with a colleague who was very different from you?

12. You're working on a key project that you can't complete, because you're waiting on work from a colleague. What do you do?

13. You realize that an early mistake in a project is going to put you behind deadline. What do you do?

14. In your last job what kinds of pressure did you encounter and how did you react In RDBMS?

Do not show your fear or uneasiness in handling pressure. Everyone likes to have a worker who can handle pressure calmly and with a clear train of thought. Show how you would logically come to a conclusion in a pressure filled situation.

15. What do you like to do for fun?

Be open to sharing hobbies and activities that you enjoy. Make sure you're genuine about it and don't list off things you don't really like because if they ask you a follow up question it'll be harder for you to answer.

16. What did you like least about your last (or current) job In RDBMS?

Don't vent or focus on the negative with brutally honest answers such as "My boss was a jerk," or "The company culture was too politically correct," or "They just weren't giving me the opportunity to take my career to the next level." Instead, keep the emphasis on the positive, even though there are sure to be things you weren't happy about.

17. What attracted you to this company In RDBMS?

You could discuss the company's vision, culture and solutions/services as reasons for wanting to join it.

18. Describe a time when you anticipated potential problems and developed preventive measures?

The key here is to show that you were proactive. How did you find out about the potential problems? How did you address it quickly?

19. How do you adapt to new working environments In RDBMS?

It's important that you demonstrate that you can adapt to changing environments quickly. You want to stress that you can manage change. The one thing in life that is constant after all, is change.

20. What's the last book you read?

Try to talk about a book related to the industry, for example, if you're applying for a role related to business, cite a business book.

21. How did you handle meeting a tight deadline In RDBMS?

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.

22. Tell me about a time when you helped resolve a dispute between others?

Be sure to discuss a very specific example. Tell the interviewer what methods you used to solve the problem without focusing on the details of the problem.

23. 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 In RDBMS, such as your strong work ethic or your willingness to pitch in on other projects when needed.

24. What role are you ready to take in a group?

Ideally, you want to take on the role you're interviewing for, but you want to be flexible with your responsibilities In RDBMS if there are any changes.

25. Basic 15 Interview Questions that Test Communication Skills In RDBMS:

For most jobs, communication skills In RDBMS are important. It's hard to work as a team if people aren't communicating well.

At some jobs, like customer service or sales, communication skills are an absolute essential.

These questions are meant to help gauge a candidate's ability to communicate.

1. How do you prefer to build rapport with others?

2. How would you go about simplifying a complex issue in order to explain it to a client or colleague?

3. How would you go about persuading someone to see things your way at work?

4. How would you go about explaining a complex idea/problem to a client who was already frustrated?

5. What would you do if you there was a breakdown in communication at work?

6. Talk about a successful presentation you gave and why you think it did well.

7. How would you explain a complicated technical problem to a colleague with less technical understanding?

8. Do you prefer written or verbal communication In RDBMS?

9. Describe a time when you had to be careful talking about sensitive information. How did you do it?

10. What would you do if you misunderstood an important communication on the job?

11. Talk about a time when you made a point that you knew your colleagues would be resistant to.

12. Is it more important to be a good listener or a good communicator In RDBMS?

13. Tell me about a time you had to relay bad news to a client or colleague.

14. Rate your communication skills on a scale of 1 to 10. Give examples of experiences that demonstrate the rating is accurate.

15. How have you handled working under someone you felt was not good at communicating?

26. What types of books or magazines do you typically read?

Describe both your personal and professional favorites. If you happen to like professional books / magazines that relate to the industry of the company you're applying for - that's definitely worth highlighting.

27. How do you define arrogance? Are you arrogant?

Arrogance is having an attitude of superiority beyond reason. Confidence is believing in yourself without being cocky. You should not be arrogant.

28. What are three positive characteristics you wish you had?

The key here is to be honest about your wish list but then to describe how you plan on developing or growing those characteristics so that it becomes a reality. For example, I wish I had a stronger work ethic and I am reading a book right now about how to instill a better discipline around getting work done efficiently.

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. How did you find out about this job In RDBMS? What do you know about the job?

Possible ways to find out about the job:
Online website listing, friend, professional referral, mentor, career fairs, networking events. You should know about the roles and responsibilities of the job and what they're looking for. Make sure you read up on that online beforehand or ask the person that referred you.

31. Have you ever been fired and if yes, why?

Answer this as positively as possible and try to avoid disparaging the company you had previously worked for. The key is to accept the fact that yes, you were fired, but you've learned from the mistakes that got you there and you're better now because of it. If you haven't been fired, well, then this question's a piece of cake isn't it?

32. What are your lifelong dreams?

If your dreams don't relate to the job closely, make sure you highlight aspects of the job that will help develop the skills that will help you with your dreams. Ideally, you want your dreams to relate strongly to the career path you're interviewing for though.

33. Describe to me a time where you had to make a hard decision In RDBMS?

Hard decisions are hard for a reason. It could dramatically effect the company. It could affect other workers. So if you have a story about how you made a hard decision and had a good outcome, share that. If you have one where the outcome wasn't great, explain how you would have changed the way you approached the decision to show you learned how to improve.

34. What is your greatest failure In RDBMS, and what did you learn from it?

When I was in college, I took an art class to supplement my curriculum. I didn't take it very seriously, and assumed that, compared to my Engineering classes, it would be a walk in the park. My failing grades at midterm showed me otherwise. I'd even jeopardized my scholarship status. I knew I had to get my act together. I spent the rest of the semester making up for it, ended up getting a decent grade in the class. I learned that no matter what I'm doing, I should strive to do it to the best of my ability. Otherwise, it's not worth doing at all.

35. What does success mean to you?

I am punctual, I always have excellent attendance on any job In RDBMS, I have a keen eye for both large and small details, and I am always finding ways to improve a process and shorten the length of time it takes to complete a project.

36. How long do you envision yourself staying with this company?

Understand that companies invest a lot of money into hiring the right staff. You want to emphasize that you are in it for the long run and you want to develop a career there and that it's not just a "5 month stepping stone" type of a job. You should be thinking how you're going to grow with that company. After all, don't you want to invest your energy and time with a company that is going to continue to be successful and one that will help you grow?

37. Give me a few examples of how you're results oriented?

Make you give an example where you discuss details and metrics. For example, I was a tutor in my last job and mentored 5 students on their SAT test taking skills and raised their scores by 15% on average after a 3 month teaching stint.

38. How do you feel about taking no for an answer?

It's good to be persistent, but not overbearing. Everyone will face rejection at some point in their life, so at some point you'll have to take no for an answer but then learn why you were turned down.

39. How well do you know this industry?

Two things businesses need to pay attention to in their industries are what their competition is doing and the customers. You may not always agree with your competitors but it is important to be aware of what changes they are making. Very well. I have been in the industry for over 6 years.

40. Describe a time when you've been overwhelmed with work?

Show how you were able to over the "overwhelmed" feeling - by delegating tasks, getting people on your team to help you out, or by prioritizing your work and focusing on the most important issues first In RDBMS.

41. What are three positive character traits you don't have?

List three attributes that you aspire to attain / build in the next few years - and then explain how you would develop those.

42. What makes a product successful?

Basing on the monetization, these questions give you the chance to prove your personal try. Do not show extremely your optimism and pursue the unreality. Give your answers the reality.
It is useful to predict a five to ten- year- scenario of expectations in order to gain your targets that you set up and it is the period of time to see how your plans and targets are performed.
Therefore, the quality of the product and marketability of the mentioned industry need to be highlighted. This will help you to achieve the interviewer's attention and insurance to you personality and you can get the honest and long- term goals.

43. 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!)

44. Explain me about a challenge or conflict you've faced at work In RDBMS, and how you dealt with it?

In asking this interview question, your interviewer wants to get a sense of how you will respond to conflict. Anyone can seem nice and pleasant in a job interview, but what will happen if you're hired?. Again, you'll want to use the S-T-A-R method, being sure to focus on how you handled the situation professionally and productively, and ideally closing with a happy ending, like how you came to a resolution or compromise.

45. What motivates you to work In RDBMS?

Describe what makes you passionate about the work. It could be the company's vision, the product, your desire to succeed, the clients, your peers and so on. They key is to first understand what internally motivates you to do your job and then to emphasize that in a positive way

46. What motivates you to succeed?

Your interviewer will likely want to know the reasons why you will remain motivated to do your best during your employment with the company In RDBMS. Perhaps you are interested in being challenged, but you may also have interest in being recognized for your hard work in the form of the number of sales you can attain. A great example answer for this question is “I always do my best in everything, including my job. I take pride in my success, and I also want the company for which I work to be successful. Being affiliated with a company that is known for its excellence is very important to me.”

47. How would you be an asset to us In RDBMS?

Think again about the job specification and the skills needed for this role In RDBMS. Have a paragraph prepared highlighting how you will be able to do the job and what you can bring to the team. It goes without saying that this paragraph should be positive.

48. How important is the vision of the company to you?

It should be very important if you want a long standing career. Remember, you're investing your time, energy and earnings potential into a company so you want to make sure it's a sustainably successful company that will grow with you over the long haul.

49. What are your presentation skills like In RDBMS?

Make sure you share a story that demonstrates your presentation skills in front of many people. If you are really brave, offer to give a snippet of that presentation to the interviewer. This will definitely be different from what most people do.

50. How many basketballs would fit in this room?

One. You did not ask what is the maximum number of basketballs you can fit in the room.

51. Where do you see yourself professionally five years from now In RDBMS?

Demonstrate both loyalty and ambition in the answer to this question. After sharing your personal ambition, it may be a good time to ask the interviewer if your ambitions match those of the company.

52. How would your friends describe you?

My friends would probably say that I'm extremely persistent – I've never been afraid to keep going back until I get what I want. When I worked as a program developer, recruiting keynote speakers for a major tech conference, I got one rejection after another – this was just the nature of the job. But I really wanted the big players – so I wouldn't take no for an answer. I kept going back to them every time there was a new company on board, or some new value proposition. Eventually, many of them actually said "yes" – the program turned out to be so great that we doubled our attendees from the year before. A lot of people might have given up after the first rejection, but it's just not in my nature. If I know something is possible, I have to keep trying until I get it.

53. Does your boss know you're here today?

Usually, you probably haven't told your boss for obvious reasons. So it's ok to say that they do not. You don't want to upset the balance at your current job after all and nothing is guaranteed in an interview. The interviewer should understand this stance.

54. What kind of salary do you need In RDBMS?

This is a loaded question and a nasty little game that you will probably lose if you answer first. So, do not answer it. Instead, say something like, that's a tough question. Can you tell me the range for this position? In most cases, the interviewer, taken off guard, will tell you. If not, say that it can depend on the details of the job. Then give a wide range.

55. How do you keep each member of the team involved and motivated?

Many managers mistakenly think that money is the prime motivator for their employees. However, according to surveys by several different companies, money is consistently ranked five or lower by most employees. So if money is not the best way to motivate your team, what is?

Employees' three most important issues according to employees are:
☛ Respect
☛ A sense of accomplishment
☛ Recognition

56. What is your desired salary In RDBMS?

Bad Answer: Candidates who are unable to answer the question, or give an answer that is far above market. Shows that they have not done research on the market rate, or have unreasonable expectations.

Good answer: A number or range that falls within the market rate and matches their level of mastery of skills required to do the job.

57. Why are you leaving your current job?

This is a toughie, but one you can be sure you'll be asked. Definitely keep things positive-you have nothing to gain by being negative about your past employers. Instead, frame things in a way that shows that you're eager to take on new opportunities and that the role you're interviewing for is a better fit for you than your current or last position. For example, “I'd really love to be part of product development from beginning to end, and I know I'd have that opportunity here.” And if you were let go? Keep it simple: “Unfortunately, I was let go,” is a totally OK answer.

58. Do you have any question regarding this job In RDBMS?

Never ask Salary, perks, leave, place of posting, etc. regarded questions. Try to ask more about the company to show how early you can make a contribution to your organization like. “Sir, with your kind permission I would like to know more about induction and developmental programs?” OR Sir, I would like to have my feedback, so that I can analyze and improve my strengths and rectify my shortcomings.

59. Rate yourself on a scale of 10?

If you truly believe you're a 10, you better be able to explain why with examples / stories. If you believe you're a great contributor and have room to grow, say 8 or 9. If you're below that, explain what you would do to improve yourself to get the ranking you believe you can be.

60. Tell me the difference between good and exceptional?

Good gets the job done on time and is high quality. Exceptional is a game changer - it stands out, it's creative, it's above and beyond expectations. Tell the interviewer a story about how you were exceptional.

61. Explain me about a time when you reached a goal within a tight deadline?

I work well under pressure to meet deadlines without jeopardizing the quality of my work. I have always worked in a fast pace environment where we are constantly under pressure to achieve best results within a time frame.

62. What does "thinking outside the box" mean to you?

It means not doing things exactly the same way as everyone else. You've got to challenge the status quo and bring something new to the business.

63. What techniques and tools do you use to keep yourself organized In RDBMS?

Utilizing a calendar, having a notebook with your "to do" list, focusing on your top 3 priorities each and every day, utilizing a systematic way of storing documents on your computer (like box.net)

64. What is your greatest weakness In RDBMS? What are you doing to improve it?

I believe my biggest weakness In RDBMS is wanting to help anyone I can help. What I mean is I am willing to take on task that are not my job. I want to learn all I can. However, that has helped me get promoted or even asked to help in times of need in other department. I have been know as the "go to person" when help is needed.

65. How do you evaluate your ability to handle conflict?

I pride myself on being a good problem solver. Through my previous job and management positions I have faced numerous conflicts in different situations, and my experiences have helped me to hone my issue resolution skills. I believe that it is important to get to and address the root of the issue, in a respectable manner.

66. There's no right or wrong answer, but if you could be anywhere in the world right now, where would you be?

Just be honest about where you'd like to be - you never know - you may end up bonding with the interviewer with the location. However, you want to stress that you want to work out of the location that you're interviewing for.

67. What are three positive things your last boss would say about you?

It's time to pull out your old performance appraisals and boss's quotes. This is a great way to brag about yourself through someone else's words:
“My boss has told me that I am the best designer he has ever had. He knows he can rely on me, and he likes my sense of humor.”

68. Explain an idea that you have had and have then implemented in practice?

Often an interview guide will outline the so-called ‘STAR' approach for answering such questions; Structure the answer as a situation, task, action, and result: what the context was, what you needed to achieve, what you did, and what the outcome was as a result of your actions.

69. What's the most rewarding work you've ever done and why?

Companies love it when you discuss how you've made an impact on your teammates, clients, or partners in the business or in school. It should be rewarding because of the hard work and creative process that you've put into it.

70. Why should the we hire you as this position In RDBMS?

This is the part where you link your skills, experience, education and your personality to the job itself. This is why you need to be utterly familiar with the job description as well as the company culture. Remember though, it's best to back them up with actual examples of say, how you are a good team player.

71. How long will it take for you to make a significant contribution?

First define significant contribution - once you do that - lay out a timeline plan in which you think you can achieve that.

72. How much time do you need to join the organization In RDBMS?

You should be able to join it right away, barring plans you've already made (family travel, vacation, other obligations). The key is to simply be open in communication of what's already committed on your schedule. Most companies are accommodating. If they are not, weight the importance of joining that company vs. your plans.

73. How would you rate your communication and interpersonal skills for this job In RDBMS?

These are important for support workers. But they differ from the communication skills of a CEO or a desktop support technician. Communication must be adapted to the special ways and needs of the clients. Workers must be able to not only understand and help their clients, but must project empathy and be a warm, humane presence in their lives.

74. Are you planning to continue your studies and training In RDBMS?

If asked about plans for continued education, companies typically look for applicants to tie independent goals with the aims of the employer. Interviewers consistently want to see motivation to learn and improve. Continuing education shows such desires, especially when potentials display interests in academia potentially benefiting the company.
Answering in terms of “I plan on continuing my studies in the technology field,” when offered a question from a technology firm makes sense. Tailor answers about continued studies specific to desired job fields. Show interest in the industry and a desire to work long-term in said industry. Keep answers short and to the point, avoiding diatribes causing candidates to appear insincere.

75. What would you do if our competitor offered you a position In RDBMS?

I would weigh the offer and consider it, however, this company and this role is my first choice.

76. Why do you want to work In RDBMS for this organisation?

Being unfamiliar with the organisation will spoil your chances with 75% of interviewers, according to one survey, so take this chance to show you have done your preparation and know the company inside and out. You will now have the chance to demonstrate that you've done your research, so reply mentioning all the positive things you have found out about the organisation and its sector etc. This means you'll have an enjoyable work environment and stability of employment etc – everything that brings out the best in you.