Senior Linux Infrastructure Engineer

Join our team as a Senior Linux Infrastructure Engineer. In this hands-on role, you will own the systems layer of our production environment, diagnose and tune systems under real production load, lead troubleshooting on hard problems, write and maintain configuration management code, run containerized workloads, automate in Bash and Python, operate core network services, manage virtualization, handle secrets properly, own observability, and work through change management and code review. You will have the opportunity to make a significant impact on our infrastructure and systems.

• Posséder la couche système de notre environnement de production, de la configuration matérielle au code de gestion de configuration.
• Diagnostiquer et ajuster les performances des systèmes sous une charge de production réelle, en se concentrant sur des aspects tels que la planification CPU et le comportement de la mémoire.
• Écrire et maintenir le code de gestion de configuration, construire l'infrastructure de manière déclarative avec des outils tels que Salt, Ansible, Chef ou Puppet.
• 6+ years in a Linux systems, infrastructure, or SRE role
• Virtualization experience with at least one of VMware, Xen, or KVM
• Excellent written communication. Runbooks, design proposals, and incident write-ups are a core part of this job, not an afterthought
• Git and peer review as a daily habit, including the discipline to keep changes reviewable
• The ability to get productive quickly in areas where you do not yet have depth
• Foundational networking. Comfortable across layers — VLANs and routing, DNS, DHCP, TCP behavior, and TLS — and able to determine whether a problem is the application, the host, or the network
• Scripting and automation. Strong Bash and working Python. You write code that other engineers can maintain
• Systems fundamentals. Processes and signals, systemd, cgroups and namespaces, filesystems, and what actually happens when a host exhausts memory or file descriptors
• Declarative configuration management at production scale — Salt, Ansible, Chef, or Puppet. You have authored and maintained the code, not only run it
• Troubleshooting methodology. A disciplined, hypothesis-driven approach that works on a system you have never seen before. We care more about how you narrow the problem than about which commands you happen to know
• Performance analysis. You can go from a vague complaint to a named subsystem using the standard tooling — perf, strace, ss, iostat, bpftrace, or equivalents — and explain what the numbers mean
• Proxy and load-balancing experience with Nginx or HAProxy
• Containerization and orchestration. Production experience with Kubernetes or Nomad, including the operational realities: scheduling, resource pressure, rollouts, and debugging a workload that will not start
• If you’re excited about this role, but your experience doesn’t align perfectly, we encourage you to apply anyway
• Vault administration — policies, auth methods, and rotation at scale
• Production ownership of Redis or RabbitMQ as a primary responsibility rather than a dependency
• Elastic Stack operations at volume: index lifecycle, mapping decisions, and cluster tuning
• Experience in a regulated environment, or anywhere downtime has a direct revenue cost
• Colocation or bare-metal experience: hardware lifecycle, remote hands, and capacity planning against a finite footprint