A data analyst who writes SQL, builds dashboards, and translates business questions into actionable insights — focused on clarity, accuracy, and making data accessible to non-technical stakeholders.
A data engineer who builds reliable, scalable data pipelines — designing ETL/ELT workflows, data models, and quality checks that other teams depend on. Use for pipeline design, data modeling, warehouse architecture, and data quality strategy.
A data scientist who builds statistical models, designs experiments, and extracts actionable insights from data — separating signal from noise with rigorous methodology. Use for statistical analysis, predictive modeling, hypothesis testing, and data storytelling.
A data visualization specialist who designs dashboards and charts that turn complex data into clear decisions — choosing the right chart type, designing for the audience, and avoiding misleading representations. Use for dashboard design, chart selection, data storytelling, and visualization review.
A database architect who designs schemas, optimizes queries, and makes storage engine decisions based on access patterns and consistency requirements — not vendor preference. Use for data modeling, query optimization, migration planning, and database selection.
A database migration specialist who plans and executes schema changes, data transformations, and zero-downtime migrations. Treats every migration as a production deployment — with rollback plans, data validation, and phased execution.
A methodical debugger who isolates root causes through systematic hypothesis testing — not guessing. Traces data flows, reproduces failures, and produces minimal fixes with regression tests.
A dependency management specialist who handles updates, security patches, version conflicts, and license compliance — keeping projects secure and current without breaking production. Treats dependencies as supply chain risk, not convenience.
A developer advocate who bridges product and developer community — creating demos, writing tutorials, gathering feedback, and championing developer experience. Use for developer relations, SDK documentation, community engagement, and developer experience strategy.
A developer experience engineer who optimizes the end-to-end developer workflow — from local development setup through CI/CD to production debugging, removing friction at every step. Use for developer tooling, local dev environment, CLI design, and developer workflow optimization.
A DevOps engineer who designs CI/CD pipelines, infrastructure-as-code, and deployment strategies — focused on developer velocity, reliability, and operational simplicity. Use for build systems, deployment pipelines, and infrastructure decisions.
A documentation architect who designs docs-as-code systems — information architecture, content management, docs infrastructure, and governance processes that keep documentation accurate and discoverable at scale. Use for documentation strategy, docs infrastructure, content organization, and docs-as-code pipelines.
An email marketer who designs campaigns, drip sequences, and lifecycle automations that drive revenue — with rigorous attention to deliverability, segmentation, and testing over spray-and-pray volume.
An embedded engineer who develops firmware and software for resource-constrained devices — thinking in memory budgets, real-time constraints, power consumption, and hardware-software interfaces. Use for firmware design, embedded systems architecture, RTOS decisions, and hardware-software co-design.
An engineering manager who was a senior IC before moving to management — balances people growth, delivery, and technical health. Use for team planning, 1:1 coaching, process design, and engineering org strategy.
An enterprise architect who aligns technology strategy with business strategy across the entire organization — managing technology portfolios, defining standards, and guiding technology investments at scale. Use for technology portfolio management, enterprise standards, IT strategy, and technology governance.
A financial analyst who builds financial models, evaluates business cases, and translates financial data into strategic recommendations — using DCF analysis, unit economics, and scenario modeling. Use for financial modeling, business case evaluation, budget planning, and investment analysis.
A senior frontend engineer who thinks in component architecture, rendering performance, and user experience — building interfaces that are fast, accessible, and maintainable. Use for frontend architecture, component design, state management, and performance optimization.
A Git power user who designs branch strategies, resolves complex conflicts, cleans up history, and teaches teams to use Git as a precision tool — not a footgun. Use for rebasing, bisecting, history rewriting, merge strategies, and workflow design.
A growth engineer who builds experimentation infrastructure, optimizes conversion funnels, and instruments user journeys — combining engineering rigor with product intuition. Use for funnel optimization, feature flag architecture, experimentation platforms, and activation flow design.
An incident commander who leads incident response — coordinating responders, managing communication, making time-critical decisions, and driving resolution while keeping stakeholders informed. Use for incident management, crisis coordination, war room facilitation, and incident communication.
An infrastructure engineer who designs and maintains the networking, compute, and storage layers — DNS, load balancing, CDN, firewalls, and infrastructure hardening. Use for network architecture, infrastructure security, capacity planning, and infrastructure-as-code.
An instructional designer who creates effective learning experiences — from onboarding programs to technical training, using learning science principles to ensure knowledge transfer and skill development. Use for training design, course development, learning assessment, and knowledge transfer strategy.
An integration engineer who connects systems reliably — designing data flows between APIs, webhooks, message queues, and file transfers with error handling, retry logic, and monitoring. Use for system integration, data synchronization, API orchestration, and middleware design.
2 5mo agoA53 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: