CareerTransformation-CT105 (Sep22)

Do's & Dont's at day-to-day IT Job! CT105Day5 (9Sep)

CT105Day4: How to build corporate mindset for massive Success? (8Sep)

CT105Day3: How to plan your Career? Step-by-step guide for career RoadMap planning (7Sep)

1) What is the most important goal you want to achieve immediately in your career.

One liner Goal statement.

2) Assign a deadline

3) Write down, all possible ideas, which will take you to your goal.

4) Pareto principle - 80/20 principle

80% of the output, will come when you focus on 20% of your ideas.

5) Apply pareto principle to identify top 20% of your ideas, which you want to implement next.

- Best utilization of your 24 hrs. Do the things which matter.

6) Out of these important ideas, what is it that you can do right from tomorrow.

Daily / weekly execution should happen.

7) Allocate time for tomorrow to work on these ideas.

8) Setup a mobile reminder to do it, on your chosen time.

9) Do it.

10) 9PM session - review whether we did the task.

?

Day2 (6Sep) - Career RoadMap planning

Freshers - Jobseekers

• Enhance technical skills
• Grow logical problem solving skills
• Build applications without referring to notes. Any problems solve it using google
• Communication - you should be able to explain
• Confidence is the key
• Maintain a github profile & keep it updated.
• Keep preparing for interview questions, keep coding & practicing.
• Create your profile on job portals (Naukri, and other top profiles google)
• Keep applying via all possible mediums - job portals, websites, linkedIn, email, contact.
• Eye catchy email subject & cover-letter body.
• Look for offcampus, internship

?

• Working professionals career growth
• 0-2 years:

1. Functionally overall project.
2. Tech standards & practices as per your team & project.
3. Understand end-to-end SDLC process.
4. Able to independently solve problems using google. Like exceptions & debugging.
5. Interaction with other team members to accomplish the project
6. Able to code, as per the design/architecture/standards of the application.
7. Be good in your primary technology.

• 2-4 years:

1. Able to fully groom the requirements. Ask clarifications, and impact analysis.
2. For your assigned tickets, should be able to end-to-end convert requirements into code and take to PROD.
3. Can build anything functionally.
4. Starts building from design, performance, maintenance perspective.
5. If you want to get to full-stack, become master in your primary, and then start taking some work on the other technology.
6. Start guiding juniors on the 0-2 years role.
7. Become good with estimations.

• 4-6 years:

1. Should be really good with design - performance - maintenance wise building right application.
2. Should become capable to lead small teams and build applicable with them.
3. Extensive code reviews - develop habit to identify issues when you see the code.
4. Capable to enforce additional tech enhancement processes, like unit-testing, sonar
5. Make a decision, how you want to take your career forward, architect line, Technical manager or people management(ScrumMaster) line. Based on this decision, try to go forward.
6. Have necessary training/certifications in these areas to continue forward.

• 6+:

1. Tech Lead responsible for all technical decisions for the team.
2. Requirement gathering / grooming - with Client / Team. (along with SM). Impact analysis and maintains system.
3. Functionally ownership & technically responsible for the entire team.
4. Defining tech solutions with team, and stamping with peers(of your team) & architect.
5. Good in design patterns & building scalable, reusable, maintainable systems.
6. Is rigorous coder in the system.
7. Effective unit-testing & automation.
8. Approach & Peer code review
9. Estimation and sizing project work for the upcoming release. (Along with scrum master)
10. Ensure that defined system processes are effectively applied.
11. Any tech process - Sonas / cloud formation templates
12. Innovate and advance the teams technical skills.
13. Growth tech plan for teammembers
14. Giving productive feedback to team-mates (Along SM)

Day1 (5Sep) - Overview