Skip to main content
David Careers

Principal Software Engineer (SRE/DevOps) - Remote

Posted yesterday

invisible technologies defunctMillbrae (CA)
Computer Systems Engineers/ArchitectsComputer Systems Design Services

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Principal Software Engineer (SRE/DevOps) - Remote Invisible Technologies offers unusual services (a combination of outsourcing and automation) to fast-scaling, innovative companies. Each company understands and uses our services in a variety of ways. It's critical we can communicate to segments of users with visually appealing, and highly communicative assets. You're helping us explain the benefits of our product in a way that words alone never could.
Job Description: Principal engineers at Invisible are able to follow multiple paths. Some of our Principal engineers are technical leads of teams and are responsible for people management of those teams. They oversee the technical vision for their area and ensure that there is proper mentorship. Other principal engineers lead through technical initiatives. These engineers oversee broad multi-team technical initiatives and own parts of our software stack (ex. Principal engineers might research and roll out new technical frameworks or might develop a new generation of our UI component library.
Qualifications:
  • We know that if we have a DevOps team we aren't practicing DevOps both are listed to make it clear that we're looking for a multi position player who's comfortable with application engineering AND infrastructure.
  • A good candidate will have a strong understanding of cloud architecture including the major cloud providers (AWS, GCP, etc).Candidates should understand underlying networking and security considerations when developing the architecture of our deployment environments.
  • Candidates should have a strong understanding of authentication and authorization frameworks such as IAM, Security Groups, RBAC, etc.
  • Candidates should have experience with Kubernetes and be able to point to deployments they have architected or managed.
  • Candidates should have a strong understanding of the operating model of Kubernetes and be able to explain the requirements for designing deployments for new applications.
  • Ideal candidates would have experience with infrastructure as code tools such as Terraform, Cloud
  • Formation, Ansible or Puppet.
  • We're always eager to learn and grow and try new technologies.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this