Software or Infra Engineer : confirmed to principal - full remote

Join Batvoice, a fully remote company, as a confirmed to principal engineer. You will participate in major architectural changes, focusing on performance and security. The role offers rapid advancement opportunities, comprehensive healthcare coverage, and a stock option plan. You will work on various projects, including re-examining web architecture, planning a change to the permissions model, capacity planning for infrastructure, and reworking access control in environments.

• Participer aux changements architecturaux majeurs de l'entreprise, en particulier en ce qui concerne l'architecture web et le stockage.
• Contribuer à la planification et à l'exécution de projets visant à améliorer le modèle de permissions et à planifier la capacité de l'infrastructure.
• Collaborer avec d'autres ingénieurs pour examiner et améliorer les systèmes existants, en mettant l'accent sur la performance et la sécurité.

Research has shown that having strict quantitative requirements discourages applicants that would have otherwise performed well at the position from applying. As such, instead of experience, we define skills that will be relevant to these positions.

As long as you have at least one, you'll be considered for the technical interview, and the more (and better) you have, the higher your chance to be hired. To estimate what seniority you'll be judged as and for further details on how we make hiring decisions, take a look at our [Seniority](https://batvoice.notion.site/Engineering-Progression-4707300dc3254266bc538ad917005754) definitions, company [Values](https://batvoice.notion.site/Values-13ff80e07c5e4c3fa72493dd76dc3d07), and documented [Interview Process](https://batvoice.notion.site/Interview-Process-Engineering-1c1d68b3d5cb45dca5a5d8c45fd7cf85). Note that the salary will depend on the evaluated seniority, which we define up to Senior (past that it gets too variable).

• **Python** : it's the language we use, though if you're intimately familiar with other dynamic languages (for example, say you can discuss the BEAM VM internal workings) we're sure you'll pick it up quickly.
• **Databases** : currently we're on **Postgres** (with **TimescaleDB** on some tables), but we're hitting its limits, in part due to ORM use, in part due to how it functions internally. As such knowing general database internals (for example how the query planner works) is more important than "having worked with Postgres before", though that counts for something too.
• **Web Frameworks** : currently we're using **Django** but the important part isn't so much that (though knowing what it's like is appreciated, it's somewhat different than other comparable frameworks), but rather understanding what a framework does internally and being able to predict the impact. For example, do you know how an ORM works? Or perhaps what limitations a class-based router might have? Talk about them!
• **Kubernetes** : our infrastructure lives in k8s, typically **EKS**, managed by **Terraform** and **FluxCD**. Our data pipelines go through **Argo** Workflows. We have a few physical machines connected to all of this via **Tailscale**. If multiple of these words mean something to you, you're likely to be able to help out with our infrastructure.
• **Maintenance** : it's exciting to build new things, but what about keeping them working ? Someone needs to watch for security issues, update kubernetes operators, push for major python version upgrades, etc. And if it's all documented and part of procedures, we can also more easily answer to audits (we get audited fairly often, but we always pass; it'd just be nice to do so with less effort). A mind for keeping things like this in mind is also a mind to know how things work, and be able to explain them too.

Ideally, you should talk about which of these scopes (and how) you want to contribute, to make the interview process simpler (you will be directly tested on those).