1. Did you consider yourself a team player?
Of course you're a team player - who isn't. But a simple yes probably isn't the response the interviewer is looking for. Be ready to provide specific example of how you've worked as part of a cohesive team to get things accomplished and how you've focus on team performance rather than individual performance. Make sure not to brag as this will make it appear as that you're more concerned about your own performance and accomplishments than those of the team.
2. Who has been an inspiration for you?
Cite your role models (possible examples could be your parents, people successful in the industry, world leaders, etc)
3. How much are you willing to sacrifice to be successful at work As Unix System Engineer?
With anything comes sacrifice. The questions is how much of it are you willing to sacrifice with regards to work life balance, stress, etc?
4. Can you explain why you changed career paths As Unix System Engineer?
Don't be thrown off by this question-just take a deep breath and explain to the hiring manager why you've made the career decisions As Unix System Engineer you have. More importantly, give a few examples of how your past experience is transferable to the new role. This doesn't have to be a direct connection; in fact, it's often more impressive when a candidate can make seemingly irrelevant experience seem very relevant to the role.
5. How would your boss and co-workers describe you?
First of all, be honest (remember, if you get this job, the hiring manager will be calling your former bosses and co-workers!). Then, try to pull out strengths and traits you haven't discussed in other aspects of the interview As Unix System Engineer, such as your strong work ethic or your willingness to pitch in on other projects when needed.
6. How do you think you might fit this position As Unix System Engineer?
An important part of research before the interview is what the company does and how the job role relates to that. This includes the company philosophy and working methods. Questions such as this seek to find out how a candidate will fit into the organisation As Unix System Engineer. Answer positively; including practical examples of how you anticipate you would perform in the new role.
7. Why did you select the University _______?
Discuss the academic program, the extracurricular program(s), the school spirit, the quality of your peers, and the professors.
8. When were you most satisfied in your job As Unix System Engineer?
I'm a people person. I was always happiest and most satisfied when I was interacting with community residents, making sure I was able to meet their needs and giving them the best possible comfort in a tough situation. It was my favorite part of the job, and it showed. Part of the reason I'm interested in this job is that I know I'd have even more interaction with the public, on an even more critical level.
Discuss your work experiences. The key is to show you're calm under pressure and can handle sensitive situations with a clear train of thought.
10. What critical component of this position As Unix System Engineer 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 Unix System Engineer (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).
11. 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 Unix System Engineer. 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.
12. Can you tell me a little about yourself?
This question seems simple, so many people fail to prepare for it, but it's crucial. Here's the deal: Don't give your complete employment (or personal) history As Unix System Engineer. Instead give a pitch-one that's concise and compelling and that shows exactly why you're the right fit for the job. Start off with the 2-3 specific accomplishments or experiences that you most want the interviewer to know about, then wrap up talking about how that prior experience has positioned you for this specific role.
13. Give me an example of a time when you set a goal and were able to meet or achieve it?
Show that you set great goals and the process and steps you took to achieve it. Details really matter here.
14. Tell me about a time when you were forced to make an unpopular decision?
Not every decision is popular. In fact, almost every decision is bound to make someone unhappy at some point. The key is to demonstrate how it impacted others positively and why you chose it.
15. How do you handle confidentiality in your work?
Often, interviewers will ask questions to find out the level of technical knowledge As Unix System Engineer that a candidate has concerning the duties of a care assistant. In a question such as this, there is an opportunity to demonstrate professional knowledge and awareness. The confidentiality of a person's medical records is an important factor for a care assistant to bear in mind.
16. What are your greatest professional strengths As Unix System Engineer?
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 As Unix System Engineer); 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.
17. How well do you know our company?
Well, a developed company that is gradually building their reputation in the competitive world.
18. If you were hiring a person for this job As Unix System Engineer, what would you look for?
Discuss qualities you possess required to successfully complete the job duties.
19. What do you expect from this job As Unix System Engineer?
Talk about the potential career development, your career aspirations, your work relationships and the learning you'll receive.
20. What relevant work experience do you have in this career field As Unix System Engineer?
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.
21. What three character traits would your friends use to describe you?
Friends would typically use attributes like (assuming you have these): Trustworthy, honest, hardworking, friendly, courageous, nice, diligent, organized and so forth. Not saying you have all of these, but the best way for you to find out is to survey your friends by asking them what they consider your brand to be.
22. Give me a few examples of how you're results oriented?
Make you give an example where you discuss details and metrics. For example, I was a tutor in my last job and mentored 5 students on their SAT test taking skills and raised their scores by 15% on average after a 3 month teaching stint.
23. Did you get on well with your last manager?
A dreaded question for many! When answering this question never give a negative answer. “I did not get on with my manager” or “The management did not run the business well” will show you in a negative light and reduce your chance of a job offer. Answer the question positively, emphasizing that you have been looking for a career progression. Start by telling the interviewer what you gained from your last job As Unix System Engineer
24. Describe what a bad work environment would look like to you As Unix System Engineer?
There could be a multitude of things to discuss here: Business ethics (wrongdoing), inconsiderate teammates, non-supportive management, a product that does not do what you're promising customers and so forth.
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. 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 As Unix System Engineer.
27. 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.
28. What do you feel you deserve to be paid?
Do your research before answering this question - first, consider what the market average is for this job. You can find that by searching on Google (title followed by salary) and globalguideline.com and other websites. Then, consider this - based on your work experience and previous results, are you above average, if yes, by what % increase from your pay today from your perspective? Also - make sure if you aim high you can back it up with facts and your previous results so that you can make a strong case.
29. What's been your biggest failure to date?
Describe your biggest failure and discuss what you've learned from it and ideally how you've been successful since because of that lesson.
30. How do you feel about technology at the workplace in general?
It's a great enabler for us to collaborate better as a team, for us to reach customers more efficiently and frequently and I believe it can help any company become more efficient, leaner, and more productive.
31. How well do you multi-task?
Multi-tasking is an important part of most jobs. You want to show that you're good at it but not overwhelmed with it. So discuss just a few things you can multi-task well on - for example: "I'm good at multi tasking between work email and working on projects As Unix System Engineer and the reason it because I'm good at prioritizing my work emails.
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.
33. How would you feel about working for someone who knows less than you As Unix System Engineer?
The reality is, the majority of the time someone is in a management/leadership position is because of their experience and past success. So they probably possess at least a unique set of knowledge from you. So you'll want to learn from them as much as possible. If it's not the case, then discuss how you would look for mentors in different departments to help your personal career development.
34. How do you take "No" for an answer?
You want to be persistent enough to understand why someone is saying no so that you could potentially convince them otherwise with a sound reason. However, if they are still saying "no" to you, then you need to humbly accept their position and move on.
35. What do you know about this company?
Research the company on Google by searching recent news (to remain current on them) and their website. Make sure you understand their products / services, vision, competitive differentiators, and work culture.
Discuss your aspirations for the near, immediate and long term. You want to show them you are thinking of making an impact now as well as the future.
37. How do you feel about taking on repetitive tasks As Unix System Engineer?
This answer depends on whether or not the job has a lot of repetitive tasks with no variation. If it does, then you would need to be okay with the idea of doing the same task over and over again. If you feel you can offer more than repetitive work, then describe how you would be able to do so.
38. How well do you know this industry?
Two things businesses need to pay attention to in their industries are what their competition is doing and the customers. You may not always agree with your competitors but it is important to be aware of what changes they are making. Very well. I have been in the industry for over 6 years.
39. Why should I hire you As Unix System Engineer?
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.
40. How do you deal with pressure or stressful situations?
Choose an answer that shows that you can meet a stressful situation head-on in a productive, positive manner and let nothing stop you from accomplishing your goals. A great approach is to talk through your go-to stress-reduction tactics (making the world's greatest to-do list, stopping to take 10 deep breaths), and then share an example of a stressful situation you navigated with ease.
41. 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.
You can learn on the job, through books and magazines, through social networks, blogs, seminars, mentors and so on. Continuous improvement is important because the one thing in life that is constant is change. And you have to continue to push yourself day in and day out to be the best.
43. 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 As Unix System Engineer. 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.
44. 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.
45. 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.
46. Give me an example of when you competed hard and won?
You can reference many different areas here when discussing a story of where you won in competition: Work experience (ideal), sports, clubs, classes, projects.
47. What is your desired salary As Unix System Engineer?
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.
48. What was the biggest professional risk you have taken and what was the outcome?
First discuss how you weighed the pros and cons of the risk and the results you'd believe you could achieve. Then discuss the action plan you put into place for it and outline that step by step. Then discuss the outcome and if it wasn't optimal talk about what you would do differently in hindsight.
49. 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.
Just be honest about where you'd like to be - you never know - you may end up bonding with the interviewer with the location. However, you want to stress that you want to work out of the location that you're interviewing for.
51. 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.
52. 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.
53. How do you plan to go by an example for your subordinates?
Sticking to the rules by yourself, working hard and not mind participating on basic tasks is a good answer.
54. What types of personalities do you work with best?
In the past, I have found it difficult to work with others who see themselves as better than others, who can take criticism, and who refuse to work with others. I have found it challenging to work with them b/c I am a team oriented person who feels the importance of working together over the needs of the individual especially in a learning environment.
55. 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.
56. How much time do you need to join the organization As Unix System Engineer?
You should be able to join it right away, barring plans you've already made (family travel, vacation, other obligations). The key is to simply be open in communication of what's already committed on your schedule. Most companies are accommodating. If they are not, weight the importance of joining that company vs. your plans.
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 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.
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.
60. Tell me the difference between good and exceptional?
Good gets the job done on time and is high quality. Exceptional is a game changer - it stands out, it's creative, it's above and beyond expectations. Tell the interviewer a story about how you were exceptional.
61. What would your first 30, 60, or 90 days look like in this role As Unix System Engineer?
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.
62. Give an example of a time you successfully worked As Unix System Engineer 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.
63. Describe to me the position As Unix System Engineer 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.
64. Why should the we hire you as this position As Unix System Engineer?
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.
65. 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.”
