---
id: TASK-5
title: Rewrite weak/duty-style bullets into IC-focused impact with metrics
status: Done
assignee: []
created_date: '2026-09-08 16:57'
updated_date: '2026-09-08 17:26'
labels: []
dependencies: []
ordinal: 5000
---

## Description

<!-- SECTION:DESCRIPTION:BEGIN -->
Rewrite bullets that sound like process ownership, leadership, or vague duties into concrete IC-focused technical outcomes with metrics.

---

**Expert-рекомендации по переформулировке:**

**Dixy — "Own cross-cutting backend changes end-to-end — requirements through production — for the systems-engineering team."**
  Проблема: process ownership, нет исхода.
  Рекомендация: "Owned end-to-end delivery of cross-cutting backend changes (requirements → production) for high-traffic mobile inventory and integration services."

**Dixy — "Parallelized GitLab CI pipelines, removing cross-team build bottlenecks."**
  Проблема: размытый масштаб (vague scale).
  Рекомендация: "Parallelized GitLab CI pipelines, cutting average pipeline time and eliminating cross-team build queues." (добавить % или минуты, если есть цифра)

**Raiffeisen — "Established observability across services with OpenTelemetry and Jaeger."**
  Проблема: нет масштаба или результата.
  Рекомендация: "Rolled out OpenTelemetry + Jaeger across services, enabling distributed tracing for the banking infrastructure migration."

**Raiffeisen — "Drove one product's infrastructure migration to 80% completion; unified technical roadmapping and the technical-debt process across three teams."**
  Проблема: heavy manager language.
  Рекомендация: "Led technical design and delivery of infrastructure migration to 80% completion; defined and enforced technical-debt reduction process used by three product teams."

**Samokat — "Launched 3 new products to production, owning backend architecture and delivery end-to-end."**
  Проблема: good but generic.
  Рекомендация: "Architected and delivered backend for 3 new consumer products from zero to production (Kafka event streaming, WebSocket real-time layer, DDD boundaries)."

**Samokat — "Introduced Domain-Driven Design as the architectural baseline; established a technical-debt process across teams."**
  Проблема: process-heavy.
  Рекомендация: "Established Domain-Driven Design as the architectural standard and a lightweight technical-debt process adopted by multiple teams."

**Дополнительно (из Section 3 — IC-позиционирование):**
- Summary: "I own work end-to-end" → "Delivers end-to-end backend systems with measurable outcomes"
- Avoid "unified technical roadmapping", "established … process across teams", "ran 10+ internal seminars" — если нельзя привязать к конкретному инженерному результату.
- Предпочтительные формулировки: "Owned architecture and delivery of…", "Designed and implemented…", "Reduced X by Y through…", "Built the Core framework used by N services".
- Везде: добавить concrete impact numbers (users, RPS, data volume, $ processed, latency).
<!-- SECTION:DESCRIPTION:END -->

## Implementation Plan

<!-- SECTION:PLAN:BEGIN -->
Пошаговый план:

1. Найти в western-cv-template.html каждый bullet из таблицы выше и заменить на рекомендованную формулировку.
2. Проверить Summary — заменить "I own work end-to-end" на версию с measurable outcomes.
3. Пройтись по всем остальным bullet'ам на предмет "process ownership" формулировок — заменить на system/code impact.
4. Добавить цифры/метрики везде, где они есть или вспоминаются (latency, throughput, users, volume).
5. Убрать формулировки "across teams", "unified roadmap", "established process" без технического контекста.
6. Проверить, что общий тон — senior IC, а не tech lead / practice lead / people manager.
7. Пересобрать PDF и проверить, что влезает в 2 страницы.
<!-- SECTION:PLAN:END -->

## Implementation Notes

<!-- SECTION:NOTES:BEGIN -->
Ключевые принципы:
- "Improved X by Y%" / "Reduced latency from A to B" / "Handled N events/sec" — лучше, чем "owned / led / established".
- Job titles остаются реальными (Lead, Team Lead) — это ок для senior IC, если сами bullet'ы про код, а не про людей.
- "Led" допустимо, если это "Led technical design and delivery of X" (т.е. техническое лидерство), а не "Led a team of 5 people".
- Vary repeated language: "end-to-end", "across teams", "technical-debt process" встречаются по 2-3 раза — разбавить синонимами.

Metrics provided by user:
- Dixy CI: pipeline wait reduced ~30 min → ~5 min (83%)
- Dixy system: 2,000 stores, ~1,000 RPS, 800 GB+ data
- Samokat: 150 RPS, 800K+ users, 20 GB data
- Raiffeisen observability: 20 services (traffic volume unknown, skipped)
- Soft Telematics: 1M+ connected devices

Additional edits beyond the table:
- Soft Telematics: rewrote both bullets with nation-scale/1M+ devices framing
- Balance Platform: replaced "ran 10+ seminars" with org-wide adoption framing

PDF built: western-cv-template-20260908-172617.pdf
<!-- SECTION:NOTES:END -->

## Final Summary

<!-- SECTION:FINAL_SUMMARY:BEGIN -->
Rewrote 9 bullets + Summary per TASK-5 recommendations. Applied metrics from user: Dixy (~1K RPS, 2K stores, 800GB), Samokat (150 RPS, 800K users, 20 GB), Raiffeisen (20 services), Soft Telematics (1M+ devices). Replaced process/leadership language with IC-focused technical impact. Built PDF (2-page fit verified).
<!-- SECTION:FINAL_SUMMARY:END -->