Goals

Process Adherence 20
-Source Code Version
-Agile
-Communication & Collaboration
-Requirement Analysis & Estimations
Coding & Development 20

-Security
-Coding
-Coding Guidelines
-Code organization within a file
-Code organization across files
-Source tree organization
-Code redability
-Defensive coding
-Error Handling
-Frameworks
-Database
-Security
-Scalability
-Code & design reviews

UT/CD/CI 15
Learning/Knowledge and development 10
Mentoring/Coaching

Monitoring 10

-Health check of apps and servers

-Live issues

Mentoring/Coaching 10

-mentoring Team
Team Management 15

-Career Mapping
-Process Improvement
Target
- Adequate knowledge of GIT version control required for
development
- Follow all git process
-Every commit has min 20 charater message
-Keep all repositories clean and upto date
-Ensure that all git code hooks are used
-Emails are read on time and replied
-JIRA stories are well maintained with comments and status
updates
-Follow ups on pending tasks done on time
-DIPSUMs and iteration meetings are attended on time and
actively engaged professionally. Appropriate status shared and
concerns raised in timely manner.
-Actively involved in requirement analysis, impact analysis, story
grooming.
-Ensure that estimations are accurate.
-Give feedback to junior team members for improvement
-Stories are groomed with minimum ambiquity
-Understand Agile Manifesto and Agile@Naukri Charter.
-Works towards increasing quality and velocity of team.
-Proactive and taking initiative to improve processes
 -Understand security gls and tc of them during dev
-0 Security bugs during VA scan for your stories/projects
-Ensure that VA scan is done wherever required.
-All standard coding guidelines followed during development
-Ensure that no code goes without review,review comments
documented in JIRA
-Do code review of team members extensively
-Guide and mentor members on code quality and development
process
-Good understanding of frameworks
-Database queries are optimized and reviewed by
manager/lead/PD
-Good code and domain knowledge, resulting in minimum
development bugs (less than 10% of Stories)
-20-30% of bandwidth goes in development activities (Prd
stories, Tech Debt, New prd initiatives, Dev testing)
-Actively involved in design discussions with PD and other team
members
-Design docs are created and added in JIRA
-Tech debt is being tracked actively and planned in regular
iterations
-Focus on code reusability and performance to be added

-Writes all the UTs along with the stories picked and also writes
UTs for the legacy code
- Ensure that team understand the value of CI/CD and all
necessary infra is in place for CI/CD
- Regular audits are done to ensure people are following process
and give feedback
- Guide all team members in writing good UTs
- Makes sure that all the deployment \ goes to QA only if all UT
cases are green
- Jenkins integration
-Shown initiative in improving UTs and CI/CD implementation
 -Ensure that at least 1 training/workshop per month is attended
-Give at least 1 tech talk every quarter with in own team
-Atleast 1 tech talk every 2 quarter to audience outside team
-Discuss with manager and identify set of trainings required to
achieve rest of goals

-All live issues are completed as per SLA

-Ensure that live issues are minimum (< 5% of stories) in the
team
-Plan and implement app monitoring roster
-Reports are tracked actively for any issues
-Team is aware of server architecture
-Identify manual tasks and get it automated

Start mentoring and guiding team members

-Understand the training needs of team and plan trainings and
knowledge upgrade
-Resource planning and alignment with work
-Identifying the training needs of individual and team members
-Give feedback on performance in a structured manner
-Motivate team through constant appreciation and engagement
-Find ways to improve team morale
-Work as bridge between team and management
Touchstone/project
Ensuring GIT - Any merging issues / time taken for forward merging / Proper comments
Email communication should be proactive - no follow-up should be there, communication with
concerned stake holders (i.e. product, diff team), appropriate content in mail

Ensuring JIRA - proper comments, epic, lable, proper status update, RCA (in case of bugs),
request with permanent fix (in case of roster), Release notes should be there

train users for story grooming to minimize the dependencies.

Increase vel & quality - can measure in capacity planning of team

In case of any concern/issue regarding process with in team it should be raised proactively &
properly

Even distribution of stories for grooming with-in team - no dependency on any particular

Team should develop all stuff on loacl env using docker images
Projects:
Campus Discovery Tool
Social Login
Web CV Revamp
Off campus Search Approx
Govt. Jobs
SEO Double the organic CV registration
Recruiter Management in CDM
Net Engage Responsive
Tech Projects
Suggester Merging
Chat Engine replacement for netengage
movement of profile pic/ uploaded pics on akamai
Merge jobalert into jobsearch
enhancement on sending jobalert

- ensure VA is happening wherever applicable and all stories should be mentioned/linked in VA

story.
- Comminication should be well ahead to VA team for the same
- plan to ensure 0 slow query on production
- workaround 0 functional bug in story having (0,1,2,3,5 pointers)
- up to 2 functioanl bugs in story having 8,13 pointers
- 0 bug in pre-defined test cases, due to merging, UI integration, across team back end
integration
- understand server architecture, draft it & maintain
- scalability of current architecture
- proactivily raise alarm for any architectural/server/process realted issue (i.e. porting taking
time, git hook will hamper vel etc...)
- Active & proper code review should be in place with in team as per process
- Should come - up with plan for optimization / improvement on concerned areas with
revamp / usage new technology / refactor existing algo etc ... and lead the execution phase as
well

- Development should be done on docker (CD enviornment)

- UT should be 100% wherever applicable
- Should be responsible for team's commitment for UT coverage
- Plan to implement UT for frequently evolving/changing legacy code
- Ensure that atleast 30% tech talks per year should be attended
- Give atleast 1 tech talk every quarter with in own team
- Write atleast 2 blogs in an year
- Atleast 2 tech talks in an year to audience outside team
- Discuss with manager and identify set of trainings required to achieve rest of goals
- Start mentoring and guiding SE, SSE

target to achieve 99% uptime

app logs cleanup
server performance check periodically.

- Discuss with manager and identify set of trainings required to achieve rest of goals
- Start mentoring and guiding SE, SSE

for process improvement:

reduction of customer issue resolution time 20%
roaster implementation
Career mapping :
internal learning sessions
full stack development for talent engagement