What are the responsibilities and job description for the Cloud Architect / DevOps Engineer position at Innovated Studios?
Innovated Studios builds high-traffic, high-expectation interactive systems for world-class brands. That means cloud architecture, on-prem edge deployments, media pipelines, and production-grade observability, all working together.
What you’ll do
- Design and own cloud architecture for multi-tenant platforms, real-time services, and event-driven systems.
- Build deployment systems that are boring in production: CI/CD, release automation, safe rollouts, rollback plans, and environment parity.
- Operationalize “edge cloud” deployments when needed, including secure networking, device provisioning, and reliable updates.
- Run the reliability playbook: SLOs, alerting, on-call hygiene, incident response, postmortems, capacity planning, and cost control.
- Create opinionated platform primitives (templates, Terraform modules, Helm charts, pipelines) so teams ship faster with fewer mistakes.
- Harden security by default: secrets management, IAM, least privilege, network segmentation, audits, and compliance-friendly logging.
- Make observability actually usable: traces, logs, metrics, dashboards, and alert tuning that engineers trust.
- Partner closely with product and engineering to turn “it works on my machine” into repeatable, scalable delivery.
You’re a great fit if you…
Have 5 years in DevOps / SRE / Cloud Architecture (or equivalent battle scars and proof).
Have shipped systems with real uptime requirements and know what breaks first.
Can design across compute, networking, security, and data without creating a maze.
Are comfortable jumping between deep technical work and clear communication with non-infra stakeholders.
Think in automation and primitives, not one-off fixes.
- Care about cost as a first-class constraint (FinOps mindset).
Required skills
- Cloud architecture (Azure preferred, AWS/GCP welcome): networking, IAM, load balancing, autoscaling, managed databases, queues.
- Infrastructure as Code: Terraform (preferred), Pulumi, Bicep, or equivalent.
- Containers and orchestration: Docker, Kubernetes (AKS/EKS/GKE) and/or serverless container platforms.
- CI/CD: GitHub Actions, Azure DevOps, GitLab CI, or similar, with strong release discipline.
- Observability stack: OpenTelemetry, Prometheus, Grafana, Loki, Sentry, ELK, or equivalent.
- Security fundamentals: secrets management (Vault/Key Vault), RBAC, network policies, secure SDLC.
- Systems debugging: Linux, networking, performance bottlenecks, log forensics.
Strong pluses (depending on project)
- Media real-time systems: WebRTC, RTSP, FFmpeg, MediaMTX, GStreamer, CDN strategies, streaming reliability.
- Event-driven architectures: Service Bus/Kafka/RabbitMQ, retries, DLQs, idempotency, backpressure.
- GPU workloads: CUDA environments, model serving, batching, throughput tuning, containerizing inference.
- Edge deployments: device fleet management, remote updates, offline-first patterns, secure tunnels/VPNs.
What success looks like (first 60–90 days)
- You’ve stabilized and standardized our deployment patterns across environments.
- We have clearer SLOs, better dashboards, fewer noisy alerts, and faster incident resolution.
- Teams are shipping faster because the platform “just works.”
- Costs are more predictable, and performance is measurably improved.
How we work
Small teams, high ownership, minimal bureaucracy.
- We value speed, but never at the expense of reliability and security.
- We ship, we measure, we iterate.