Infrastructure Systems Operations Engineer Junior to Mid

About the role

This position focuses on the daily operation and maintenance of ZIGChain's core infrastructure, which includes Linux servers, AWS cloud services, and blockchain nodes. The engineer will be responsible for routine administration tasks, ensuring services and networking function correctly, and proactively monitoring system health. A key aspect of the role involves troubleshooting issues across these environments to maintain smooth operations.

The role involves contributing to infrastructure-as-code initiatives, specifically using Terraform, where the engineer will gradually take on more ownership of configurations. Support for blockchain node operations within the ZIGChain ecosystem is also a core responsibility. The engineer will automate recurring tasks and diagnostics through scripting, aiming to improve efficiency and system reliability.

Success in this role means ensuring the infrastructure remains secure, well-maintained, and consistently operational. This includes adhering to best practices for credential and access hygiene, such as proper SSH key handling and implementing least-privilege IAM policies. The engineer will also contribute to keeping systems patched and secure, playing a direct part in the overall stability and integrity of ZIGChain's technical environment.

The salary for this position ranges from $40,000 to $50,000.

Skills that matter here

• Linux: This role requires fluency in Linux administration, including CLI operations, systemd management, package handling, log analysis, and troubleshooting services and networking.
• AWS: The engineer will operate and debug core AWS services like EC2, VPC, IAM, S3, CloudWatch, and load balancers.
• Terraform: The position involves authoring and applying Terraform configurations, understanding state, and the plan/apply cycle for infrastructure-as-code.
• Bash: Shell scripting with Bash is essential for automating tasks and performing diagnostics within the infrastructure.
• Networking: A foundational understanding of networking concepts like TCP/IP, DNS, SSH, firewalls, and security groups is necessary for this role.
• Git: Comfort with the everyday Git workflow, including branching, committing, and pull requests, is required for managing code and configurations.

Who this role suits

• Someone who enjoys hands-on operational work, focusing on the day-to-day maintenance and monitoring of systems.
• An individual who is methodical about security practices, including credential management and access control.
• A person who is keen to automate routine tasks and improve system efficiency through scripting.
• A candidate who understands the importance of infrastructure-as-code and is willing to contribute to Terraform configurations.

From the employer

What You'll Do

• Operate and maintain our Linux, AWS, and blockchain-node infrastructure on a day-to-day basis.
• Own routine administration, monitoring, and troubleshooting of services and networking.
• Contribute to our infrastructure-as-code work with Terraform, growing your ownership over time.
• Support blockchain node operations across our ecosystem.
• Automate recurring tasks and diagnostics through scripting.
• Help keep our systems secure, patched, and running smoothly.

Requirements

Must-Haves:

• Linux administration: CLI fluency, systemd, package management, log analysis, and troubleshooting of services and networking.
• Shell scripting (Bash) for automation and diagnostics.
• Working knowledge of core AWS services: EC2, VPC, IAM, S3, CloudWatch, and load balancers (ELB/ALB). You should be able to operate and debug them, not necessarily architect them.
• Terraform at a working level: you have authored and applied configurations and understand state and the plan/apply cycle. Prior Terraform experience on any cloud is fine, it doesn't need to be AWS.
• Networking fundamentals: TCP/IP, DNS, SSH, firewalls and security groups.
• Git: comfortable with the everyday branch/commit/PR workflow.
• Sound credential and access hygiene: proper SSH key handling, least-privilege IAM, keeping secrets out of code and repositories, and keeping systems patched.