Architecture review
Format: 2–4 hours plus preparation on your materials.
For: teams before scaling, a release, or a change in load profile.
Outcome: a review of the key architectural decisions, risks, bottlenecks, and a prioritized change plan.
For teams, CTOs, and product owners who need an experienced eye on backend architecture and processes. I work remotely, in Russian and English.
Format: 2–4 hours plus preparation on your materials.
For: teams before scaling, a release, or a change in load profile.
Outcome: a review of the key architectural decisions, risks, bottlenecks, and a prioritized change plan.
Format: interviews plus a review of code and processes, a report with a roadmap.
For: engineering managers and CTOs who need an external assessment of the team.
Outcome: a report on processes, code review, and tech debt; a prioritized improvement roadmap.
Format: a session with the team after an incident.
For: teams after a serious outage that need a structured review without blame-hunting.
Outcome: timeline, root causes, a plan to prevent recurrence.
Format: fixed hours per month, ongoing availability to the team.
For: product teams that need a senior engineer “on call” without hiring full-time.
Outcome: regular design reviews, help with decisions, mentoring for key developers.
Email with the subject Consult or Telegram — I reply within 24–48 hours.