1. Do you know anyone working with this organization?
It would be great if you did - then you could potentially use them as a referral if they thought highly of you.
2. 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.
3. Top 11 Questions to Verify Experience and Credentials Regarding Unix Shell Scripting And C:
Sometimes people want a job a little too bad - and they may fudge their credentials and experience a bit.
If you've run into this problem, are worried about it, or have credentials and experience that are absolutely essential, you may need to ask a few verification questions.
If you are a candidate, you should review your resume and make sure you know all the key points, and that nothing has been misconstrued.
1. What grades did you get in college?
2. What were your responsibilities when you worked in job x?
3. How many people were on your team at your last job?
4. What will your previous manager/supervisor say when I ask where you needed to improve?
5. What was your beginning and ending salary at job x?
6. What were your beginning and ending titles at job x?
7. Are you eligible for rehire at job x?
8. What tools are necessary for performing job x?
9. Describe to me how you would perform [x typical job task].
10. What was the focus of your thesis?
11. When did you leave company x?
4. How does your present position differ from past ones?
Describe the difference with regards to responsibilities, culture, team, career opportunity, and the work itself.
5. How do you keep others informed on work issues?
Possible methods:
Talking to them, emailing them, sharing best practices in meetings
6. 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.
First, find out which skills are the ones that you're currently lacking. Then identify what the steps would be to acquire/build those skills. Then take action to do so.
8. What kind of car do you drive?
The only time this might matter is if the job requires a certain type of car because of the responsibilities. For example, if you need to load a lot of construction materials into your car, you'll probably need a truck.
There are some questions that your potential employer aren't allowed to ask (but trust me, they probably want to). For instance, they shouldn't really ask about your family or how far away you live from your potential place of employment. If you can find a way to answer these questions anyway (with the answers they want to hear), that will give them a little added info to help them make the (right) decision!
10. 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 Regarding Unix Shell Scripting And C. 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.
With anything comes sacrifice. The questions is how much of it are you willing to sacrifice with regards to work life balance, stress, etc?
12. Explain what are your strengths Regarding Unix Shell Scripting And C?
Bad Answer: Candidate is unprepared for question or only gives generic answers.
This is the most common job interview question - everybody should be expecting it. If they don't seem prepared, or give a fairly stock answer, it's probably a bad sign.
Good answer: The consensus is to go for quality, not quantity here. Candidates should give a short list of strengths, and back each one up with examples that illustrate the strength. Also, they should explain how these strengths will be useful in the job you're applying for, and use this question to say something interesting about themselves.
13. What do you see yourself doing within the first 30 days of this job?
Typically the first 30 days are designed for you to learn as much as possible Regarding Unix Shell Scripting And C. Work hard to get to know your teammates, how they work together, and how you can make the biggest impact.
14. Name five characteristics that describe you?
Here are a few you could choose from:
Hard working, strong willed, persistent, intelligent, adept, amicable, friendly, collaborative, eager, humble.
15. What kind of work interests you the most?
You can talk about what you're passionate about. What motivates you. What excites you.
16. What do you think about Teamwork?
I enjoy teamwork and am used to shift work. I think I would adapt well to the role. I am looking for new challenges Regarding Unix Shell Scripting And C and I know I would learn a lot as cabin crew, not just about people and places, but skills like first aid too, how can I help others with in my limits.
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.
18. If you have multiple projects on your plate, how do you handle completing them on time?
Prioritize based on business importance. Set clear timelines for each so that you know which ones to knock out first. Get your teammates to help if necessary.
19. How did you handle meeting a tight deadline Regarding Unix Shell Scripting And C?
Review every deadline you need to meet. Prioritize your projects by deadline and factor in how important each project is. Record your deadlines on a digital calendar or spreadsheet.
20. What kind of work interests you the least Regarding Unix Shell Scripting And C?
What bores you? What fails to challenge you? What fails to excite you?
21. How will you approach learning this "new" job Regarding Unix Shell Scripting And C?
Interview peers and leaders/managers, read industry news, practice the skill sets needed, absorb information on the job as much as possible.
22. How open are you to relocation?
If you're not, then say you're not. Don't lie about it just to get the job. There's no point if you won't move for the job anyway and lying is unethical. If you are open to relocation Regarding Unix Shell Scripting And C, let them know which areas you'd be willing to relocate to.
23. What does your professional network look like?
If you have a professional network, discuss it detail (# of contacts, people you know, their positions and what you've learned from them or how you've worked with them). If you don't have one, discuss how you would develop one (career fairs, networking events for that industry, through your existing friends, etc)
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.
25. What other companies are you interviewing at?
Be open and share if you are indeed interviewing elsewhere, but do it in a humble way. This way you don't seem arrogant and the interviewer knows your skills are valued by other companies. This also tends to make them want you more as they know they are competing for your services.
26. Describe a time where you've failed and bounced back?
Share a story to describe this. For example: "I accidentally made the mistake of telling a customer I could deliver on a solution set on a certain date and then later found out our business partner couldn't do it on that time. I learned that I shouldn't rush into important decisions and promises like this and that I should always check with my counterparts first before committing to a statement of work."
27. Why do you want to work in this industry Regarding Unix Shell Scripting And C?
Make sure you research the industry first. Then find at least 3 core things about that industry that you're passionate about (for example: how their solutions impact clients, their culture, the leadership, etc)
28. What does success mean to you?
I am punctual, I always have excellent attendance on any job Regarding Unix Shell Scripting And C, 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.
29. What skills do you bring to the table?
Think of your skill sets with regards to: analytical skills, interpersonal skills, communication skills, computer skills, presentation skills, management skills, sales skills and so forth.
30. How important is a positive attitude to you?
Incredibly important. I believe a positive attitude is the foundation of being successful - it's contagious in the workplace, with our customers, and ultimately it's the difference maker.
31. What are your presentation skills like Regarding Unix Shell Scripting And C?
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.
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. What is the most important quality a supervisor should have?
The ability to inspire / lead a team towards one common vision.
34. Describe yourself in three words?
Pick three adjectives but then back up each with a real life story that demonstrates those characteristics.
35. What role do you see technology playing in this role?
Technology is important to almost every job today but it's not meant to be abused. I believe it's important to increase productivity and not for personal use.
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. How do you handle repetitive tasks?
Some people enjoy it, others don't. Which are you? If you don't like it, can you at least do it well? And if you don't like it, be ready to explain why in a positive way (i.e. your potential is to do much more than simply be repetitive)
38. 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?
39. What differentiates you from the competition?
Think about what you bring to the table that you truly believe is unique - the easiest way to do is to think of your own personal stories that demonstrate your work ethic, skills, and dedication. Most people have some or all of those skills, but the unique stories are what make people stand out in interviews.
40. 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.
41. 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.
42. 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.
43. Describe a typical work week for this position Regarding Unix Shell Scripting And C?
Interviewers expect a candidate for employment to discuss what they do while they are working in detail. Before you answer, consider the position Regarding Unix Shell Scripting And C 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.
44. 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.
45. What is your desired salary Regarding Unix Shell Scripting And C?
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.
46. How good are you at problem solving?
Describe the problem first and then discuss how you were able to fix it.
47. Give me an example of an emergency situation that you faced. How did you handle it?
There was a time when one of my employers faced the quitting of a manager in another country. I was asked to go fill in for him while they found a replacement and stay to train that person. I would be at least 30 days. I quickly accepted because I knew that my department couldn't function without me.
48. 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.
49. 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.
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.
51. What would you do if our competitor offered you a position Regarding Unix Shell Scripting And C?
I would weigh the offer and consider it, however, this company and this role is my first choice.
52. If I talked to your three biggest fans, who would they be and why?
If you can reference three professionals with executive titles (CXO, VP, Director, Manager), that carries a lot of weight. Make sure you highlight how you've helped them achieve their biggest objectives and how that's made them your fan.
Fully understand my responsibilities, work hard and exceed expectations, learn as much as possible, help others as much as possible, understand what my teammates' goals and needs are, be on time, and gain a mentor.
54. Does your boss know you're here today?
Usually, you probably haven't told your boss for obvious reasons. So it's ok to say that they do not. You don't want to upset the balance at your current job after all and nothing is guaranteed in an interview. The interviewer should understand this stance.
55. How do you ensure all of your work gets accomplished in a productive manner?
The key is to prioritize what's important in your work and to stay organized to accomplish the tasks. A strong work ethic also helps.
56. 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.
57. 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.
58. How do you think I rate as an interviewer?
I think you did fine. I'm sure you've conducted a lot of interviews, and it's probably second nature for you now. Thanks for taking the time to meet with me today. I'm sure you have a lot of things you have to juggle every day.
I'd say you rate at least ten out of ten. The questions you asked seemed spot on. I can tell you guys are working hard to find the perfect applicant for the job. I'm glad I could meet with you.
59. How much do you expect to get paid Regarding Unix Shell Scripting And C?
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.
60. What does "thinking outside the box" mean to you?
It means not doing things exactly the same way as everyone else. You've got to challenge the status quo and bring something new to the business.
