What a Senior } should know

Shapes API documentation strategy at the product level, including versioning policy and deprecation notices. Designs developer portal considering DX metrics — time-to-first-call, completion rate. Implements docs-as-code approach.

Participates in REST API design for complex product scenarios. Defines API-first strategy for the product. Designs API contracts considering extensibility and partner integration needs. Reviews OpenAPI specs.

Plans capacity for multiple teams considering cross-team dependencies and infrastructure constraints. Designs scaling strategy for the product, balancing cost and performance. Forecasts resource needs.

Actively participates in microservice decomposition decisions as TPM. Defines product bounded contexts considering team topology. Evaluates impact on delivery speed, data consistency, and user experience. Drives architecture roadmap.

Actively participates in system design for complex product scenarios. Understands distributed systems challenges: CAP theorem, eventual consistency. Defines non-functional requirements considering scale and reliability targets.

Defines tech debt management strategy for the product. Implements tech debt budget: 20% capacity allocation. Designs metrics for tracking debt growth and payoff. Makes architecture decisions considering debt accumulation.

Defines SLI/SLO strategy for the product with a user-centric approach. Designs error budget policies: what happens when budget is exhausted. Links SLO with product decisions — feature rollout, scaling, architecture changes.

Participates in architectural code reviews, evaluating impact on product roadmap and scalability. Reviews API contracts for backwards compatibility. Defines criteria for mandatory TPM review in pull requests.

Builds quarterly experimentation strategy considering technical service architecture. Designs multivariate tests accounting for backend load and feature flag interactions. Prioritizes hypotheses using ICE/RICE frameworks.

Builds backlog management system for multiple teams with cross-team dependencies. Defines strategy for balancing product features, tech debt, and platform work. Implements backlog health metrics and cycle time tracking.

Builds funnel analytics system for the product, linking conversion rates with technical SLI/SLO. Designs real-time alerting for funnel degradation. Defines optimization strategy considering architectural constraints.

Builds GTM strategy for a technical platform or API product. Defines developer adoption funnel and partnership integrations. Coordinates cross-functional launch with engineering, DevRel, and marketing teams.

Builds culture of hypothesis-driven development in the team. Designs experiments with controlled technical variables. Defines experiment taxonomy: discovery, optimization, validation. Links results with roadmap.

Builds JTBD-driven product strategy for a technical platform. Conducts switch interviews with technical users. Defines competitive landscape through lens of jobs. Links JTBD with architecture decisions.

Builds continuous market intelligence system for a technical product. Defines competitive differentiation through technical capabilities. Analyzes build-vs-buy decisions considering architectural trade-offs.

Builds OKR system for the product linking technical investments with business outcomes. Defines leading and lagging indicators for platform and infrastructure work. Facilitates OKR alignment between product and engineering.

Defines product analytics strategy including event taxonomy and data governance. Designs tracking architecture for microservice environments. Links product events with backend metrics for full-stack observability.

Shapes strategic product roadmap with technical architecture evolution. Plans 4-6 quarters ahead considering platform capabilities and migration paths. Defines investment balance between product, platform, and infrastructure.

Creates strategic product vision for a technical platform. Defines technology-enabled differentiators. Shapes narrative linking technical architecture evolution with customer value. Inspires engineering and product teams.

Manages complex stakeholder landscape for a technical platform. Coordinates alignment between product, engineering, DevOps, and business. Facilitates architecture decision making with multiple technical stakeholders.

Builds systematic user research program for a technical platform. Defines research roadmap with a mix of generative and evaluative methods. Conducts complex studies: diary studies with developers, API usability testing.

Applies user story mapping to complex technical products with multiple user personas and API consumers. Integrates technical architecture decisions into story map. Defines release strategy through mapping considering platform dependencies.

Defines delivery metrics system for the product, linking engineering performance with business outcomes. Implements value stream mapping to optimize flow from idea to production. Designs alerting for metric degradation.

Coordinates dependencies for complex cross-team initiatives with technical and product components. Designs dependency resolution strategies: API contracts, interface agreements, platform capabilities. Forecasts conflicts.

Builds estimation system for large initiatives with technical dependencies. Applies Monte Carlo simulation for timeline forecasting. Decomposes epics considering architectural risks and infrastructure work.

Designs Kanban system for multiple teams with unified flow. Implements multi-level Kanban: team, product, portfolio. Defines policies for each state considering technical quality gates and deployment readiness.

Builds systematic process improvement for the product team. Applies Theory of Constraints to identify bottlenecks. Designs experiments for process changes with A/B testing of workflows.

Defines release strategy for the product: cadence, rollout strategy, rollback procedures. Designs progressive delivery with canary releases and feature flags. Coordinates cross-team release dependencies and integration testing.

Builds systematic risk management for the product. Designs risk framework considering architectural, operational, and business risks. Defines risk appetite for technical decisions. Integrates risk review into delivery process.

Scales Scrum for multiple teams: Scrum of Scrums, Nexus. Coordinates cross-team sprint planning with technical dependencies. Defines common Definition of Done with architecture and performance requirements.

Establishes architectural documentation process for the product, including RFCs and design docs. Defines technical specification templates with business context. Ensures traceability from business requirements to architectural decisions.

Designs comprehensive architectural diagrams for cross-team alignment: system context, container, and component levels. Creates dynamic diagrams for complex workflows. Defines visualization standards for teams.