1. What can you offer us that someone else can not?
Bad Answer: Going negative - if the candidate starts trash talking other candidates, it's a sure sign of a bad attitude. Also, if they can't provide a solid answer, it may show that they lack thorough knowledge of the skills the job requires, and an understanding of where they fit in.
Good answer: The candidate can name specific skills, abilities or understandings they have that apply directly to the job that other candidates are unlikely to have, or are in short supply.
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.
3. 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.
4. What do you consider to be your greatest strength?
There isn't any right answer. Just make sure to make your response positive and true. A few good examples include: Your ability to solve complex problems, Your ability to work well on a team, Your ability to shine under pressure, Your ability to focus in chaotic situations, Your ability to prioritize and organize, Your ability to cut through the fluff to identify the real issues, Your ability to influence other positively. If your strength relates to the position in question that will be more beneficial - but again be honest, don't create a strength for yourself just because you think it will sound good.
5. 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.
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 Regarding Software Technical 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).
7. What has been your biggest professional disappointment?
When discussing a professional disappointment, make sure to discuss a scenario you could not control. Be positive about the experience and accept personal responsibility where applicable.
8. How did you hear about the position Regarding Software Technical Architect?
Another seemingly innocuous interview question, this is actually a perfect opportunity to stand out and show your passion for and connection to the company and for job Regarding Software Technical Architect. For example, if you found out about the gig through a friend or professional contact, name drop that person, then share why you were so excited about it. If you discovered the company through an event or article, share that. Even if you found the listing through a random job board, share what, specifically, caught your eye about the role.
9. What makes you right for this position?
This question can be tricky because you need to show your worth Regarding Software Technical Architect without sounding cocky or arrogant. Research the business ahead of time and become familiar with its mission and values. Take the time to figure out how your personal qualities fit the needs of the business and use that fit to provide your answer.
10. Top 13 Situational Interview Questions Regarding Software Technical Architect:
Situational interviews Regarding Software Technical Architect 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 Regarding Software Technical Architect?
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 Regarding Software Technical Architect?
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?
11. What have you learned from mistakes on the job?
Candidates without specific examples often do not seem credible. However, the example shared should be fairly inconsequential, unintentional, and a learned lesson should be gleaned from it. Moving ahead without group assistance while assigned to a group project meant to be collaborative is a good example.
12. Explain what are your weaknesses Regarding Software Technical 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.
13. How would your references describe you?
Think of three major characteristics that demonstrate your best qualities related to work and then have quick stories to describe why.
14. What do you ultimately want to become?
Do you want to be an entry level worker Regarding Software Technical Architect? Do you want to be a leader? Do you want to be an entrepreneur? Do you want to be a philanthropist? Do you want to be in middle management? Ask yourself these questions to figure it out.
15. What is your greatest achievement outside of work Regarding Software Technical Architect?
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.
16. Explain me what do you know about our company?
Bad Answer: They don't know much about the company. If a candidate is serious and enthusiastic, they should have done some basic research.
Good answer: An answer that shows they've really done their homework and know what the company does, any important current events that involve the company, and the work culture.
17. What are your greatest professional strengths Regarding Software Technical Architect?
When answering this question, we recommends being accurate (share your true strengths, not those you think the interviewer wants to hear); relevant (choose your strengths that are most targeted to this particular position Regarding Software Technical Architect); and specific (for example, instead of “people skills,” choose “persuasive communication” or “relationship building”). Then, follow up with an example of how you've demonstrated these traits in a professional setting.
18. What motivates you at the work place?
Keep your answer simple, direct and positive. Some good answers may be the ability to achieve, recognition or challenging assignments.
19. 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.
20. 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.
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.
22. 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.
23. What is your greatest strength Regarding Software Technical Architect?
This is your time to shine. Just remember the interviewer is looking for work related strengths Regarding Software Technical Architect. Mention a number of them such as being a good motivator, problem solver, performing well under pressure, being loyal, having a positive attitude, eager to learn, taking initiative, and attention to detail. Whichever you go for, be prepared to give examples that illustrate this particular skill.
24. What are you looking for in a new position Regarding Software Technical Architect?
I've been honing my skills Regarding Software Technical Architect for a few years now and, first and foremost, I'm looking for a position where I can continue to exercise those skills. Ideally the same things that this position has to offer. Be specific.
25. Think about the changes you have seen and tell me how you handle change?
You can cite personal life changes, work place changes, career changes, technology change, industry change. The key is to discuss how seeing or experiencing that change has helped your development. For example, the recent changes in social media has broadened my horizons and helped me learn new forms of efficient marketing.
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.
27. 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 Regarding Software Technical 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.
28. 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.
29. 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 Regarding Software Technical Architect. 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.”
30. Why did you choose your major in college or tech school?
People usually choose their major based on their passions or the career path they want to head towards.
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).
32. Describe yourself in three words?
Pick three adjectives but then back up each with a real life story that demonstrates those characteristics.
33. 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 Regarding Software Technical Architect.
34. How do you feel about this company's vision?
First find out where the company envisions itself in 3-5 years. If you can't find the vision of the company, that's probably a big question mark on the company itself. Once you do, identify how those company's visions align to your personal values and goals and then articulate how tightly correlated that is to the interviewer. For example - this company wants to be the #1 provider of green technology in the world and I feel strongly about that vision because we've got a chance to collectively impact the world to become a greener society and save our clients at the same time!
35. 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.
36. Tell me about a time when you were held accountable for a problem that you hadn't caused?
If someone puts the blame on you (incorrectly), the best thing you can do is NOT to retaliate. You want to make it known that you were not to blame (explain all the facts) and then focus on fixing the problem in the best way possible.
37. 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.
38. 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.'
39. Do you have good manners? What types of people need to be treated with good manners?
You should have good manners. Everyone should be treated with courtesy and respect.
40. What types of situations do you consider "unfixable"?
Most situations are "fixable" - the ones that are not are typically related to business ethics (someone is cheating the company, someone is stealing, etc)
41. What are ideas or initiatives you've led and what was the outcome?
Describe your most unique ideas and initiatives that had the best results for the company. Make sure you highlight your creativity, your results, your diligence and your ability to execute.
42. What do you consider to be your weaknesses?
What your interviewer is really trying to do with this question-beyond identifying any major red flags-is to gauge your self-awareness and honesty. So, “I can't meet a deadline to save my life Regarding Software Technical Architect” is not an option-but neither is “Nothing! I'm perfect!” Strike a balance by thinking of something that you struggle with but that you're working to improve. For example, maybe you've never been strong at public speaking, but you've recently volunteered to run meetings to help you be more comfortable when addressing a crowd.
43. What are your presentation skills like Regarding Software Technical 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.
44. 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 Regarding Software Technical Architect.
45. What have you done to prepare yourself to be a supervisor?
1. Learn from current supervisors (best practices)
2. Mentor others
3. Be exceptionally good at your current job so that it builds your credibility
4. Have a high emotional IQ
Do the following steps:
☛ 1. Turn ON two switches, and leave one OFF.
☛ 2. Wait a few minutes.
☛ 3. Turn one switch from ON to OFF. One is now ON and two are OFF
☛ 4. Enter the room. - If the light is ON, it is controlled by the switch you left ON. - If the light bulb is OFF, touch it. If it is warm it is controlled by the switch you turned ON and OFF. If it is cold, it is controlled by the switch you never turned on.
47. What's a time you disagreed with a decision that was made at work?
Everyone disagrees with the boss from time to time, but in asking this interview question Regarding Software Technical Architect, hiring managers want to know that you can do so in a productive, professional way. “You don't want to tell the story about the time when you disagreed but your boss was being a jerk and you just gave in to keep the peace. And you don't want to tell the one where you realized you were wrong,”. Tell the one where your actions made a positive difference on the outcome of the situation, whether it was a work-related outcome or a more effective and productive working relationship.
48. How would you impact the company?
Consider first the role that you're applying for and then think of 3 ways where you could potentially impact the company's bottom line and top line. Then consider how you impact the company in a creative manner (how do you help productivity, the development of new products, marketing etc - of course this part is specific to the role you're applying for)
49. What did you major in and why?
Tell them your major and the motivations behind why you chose it and how it's helped to prep your of this potential job.
50. How would your former employer describe you?
In all likelihood, the interviewer will actually speak with your former employer so honesty is key. Answer as confidently and positively as possible and list all of the positive things your past employer would recognize about you. Do not make the mistake of simply saying you are responsible, organized, and dependable. Instead, include traits that are directly related to your work as a medical assistant, such as the ability to handle stressful situations and difficult patients, the way you kept meticulous records, and more.
51. 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.
This depends on the job role. Make sure you break it down into
53. 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.
54. What do you know about this department?
One good way to find out about the department is to try to "informally" interview the existing employees over coffee (outside of the office) if possible. It's hard if you don't have any connections there, but if you do a great way to learn about it. Other than that, it's often hard to learn about the department so you can turn the table back on them by asking questions to learn about it.
It should say the same thing - after all - if you think this salary is fair then it should suit the responsibilities!
56. 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.
57. 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.
58. What aspect of supervision do you find the most difficult?
Managing different personalities and keeping them focused on the goal at hand.
59. What do you expect to be earning in 5 years Regarding Software Technical Architect?
Discuss how you expect yourself to be excellent at your job. Thus, it would be reasonable to expect pay that is based on the merit of your work.
60. How would you motivate your team members to produce the best possible results?
Trying to create competitive atmosphere, trying to motivate the team as a whole, organizing team building activities, building good relationships amongst people.
61. What is your biggest achievement?
Quality work to be is about doing work to the require or set standard, which is very important when it comes to warehouse operations.
62. 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.
63. What type of work environment do you prefer?
Ideally one that's similar to the environment of the company you're applying to. Be specific.
64. 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.”
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.
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)
67. What problems have you encountered at work?
Wow, do we have problems! Where do I begin? Well, most of the problems are internal, just people not working well with each other. I have one person on our team who is a real problem, but it seems like management is afraid to do anything about it. So we all end up having to do extra work to cover for this person, who just doesn't work. We all say that he's retired in place. I think he's just holding on until retirement in a couple years. But he's a real problem. I complain about it--a lot--but nothing ever seems to get done. I've even written negative reviews about the person, hoping he will get canned, but it doesn't happen. I can't wait for him to retire.
68. Why do you want to work Regarding Software Technical 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.
69. How do you handle stressful situations?
By remaining calm, weighing out all my options and executing a plan to get the situation resolve .
70. Why should the we hire you as this position Regarding Software Technical 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.
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.
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.
73. What do you look for in terms of culture -- structured or entrepreneurial?
A good answer is to discuss the importance of having both elements in a company Regarding Software Technical Architect. Structure is good to maintain a focus on priorities and making sure people are productive but having an entrepreneurial spirit can help cultivate new ideas that can truly help the company.
74. What is your desired salary Regarding Software Technical Architect?
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.
75. Do you think a leader should be feared or liked?
Liked. You want to work harder for people that inspire and motivate you. Fear only lasts for so long.
76. How would you define success?
Success is defined differently for everybody. Just make sure the parameters are defined by you with regards to work life balance, financial gain, career growth, achievements, creating meaningful work / products and so forth. If you can clearly articulate what it means to you that is a strong answer.
77. Do you like to start personal relationships with other employees?
Well, the right answer is yes and no. Good personal relations can improve the overall performance of a team. But on the other hand, you should not let your emotions to affect your decisions in work.
Show that you were communicative with that person and that you were able to collaborate effectively in sharing ideas and work tasks. They want to see that you can be a team player.
79. How much do you expect to get paid Regarding Software Technical Architect?
For this be prepared and research salary to find out what similar positions are paying in your area before you go to the interview. Try to find this information out before giving your salary expectations. You can and should provide a range instead of an exact number. But again, don't say any numbers you're not comfortable with because if the employer offers you a salary at the lowest end of your range, you don't have much to negotiate with when it comes to getting a higher salary.
