Skip to main content

Just another career path

As a software engineer, I recently have heard of a lot of feedback from my colleagues and friends that they don’t see their career path or they don’t know how to move to the new levels in their company. No exception, I used to have that thinking before. 

In my opinion, there is a very important reason why people are struggling to find the answer because “career path is not always the job titles”. Normally, each company has its own job titles such as junior-level developer, middle-level developer, senior-level developer, teach lead, software architect, CTO, etc. Hence, it is not true that a job title is reasonable for every company.

The interview is often conducted hardly to find a candidate matching the company title. If we have a good enough job title standard, the interview would take place very easily, right?

Therefore, I prefer to define my own career path through what skills are gained under a job title.

But wait, why do I need a career path?

To me, a career is an indispensable part of my life (and anyone else, sure?). My career path helps me visualize the big picture which motivates me to focus on the right track to achieve my next level. After all, a good career should bring me the fullest life having the following conditions:

  • It gives me a chance to indulge my passion

  • It gives me a chance that my contribution is appreciated

  • It gives me a chance to earn good enough money

Anyone should have their own career path, here is mine:

I see each level as a step of a ladder. It is very risky to skip any step. It doesn't mean that you delay getting to know what to be learned in the next steps. Don't let it be a black box and then get "surprise!". For example, to achieve my long-term goal as an intrapreneur/entrepreneur, I don't run a business now but I keep practicing as it a real business when building side projects with my friends.

Detail of level in my career path

No matter what the job title is, I categorize a level by the following criteria:

  • 👷 Project/Product contribution

  • ✋ Ability to lead and mentor the team

  • 🕑 Years of working experience

Who are they?

Get recognized (example)

Apprentice

Try to do things right

  • 👷 Learn how to use tools

  • ✋ Learn to collaborate well with other members

  • 🕑 Usually 1 - 3 years

Journeyman

Keep doing the right things right

  • 👷 Know how the used tools work

  • ✋ Collaborate and cover/mentor some members well.

  • 🕑 Usually 3 - 5 years

Master

Keep doing the right things better

  • 👷 Know how to build a tool

  • ✋ Lead and mentor some teams

  • 🕑 Usually 5 - 10 years

Intrapreneur or Entrepreneur

Turn off the old and create new right things

  • 👷 Innovate tools

  • ✋ Lead and mentor the whole department/company

  • 🕑 Usually 10 - xx years


Leave a comment to share your opinions


Read more:

Comments

Popular posts from this blog

Junit - Test fails on French or German string assertion

In my previous post about building a regex to check a text without special characters but allow German and French . I met a problem that the unit test works fine on my machine using Eclipse, but it was fail when running on Jenkins' build job. Here is my test: @Test public void shouldAllowFrenchAndGermanCharacters(){ String source = "ÄäÖöÜüß áÁàÀâÂéÉèÈêÊîÎçÇ"; assertFalse(SpecialCharactersUtils.isExistSpecialCharater(source)); } Production code: public static boolean isExistNotAllowedCharacters(String source){ Pattern regex = Pattern.compile("^[a-zA-Z_0-9_ÄäÖöÜüß áÁàÀâÂéÉèÈêÊîÎçÇ]*$"); Matcher matcher = regex.matcher(source); return !matcher.matches(); } The result likes the following: Failed tests: SpecialCharactersUtilsTest.shouldAllowFrenchAndGermanCharacters:32 null A guy from stackoverflow.com says: "This is probably due to the default encoding used for your Java source files. The ö in the string literal in the J...

Coders are NERDS | Learning English with Podcast

Let's learn three English vocabulary words based on real-life context through a humorous video about the life of software coders, especially at big tech companies when they work from home. Credit to Joma Tech. 🤓

Git Feature Branch Workflow

Motivator It's important for a team to have an agreement on how the changes of source code should be applied. According to projects and teams size, we will define a workflow or select one from recommended workflows ; the "Feature Branch Workflow" is a candidate. What is it? - One branch "master" for main codebase - Several separated branches for features development Why should we care? - Be super simple and allow each developer works on a particular feature. - A stable codebase (master) benefits for continuous integration (CI) environment - Leverage "Pull request" for Code review How it works? A lifecyle of a feature branch (usually created by a story) 1. Creator creates a new branch from a story.  For example: "ABC-1-setup-projects" 2. Creator checkouts the created branch and works on the branch (commits, pushes) 3. Creator has done the feature, he uses "pull request" to merge his branch into branch "master...

[Snippet] CSS - Child element overlap parent

I searched from somewhere and found that a lot of people says a basic concept for implementing this feature looks like below: HTML code: <div id="parent">  <div id="child">  </div> </div> And, CSS: #parent{   position: relative;   overflow:hidden; } #child{   position: absolute;   top: -1;   right: -1px; } However, I had a lot of grand-parents in my case and the above code didn't work. Therefore, I needed an alternative. I presumed that my app uses Boostrap and AngularJs, maybe some CSS from them affects mine. I didn't know exactly the problem, but I believed when all CSS is loaded into my browser, I could completely handle it. www.tom-collinson.com I tried to create an example to investigated this problem by Fiddle . Accidentally, I just changed: position: parent; to position: static; for one of parents -> the problem is solved. Look at my code: <div class="modal-body dn-placeholder-parent-positi...

Set up a web server for learning HTTP headers

Motivation We all follow the client-server model using the HTTP protocol for most of our web apps today. In development, we simply may have a backend API server and a frontend (web pages or mobile apps) only. However, it seemed that a proxy server is always required for production. In fact, most of the hardest issues in production come from integration. The requests and responses might be modified by the proxy server. Therefore, the understanding of HTTP protocol is one of the key skills to resolve those issues. I wanted to dive deep into HTTP with some core concepts such as caching, cookies, and CORS. I didn't intend to go quickly rather than moved slowly to have a well understanding of what I do. Prepare a server The easiest way is to use my laptop as a server then I can just use "localhost". I can also use ngrok to make my web server online. Finally, I use an online tool such as RedBot to check the HTTP headers. To make it more excited though, I deployed the app on A...