Titles are external only. An environment where people have a "this is not a part of my job description" attitude is not what we like. Titles however allow our customers to understand your roles and responsibilities.
Learn to learn
Understand the need for tests, code conventions, linting, configuration rules, and continuous integration.
Participating in agile ceremonies.
Learn how to communicate well.
Own the development of small features (not more than 3 story points) or modules (the epic should not be more than 21 story points).
Write unit, integration, and acceptance tests.
Lead discussions around coding conventions, architecture patterns, and framework choices.
Maintain hygiene by creating CI pipelines.
Own business verticals/modules. Every project core modules or services, as a senior software engineer you need to own atleast one of them.
Mentor team members.
Participate and conduct sharing sessions.
At this junction responsibilities move towards the ability to organize, lead, forsee technical challenges, and the softer side of software development.
We encourage everyone to reach out to their manager and schedule atleast a monthly 1 on 1. Rapid feedback and improvement is the best way to move forward.
Appraisals are done yearly. We follow the Objectives and Key results system.