Showing posts with label Career growth. Show all posts
Showing posts with label Career growth. Show all posts

03 June 2018

increasing salary with number of years of experience

Over the last 3 months at least 5 colleagues have asked me questions related to how to keep their salary growing as experience under their belt keep growing. Let's look some of the questions I encountered over lunch breaks, commuting in cabs between home and office and other networking events:

  • My experience is growing but my salary is not growing, any suggestions from your end?
  • How is the job market now I have 8 years of experience in IT?
  • Will I get a job when I try to change the company?
  • I'm a lead now with 10 years of experience under my belt, leading team of 6 junior people and my Manager has 40 people under him.

    With this prevailing ratio in the software industry, as years rolls and I become more experienced will I get position for my experience?

May be after reading this blog post so far, it might have also ringed similar questions in your mind too. Keep reading further, I will try to answer these questions over next few paragraphs.

I really understand the concerns people have behind these questions because I too had such questions in my mind 2 years back.

Now let me try to my answer to these questions.

Experience v/s Exposure

As years goes by, yes you will definitely become more experienced by a mere number of experience. But you need to ask yourself can I do more complex tasks now comparing to 2 to 3 years back? Please understand you need to gain expertise in whatever you do as become more experience any field.

For instance, let's consider Software Developer job. In first 1 - 5 years you are expected to do programming more, later over 6 - 9 years you are expected to take design components, do POCs, etc. And over 10 years & above you are expected to design solutions and provide architecture guidelines etc. Please note here as years of experience goes you need to build different skills set to grow your career and hence the salary.

That is why with more number of experience you need to gain more exposure as well to salary raise.

Understand value addition

As years of experience grows you need to add more value to keep getting salary raise. Just because you are there in the company for long years no one keeps giving good salary raise.

For example with 12 years of experience you need to talk comfortably with the leadership team on newer technology developments and how can some of them be adopted in the company to improve operation metrics, KPIs(Key Performance Indicators), reduce costs, etc

Turn the problem upside down. For a moment think you are running a business and would you give salary what you are expecting to person with the same skill set as you.

Skip level manager should know you by name

This is not a step but you could use this as a yardstick. You report to manager/lead and then you manager/lead reports to his manager. Your manager boss is your skip level manager. You need to be active and notable in your area of expertise so that your skip level manager knows you by name.

To gain attention with senior management start giving tech talks in your organization, introduce tools which can reduce development efforts. You need to have such an expert level such that your manager should refer you to other people to solve their issues /problems.

Invest in training

Especially in IT industry you need to keep upgrading your skill set. There are lot very good training platforms available in the market. Below are few such training platforms online.

  1. Pluralsight
  2. Lynda
  3. Coursera
  4. udemy.com

Spend some bucks, buy subscription and go though courses. It’s like sowing high yield seeds for better crops later in the season.

Networking

  1. Be active on LinkedIn which is a professional networking site. It’s worth spending 2 -3 hours every week.

    Follow the people whom you know are getting good salary. See whom they connect to and what they follow on the site. Especially see what new skills they are adding to their resumes of late.

  2. Subscribe to sites like infoq.com, medium.com, msdn monthly magazine etc for your area of topics.

    Read at least 2 -3 article published on these sites every week to get good grasp on what is going on in your area of work.

26 May 2018

one way to keep developer job interesting all the time

Recently one of my close acquaintance said he is experiencing boredom in his developer job because of mundane work and said he has free time sometimes. And he was not at all happy with the situation.

After spending some time researching I sent an email with the below content. My close acquaintance is a C++ developer.

------------------------

Dear,

https://github.com/trending/c++

Today you mentioned that your work in not interesting. You can make your developer job interesting if you wish to, by following below:

  • Go through the link at the beginning of the email.
  • It shows all the interesting projects being built in C++ (Similarly you can see trending projects for other languages as well).
  • See which projects suits you and sparks interest in you and START contributing to them on github.

It helps you in two BIG ways:

  • Firstly, it gives you interesting work.
  • Second, it will acts a GOOD resume and recruiters will start calling you with job oppurtunities looking @ your contributions on a pubic forum like github.

------------------------

10 November 2017

how to crack software developer interview in style

Junior level professionals in the Software Development industry will be changing their job very often. The interview will be very competitive in well-paying companies. To clear interview you can refer popular blogs based on your skill, refer interview books in the market.

Issues with conventional ways to prepare for interview

But the problem with these conventional ways is that, you hardly find any single blog or website to sharpen your skill set. You end up opening multiple tab in a browser for each link available in the googlesearch. This will lead to confusion on which one to read.

Though interview books are good for interview preparation, they are very narrow in terms of what they cover and more over you will such interviews books only for most widely skills like JAVA, .NET, etc. Also its difficult to find revised books latest frameworks & technologies in market.

Using stackoverflow to prepare for interview

I think you can easily clear interview if you went through question and answers on stackoverflow for a given skill.

For example for C# language as of this blog post publish, they are around 125,334 questions. That is very vast universe of questions.

Also its easy to find top rated questions and answers. So if you start preparing for top voted questions and answers, over 2 -3 months you can very well sharpen your skill to clear difficult interviews.

Viewing top rated C# questions on stackoverfow.

Viewing top rated JAVA questions for stackoverfow.

Viewing top rated algorithm questions on stackoverfow.

Viewing top rated distributed computing questions on stackoverfow.

05 February 2017

why you shoudn't be a top performer in the team

Often times it’s a question among IT / software engineers that, what rating I will get, he will get or she will get. People tend to worry more about ratings, especially its more true with top performing guys in the team. The top performing guys think at the times, "will I get top rating in the next current appraisal cycle or not"?

This post is not about discussing whether worrying/thinking on appraisal rating is BAD or GOOD. This blog post is ALL about, why you shouldn’t be worried about not being top performer in the team.

(Disclaimer: I am not telling you must not be a top performer in your team)

Why you shouldn’t be worried about being top performer in the team?

Consider a team of 6 people. In general among them in one or two will be too GOOD and performing most of the new / complex stuffs. The rest of the people will work with those one OR two guys who really doing great.

In this kind of usual set up, there is ample opportunity for the other 4 people to learn from the people who performing BEST in the team. The “MEETS Expectation” people can learn a lot from the TOP performing people in terms of:

  • best designs
  • best algorithm to solve a given problem & deriving at the right approach to deal with an issue
  • AND most importantly how do they keep abreast of themselves with latest technology or new development in their area of specialization

So “MEETS Expectations” can learn a lot of those TOP performing guys. So in effect the “Meets Expectation” people knowingly or unknowingly will become GOOD at their skills. So overtime “Meet Expectation” can COMPLETE with TOP performing people in the team.

On other hand the “TOP performing” people doesn’t have the ADVANTAGE of working with people who are really smarter than themselves.

So I think from gaining knowledge perspective (in this knowledge based economy) it’s better to work with the people who are SMARTER than yourself. In that setup you will be becoming smarter and smarter with every day passes by working with people smarter than you. So feel free to change team / company to work with the people who are smarter than you.

Hence the post catchy title “why you shouldn’t be a top performer in the team”.

11 May 2013

being successful developer at new job

What combo makes a successful developer

In IT or Information Technology industry people will be changing their jobs. This could be an internal job in the same company or when you join another company as a lateral hire. Myself being a developer, let’s talk on how to become successful at a new job when you joined as developer role.

Priority items to pursue by any professional at new job to become successful :

  • Right skill for the new job.
  • Understand the project in depth at the new job.
  • Attitude matters at a new job most. Maintain good professional relationship with juniors, peers and managers alike.

Let's see in detail what it meant for developer to succeed at new job.

Filling the skill set gap for the new job:

when joined a new job or role and started working on the new project, it's always important to acquire the skill set what you’re new job requires. For example, you would have worked on .NET framework version 2.0, but the new project is being on the latest .NET framework.

another example could be when you don't have any experience in the database tier. You need to quickly learn the bare minimum database skills required for the new project you work on working on the new project.

without the right skills for the new job, it will be very difficult for effective participation in design discussion and to contribute significantly to the implementation.

So quickly fill the gap in your skill set and start contributing to come become successful developer at the new job.

Understanding the project in depth at the new job:

However technically good we are, what also equally a matter is, how much knowledge we got on the project itself. Developer at the new job should understand quickly the overall architecture and structure of the project at least in high level. Try to understand below on the new project:

  1. The structure of the .NET projects and solutions involved in the systems and the dependency involved between them.
  2. What are the different systems involved in the system? How does the data flow happen between the systems involved?
  3. What is the deployment architecture and how does each component in the system get deployed?
  4. Understand the relationship between the data involved in the system. Try looking at your database schema diagrams.

Attitude matters a lot:

We should behave professionally at the working place. Below points helps:

  1. Don't let your emotions flow freely when you are at a new job. At a new job, you have not yet understood people around. So they might misunderstand your emotions.
  2. Don't try to take control of the things in a hurry. Have patience. Respect your juniors.
  3. First impression is best impression. If you get a chance to speak in front of people in the whole project, don't miss the chance. Share your opinion and thank the people who are helping you to understand the project better.