Junior Dev Ops
Edina, MN · On-site +1
$55 - $75.50/hr
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.
Junior Dev Ops
Edina, MN · On-site +1
$55 - $75.50/hr
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.
Remote Splunk information
What is a Remote Splunk?
A Remote Splunk job involves working with Splunk, a data analysis and monitoring platform, from a remote location. Responsibilities typically include configuring, managing, and troubleshooting Splunk environments, creating dashboards, and analyzing log data to identify security or operational issues. These roles are common in cybersecurity, IT operations, and data analytics. Remote Splunk professionals need expertise in Splunk software, data ingestion, scripting, and sometimes cloud platforms.
What does a typical workday look like for someone in a Remote Splunk role?
In a Remote Splunk role, your day typically involves monitoring and analyzing log data to detect security incidents, creating and optimizing Splunk queries, building dashboards, and collaborating with IT or security teams to troubleshoot issues. Most tasks are performed independently from your home office, but you’ll often participate in virtual meetings to review findings, implement solutions, and support ongoing projects. You may also spend time documenting processes, providing input on best practices, and staying updated on new Splunk features or security trends. This remote structure allows for flexibility while remaining highly connected to team goals and incident response efforts.
What are the key skills and qualifications needed to thrive in the Remote Splunk position, and why are they important?
To excel as a Remote Splunk professional, you need strong analytical skills, experience with Splunk or SIEM tools, and a background in IT, cybersecurity, or systems administration. Familiarity with Splunk Enterprise, Splunk Cloud, SPL (Search Processing Language), and relevant certifications like Splunk Certified Power User or Administrator is highly beneficial. Excellent problem-solving abilities, attention to detail, and effective communication are key soft skills for this role. These competencies help ensure the efficient detection, analysis, and mitigation of security incidents while facilitating effective teamwork in a remote environment.
What are popular job titles related to Remote Splunk jobs in Minnesota?
For Remote Splunk jobs in Minnesota, the most frequently searched job titles are:
What job categories do people searching Remote Splunk jobs in Minnesota look for?
The top searched job categories for Remote Splunk jobs in Minnesota are:
What cities in Minnesota are hiring for Remote Splunk jobs?
Cities in Minnesota with the most Remote Splunk job openings:
Key responsibilities
Help maintain AWS infrastructure, including ECS and EC2 workloads, networking, and delivery layers.
Write and extend Terraform modules, and automate recurring manual tasks using Python and Bash.
Maintain and troubleshoot CI/CD workflows, build and extend monitoring dashboards, and support production issues.
Job description
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.
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:
Nice to have, not required:
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
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
About sportsdigita
Sourced by ZipRecruiter
Company size
51 - 200 Employees
Headquarters location
Edina, MN, US
Year founded
2011