Junior Dev Ops

Overview DIGIDECK is the presentation platform behind sales teams at professional sports franchises, arenas, live entertainment venues, and destination marketing organizations. When one of our customers walks into a room to close a seven-figure sponsorship, they are presenting on our platform, live, often on someone else's WiFi, with no room for a loading spinner. That makes our infrastructure the thing standing between a rep and a closed deal. You would be joining a small engineering team where the environment you are working in is the whole environment, not one service inside a hundred. Your work is visible and your decisions stick. What You Will Own These are the areas you'd start contributing to in your first few months, with support from the team. AWS infrastructure. Help maintain our ECS and EC2 workloads across development, staging, and production — clusters, services, tasks, and the compute underneath. Work with the networking layer (VPC, subnets, security groups, load balancers) and the delivery layer (CloudFront, S3, Route 53, ACM). Infrastructure as code. Write and extend Terraform. We already have modules and remote state in place; you'll add to them and help keep environments consistent rather than snowflaked. Automation. Replace recurring manual work with Python and Bash. Staging database refreshes, certificate renewals, environment syncs between AWS accounts — the tasks that eat an afternoon every month are the ones we want automated. CI/CD. Maintain and troubleshoot our Bitbucket Pipelines workflows and self-hosted runners. Monitoring. Build and extend Grafana dashboards, tune alerting, and investigate performance and availability issues. A meaningful part of this job is noticing something is wrong before a customer tells us. Production support. Join the on-call rotation once you're ramped, help troubleshoot ECS agent issues, networking problems, and deployment failures, and write the follow-up — including what we're changing so it doesn't recur. Documentation. Keep infrastructure and runbooks current in Confluence. On a small team the runbook you write matters as much as the fix you ship. What You Will Grow Into Not day-one expectations. This is where the role goes. Databases: deeper support of RDS and MongoDB Atlas, including automated environment synchronization and refreshes Security and access: IAM, KMS, Secrets Manager, and identity management through JumpCloud and SSO integrations SOC 2 Type II: supporting compliance activities, maintaining audit evidence, and monitoring controls Cost optimization: autoscaling policies, scheduled scale-down of non-production environments, and finding AWS spend we don't need Kubernetes: we don't run EKS today. If and when we do, you'd help build it — which is a rare thing to get to do at this stage of a career Our stack You will not have used all of this. We expect you to learn most of it here. Cloud AWS — ECS, EC2, VPC, ALB, CloudFront, Route 53, S3, RDS, ElastiCache/Redis, ECR, Lambda, SSM, IAM IaC Terraform (modules, remote state), CloudFormation Containers & CI/CD Docker, Bitbucket Pipelines, self-hosted runners Databases Amazon RDS, MongoDB Atlas, Redis Security IAM, KMS, Secrets Manager, ACM, JumpCloud, SSO, SOC 2 Monitoring Grafana, AWS monitoring and logging Scripting Python, Bash, Linux shell Tooling Git, Bitbucket, Jira, Confluence Requirements You'll need: 1–2 years of hands-on experience with AWS, or equivalent depth through internships, coursework, or personal projects you can walk us through in detail Comfort in a Linux shell, and enough Python or Bash to automate something end to end Working knowledge of CI/CD — what a pipeline does and how to read it when it breaks Exposure to Terraform or another IaC tool, even if only in a learning context Genuine curiosity about how systems fail. The best infrastructure engineers are the ones who can't leave a weird log line alone. Clear written communication Legal authorization to work in the United States Nice to have, not required: A CS degree or equivalent formal background — we care what you can do, not where you learned it Docker in a real environment Any exposure to RDS, MongoDB, or Redis Experience with a system that had real users and real uptime expectations Kubernetes at any depth