Frequently Asked Questions

We analyze delivery patterns across six dimensions — including work complexity, collaboration, and consistency — to give you objective insights into each engineer's growth. No subjective judgment, just real signals from actual work.

No — it's designed to guide and support growth, not punish. The goal is to provide objective feedback, enable coaching, and recognize achievements through gamification.

We capture metadata like start/end dates and roles (e.g., React vs. Java dev), which supports contextual analysis. We also support vacations, part-time and annotations for key events.

Not at all. It enhances them by giving a factual foundation for discussions — helping managers coach more effectively and fairly.

Yes. Metrics are normalized and balanced across projects and technologies — avoiding bias toward quantity over quality.

Yes. We surface patterns that may indicate risk — like work overload or inconsistent delivery — so you can have supportive conversations before issues escalate.

No actual code is stored. All analysis is done using transient diffs, and data is encrypted and processed securely via Google Cloud and Anthropic Claude.

You get a baseline report immediately after integration, and clear trends emerge within a month — useful for team leads, CTOs, and coaching efforts.

We're transparent with the team and frame this as a tool for self-awareness, improvement, and recognition — not surveillance.