Software Engineer with Namespace labs

Remote (Worldwide, +/_ 4hrs CET Workhours)

$80K - 150K a year

Join Namespace to build the development and production platform for teams that ship.

After iterating our core product with a small team and a closed user group, we're looking to grow our team as we get ready to ship a GA product and accelerate GTM. We are looking for people who share our passion for creating a unified development and production platform to help teams focus on building their applications.

Namespace container and virtualization infrastructure

As we build the 

development and production platform for teams that ship
, we look to containers and virtual machines to isolate user workloads – whether it's development workloads, separate end-to-end tests, or production. But we want containers and virtual machines to work for the user, and we strive for their performance and usability to reach that of running services locally.

In this role you will:

  • Be responsible for designing and implementing key components of Namespace's Firecracker-based hosting platform.
  • Be responsible for the performance and robustness of our use of k3s and containerd, and for extracting learnings to apply to users' own Kubernetes usage.
  • Operate across multiple layers of our stack, whether interfacing with the underlying container and virtualization infrastructure or with our frontends.
  • Collaborate closely with, and be engaged with product and engineering across the company.
  • Directly contribute to the product roadmap, together with the rest of the team, and be empowered to drive key product and technical design decisions.

You will thrive in this role if you:

  • Feel deeply comfortable in at least one of Kubernetes, containerd, KVM, or Firecracker.
  • Previously worked with Go, Rust, and/or in other distributed control planes (e.g. Kubernetes control plane, Kubernetes controllers, Envoy, etc).
  • Have interacted directly with linux cgroups, including network namespaces.
  • Have operated containerized / virtualized workloads in larger production deployments, including handling observability and incident response.
  • Have experience with load balancing, ingress and egress network policies, HTTP and/or gRPC.
  • Believe that preparing and running a VM should take not much longer than a container.
  • Are energized about the idea of packing as much unique work into bare metal machines in an as cost-efficient a manner as possible.
  • You can concisely describe your ideas in written form, and quickly put together proofs of concept.
  • Excel in a work environment that is mostly asynchronous (reading, writing, messaging, videos).
  • Have a passion for infrastructure, and keep yourself up to date with advances in the industry.
  • Thrive in ambiguity and can charter your own path.
  • You're energized to learn and apply new technologies and skills.
  • Feel a sense of responsibility to bring the most value possible to users.

We don't expect everyone to meet 100% of the qualifications above, so if you don't, you should still seriously consider applying.

You can expect:

  • Industry-competitive salary (we're happy to share the details with you early on).
  • Equity package with friendly terms intended to become life-changing for early team members.
  • Fully remote with flexible hours wherever you call home, although we ask that your workday overlaps at least four hours with CET. Equipment budget for your home office.
  • 25 days PTO, health benefits, and pension account with full employer match.

Life at Namespace Labs:

  • We pride ourselves in being a small team that can achieve beyond what's usually expected for our numbers.
  • We balance our long-term vision with short-term pragmatism.
  • We believe in being fully transparent internally on how decisions are made, on how the company is doing, and we use that information to drive our decisions.

What to expect from the hiring process:

Nothing beats seeing your work and you seeing ours. Right at the application stage we'd love examples of your past technical work (e.g. link to an open repo with your code), and design work (e.g. design document, an email proposal, UI mock, or a code comment) that you feel best represents how you approach problem solving. We also make sure you get to engage with our product and team through out the process.