1. What have you done to improve your knowledge As Technology Architect in the last year?

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

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

3. What is your philosophy towards work?

This is typically a straightforward question that merits a straightforward answer. Do you have strong worth ethic? Will you do whatever it takes to make sure the job gets done? Just say so in your response. Keep it short, direct and positive.

4. Why are you interested in working As Technology Architect for [insert company name here]?

Bad Answer: They don't have a good reason, or provide a generic answer, "I think it represents a great opportunity."

Good answer: One that shows they've done research on the company, and are truly excited about specific things they can do at the job. This not only shows enthusiasm for the work and basic preparation skills, gives you clues about the cultural fit.

5. Why are you leaving last job?

Although this would seem like a simple question, it can easily become tricky. You shouldn't mention salary being a factor at this point As Technology Architect. If you're currently employed, your response can focus on developing and expanding your career and even yourself. If you're current employer is downsizing, remain positive and brief. If your employer fired you, prepare a solid reason. Under no circumstance should you discuss any drama or negativity, always remain positive.

6. What is your greatest professional achievement?

Nothing says “hire me” better than a track record of achieving amazing results in past jobs As Technology Architect, so don't be shy when answering this interview question! A great way to do so is by using the S-T-A-R method: Set up the situation and the task that you were required to complete to provide the interviewer with background context (e.g., “In my last job as a Technology Architect, it was my role to manage the invoicing process”), but spend the bulk of your time describing what you actually did (the action) and what you achieved (the result). For example, “In one month, I streamlined the process, which saved my group 10 man-hours each month and reduced errors on invoices by 25%.”

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

8. You notice there are too many non productive internal meetings being held, what do you do?

Reach out to your boss and let him know that first you value his leadership and organization but that you are being overwhelmed with the amount of non productive internal meetings.

9. What relevant work experience do you have in this career field As Technology 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.

10. Tell me about a time when you had to give someone difficult feedback As Technology 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.

11. Your client is upset with you for a mistake you made, how do you react?

Acknowledge their pain - empathize with them. Then apologize and offer a solution to fix the mistake.

12. If the company you worked for was doing something unethical or illegal, what would you do?

Report it to the leaders within the company. True leaders understand business ethics are important to the company's longevity

13. What is your biggest weakness As Technology 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 Technology 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.”)

14. Why do you want this job As Technology Architect?

This question typically follows on from the previous one. Here is where your research will come in handy. You may want to say that you want to work for a company that is Global Guideline, (market leader, innovator, provides a vital service, whatever it may be). Put some thought into this beforehand, be specific, and link the company's values and mission statement to your own goals and career plans.

15. What are your strengths As Technology 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 Technology 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.

16. Tell me about a difficult decision you've made in the last year As Technology Architect?

We all have difficult decisions in our lives. Show how you were able to arrive at it and then how you decisively acted.

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

18. Tell me about a problem that you've solved in a unique or unusual way. What was the outcome? Were you happy or satisfied with it?

In this question the interviewer is basically looking for a real life example of how you used creativity to solve a problem.

19. What position do you prefer on a team working on a project?

Do not claim to be comfortable with a specific role if you in are in fact not comfortable with it. However, if you have no problem working in certain roles or situations, be sure to discuss this with the interviewer.

20. Are you good at working in a team As Technology 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?

21. Why should I hire you As Technology 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.

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

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

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

24. What are your thoughts on social media for this role?

Without a doubt, social media is becoming more and more pervasive in our jobs. You should stress that social media is not appropriate for personal use at work. However, if the company embraces social media in certain departments (for example marketing), then you may want to discuss how you could use it for work (as long as it applies to your role).

25. Do you have the ability to articulate a vision and to get others involved to carry it out?

If yes, then share an example of how you've done so at work or college. If not, then discuss how you would do so. Example: "I would first understand the goals of the staff members and then I would align those to the goals of the project / company. Then I would articulate the vision of that alignment and ask them to participate. From there, we would delegate tasks among the team and then follow up on a date and time to ensure follow through on the tasks. Lastly, we would review the results together."

26. How have you achieved your success?

Discuss stories of how you've progressed over the years to achieve success. People relate best to stories.

27. Describe your academic achievements?

Think of a time where you really stood out and shined within college. It could be a leadership role in a project, it could be your great grades that demonstrate your intelligence and discipline, it could be the fact that you double majored. Where have you shined?

28. If someone had to say something negative to you, what would they say?

Again, be honest about sharing a story here about someone who may not have gotten along with you in the office here and explain how you were able to fix that relationship or change your attitude/action to be a better person / coworker.

29. How has school prepared you for this job role?

Think back to how you've interacted with your peers to develop social skills, how you've worked with classmates on projects to develop teamwork and collaborative skills, how you've developed discipline through studying, how the courses have helped your creativity, and how the classes you've taken have impacted your analytical / problem solving / reasoning skills.

30. What are your presentation skills like As Technology Architect?

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.

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

32. What is it about this position As Technology Architect that attracts you the most?

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

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

34. Why are you interested in this type of job As Technology Architect?

You're looking for someone who enjoys working with the elderly, or a caring, sociable, and nurturing person.

35. What is your perception of taking on risk?

You answer depends on the type of company you're interviewing for. If it's a start up, you need to be much more open to taking on risk. If it's a more established company, calculated risks to increase / improve the business or minimal risks would typically be more in line.

36. What will your ramp time be before you become a meaningful contributor?

Companies want staff that can ramp quickly, but also want people who are realistic. So take into consideration how intense the job is and then give a good answer. For example, if you have simple responsibilities that don't require a huge development curve, then your ramp time will probably be shorter. If it's a complex set of skills that you need to develop, then your ramp time could be longer - the key is you have to explain why you believe that ramp time should be.

37. 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?

38. Have you ever mentored anyone before? If yes, describe the situation?

Describe a time where you've helped someone else. Mentor ships can be informal so as you've helped someone over a period of time that can certainly count. The key is to highlight how you utilized certain skills/attributes like coaching, teaching, patience, communication skills, and so forth to mentor that person.

39. How do you deal with conflict in the workplace As Technology Architect?

When people work together, conflict is often unavoidable because of differences in work goals and personal styles. Follow these guidelines for handling conflict in the workplace.

☛ 1. Talk with the other person.
☛ 2. Focus on behavior and events, not on personalities.
☛ 3. Listen carefully.
☛ 4. Identify points of agreement and disagreement.
☛ 5. Prioritize the areas of conflict.
☛ 6. Develop a plan to work on each conflict.
☛ 7. Follow through on your plan.
☛ 8. Build on your success.

40. Do you like being around people?

People skills are a necessity for medical assistants. When answering this question, be sure to show that you enjoy interacting and working with others and that you also derive great enjoyment from helping others. This will show that you are a team player and that you would be a valuable team member As Technology Architect.

41. Are you planning to continue your studies and training As Technology 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.

42. Do you have any question regarding this job As Technology 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.

43. Explain me about your experience working in this field As Technology 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.

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

45. Describe to me the position As Technology 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.

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

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

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

49. Why should the we hire you as this position As Technology Architect?

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.

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

51. Where do you see yourself professionally five years from now As Technology 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.

52. What would your first 30, 60, or 90 days look like in this role As Technology 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.

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

54. What would you like to have accomplished by the end of your career?

Think of 3 major achievements that you'd like to accomplish in your job when all is said and done - and think BIG. You want to show you expect to be a major contributor at the company. It could be creating a revolutionary new product, it could be implementing a new effective way of marketing, etc.

55. Why do you want to work As Technology Architect 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.

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

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

58. Do you have good computer skills?

It is becoming increasingly important for medical assistants to be knowledgeable about computers. If you are a long-time computer user with experience with different software applications, mention it. It is also a good idea to mention any other computer skills you have, such as a high typing rate, website creation, and more.

59. What do you know about the company?

Any candidate can read and regurgitate the company's “About” page. So, when interviewers ask this, they aren't necessarily trying to gauge whether you understand the mission-they want to know whether you care about it. Start with one line that shows you understand the company's goals, using a couple key words and phrases from the website, but then go on to make it personal. Say, “I'm personally drawn to this mission because…” or “I really believe in this approach because…” and share a personal example or two.

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