Skip to main content

Be Successful in Job Interviews


Every interview is a lottery. 

Depending on the industry, company type and who interviews you - on one day you would need to impress with your confidence and good looks, and the other day you would need to show how well you are able resolve particular tasks.

In 95% of cases there will be no honest response from the interviewer. That's quite bitter at the beginning, but it is logical from the interviewer perspective. It is also very rarely if someone would be happy to keep in touch after the unsuccessful interview.

However there is a good set of solutions: 

1. Work hard and master your skills, 
2. Improve your self-confidence and presentation skills, 
3. Work and study after hours to improve yourself even more, 
4. Go to interviews and don't stop sending your resumes to the companies you want to work for 

If you do all the above some day you will get the right job! It is easy. :)

Comments

Popular posts from this blog

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi...

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like...