Skill-Profil

Task Queues

Celery, Dramatiq, BullMQ, Hangfire: deferred tasks, retry, scheduling

Backend Development Background Jobs & Task Queues

Rollen

11

wo dieser Skill vorkommt

Stufen

5

strukturierter Entwicklungspfad

Pflichtanforderungen

30

die anderen 25 optional

Domäne

Backend Development

skills.group

Background Jobs & Task Queues

Zuletzt aktualisiert

17.3.2026

Verwendung

Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.

Was wird auf jedem Level erwartet

Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.

Rolle Pflicht Beschreibung
AI Product Engineer Uses Task Queues at a basic level in LangChain/LlamaIndex. Performs simple tasks using ready-made templates. Understands basic concepts and follows team practices.
Backend Developer (Go) Understands task queues for Go: basic worker patterns, channel-based job processing. Uses simple queue implementations.
Backend Developer (Node.js) Pflicht Uses Task Queues at a basic level. Performs simple tasks following established templates. Understands basic concepts and follows team practices.
Backend Developer (PHP) Pflicht Uses Task Queues at a basic level. Performs simple tasks using ready-made templates. Understands basic concepts and follows team practices.
Backend Developer (Python) Pflicht Understands background task concepts. Creates simple Celery tasks. Uses delay() and apply_async(). Understands the difference between synchronous and asynchronous processing.
Computer Vision Engineer Uses Task Queues at a basic level in PyTorch/OpenCV. Performs simple tasks using ready-made templates. Understands basic concepts and follows team practices.
Data Engineer Uses Task Queues at a basic level in Airflow/dbt. Performs simple tasks using established templates. Understands basic concepts and follows team practices.
LLM Engineer Uses Task Queues at basic level in transformers/vLLM. Performs simple tasks using ready templates. Understands basic concepts and follows team practices.
ML Engineer Understands the fundamentals of Task Queues. Applies basic practices in daily work. Follows recommendations from the team and documentation.
MLOps Engineer Uses Task Queues at a basic level in Kubeflow/MLflow. Performs simple tasks using ready-made templates. Understands basic concepts and follows team practices.
NLP Engineer Knows task queue basics: Celery, RabbitMQ, Redis Queue. Uses queues for async NLP processing: batch text processing, background model inference. Understands producer/consumer pattern.
Rolle Pflicht Beschreibung
AI Product Engineer Independently implements tasks with Task Queues in LangChain/LlamaIndex. Understands internals and optimizes performance. Writes tests using eval frameworks.
Backend Developer (Go) Implements task queues: Asynq for background jobs, priority queues, scheduled tasks. Configures retry policies.
Backend Developer (Node.js) Pflicht Independently implements tasks with Task Queues. Understands internals and optimizes performance. Writes tests.
Backend Developer (PHP) Pflicht Independently implements Task Queue tasks. Understands internals and optimizes performance. Writes tests.
Backend Developer (Python) Pflicht Configures Celery with different brokers (Redis, RabbitMQ). Uses chains, groups, chords for workflows. Configures retry with exponential backoff. Monitors tasks via Flower. Handles errors and dead letter queues.
Computer Vision Engineer Independently implements tasks with Task Queues in PyTorch/OpenCV. Understands internals and optimizes performance. Writes tests using evaluation metrics.
Data Engineer Independently implements tasks with Task Queues in Airflow/dbt. Understands internals and optimizes performance. Writes tests with great_expectations.
LLM Engineer Independently implements tasks with Task Queues in transformers/vLLM. Understands internals and optimizes performance. Writes tests using eval harness.
ML Engineer Uses Celery for ML task orchestration: training, batch inference, feature computation. Configures priorities and retry policies. Monitors tasks through Flower.
MLOps Engineer Independently implements Task Queue tasks in Kubeflow/MLflow. Understands internals and optimizes performance. Writes tests using model monitoring.
NLP Engineer Independently designs asynchronous NLP pipelines via queues: priority queues for different NLP tasks, retry strategies, dead letter queue. Monitors execution via Flower/dashboard.
Rolle Pflicht Beschreibung
AI Product Engineer Pflicht Designs task queue architectures for AI product workloads: async model inference, batch processing pipelines, and priority-based job scheduling with Celery or BullMQ. Optimizes queue throughput for user-facing latency requirements.
Backend Developer (Go) Designs distributed task processing: multi-worker architectures, rate limiting, idempotency patterns.
Backend Developer (Node.js) Pflicht Designs background job processing: BullMQ for task queues, priority queues, scheduled jobs, rate limiting. Configures retry policies with exponential backoff. Monitors queue health via Bull Board.
Backend Developer (PHP) Pflicht Designs queue architecture: prioritization, rate limiting, circuit breaker for external services. Ensures exactly-once processing through idempotency keys. Monitors throughput, latency, failure rate.
Backend Developer (Python) Pflicht Designs background processing architecture. Optimizes concurrency and prefetch. Configures priority queues. Implements idempotent tasks. Migrates between queues without task loss.
Computer Vision Engineer Pflicht Designs task queue systems for computer vision pipelines: distributed image/video processing, GPU-aware job scheduling, and result aggregation. Implements retry strategies and dead letter queues for handling processing failures.
Data Engineer Pflicht Designs asynchronous processing through Celery/RQ: background tasks for data processing, priority queues for different SLAs, dead letter queues for failed tasks. Configures retry policies and monitoring.
LLM Engineer Pflicht Designs Task Queue solutions for production systems. Optimizes performance and scalability. Chooses between alternative approaches. Mentors the team.
ML Engineer Designs task queue architecture for ML workloads. Optimizes worker pools for CPU/GPU tasks. Configures autoscaling workers based on queue depth.
MLOps Engineer Pflicht Implements task queues for MLOps processes: Celery for async model training, batch prediction processing, and experiment report generation. Configures task prioritization, retry policies for long-running training jobs, and dead-letter queues for handling ML pipeline failures.
NLP Engineer Designs production task queue infrastructure for NLP: distributed processing, fair scheduling between NLP models, backpressure handling for high-load text processing.
Rolle Pflicht Beschreibung
AI Product Engineer Pflicht Defines task queue strategy for AI products: selects between Celery, SQS, and cloud-native solutions based on scale requirements. Establishes patterns for idempotent task execution, monitoring, and autoscaling workers by queue depth.
Backend Developer (Go) Defines task queue standards: job processing guidelines, monitoring, error handling policies.
Backend Developer (Node.js) Pflicht Defines queue strategy: BullMQ for Node.js jobs vs Kafka for cross-service events, dead letter handling, idempotency standards. Implements monitoring and alerting for queue processing.
Backend Developer (PHP) Pflicht Defines background processing standards: job class structure, error handling, retry policies, monitoring. Chooses between different queue backends based on workload.
Backend Developer (Python) Pflicht Designs background processing strategy for the platform. Chooses between Celery, Dramatiq, arq for different cases. Designs distributed task processing. Implements monitoring and observability for tasks.
Computer Vision Engineer Pflicht Defines task queue architecture for large-scale vision processing: multi-stage pipelines with fan-out/fan-in patterns, resource-aware scheduling across GPU clusters, and SLA-driven priority management for real-time vs batch workloads.
Data Engineer Pflicht Defines task orchestration strategy: Celery for micro-tasks vs Airflow for DAGs, choosing between push/pull models. Implements idempotency standards and queue monitoring.
LLM Engineer Pflicht Defines Task Queues architectural decisions at product level. Establishes standards. Conducts design reviews and defines technical roadmap.
ML Engineer Defines async ML processing strategy. Evaluates Celery vs Dramatiq vs Ray for ML workloads. Designs task orchestration for ML platform.
MLOps Engineer Pflicht Defines the async processing architecture for the MLOps team: Celery/RQ for lightweight tasks, Kubeflow Pipelines for heavy training workflows. Standardizes retry and backoff patterns for GPU training jobs, configures queue monitoring and alerting for stuck ML tasks via Flower and Prometheus.
NLP Engineer Defines task queue standards for the NLP team. Establishes best practices for async processing, monitoring, and scaling strategies for NLP workloads.
Rolle Pflicht Beschreibung
AI Product Engineer Pflicht Defines enterprise task queue strategy across AI products: evaluates emerging technologies (Temporal, Inngest), establishes reliability standards for distributed job processing, and designs reference architectures for event-driven AI workflows.
Backend Developer (Go) Shapes task processing strategy: platform job infrastructure, distributed processing governance.
Backend Developer (Node.js) Pflicht Designs distributed task processing: BullMQ for lightweight jobs, Kafka for heavy stream processing, temporal for long-running workflows. Defines orchestration patterns and SLA.
Backend Developer (PHP) Pflicht Designs async processing platform: scheduling, workflow orchestration, distributed job processing. Ensures scalability and fault tolerance at organizational level.
Backend Developer (Python) Pflicht Defines company async processing strategy. Designs event-driven architecture. Evaluates managed services vs self-hosted. Establishes task processing standards.
Computer Vision Engineer Pflicht Defines company-wide task queue strategy for compute-intensive workloads: establishes standards for distributed job orchestration, evaluates workflow engines (Temporal, Prefect) for vision pipelines, and designs cost-optimized processing architectures.
Data Engineer Pflicht Designs distributed processing architecture: task queues for near-real-time vs batch schedulers, hybrid approaches. Defines SLA and capacity planning for different priority levels.
LLM Engineer Pflicht Defines Task Queues strategy at organizational level. Evaluates new technologies and approaches. Establishes enterprise standards and reference architectures.
ML Engineer Defines task processing strategy for enterprise ML. Designs distributed job scheduling for ML platform. Evaluates serverless vs dedicated workers.
MLOps Engineer Pflicht Designs the ML task orchestration strategy at the platform level: choosing between Celery, Kubeflow Pipelines, and Argo Workflows for different workload types. Defines GPU resource prioritization architecture between teams, fairness scheduling policies, and automatic worker pool scaling for ML computations.
NLP Engineer Shapes enterprise async processing strategy for the NLP platform. Defines event-driven architecture standards, message bus, and task orchestration at organizational level.

Community

👁 Beobachten ✏️ Aenderung vorschlagen Anmelden, um Aenderungen vorzuschlagen
📋 Vorschlaege
Noch keine Vorschlaege fuer Task Queues
Kommentare werden geladen...