Professional Career

November 11, 2018— 1968 days ago, 0 views.

Jobs Titles Are a Lie

A job title is just something that resumes your professional profile.

Landing Page Engineer sounds fine to me Kiko Beats

That’s so difficult; It’s like trying to resume your entire life in a tweet, but at the same time it’s necessary.

People out there need to figurate what kind of problem resolver are you.

That doesn’t mean you can do only that (probably yes in your daily job), but it’s a way to project what kind of jobs are you interested in.

You are going to be eventually a Senior in a very specific aspect, but still Junior in most of the engineer aspects.

That’s something that is happening all the time, just because engineering englobes so many things.

The Junior/Senior dilemma is about projecting the years of experience in your job title align with what you want to work.

Also, it’s a way for recruiters to fit your profile with their salary range batch.

But the most important thing: Don’t take it too seriously.

You are not your job title, it’s just a projection.

Even you are in the same job title and salary range that your colleges, that doesn’t mean you have the same benefits.

That is not happening because Human Resources departments are horrible people; it’s happening simply every person and conditions are different.

A non-exhaustive list of simple things that fluctuates your base salary could be:

Negotiate your initial base salary is one of the most important decisions in financial terms. It’s your main source of money.

Always, try to negotiate. Try it, not demand it.

Just a good moment to negotiate. It could be later when you demonstrate your potential in the company.

Understand how much you worth. Setup middle/long term goals in your professional career inside the company and acts consistently to move forward.

Your job as a programmer is solving problems, not writing code. Solving problems requires:

Based on that, we can divide your professional profile into

Implementers: You’re an inexperienced programmer, and your tasks are defined by someone else. You just implement small, well-specified chunks of code.
Solvers: As you become more experienced, you become a Solver: are able to come up with solutions to less well-defined problems.
Finders: You begin identifying problems on your own and figuring out their underlying causes.

The benefit from the move from Implementers to Finders is about autonomy:

You have a privileged point of view so you can define solutions with better context.
You can pick the problems to solve, being sure you are not resolving the wrong problem.
You are doing less unnecessary work since you have a team and a process.
More decisions depend of you, being profile is more valuable.