DevOps Specialist

About R'Dash:

Key Responsibilities:

• Design, build, and maintain our multi-cloud infrastructure using Terraform and Infrastructure as Code (IaC) principles.
• Manage and optimize Kubernetes clusters for high availability and performance.
• Build and maintain CI/CD pipelines using GitHub Actions for Django, FastAPI, and React/TypeScript applications.
• Deploy, configure, and maintain open-source tools like n8n, Metabase, Grafana, and Airbyte.
• Instrument applications with Prometheus, build Grafana dashboards, and set up actionable alerts.
• Debug complex issues across servers, Kubernetes networking, and database performance bottlenecks.
• Write Python, Go, or TypeScript code for automation and custom integrations.
• Optimize Postgres and MongoDB databases for performance and reliability.
• Research, evaluate, and deploy new tools that enhance engineering productivity.

Qualifications:

• Strong Linux fundamentals and familiarity with system internals.
• Deep networking knowledge across Linux, Kubernetes, and cloud networking.
• Proven Kubernetes expertise managing production workloads.
• Experience with AWS, GCP, or Azure (Azure preferred).
• Strong database knowledge (Postgres/MySQL) including tuning, backups, and replication.
• CI/CD experience, particularly with GitHub Actions.
• Solid understanding of logging, monitoring, and observability.
• Experience with Terraform or similar IaC tools.
• Proficiency in Python or TypeScript.
• Exceptional debugging skills for distributed systems.

Nice-to-Haves (Highly Impressive):

• GitOps experience (ArgoCD, Flux).
• cert-manager and SSL/TLS certificate management.
• Experience with ISO 27001 or SOC2 compliance.
• Disaster Recovery setups across regions or zones.
• Postgres Change Data Capture (CDC) implementation.
• Experience with OLAP databases.

Tech Stack:

Deal-Breakers:

• You’ve only learned these technologies from tutorials.
• You prefer strictly defined, repetitive tasks.
• You need detailed instructions rather than exploring solutions independently.
• You’ve never debugged a production outage.
• You’re uncomfortable writing or debugging code.

What We’re Really Looking For: