ZipRecruiter

Log In

2

Internship Remote Recipe Developer Jobs in Minneapolis, MN

Sportsdigita

Junior Dev Ops

Edina, MN · On-site +1

$55 - $75.50/hr

You would be joining a small engineering team where the environment you are working in is the whole ... We already have modules and remote state in place; you'll add to them and help keep environments ...

Sportsdigita

Junior Dev Ops

Edina, MN · Remote

$54 - $74/hr

You would be joining a small engineering team where the environment you are working in is the whole ... We already have modules and remote state in place; you'll add to them and help keep environments ...

previous pagenext page

Showing results 21-40

All JobsRecipe Developer JobsInternship Remote Recipe Developer JobsInternship Remote Recipe Developer Jobs in Minneapolis, MN

Internship Remote Recipe Developer information

See Minneapolis, MN salary details

$12

$23

$41

How much do internship remote recipe developer jobs pay per hour?

As of Sep 5, 2026, the average hourly pay for internship remote recipe developer in Minneapolis, MN is $23.90, according to ZipRecruiter salary data. Most workers in this role earn between $19.33 and $25.34 per hour, depending on experience, location, and employer.

What is the difference between Internship Remote Recipe Developer vs Remote Food Content Writer?

AspectInternship Remote Recipe DeveloperRemote Food Content Writer
CredentialsCooking or culinary background, food safety knowledgeWriting, editing, culinary knowledge beneficial
Work EnvironmentDeveloping recipes, testing in kitchens, remote collaborationWriting articles, creating content, remote work
Industry UsageFood brands, culinary websites, recipe platformsFood blogs, magazines, digital media

The main difference is that an Internship Remote Recipe Developer focuses on creating and testing recipes, often requiring culinary skills, while a Remote Food Content Writer primarily produces written content about food topics. Both roles are remote and industry-related but serve different functions within the food media landscape.

How to get a job as an internship remote recipe developer?

To secure an internship as a remote recipe developer, candidates should have strong culinary skills, experience in recipe creation, and proficiency with digital tools like content management systems or social media platforms. Building a portfolio of tested recipes and applying through company websites or culinary internship programs can improve chances. Relevant certifications or food safety knowledge can also be advantageous.

What are popular job titles related to Internship Remote Recipe Developer jobs in Minneapolis, MN?

For Internship Remote Recipe Developer jobs in Minneapolis, MN, the most frequently searched job titles are:

What job categories do people searching Internship Remote Recipe Developer jobs in Minneapolis, MN look for?

The top searched job categories for Internship Remote Recipe Developer jobs in Minneapolis, MN are:

What cities near Minneapolis, MN are hiring for Internship Remote Recipe Developer jobs?

Cities near Minneapolis, MN with the most Internship Remote Recipe Developer job openings:

Internship Remote Recipe Developer jobs near you
Infographic showing various Internship Remote Recipe Developer job openings in Minneapolis, MN as of July 2026, with employment types broken down into 82% Full Time, 6% Part Time, 1% Temporary, and 11% Contract. Highlights an 82% Physical, 5% Hybrid, and 13% Remote job distribution, with an average salary of $49,706 per year, or $23.9 per hour.

Junior Dev Ops

Sportsdigita

Edina, MN • On-site, Remote

$55 - $75.50/hr

Full-time

Posted 6 days ago

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.
  • 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

Apply