3

Remote Entry Level Instrumentation & Controls Engineer Jobs in Minneapolis, MN

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

Analyzing processes, controls, and tools to identify opportunities for ServiceNow configuration and ... Bachelor's degree in Computer Science, Information Systems, Cyber Security, Engineering ...

Showing results 21-40

Remote Entry Level Instrumentation Controls Engineer information

See Minneapolis, MN salary details

$29

$56

$85

How much do remote entry level instrumentation & controls engineer jobs pay per hour?

As of Sep 13, 2026, the average hourly pay for remote entry level instrumentation & controls engineer in Minneapolis, MN is $56.92, according to ZipRecruiter salary data. Most workers in this role earn between $44.42 and $64.71 per hour, depending on experience, location, and employer.

What is a remote entry level instrumentation & controls engineer?

Remote Entry Level Instrumentation & Controls Engineers are professionals who work from off-site locations to assist in designing, developing, and maintaining systems that monitor and control machinery or processes in industries such as manufacturing, energy, or utilities. Their work typically involves programming, configuring instrumentation devices, troubleshooting, and supporting control systems under the guidance of senior engineers. Entry level roles focus on learning industry standards, supporting project teams, and gaining hands-on experience with instrumentation hardware and software. Working remotely, they use digital collaboration tools to communicate with on-site staff and complete project tasks.

What are the key skills and qualifications needed to thrive as a remote entry level instrumentation & controls engineer?

To thrive as a Remote Entry Level Instrumentation & Controls Engineer, you need a foundational knowledge of electrical engineering principles, instrumentation systems, and control theory, typically supported by a relevant engineering degree. Familiarity with industry-standard software such as AutoCAD, PLC programming platforms (e.g., Rockwell, Siemens), and SCADA systems is essential, and certifications like EIT (Engineer-in-Training) can be advantageous. Strong problem-solving skills, attention to detail, and effective remote communication are key soft skills that distinguish successful candidates. These skills and qualifications ensure accurate system design, efficient troubleshooting, and effective collaboration with multidisciplinary teams in remote work environments.

What are some common challenges faced by remote entry level instrumentation & controls engineers, and how can they be overcome?

Remote entry level Instrumentation & Controls Engineers often face challenges such as limited hands-on access to equipment, coordinating with on-site teams, and managing effective communication across time zones. To overcome these, it's helpful to leverage virtual simulation tools, participate actively in video meetings, and maintain clear documentation of your work. Building strong relationships with senior engineers and local technicians can also help you gain practical insights and support when troubleshooting issues remotely.

What are popular job titles related to Remote Entry Level Instrumentation & Controls Engineer jobs in Minneapolis, MN?

For Remote Entry Level Instrumentation & Controls Engineer jobs in Minneapolis, MN, the most frequently searched job titles are:

What job categories do people searching Remote Entry Level Instrumentation & Controls Engineer jobs in Minneapolis, MN look for?

The top searched job categories for Remote Entry Level Instrumentation & Controls Engineer jobs in Minneapolis, MN are:

Junior Dev Ops

Edina, MN โ€ข On-site, Remote

Sportsdigita
51 - 200 employees

$55 - $75.50/hr

Full-time

Posted 13 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