1. What's your dream job?

Along similar lines, the interviewer wants to uncover whether this position As Data Warehouse Architect is really in line with your ultimate career goals. While “an GGL star” might get you a few laughs, a better bet is to talk about your goals and ambitions-and why this job will get you closer to them.

2. What experience do you have As Data Warehouse Architect?

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)

3. What have you done to improve your skills over the past year As Data Warehouse Architect?

You'll want to be prepare with some very specific examples of what you've done over the last year and what you're currently doing to improve your professional knowledge and skill set as well as anything else you're doing the shows self improvement.

4. Top 11 Interview Questions to Ask when Emotional Intelligence Matters As Data Warehouse Architect:

Emotional intelligence, or EQ, has come into vogue as a good trait to hire for.

EQ is the ability to use emotional information to guide thinking and behavior, to recognize other people's emotions and your own, and to discriminate between different feelings and label them appropriately.

EQ is considered essential to help teams function well. Here are some of the top questions for help you get an idea of how candidates perceive their emotions and those of others.

1. If you started a company today, what would its top values be?

2. Who inspires you? Why?

3. How could you create more balance in your life?

4. What makes you angry?

5. How do you have fun?

6. How good are you at asking for help?

7. How did you deal with a bad day?

8. What's something you're really proud of? Why?

9. Tell me about a time when your mood altered your performance (positively or negatively).

10. Has there ever been a time when you felt you needed to change your behavior at work? How did you do it?

11. Did you create friendships that lasted while working at a previous job?

5. What are your strengths As Data Warehouse Architect?

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 Data Warehouse Architect 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.

6. What is your biggest weakness As Data Warehouse Architect?

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 Data Warehouse Architect 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.”)

7. What relevant work experience do you have in this career field As Data Warehouse Architect?

Talk about specific work related experience for the position you're interviewing for. Make sure the experience is relevant. Don't talk about previous experience that is not related to the position in question. If you don't have specific career related experience speak about prior experience that has helped you develop the specific knowledge and skills required for the position you are applying for.

8. What education or training have you had that makes you fit for this profession As Data Warehouse Architect?

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.

9. Tell us about a suggestion you have made that has benefited an organization you've worked for?

This is another opportunity to show the interviewer what you're capable of so make sure to be prepared for this type of question. Have an example ready and make sure its an example of a suggestion you've made that was accepted and that have positive influence. If you can come up with an example that relates to the position you're applying for that would be even better.

10. Explain what are your weaknesses As Data Warehouse Architect?

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.

11. How long do you want to work for us if we hire you?

Here being specific is probably not the best approach. You may consider responding, “I hope a very long time.” Or “As long as we're both happy with my performance.”

12. Are you good at working in a team As Data Warehouse Architect?

Before you answer, consider how you best contribute to a team:

☛ Do you get along easily with people?
☛ Are you an effective collaborator?
☛ Can you communicate with people from various backgrounds and with different personalities?
☛ Can you motivate people?
☛ Do you know how to push back tactfully?
☛ Can you mediate conflicts?
☛ Can you deal with difficult personalities?

13. How do you propose to compensate for your lack of experience?

The first thing you should do is discuss experience you have the interviewer is unfamiliar with. Once that is detailed, tell the person conducting the interview that you are able to learn new tasks and information in a reasonable period of time and possess a strong work ethic. However, only state this if you can live up to these expectations.

14. What do you know about our company?

You always want to make sure that you're pretty familiar with the company that you're interviewing with. Nothing looks worse than a candidate who knows nothing about the company they say they're interested in working for. Find out everything you can about the company, its culture and its goals. You will also want to know how the company is positioned in its market as well as who its major competitors are.

15. Tell me about a time when you had to give someone difficult feedback As Data Warehouse Architect?

By asking this question, your interviewer hopes to learn whether you can communicate effectively, address issues in the workplace and motivate others during difficult times. Giving negative feedback requires honesty, thoughtfulness and tact. Answering this question well can help show an interviewer that you would be a good fit for a managerial position or a position that involves working closely with others.

16. Have you ever you have been in a position As Data Warehouse Architect 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.

17. 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 As Data Warehouse Architect , I just wanted to make change for proper growth.

18. What critical component of this position As Data Warehouse Architect 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 As Data Warehouse Architect (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).

19. How do you measure success?

There may be several good answers. Some include: you're able to set realistic, yet aggressive goals that push you and you're able to achieve them, you go the extra mile on all projects, client satisfaction is high, your boss is elated at your performance on all projects, etc.

20. Would you like doing repetitive work?

Why not, I am not only doing a repetitive work but also earning but also getting a good salary by the company As Data Warehouse Architect. And second thing is that nothing is interesting in the life till we are not interested.

21. Do you think you are overqualified for this position As Data Warehouse Architect?

No matter your previous job experience or educational background, be sure to tell the interviewer you have the knowledge and skills to successfully execute the job responsibilities.

22. How do you evaluate success As Data Warehouse Architect?

I evaluate success As Data Warehouse Architect in different ways. At work, it is meeting the goals set by my supervisors and my fellow workers. It is my understanding, from talking to other employees, that the Global Guideline company is recognized for not only rewarding success but giving employees opportunity to grow as well.

23. Tell me why do you want this job As Data Warehouse Architect?

Bad Answer: No solid answer, answers that don't align with what the job actually offers, or uninspired answers that show your position is just another of the many jobs they're applying for.

Good answer: The candidate has clear reasons for wanting the job that show enthusiasm for the work and the position, and knowledge about the company and job.

24. Do you have any blind spots?

This question is often meant to trick candidates since acknowledgment of blind spots would indicate they were aware of them. Also, do not disclose bad habits or other personal concerns. Let the interviewer find out about your personal flaws through the course of the interview without directly stating these flaws.

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

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

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

28. What is your greatest strength? How does it help you As Data Warehouse Architect?

One of my greatest strengths, and that I am a diligent worker... I care about the work getting done.. I am always willing to help others in the team.. Being patient helps me not jump to conclusions... Patience helps me stay calm when I have to work under pressure.. Being a diligent worker.. It ensures that the team has the same goals in accomplishing certain things.

29. What challenges are you looking for in this position?

A typical interview question to determine what you are looking for your in next job, and whether you would be a good fit for the position being hired for, is “What challenges are you looking for in a position As Data Warehouse Architect?” The best way to answer questions about the challenges you are seeking is to discuss how you would like to be able to effectively utilize your skills and experience if you were hired for the job. You can also mention that you are motivated by challenges, have the ability to effectively meet challenges, and have the flexibility and skills necessary to handle a challenging job. You can continue by describing specific examples of challenges you have met and goals you have achieved in the past.

30. How do you handle conflicts with people you supervise?

At first place, you try to avoid conflicts if you can. But once it happens and there's no way to avoid it, you try to understand the point of view of the other person and find the solution good for everyone. But you always keep the authority of your position.

31. Do you work well on a team? How would you define teamwork?

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

32. What are your salary requirements As Data Warehouse Architect?

The #1 rule of answering this question is doing your research on what you should be paid by using site like Global Guideline. You'll likely come up with a range, and we recommend stating the highest number in that range that applies, based on your experience, education, and skills. Then, make sure the hiring manager knows that you're flexible. You're communicating that you know your skills are valuable, but that you want the job and are willing to negotiate.

33. What does success mean to you?

I am punctual, I always have excellent attendance on any job As Data Warehouse Architect, 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.

34. Why do you want to join our company?

This is a question that is aimed at finding out whether you know enough about the company and the basic market. The best way to answer this question is to do some research on the company and highlight its positive points.

35. What other companies are you interviewing with?

Companies ask this for a number of reasons, from wanting to see what the competition is for you to sniffing out whether you're serious about the industry. “Often the best approach is to mention that you are exploring a number of other similar options in the company's industry,”. It can be helpful to mention that a common characteristic of all the jobs you are applying to is the opportunity to apply some critical abilities and skills that you possess. For example, you might say 'I am applying for several positions with IT consulting firms where I can analyze client needs and translate them to development teams in order to find solutions to technology problems.'

36. 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.)

37. Why do you feel you will excel at rhis job?

This question presents an excellent opportunity for you to discuss your education, qualifications and personal traits. You might say something like “I studied property management as well as behavior during my college years and I have two years' experience in real estate.
I can gauge the homes or apartments in which clients will be interested based solely upon the needs of their families. Finally, my organizational skills will allow me to schedule appointments or showings confidently and arrive for them punctually.” This shows your interviewer that you have all of the skills necessary to become successful not only for yourself, but also for your employer.

38. Why should we select you not others?

Here you need to give strong reasons to your interviewer to select you not others. Sell yourself to your interviewer in interview in every possible best way. You may say like I think I am really qualified for the position. I am a hard worker and a fast learner, and though I may not have all of the qualifications that you need, I know I can learn the job and do it well.”

39. 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).

40. How do you imagine a typical day of an employee in our company As Data Warehouse Architect?

Just do not say that you imagine to only walk and watch what people do. Rather try to show them your attention to details and proactive attitude to job. Mention that you would try to observe the problems, weaknesses as well as opportunities to improve the results and take measures according to it.

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

42. What is it about this position As Data Warehouse Architect that attracts you the most?

Use your knowledge of the job description to demonstrate how you are a suitable match for the role.

43. How do you handle your anger?

I don't get angry very easily but in the rare occasion that I do, I hold it in and act as though nothing is wrong.

44. If hired, how do you intend on making a difference with our company?

Dedicate myself to learn everything about the new company that I can, look for ways and ideas that could improve, processes, safety, removing obstacles from the associates, I want to advance within the company.

45. What are your personal skills which make you a candidate for the position As Data Warehouse Architect?

The list of crucial character traits includes patience, tact, and poise, with personal and cultural sensitivity. One needs the ability to work long hours, with much walking and some physical tasks. But the most important trait of all is to love people and to have the desire to care for them.

46. How would you estimate the weight of the Chrysler building?

This is a process guesstimate where the interviewer wants to know if you know what to ask. First, you would find out the dimensions of the building (height, weight, depth). This will allow you to determine the volume of the building. Does it taper at the top? (Yes.) Then, you need to estimate the composition of the Chrysler building. Is it mostly steel? Concrete? How much would those components weigh per square inch? Remember the extra step: find out whether you're considering the building totally empty or with office furniture, people, etc. If you're including the contents, you might have to add 20 percent or so to the building's weight.

47. Why should I hire you As Data Warehouse Architect?

To close the deal on a job offer, you MUST be prepared with a concise summary of the top reasons to choose you. Even if your interviewer doesn't ask one of these question in so many words, you should have an answer prepared and be looking for ways to communicate your top reasons throughout the interview process.

48. What have you done to reduce costs, increase revenue, or save time?

Even if your only experience is an internship, you have likely created or streamlined a process that has contributed to the earning potential or efficiency of the practice. Choose at least one suitable example and explain how you got the idea, how you implemented the plan, and the benefits to the practice.

49. Why are you leaving the present company?

According to me we can not grow in the field without taking more responsibilities and risks and also we can't enhance our team leading capabilities, managerial skills without expose to wide range of people.

50. Where do you see yourself in five years As Data Warehouse Architect?

If asked this question, be honest and specific about your future goals, but consider this:
A hiring manager wants to know
☛ a) if you've set realistic expectations for your career,
☛ b) if you have ambition (a.k.a., this interview isn't the first time you're considering the question), and
☛ c) if the position aligns with your goals and growth. Your best bet is to think realistically about where this position could take you and answer along those lines. And if the position isn't necessarily a one-way ticket to your aspirations?
It's OK to say that you're not quite sure what the future holds, but that you see this experience playing an important role in helping you make that decision.

51. How would you describe your approach to Data Warehouse Architect?

In more general terms, a question such as this gives a candidate the opportunity to talk about their professional philosophy and skills. While the question is general in nature, the best answers are usually quite specific, picking one or two points and exemplifying them with instances from personal history.

52. Why are manhole covers round?

This is a classic brainteaser, which was reportedly first asked by a Microsoft interviewer. Here's how to ""solve"" this brainteaser (remember to speak and reason out loud while solving this brainteaser): Why are manhole covers round? Could there be a structural reason? Why aren't manhole covers square? It would make it harder to fit with a cover. You'd have to rotate it exactly the right way.
The pipes below are also round, so fitting them might be easier, as might be making them. So many manhole covers are round because they don't need to be rotated. There are no corners to deal with. Also, a round manhole cover won't fall into a hole because it was rotated the wrong way, so it's safer. Looking at this, it seems corners are a problem. You can't cut yourself on a round manhole cover. And because it's round, it can be more easily transported. One person can roll it.

53. Describe to me the position As Data Warehouse Architect you're applying for?

This is a “homework” question, too, but it also gives some clues as to the perspective the person brings to the table. The best preparation you can do is to read the job description and repeat it to yourself in your own words so that you can do this smoothly at the interview.

54. Do you have any questions for me?

Good interview questions to ask interviewers at the end of the job interview include questions on the company growth or expansion, questions on personal development and training and questions on company values, staff retention and company achievements.

55. Explain me about your experience working in this field As Data Warehouse Architect?

I am dedicated, hardworking and great team player for the common goal of the company I work with. I am fast learner and quickly adopt to fast pace and dynamic area. I am well organized, detail oriented and punctual person.

56. Where do you see yourself professionally five years from now As Data Warehouse Architect?

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.

57. Have you got any questions?

This is your final opportunity to persuade the interviewer that you are the right candidate for the job. Now is not the time to ask questions about holidays, pay or pensions – all these things can be asked later when you get an offer of employment. Now is the time to ask about any reservations that the interviewer may have about your suitability for the role. You will then give yourself one last chance to persuade the interviewer that you are the right candidate for the job.
Example Thank you. I think we have covered everything. Before we finish the interview I would like to take the opportunity to ask if you have any reservations about my suitability for this role?

58. What do you think is your greatest weakness?

Don't say anything that could eliminate you from consideration for the job. For instance, "I'm slow in adapting to change" is not a wise answer, since change is par for the course in most work environments. Avoid calling attention to any weakness that's one of the critical qualities the hiring manager is looking for. And don't try the old "I'm a workaholic," or "I'm a perfectionist.

59. How would you rate your communication and interpersonal skills for this job As Data Warehouse Architect?

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.

60. What is your greatest weakness As Data Warehouse Architect? What are you doing to improve it?

I believe my biggest weakness As Data Warehouse Architect 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.

61. 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.”

62. Do you think you have enough experience As Data Warehouse Architect?

If you do not have the experience they need, you need to show the employer that you have the skills, qualities and knowledge that will make you equal to people with experience but not necessary the skills. It is also good to add how quick you can pick up the routine of a new job role.

63. How do you handle stressful situations?

By remaining calm, weighing out all my options and executing a plan to get the situation resolve .

64. Tell me something about your family background?

First, always feel proud while discussing about your family background. Just simple share the details with the things that how they influenced you to work in an airline field.

65. Are you planning to continue your studies and training As Data Warehouse Architect?

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.

66. Do you have any question regarding this job As Data Warehouse Architect?

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.

67. What would your first 30, 60, or 90 days look like in this role As Data Warehouse Architect?

Start by explaining what you'd need to do to get ramped up. What information would you need? What parts of the company would you need to familiarize yourself with? What other employees would you want to sit down with? Next, choose a couple of areas where you think you can make meaningful contributions right away. (e.g., “I think a great starter project would be diving into your email marketing campaigns and setting up a tracking system for them.”) Sure, if you get the job, you (or your new employer) might decide there's a better starting place, but having an answer prepared will show the interviewer where you can add immediate impact-and that you're excited to get started.

68. What was the most important task you ever had?

There are two common answers to this question that do little to impress recruiters:
☛ ‘I got a 2.1'
☛ ‘I passed my driving test'
No matter how proud you are of these achievements, they don't say anything exciting about you. When you're going for a graduate job, having a degree is hardly going to make you stand out from the crowd and neither is having a driving licence, which is a requirement of many jobs.

69. How many square feet of pizza are eaten in the United States each month?

This is a classic guesstimate question where you need to think aloud. And so first off you round the U.S. population to 300 million people (it's actually about 315 million but rounding will be much easier and your interviewer will not score you lower for rounding). Then estimate how many people eat pizza. A decent educated guess is two out of every three people, or 200 million. Now let's say the average pizza-eating person eats pizza twice a month, and eats two slices at a time. That's four slices a month. If the average slice of pizza is perhaps six inches at the base and 10 inches long, then the slice is 30 square inches of pizza. So, four pizza slices would be 120 square inches (30 times 4).
Since one square foot equals 144 square inches (12 times 12), let's assume that each person who eats pizza eats one square foot per month. Since there are 200 million pizza-eating Americans, 200 million square feet of pizza are consumed in the U.S. each month. To summarize: 300 million people in America, 200 million eat pizza, average slice of pizza is six inches at the base and 10 inches long or 30 square inches, average American eats four slices of pizza a month, four pieces times 30 square inches equals 120 square inches (one square foot is 144 square inches), so let's assume one square foot per person, and thus one square foot times 200 million people equals 200 million square feet of pizza a month.

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

71. What are your salary expectations As Data Warehouse Architect?

This question is like a loaded gun, tricky and dangerous if you're not sure what you are doing. It's not uncommon for people to end up talking salary before really selling their skills, but knowledge is power as this is a negotiation after all. Again, this is an area where doing your research will be helpful as you will have an understanding of average salary.
One approach is asking the interviewer about the salary range, but to avoid the question entirely, you can respond that money isn't a key factor and you're goal is to advance in your career. However, if you have a minimum figure in mind and you believe you're able to get it, you may find it worth trying.

72. Do you work well under pressure?

Yes.. When it comes down to the wire, the best thing I can to remain focused, have some flexibility, and understand priorities.. Giving them attention in the order they are needed.

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

74. How would you observe the level of motivation of your subordinates?

Choosing the right metrics and comparing productivity of everyone on daily basis is a good answer, doesn't matter in which company you apply for a supervisory role.

75. What features of your previous jobs have you disliked?

It's easy to talk about what you liked about your job in an interview, but you need to be careful when responding to questions about the downsides of your last position. When you're asked at a job interview about what you didn't like about your previous job, try not to be too negative. You don't want the interviewer to think that you'll speak negatively about this job or the company should you eventually decide to move on after they have hired you.

76. Explain an occasion when you had to adapt in the face of a difficult situation?

One of the most useful interview tactics is to remain positive about your work and achievements. This question lets the candidate draw on their own personal history to show how they have been positive and successful in the face of difficulties. Choose a specific occasion to describe, rather than dealing with generic platitudes.

77. Describe a typical work week for this position As Data Warehouse Architect?

Interviewers expect a candidate for employment to discuss what they do while they are working in detail. Before you answer, consider the position As Data Warehouse Architect you are applying for and how your current or past positions relate to it. The more you can connect your past experience with the job opening, the more successful you will be at answering the questions.

78. Give an example of a time you successfully worked As Data Warehouse Architect on a team?

On the whole I prefer to stick to doing what I'm told rather than setting myself up to fail by doing things off my own bat. But there was this one time when I suggested to my boss at the pizza parlor that she try offering an ‘all you can eat' deal to students to boost trade on Mondays. She thought it was an interesting idea but nothing ever came of it.

79. What do you think we could do better or differently?

This is a common one at startups. Hiring managers want to know that you not only have some background on the company, but that you're able to think critically about it and come to the table with new ideas. So, come with new ideas! What new features would you love to see? How could the company increase conversions? How could customer service be improved? You don't need to have the company's four-year strategy figured out, but do share your thoughts, and more importantly, show how your interests and expertise would lend themselves to the job.