Is planning the career path pointless?

January 15, 2010 | by Aga Gibowska

Comments
http://www.pongoresume.com/images/upload/Career%20Path_040609c.jpg

http://www.pongoresume.com

The beginning of a new year is always a great time to start moving your career in a better direction. It’s pretty common that at that time many employees set Workplace and Career New Year’ s Resolutions.

This is also the time for looking back on what you achieved last year, what failures you faced and what lessons you learned. Based on that many of us start planning their career paths all over again.

But can you actually plan it? Does a strict career path limit your perspective? Or maybe it’s just pointless since we are unable to control external factors that affect us?

How to survive in a new developer’s job? Part 2

December 1, 2009 | by Aga Gibowska

Comments

man-laptop-worldIf you have just started a software developer’s career or changed a workplace these tips may comae in handy while establishing yourself in a new environment. It’s not easy to earn colleagues’ respect and reach the “core” of the company. Many fresh graduate developers fail at the very beginning for a variety of different reasons. I already presented a few tips on how to succeed in a new workplace in my previous post. Below you can read more tips that may help you survive in a new job.

How to survive in a new developer’s job? Part 1

November 24, 2009 | by Aga Gibowska

Comments

photo_2799_20081228

Are you starting your developer’s career? You stand 50% chance of losing this job within the first two years, the study revealed. Surprisingly, many great and talented people fail. I can imagine that after so many years of studying you don’t feel like getting fired. More importantly, it’s becoming the place you start spending 1/3 of your life at. You try to make yourself comfortable here and make other people feel the same with you around. How to settle yourself smoothly into the job? How to win colleagues’ respect?

5 reasons why software developers fail in their first jobs.

November 17, 2009 | by Aga Gibowska

Comments

Job_1According to the study by Leadership IQ around 46% percent of newly-hired employees will fail within the first 2 years in the new job. By failure they mean terminations, leaving under pressure, receiving disciplinary action, or receiving very negative performance reviews. This rate is also nothing different among software developers. Why people who have the right skills to do the job fail? They were carefully screened and made their way into the company. Then they get quite successful at the very beginning and suddenly something changes. Is it their fault or the company’s? Based on our experiences below I’m presenting the possible explanations for their failure and the examples of fatal mistakes when starting a new job:

How will recruitment change in 2019?

July 6, 2009 | by Aga Gibowska

Comments

Have you ever wondered what the recruitment will be like in 10 years’ time? With all the new HR 2.0 trends and social networks will it remain the same? Will the current economic crisis affect the employment conditions? How will the rapidly aging society cope on the labour market? Will CVs and cover letters survive? Who will have the actual power on the job market?

How to handle 2 killer questions at the job interview?

June 25, 2009 | by Aga Gibowska

Comments

Regardless of age and professional experience, during every recruitment process we meet several applicants who haven’t got the faintest idea what the company deals with and what the vacancy involves.  Among many other questions that candidates have to face during the interview, there are two, seemingly harmless ones, that I consider to be  killer questions for many : “What do you know about GOYELLO?” and “Why do you want to work for us?”.

Faulty recruitment process. Who’s to blame?

May 18, 2009 | by Aga Gibowska

Comments

Each and every company has to admit that they picked the wrong person for the vacancy at least once in their lifetime. It’s difficult to confess that we made a bad decision hiring Mr. Average who later proved to be a total misfit in the company, hard to get along with and delivering work results that everybody would rather forget about. Who’s to blame?