DevOps Engineer

Architect and OperatorMyota  ·  Blue Bell, PA or Remote  ·  Full-time

About the role

This role owns the platform end to end. You design and build the infrastructure that runs our cyberstorage platform, and you run it in production. We do not hand the architecture from the people who draw it to the people who keep it alive, because the engineer who operates a system should be the one with the authority to shape it. You design what you run, and you run what you design.

That ownership is the point of the role, and the feedback from living with your own decisions is what keeps the architecture honest.

The defining challenge is portability. Our storage engine, Cortex, does not run in one place. It stands up on AWS today, and it has to stand up the same way on Akamai, Azure, Google Cloud, and inside a customer's own data center. You will own the infrastructure-as-code and the deployment model that makes one architecture deploy consistently across all of them, without a separate hand-built version per environment.

If you have ever been handed “now make it run on the customer's infrastructure too” and answered with a clean, repeatable system instead of a fork, this is your kind of problem.

What you will do

• Design and build
• Own cloud infrastructure end to end: design it, implement it as code, and maintain it, available and secure by default.
• Build the deployment model that provisions Cortex identically across AWS, Akamai, Azure, GCP, and on-prem, with no provider assumption baked into the core.
• Provision the storage backends that hold shards, across object storage from multiple providers and on-prem, and the multi-instance, load-balanced gateway that keeps the S3 endpoint serving through the loss of a node or a region.
• Stand up the CI/CD that builds, tests, deploys, and reports on our products.
• Operate
• Run the platform in production: monitoring, alerting, capacity, and cost optimization, while keeping it highly available and secure.
• Find and fix issues alongside the teams that own the code, on the timeline each issue demands.
• Keep every environment patched, hardened, and audited.
• Onboard customers
• Provision customer environments and help configure their storage backends and single sign-on.
• Secure
• Patch, harden infrastructure, scan code, and support penetration testing.
• Security is what we sell, so it is also the bar for the infrastructure underneath it.
• Support the business
• Help with technical reviews, proofs of concept, and scoping alongside the sales team.
• Run performance and load testing on infrastructure that reflects real conditions.
• Establish how engineering works day to day: Agile workflows in Jira, code reviews, QA, and a release process.

What you bring

• These are the core skills for the role.
• We go deeper on any of them during the interview.
• AWS as the primary cloud: compute, storage, networking, identity, serverless, and managed data services.
• Container orchestration: Kubernetes and Docker.
• Managed Kubernetes: AWS EKS, Azure AKS, or Google GKE.
• Helm for package management.
• Linux administration.
• Single sign-on with customer identity providers over SAML and OIDC.
• Image-build tooling such as Packer.
• Bash for automation and scripting.
• Observability: log aggregation, monitoring, and alerting with tooling such as Grafana and New Relic.
• Communication that holds up under pressure.
• You work across engineers, project managers, and executives, and you are the person who explains plainly what broke and what you did about it.
• Nice to have
• Azure (identity, compute, storage, M365).
• Object storage across multiple providers, cloud and self-hosted.
• CI/CD tooling such as Circle
• CI.
• Atlassian (Jira, Bitbucket, Confluence).
• Ansible for provisioning and automation.
• VPN tooling such as Wire
• Guard.
• Node.js
• Infrastructure as code with Terraform and Terragrunt.
• Go
• PostgreSQL
• Backup platforms that integrate with Myota, such as Veeam.
• Who does well here
• You work well when the deadline is tight and the path is not fully drawn, and you stay easy to work with under that pressure.
• You are proactive: you surface the problem and bring the fix, rather than waiting for the assignment.
• You care that what you built is still understandable by the next engineer, in the code, six months from now.

About MyotaMyota is a cybersecurity company and pioneer in the emerging cyberstorage category, that works at the storage layer to make security intrinsic to the data at write time. Myota's Shard and Spread™ technology immediately encrypts each file and uses cryptographic secret sharing to shard the data, metadata, and encryption keys spreading the resulting bits of data across multiple storage repositories.

Advanced mathematical techniques make it computationally impossible for attackers to reconstitute sharded data while at the same time allowing data owners to instantly and completely reconstruct their data even if fragments are lost or unavailable.

Unlike other cyberstorage solutions that simply apply typical cybersecurity approaches at the storage layer, Myota makes security intrinsic to the data at the time it is written, protecting the data itself rather than attempting to prevent access after data is created and copied. Myota offers resiliency without redundancy.

Myota delivers proven ransom immunity and enables instant rewind while cutting storage infrastructure costs by 50%.