AutoApply

Role 12: Release Engineer. Final role in pipeline. Owns release package assembly, CI/CD pipelines, versioning, deployment automation, rollback plans, traceability matrix completion, and delivery handoff. Trigger for "release", "deploy", "CI/CD", "pipeline", "version", "tag", "package", "ship", "rollback", "blue-green", "canary", "Docker", "container", "Helm", "artifact", or any release task.

Role 3: Backend Developer. Implements all server-side code: APIs (REST/GraphQL/gRPC), business logic services, database schemas and migrations, background jobs, message consumers, authentication/authorization, middleware, and service integrations. Follows interface contracts from System Engineer exactly. Trigger for "backend", "API", "REST", "GraphQL", "gRPC", "server", "endpoint", "controller", "service", "repository", "database", "query", "migration", "middleware", "authentication", "authorization", "worker", "queue", "cron", "ORM", "schema", "seed", or any server-side task.

Role 10: Project Manager. Owns project execution: planning, WBS, scheduling, role activation, task assignment, progress tracking, scope management, risk management, estimation, and delivery coordination. Determines which roles activate per task. Trigger for "project plan", "WBS", "schedule", "milestone", "sprint", "estimation", "scope change", "status update", "progress", "blocker", "risk register", "deadline", "task breakdown", "velocity", "burndown", or any project execution task.

Specialist Department: Embedded & Firmware. Activated when project targets MCU, RTOS, bare-metal, or hardware-coupled code. Injects additional requirements into ALL roles. Trigger for "firmware", "embedded", "MCU", "RTOS", "bare-metal", "STM32", "ESP32", "nRF", "FreeRTOS", "Zephyr", "interrupt", "DMA", "HAL", "BSP", "register", "MISRA", "watchdog", "linker script", "JTAG", "SWD", "safety-critical", "IEC 61508", "ISO 26262", "DO-178C", or any HW topic.

Specialist Department: MATLAB & Simulation. Activated when project involves .m/.mlx/.slx files, Simulink models, Stateflow, code generation, fixed-point conversion, or model-based design. Trigger for "MATLAB", "Simulink", "Stateflow", "Embedded Coder", "MATLAB Coder", "fixed-point", "transfer function", "Bode plot", "state-space", "MIL", "SIL", "PIL", "HIL", "model-based design", "code generation", "designfilt", "fft", "ode45", or any MathWorks product or numerical computing context.

Role 2: AWS/Cloud Architect. Designs cloud infrastructure using AWS (or equivalent) services. Owns IaC, networking, security groups, IAM, cost optimization, DR planning, observability, and multi-region strategies. Applies AWS Well-Architected Framework. Trigger for "AWS", "cloud", "Lambda", "EC2", "S3", "DynamoDB", "RDS", "ECS", "EKS", "CloudFormation", "CDK", "Terraform", "VPC", "IAM", "API Gateway", "SQS", "SNS", "Kinesis", "serverless", "infrastructure", "cost estimate", "DR plan", or any cloud topic.

Role 14: Data Engineer. Designs and implements data pipelines, ETL/ELT processes, data warehouses, data lakes, streaming architectures, schema design, data quality frameworks, and data infrastructure. Trigger for "data pipeline", "ETL", "ELT", "data warehouse", "data lake", "Spark", "Airflow", "dbt", "Kafka", "Kinesis", "Redshift", "BigQuery", "Snowflake", "Glue", "schema", "partitioning", "data model", "data quality", "CDC", "streaming", "data ingestion", "data catalog", "lineage", "lakehouse", "medallion", "bronze silver gold", or any data infrastructure task.

Role 15: Data Scientist. Performs EDA, statistical modeling, hypothesis testing, A/B experiment design, feature engineering, model selection, and produces analytical reports with reproducible evidence. Trigger for "data analysis", "EDA", "statistics", "hypothesis test", "A/B test", "correlation", "regression", "classification", "clustering", "feature engineering", "notebook", "visualization", "pandas", "scikit-learn", "p-value", "confidence interval", or any analytical task.

Role 11: Documenter. Owns ALL documentation: README, API reference, architecture docs, user guides, changelog, ADRs, inline doc standards, runbooks, onboarding guides, and data dictionaries. Trigger for "documentation", "README", "API docs", "changelog", "guide", "tutorial", "runbook", "docstring", "JSDoc", "onboarding", "wiki", "data dictionary", "tech writing", or any documentation task.

Role 4: Frontend Developer. Implements all client-side code: UI components, pages, routing, state management, API integration, form handling, accessibility (WCAG 2.1 AA), responsive design, animations, and client-side performance optimization. Trigger for "frontend", "UI", "UX", "component", "React", "Vue", "Angular", "Svelte", "Next.js", "Nuxt", "CSS", "Tailwind", "responsive", "accessibility", "a11y", "WCAG", "state management", "Redux", "Zustand", "Pinia", "client-side", "SPA", "SSR", "SSG", "browser", "DOM", "event handler", "form", "modal", or any UI/client task.

Role 6: Integration Tester. Writes integration tests, API contract tests, E2E tests, performance/load tests, and regression suites that validate cross-component interactions, full user workflows, and NFR compliance. Trigger for "integration test", "E2E", "end-to-end", "API test", "contract test", "performance test", "load test", "smoke test", "regression suite", "Playwright", "Cypress", "Postman", "k6", "Locust", "Gatling", "Artillery", "cross-service", or any multi-component testing task.

Role 16: ML Engineer. Productionizes ML models: training pipelines, feature stores, model serving, monitoring, A/B infrastructure, versioning, MLOps. Trigger for "ML pipeline", "model serving", "MLOps", "feature store", "model registry", "SageMaker", "MLflow", "TensorFlow Serving", "TorchServe", "Kubeflow", "model monitoring", "data drift", "retraining", "inference", "batch prediction", "real-time prediction", "embedding", "LLM integration", or any ML infra task.

Role 8: Product Manager. Owns product vision, user stories, prioritization, success metrics, and stakeholder alignment. Defines WHAT to build and WHY. Produces the Product Requirements Document (PRD). Trigger for "product", "user story", "PRD", "product requirements", "prioritization", "roadmap", "MVP", "feature", "persona", "value proposition", "OKR", "KPI", "success metric", "RICE", "MoSCoW", "backlog", "sprint planning", or any product strategy discussion.

Role 9: Program Manager. Owns strategic alignment, cross-project coordination, portfolio governance, resource allocation, organizational risk management, and executive stakeholder communication. Operates at the portfolio/program level above individual projects. Trigger for "program", "portfolio", "strategic alignment", "cross-project", "resource allocation", "governance", "OKR alignment", "roadmap coordination", "dependency across projects", "executive status", "RACI", or any organizational-level planning task.

Role 7: Requirements Analyst. Transforms product vision into precise, testable, traceable requirements specifications (SRS). Writes formal FRs, NFRs, acceptance criteria using Given/When/Then, manages requirements traceability, resolves ambiguities, and validates completeness. Trigger for "requirements", "SRS", "specification", "acceptance criteria", "Given When Then", "functional requirement", "non-functional", "traceability", "scope", "constraint", "assumption", "elicitation", "user need", "business rule", or any requirements engineering task.

Role 13: Security Engineer. Performs comprehensive security audit of ALL code, dependencies, configurations, IAM policies, and data flows. Owns OWASP compliance, dependency auditing, secrets scanning, threat modeling, and formal security verdicts. Trigger for "security", "vulnerability", "OWASP", "injection", "XSS", "CSRF", "auth", "encryption", "secrets", "CVE", "audit", "threat model", "IAM review", "penetration", "compliance", "GDPR", "SOC2", "HIPAA", or any security topic.

Role 1: System Engineer. Owns system-level architecture, component design, interface contracts, data modeling, technology selection, and Architecture Decision Records (ADRs). Produces the System Architecture Document (SAD) and High-Level Design (HLD). Produces the Implementation Plan. Activates on Phase 4 of the pipeline. Trigger for "architecture", "system design", "HLD", "SAD", "component diagram", "data flow", "interface contract", "ADR", "tech stack", "scalability design", "microservices", "monolith", "API design", "data model", "state machine", "dependency analysis", "layer architecture", "design review", or any system-level design question.

Role 5: Unit Tester. Writes comprehensive unit tests for ALL source code at the function/method level. Owns test strategy, achieves coverage targets, validates acceptance criteria with isolated tests, writes test doubles, maintains test quality. Trigger for "unit test", "test coverage", "mock", "stub", "spy", "fake", "fixture", "assertion", "TDD", "test case", "edge case", "boundary", "regression", "pytest", "jest", "vitest", "junit", "googletest", "catch2", "rspec", or any unit testing task.