Kindor Scores: Unlock a Clearer View of Engineering Contributions

Over the past few months, we’ve been focused on a single question:

How can we help leaders truly understand where engineers excel and where there’s room to grow?

Today, we’re excited to introduce Kindor Scores, a new set of multidimensional indicators designed to give you a clear, data-backed view of each contributor’s impact.

These scores are calculated monthly, based on real activity. Each one highlights a different facet of engineering work—helping you identify strengths, monitor progress, and support targeted improvement efforts.

🧠 How Scoring Works

Contribution Scores follow a percentile model. A score of 90 in Coding means the contributor performed better than 90% of peers doing similar work—either within your organization or across the Kindor ecosystem.

You can view scores across time ranges (e.g. “Last Quarter”) to identify trends and consistent patterns in behavior.

When a contributor does not perform any of the activities evaluated in each category, the score will display "NA".

🔍 The 7 Contribution Scores

1. Coding Score

   Goes beyond counting PRs / MRs, this score factors in:

   • PR Cycle Time

   • PRs Size

   • Type of Work Completed (Feature Development, Bug fix, etc.)

   • Rework Rate

   • Breadth (activity across multiple languages and repositories)

2. Code Reviewing Score

   Evaluates PR Reviewing activity based on:

   • Volume of reviews (Approvals, comments and merges)

   • Assigned vs reviewed ratio

   • Review depth (Comments per review)

   • Pickup Times and PR Size

3. Task Completion Score

   Focuses on completed tasks across Jira, Notion or Clickup, it considers:

   • Tasks Complexity (Story Points)

   • Tasks Cycle Time

   • Type of Work Completed

4. Completion Rate Score

   It combines punctuality across three perspectives:

   • Sprint commitments

   • On-time completion of tasks with due date

   • On-time completion of epics with due date

5. Task Management Score

   Captures how proactively the contributor creates, updates, and organizes work in the project management tool.

6. Tech Support Score

   Measures contributions to support activities like handling service desk tickets.

7. Meeting Load

   This isn’t a score but an indicator of the time spent in meetings

📊 Why This Matters

With Contribution Scores, leaders can:

• Run fair, multidimensional performance reviews

• Benchmark contributors across teams or the industry

• Spot high performers, improvement areas, and changes over time

It’s one more step in our mission to bring clarity, accountability, and continuous improvement to tech organizations—without the guesswork.