These skills do not affect the main grade but show the breadth of your profile.
Agile Methods
▼
Understands Kanban principles: visualization, WIP limits, flow management. Can work with a Kanban board in Jira/Trello. Tracks task flow.
Optimizes the Kanban process for the team. Analyzes CFD (cumulative flow diagram) and cycle time. Defines policies for each workflow stage.
Defines the flow-based approach for the division. Trains teams on Kanban practices. Scales Kanban to the organizational level.
Shapes flow management strategy at the organizational level. Defines organizational design for value stream optimization.
AI Coding Assistants
▼
Uses ChatGPT/Claude for routine PM tasks: writing user stories, competitor analysis, preparing presentations. Knows the main capabilities and limitations of AI assistants.
Integrates AI assistants into the product workflow: research synthesis, PRD drafting, data analysis. Creates effective prompts for product-specific tasks.
Defines AI adoption strategy for the product division. Trains PMs on AI usage. Establishes guidelines for responsible AI use.
Knows about GitHub Copilot and its capabilities for accelerating development. Understands the impact on engineering productivity. Can discuss adoption pros and cons with the team.
Assesses the impact of AI coding tools on team productivity and delivery. Makes tooling budget decisions for the team. Factors AI-assisted development into planning.
Defines developer experience strategy including AI tools. Standardizes the approach to AI coding assistance for the division.
Algorithms & Data Structures
▼
Understands basic Big-O notation for meaningful performance discussions with engineers. Knows the relationship between algorithmic complexity and user experience: load speed, interface responsiveness. Can assess the potential impact of technical decisions on product performance.
Uses algorithmic complexity understanding to assess technical feasibility of product ideas. Evaluates the trade-off between complexity and UX when designing features: search, recommendations, feeds. Includes performance requirements in product specifications with business impact justification.
Defines performance strategy for the product portfolio considering algorithmic constraints. Standardizes performance requirements in product specifications for all teams. Coordinates performance optimization initiatives with engineering at the project level.
Understands basic data structures for meaningful communication with engineers about technical decisions. Knows the main concepts: arrays, objects, relationships for understanding the product's data model. Uses knowledge for writing precise user stories with correct data descriptions.
Uses data structure understanding for designing product features considering the data model. Evaluates the impact of data structure choices on UX: search speed, filtering, sorting. Creates product specifications with correct data entity descriptions and relationships.
Defines data modeling standards for product specifications at the project level. Coordinates data architecture decisions between product and engineering teams. Standardizes the approach to describing data requirements in product documentation.
API Management
▼
Understands the purpose of API documentation. Can read API docs (Swagger/OpenAPI). Can use Postman for API testing.
Defines API requirements from the product perspective. Reviews API design. Ensures API documentation quality for developer experience.
Defines API-first strategy for the division. Establishes API governance. Ensures API design consistency across products.
Application Security
▼
Understands basic security principles and their impact on user trust in the product. Knows the main OWASP vulnerabilities and can assess security risk when designing product features. Includes basic security requirements in user stories: validation, authentication.
Defines security requirements for product features considering OWASP Top 10 and compliance. Designs user experience for security-sensitive functions: 2FA, data export, privacy settings. Assesses security risk of new features and includes mitigation in product planning.
Defines security and compliance strategy for the product portfolio at the project level. Standardizes security requirements in the product development process for all teams. Coordinates with the security team on prioritizing security initiatives in the product roadmap.
CI/CD
▼
Understands the CI/CD concept and its impact on product feature delivery speed and quality. Knows the main delivery pipeline stages and can track build status in GitHub Actions. Uses CI/CD understanding for realistic feature delivery timeline estimation.
Uses CI/CD metrics to assess engineering velocity and forecast delivery timelines. Evaluates deployment frequency and lead time as delivery process health indicators. Coordinates pipeline improvements with engineering to accelerate time-to-market.
Defines delivery strategy for the product portfolio considering CI/CD infrastructure. Standardizes deployment practices for all product teams: release cadence, rollback policies. Coordinates CI/CD infrastructure investments with product delivery goals.
Clean Code & Refactoring
▼
Understands basic code quality metrics and their impact on product stability and development velocity. Knows the relationship between technical debt and feature delivery speed for roadmap planning. Can interpret SonarQube and code quality dashboard reports for product decisions.
Uses code quality metrics for product decisions: tech debt payoff vs new features. Evaluates the impact of code quality on user experience: performance, reliability, security. Includes quality improvement tasks in the product backlog with clear business justification.
Defines quality management strategy for the product portfolio at the project level. Standardizes the approach to including technical quality initiatives in the product roadmap. Coordinates the balance between feature development and quality improvement across all teams.
Cloud Providers
▼
Understands basic AWS services and their role in product infrastructure for meaningful discussions. Knows the relationship between cloud infrastructure and product capabilities: scalability, global availability. Can estimate basic infrastructure costs when planning product features.
Uses AWS understanding to assess feature feasibility and cost: global deployment, CDN, ML services. Defines infrastructure requirements for product initiatives: scaling, multi-region, disaster recovery. Includes cloud cost analysis in product business cases and ROI calculations.
Defines cloud infrastructure strategy for the product portfolio at the project level. Coordinates cloud cost optimization with engineering aligned with product growth targets. Standardizes infrastructure planning in the product roadmap for all teams.
Code Review
▼
Understands the code review process and can read PR descriptions to assess the scope of technical changes. Knows basic code quality criteria for meaningful participation in discussions with the development team. Uses code review understanding for more accurate feature timeline and risk estimation.
Participates in code review to understand technical implementation and quality of product features. Evaluates PRs for compliance with product requirements: UX, performance, accessibility. Uses code review insights to improve communication between product and engineering.
Defines product quality criteria integrated into the code review process for all teams. Standardizes the approach to technical review of product features: checklist, acceptance criteria, DoD. Coordinates engineering and product quality standards at the project level.
Concurrency & Parallelism
▼
Understands the asynchrony concept for meaningful UX requirement descriptions regarding loading and responsiveness. Knows the impact of async operations on user experience: loading states, optimistic updates, error handling. Creates user stories accounting for asynchronous system behavior.
Designs UX for asynchronous operations: progress indicators, retry mechanisms, offline support. Defines requirements for real-time functionality: notifications, live updates, collaborative editing. Evaluates the trade-off between real-time and eventual consistency for product features.
Defines real-time functionality strategy for the product portfolio at the project level. Standardizes UX patterns for async operations across all team products. Coordinates real-time infrastructure investments with engineering for product needs.
Containerization
▼
Understands basic containerization concepts for meaningful deployment discussions with the team. Knows Docker's role in the CI/CD pipeline and its impact on feature delivery speed. Can explain containerization benefits for product stability to stakeholders.
Uses Docker understanding for release strategy planning and deployment risk assessment. Evaluates the impact of container architecture on product scalability and reliability. Includes infrastructure requirements in product planning considering containerization.
Defines deployment and release strategy for the product portfolio at the project level. Coordinates infrastructure requirements with DevOps to ensure product delivery SLO. Standardizes the release management approach using container technologies.
Delivery Management
▼
Understands what dependencies are in projects. Can identify blocking dependencies. Communicates dependency status to the team.
Manages dependencies between teams. Proactively identifies risks. Creates dependency resolution plans.
Defines organizational design for minimizing dependencies. Implements team topologies and API contracts. Establishes cross-team collaboration processes.
Shapes organizational architecture for autonomous teams. Defines strategy for platform vs product teams. Minimizes organizational friction.
Participates in retrospectives and suggests process improvements. Documents current processes. Executes improvement actions from retros.
Conducts retrospectives and facilitates improvement discussions. Implements process improvements. Measures the impact of changes through metrics.
Defines process excellence standards for the division. Trains teams on continuous improvement methods. Establishes a culture of experimentation.
Git & Workflows
▼
Understands basic Git advanced concepts relevant to product management: release branching and tagging for version tracking, pull request workflows for feature delivery visibility, changelog generation from Git history. Follows team conventions for reviewing and approving merge requests.
Uses Git for working with product documentation (docs-as-code). Understands the team's branching strategy. Can create PRs with documentation.
Defines standards for documentation-in-code. Uses Git data for engineering management insights.
Integration Testing
▼
Understands the role of integration testing in ensuring product feature stability. Knows the relationship between integration tests and production bug count for assessing release quality. Can interpret integration test results for go/no-go decisions.
Uses integration test results to assess risk and quality of product releases. Defines critical integration test scenarios based on user journeys and business impact. Includes integration testing requirements in product specifications for cross-team features.
Defines quality assurance strategy for the product portfolio at the project level. Standardizes integration testing requirements for cross-team product features. Coordinates with QA lead on alignment between testing priorities and product risks.
Logging
▼
Understands the importance of logging for tracking user behavior and diagnosing issues. Knows the main logging levels and can interpret error logs to assess incident severity. Uses logs for user journey analysis and friction point identification.
Uses structured logs for product analytics: user behavior, feature usage, error patterns. Defines logging requirements for product features: what to log for business analytics. Designs event taxonomy for product analytics based on structured logging.
Defines observability requirements for the product portfolio at the project level. Standardizes event taxonomy and logging requirements for all product teams. Coordinates with engineering and data teams on creating product analytics infrastructure.
OOP & Design Patterns
▼
Knows basic design patterns for understanding technical discussions with the development team. Understands the impact of architectural decisions on development speed and product flexibility. Uses knowledge for more precise communication of technical requirements.
Uses pattern understanding to evaluate technical proposals and their impact on product flexibility. Evaluates architectural decisions through the lens of product metrics: time-to-market, extensibility, maintainability. Includes architectural considerations in the product decision-making process.
Defines architectural strategy for the product platform at the project level. Coordinates alignment between architectural and product decisions for all teams. Standardizes the framework for build vs buy evaluation considering architectural patterns.
Understands basic OOP principles for meaningful communication with engineers about codebase structure. Knows modularity and encapsulation concepts for understanding the team's architectural decisions. Uses basic knowledge for writing technically correct product requirements.
Uses OOP understanding to evaluate architectural decisions and their impact on product flexibility. Evaluates architecture modularity and extensibility for planning future product features. Includes architectural considerations in the product roadmap with business value justification.
Defines architectural principles for the product platform at the project level. Coordinates with the architecture team on alignment between technical and product decisions. Standardizes the approach to including architectural work in product planning.
Project Planning
▼
Understands team resource constraints. Helps track capacity. Participates in capacity planning sessions.
Plans resources for delivery: defines staffing needs, balances workload. Manages contractor/outsource resources.
Defines staffing strategy for the division. Establishes organizational design for optimal resource utilization.
Understands risk types in product development (technical, market, usability, value). Can identify risks. Maintains a risk register.
Conducts risk assessment for product decisions. Applies pre-mortem analysis. Defines mitigation strategies and contingency plans.
Defines risk management framework for the division. Establishes risk-aware decision-making processes. Trains PMs on risk assessment.
Defines organizational risk appetite. Manages strategic risks for the product portfolio. Shapes a culture of calculated risk-taking.
Prompt Engineering
▼
Uses AI tools to draft product specifications and user stories. Formulates prompts for competitive analysis, market research summaries, and feature prioritization assistance. Understands how to provide business context to get relevant AI outputs.
Creates complex prompts for product workflows: research synthesis, competitive analysis, PRD drafting. Applies chain-of-thought and role-based prompting.
Defines prompt engineering standards for the division. Creates shared prompt libraries. Trains the team on advanced techniques.
REST API
▼
Understands basic REST API principles for describing technical requirements for integrations and backend. Knows the main HTTP methods and can read API documentation to understand system capabilities. Creates user stories with correct API interaction descriptions between components.
Designs API requirements for product features considering client and partner convenience. Evaluates API design for developer experience and partnership integration potential. Defines versioning and backwards compatibility strategy for the product's public APIs.
Defines API strategy for the product platform at the project level. Coordinates API design between teams to ensure consistency and interoperability. Standardizes API requirements in product specifications for all product teams.
System Design
▼
Understands basic architectural concepts: client-server, REST API, database. Can communicate with developers using technical language. Reads architectural diagrams.
Understands trade-offs of architectural decisions and their impact on the product. Participates in technical discussions. Considers technical constraints in product decisions.
Participates in strategic architectural decisions. Ensures alignment between technical and product strategy.
Unit Testing
▼
Understands basic unit testing concepts: what tests verify, test/production code separation, green/red test status meaning. Follows team practices for reviewing test coverage reports and understanding quality gates in CI/CD pipelines.
Uses test metrics for release readiness and quality gate decisions. Evaluates test coverage as a technical health indicator for product modules. Includes testing requirements in Definition of Done for product user stories.
Defines quality strategy for the product portfolio: testing priorities, automation ROI, quality KPIs. Standardizes quality requirements in the product development process for all teams. Coordinates the balance between testing thoroughness and delivery speed at the project level.
User Documentation
▼
Maintains product knowledge base in Confluence/Notion. Documents decisions, specs, meeting notes. Keeps documentation up to date.
Builds the knowledge base structure for the product. Defines information architecture. Ensures knowledge accessibility for the team.
Defines knowledge sharing strategy for the division. Ensures cross-team knowledge transfer.
Shapes organizational knowledge management strategy. Defines investments in knowledge infrastructure.
Understands the importance of user documentation. Helps write help articles and FAQ. Knows UX writing basics.
Defines requirements for user documentation. Coordinates tech writers. Ensures documentation coverage for all features.
Defines documentation standards for the division. Establishes a tech writing practice.