IT roles

IT roles for vibe-coding — 46 cards, translated to English. Читать по-русски →

ADR (Architecture Decision Record)

Skeleton of an architecture decision record — so the "why" is never lost.

Agile Coach

Grows agility across several teams and the org, not just one team.

Agile · Scrum · Kanban

Manifesto, Scrum roles/events/artifacts and Kanban flow — the base of agile delivery.

Software Architect

Picks the approach and weighs blast radius: system design, trade-offs, NFRs.

Backend Engineer

Builds logic, data and APIs: server reliability, security and performance.

Bug report

What a defect needs so it gets reproduced and fixed on the first try.

Business Analyst

Bridge between business and dev: gathers requirements and maps processes.

C4 model

Four zoom levels for architecture diagrams: Context → Container → Component → Code.

CPO

Company product leader: product strategy, portfolio, business value.

CTO

Company tech leader: strategy, top-level architecture, team, risk.

Data Analyst

Answers business questions with data: metrics, dashboards, A/B, decisions.

Data / ML Engineer

Builds data pipelines and ML systems: pipelines, features, training, inference.

Work decomposition (Epic → Story → Task)

Breaking big into testable: Epic→Feature→Story→Task hierarchy and INVEST.

Definition of Done (DoD)

Agreement on when a task is truly "done" — one shared quality bar.

Definition of Ready (DoR)

Agreement on when a task can be started — so nothing "raw" gets pulled in.

Delivery / Project Manager

Drives an initiative to a result on time: plan, risks, coordination, comms.

Product / UX-UI Designer

Designs usability and interface: user journey, prototype, visual language.

DevOps / SRE

Owns infrastructure, CI/CD, observability and production reliability.

Software Engineer

Implements steps via TDD — clean, to conventions, fixing the whole problem class.

Engineering Manager

Owns people and delivery of an eng team: hiring, growth, process, results.

Estimation (story points / Fibonacci)

Estimate relatively, not in hours: story points, Fibonacci, planning poker.

Frontend Engineer

Builds what users see: UI, state, performance, accessibility.

Fullstack Engineer

Owns a feature end-to-end — from UI to database and API.

Independent verifier

Adversarially checks the result and diff: catches regressions and neighbor breakage.

Mobile Engineer

Builds native/cross-platform apps for iOS and Android.

Prioritization (RICE · ICE · MoSCoW · Kano)

How to choose what to do first: scoring formulas and priority matrices.

Product Manager

Owns the "what & why": problem, value, strategy and product metrics.

Product metrics (North Star · AARRR · HEART)

Measuring product value and growth: one guiding metric and funnel frameworks.

Product Owner

Turns wishes into value and priorities; owns the backlog and acceptance criteria.

Product thinking (JTBD · PMF · OKR · discovery)

Think in value, not features: user jobs, product/market fit, goals and experiments.

QA Automation / SDET

Automates checks: e2e/integration tests, test framework, in CI.

QA Engineer (manual)

Checks quality by hand: scenarios, edges, errors — catches defects before users.

QA Lead

Owns quality strategy: testing process, metrics, release readiness.

Release Manager

Owns shipping: release planning, readiness, rollback and prod stability.

Scrum Master

Keeper of the Scrum process: facilitates events, removes blockers, shields the team.

Security Engineer

Protects product and data: threats, vulnerabilities, secrets, secure practices.

System Analyst

Turns requirements into a technical spec: API contracts, data, integrations.

System Design Doc

A design doc before building: problem, options, chosen design, risks.

Task / ticket

What a good task is made of — so it can be picked up and done without questions.

Tech Lead

Team tech leader: code quality, decisions, reviews and engineer growth.

Tech Writer

Makes knowledge accessible: docs, guides, API reference, release notes.

Test case (BDD / Gherkin)

How to describe a testable scenario in Given/When/Then (Gherkin).

Test plan

What, how and how much we test — scope, risks, entry/exit criteria.

Unit economics (CAC · LTV · payback)

Core business-health formulas: CAC, LTV, LTV/CAC, payback, MRR/ARR, churn. Wired to the calculator.

User Story (INVEST + Given/When/Then)

Template and example of a good user story with acceptance criteria.

UX Researcher

Gets the truth about users: interviews, usability tests, insight synthesis.