Career path for the developer

Tuesday, February 16th, 2016 (0 Comment)

1. What is career path?

The novice programmer or newly graduated students will be hard to conceive of positions and titles in the programming industry (career path). Some of you still wonder:

  • What you will have titles when you go to work? How’s your job?
  • What you will have titles when you coding long-term? High salary?
  • You like code only, do not like the leader. How is your orientation?

Understanding the career path of the industry developer, you will easily orient your development in the future, as well as focusing effort on the path they have chosen. In this article, I will list the basic for career path of a developer, for myself as well as developers. These positions will be described in order from low to high.

level development

level development

2. Fresher/Junior Developer

The internship student or fresh graduate are this title (Junior Developer). Experience of Junior Developer usually is between 6 months and 1 year.

Because no experience, fresher/junior is often re-training, so when interviewed freshener, companies usually consider the ability to think logically, capable of programming, programming your potential, everyone often do not require too high for you. The work of junior usually research the current project, code modules small, simple, fix bugs, possibly with the assistance/review by senior. At the junior stage, you try to study coding, learn how to work, learn from the experience of senior.

3. Developer

Coding about 1-3 years, you will be called Developer (Many of you are good, can go straight Senior or Team Leader). At this stage, you have done over a number of projects and quite well versed in the technology.

The interview is often harder for developers. The interviewer will ask you about the project was done, the difficulties you’ve encountered, how to solve? In addition, the interview will focus on the technologies you’ve written in your CV. Because developers have experienced so will be not many supporting of the seniors, and also difficult to ask, ask for help on behalf of junior.

At this stage, you have to be coding some more complex modules, participated in the meeting, code review, discussions with clients etc. This is the stage for you to accumulate knowledge, experience, building reputation to the next rung in the career ladder.

4. Management or Technical

At a later stage, you were able to determine own path. If you want to focus on coding and techniques, you can go towards technical: Senior Developer => Technical Lead => Software Architecture. If you want to work with processes and people, you should go in the direction of management: Team Lead => Project Manager => Manager. In the first phase, the line between two roads are quite faint, but the higher your position, the boundaries are becoming clear. You can view the following summary:

Management Technical
Team Leader
You become a team leader of a small team (about 3-6 members). Except code, you also have meetings with superiors, report to clients, manage subordinates. At this stage, you will gradually learn one of leadership skills, management skills etc. In a small company, senior developer (experienced) going to become the team leader.
Senior Developer
After a period of working, you grasp and understand much technology + process. In this position, except the ability to code well, you have to know the make design and solution. Also, you have to guide the new junior developer and join review coding etc. Sometimes senior developer takes over team leader position, so you also need a bit of skill and leadership expresses.
Project Manager
Up to this position, you will have little or almost no time to code. Your main task is now reporting, management, leadership, interviewing candidates to recruit members for the new project. You are who decide the success or failure of the project.
Technical Lead
You need to understand the depth and breadth of technology, because you are the choice of technology, process for one project. The big decisions about the design, structure your coding… You will be responsible. At this stage, in addition to technical, you also have good presentations, tutorials, explanations etc…
Manager/Director
in this position, you’ve called boss, superiors, leaders,… Now you will not have time to code, meeting all day, communicate, interviews, discussions with the departments and handle administrative work.
Software Architect
To reach this position, you must have at least 10-20 years in the industry. Your task is quite arduous: From a required “ambiguity” of the customer, you have to work with BA to evaluate the solution, working with PM to build one team, working with the Technical Lead to design, making important decisions about architecture. This position, although no management rights, but it had plenty of hidden power..

In addition to the above directions, you can go towards IT Sales, Business Analyst, etc. Within the article, I cannot cover the whole of all developments in this sector. I hope after seeing this article, you will have your own career path and hope to receive the supplement, your comments..

Tags: ,

Related Posts

thinking
Tips for upgrades Career Quality Assurance – QA
thinking
Where start to learn web programming?
thinking
Seo onpage tips and optimization onpage
thinking
How to readers to return to your site

Related Posts

thinking
Tips for upgrades Career Quality Assurance – QA
thinking
Where start to learn web programming?
thinking
Seo onpage tips and optimization onpage
thinking
How to readers to return to your site

Leave a Reply

Your email address will not be published. Required fields are marked *