These skills do not affect the main grade but show the breadth of your profile.
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 budgets and SLOs based on algorithmic complexity analysis of critical paths. Designs product features considering scalability: pagination, lazy loading, progressive enhancement. Evaluates AI/ML feature feasibility based on computational complexity understanding.
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.
Designs product information architecture considering optimal data structures. Evaluates trade-offs between different data models when designing large-scale product features. Defines product data strategy: what data to collect, how to store, how to use.
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.
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 product security strategy: threat modeling, security features roadmap, compliance requirements. Designs privacy-by-design and security-by-design approaches to product development. Balances security requirements with usability for optimal user experience.
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 considering CI/CD capabilities: feature flags, A/B testing, canary releases. Designs deployment pipeline requirements to support product experiments. Uses DORA metrics for continuous delivery process improvement.
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.
Designs product strategy for managing technical quality: quality budgets, reliability targets. Defines SLOs and quality metrics based on user impact and business value. Balances code quality investments with delivery velocity through a data-driven approach.
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 strategy for the product: multi-region, serverless, managed services vs self-hosted. Designs infrastructure requirements for product scaling: capacity planning, cost optimization. Evaluates AWS services as enablers for product innovation: ML, IoT, real-time.
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.
Analyzes code review metrics to assess product technical health: cycle time, PR size, review quality. Uses code review process understanding to optimize the delivery pipeline and forecast risks. Influences quality culture by establishing product acceptance criteria in reviews.
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 product strategy for real-time and async features: push notifications, streaming, WebSocket. Designs user experience for distributed and eventually consistent systems. Evaluates real-time product feature feasibility considering infrastructure constraints.
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 product requirements for deployment architecture: blue-green, canary, feature flags. Designs release strategy considering container infrastructure for zero-downtime deployments. Evaluates ROI of container infrastructure investments for accelerating time-to-market.
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
▼
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.
Systematically optimizes processes at the product level. Applies lean thinking and waste elimination. Implements a continuous improvement culture.
Defines process excellence standards for the division. Trains teams on continuous improvement methods. Establishes a culture of experimentation.
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 integration testing strategy from the product perspective: critical paths, risk areas, automation priorities. Designs quality gates based on integration test results for the product delivery process. Evaluates ROI of integration testing investments through impact on product stability.
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 product observability strategy: what metrics, events, and logs are needed for product decisions. Designs event-driven analytics based on structured logging for data-driven product management. Uses log analysis for continuous discovery: pain points, patterns, opportunities.
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 product requirements for architecture: plugin system, marketplace, white-label, multi-tenancy. Designs platform strategy considering architectural patterns for ecosystem development. Evaluates build vs buy decisions considering architectural implications and long-term product vision.
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.
Designs product requirements considering architectural principles: modularity, extensibility, reusability. Evaluates the impact of architectural decisions on long-term product evolution and technical debt. Defines the balance between architectural perfection and delivery speed in product planning.
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.
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: public API, partner API, internal API with a clear business model. Designs an API-first approach to product platform development for ecosystem growth. Evaluates API as a product: documentation, developer portal, monetization, rate limiting.
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.
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 product quality strategy: test coverage targets, automation priorities, quality metrics. Designs a risk-based testing approach: critical user journeys are tested more thoroughly. Uses test analytics for risk forecasting and release process optimization.
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.