I know coding, am I all set for my tech job?

Finally, after learning a lot about System Design, Data Structures, and algorithms, you have cracked an interview and joined an organization.

You can write a beautiful piece of code in any language for the most complex problems, or you can design architecture for the most complicated problems.

But is that sufficient to grow and survive in an organization?

Oh Oh, No No, I never thought about that, right?

What now?

I want to grow in my organization. And growth could mean different things for different people:

  • Grow in terms of Salary
  • Grow in terms of Position
  • Grow in terms of Knowledge
  • Grow in terms of Connections
  • Grow in terms of Populartity
  • Grow in terms of Trust, that is how much other people trust you.

This Growth is a side effect of how I am performing as an engineer inside an organization. The next question is, “How to perform well as an engineer?”

But no one taught me this!

So here I compiled a list of things I should do to ensure, I am performing well and able to grow in an organization:

Follow Technical Processes:

  • Keep your Jira updated with latest status and comments
  • Put Jira ID with your commits
  • Your Merge Request should have right comments
  • Review other people Merge Requests
  • Creating documents when working on complex tasks for other people to review

Tasks Planning

  • Ensure to attend tasks planning (Sprint Planning) sessions
    • Never miss it, even if you are on sick leave
  • Estimate your tasks well
    • Break down your tasks to the most granular levels
    • Estimate each granular task
  • Help team to estimate for tasks alloted to others also
  • Challenge the requirements
    • Challenge if you feel we should not do it with reasons
    • Challenge priority, if priority is not correct
    • Challenge the Acceptance criteria
    • Challenge Story Points
  • Question the tasks and its requirements, if you are not able to understand it
  • Feel free to suggest kind of tasks you want to pick to improve your learning
  • Be attentive in Sprint Planning, there is so much knowledge to gain during it.

Daily Scrum

  • Attend daily scrum
  • Ask questions to others: what/why/how others are doing their tasks
  • Tell what you did and what you plan to do, very concisely to others
  • Raise alerts if you find anything not right or you feel tasks will not be completed on time
  • Tell everyone if you are blocked on anything
  • Suggest solutions or lend hand if other people are blocked on their tasks
  • Be Attentive
  • If you are not able to join Scrum, send your status update in writing

Follow the processes well

  • Fill up timesheet on time
  • Complete the required trainings on time
  • Fill up mandatory surveys on time

Manage your Leaves

  • Request for planned leaves, well in advance (atleast 2 weeks)
  • Ensure you update your Leave Management system for sick leaves or unplanned leaves
  • Setup “Out of Office” mail whenever you are on leave

Knowing the Organisation

  • Understand Organisation Vision and Mission
  • Know the history of Organisation
    • When was it Formed
    • Who was the founder of the organisation
  • Understand Hierarchy of Role
  • Know Names of Top Management People

Know your team

  • My team strengths
  • My team improvement areas
  • Birthdays of everyone in team
    • Everyone loves if you wish them on their special occassion

Need Mentoring?

If you want me to mentor you personally, feel free to reach out to me.

Rakesh Kalra

Hello, I am Rakesh Kalra. I have more than 15 years of experience working on IT projects, where I have worked on varied complexity of projects and at different levels of roles. I have tried starting my own startups, 3 of those though none of it were successful but gained so much knowledge about business, customers, and the digital world. I love to travel, spend time with my family, and read self-development books.