Through our unique no-code editor, we allow our customers to automate decision-making processes. We enable them to digitize their service and instantly publish what they built, making it available to their clients. Our customers have gone from very simple to incredibly complex use-cases, and they are automating more and more processes using BRYTER. In turn, we’ve seen a rising dependence on the correctness and the availability of our system. This is where we need you, to join the team that develops the execution engine at the core of our product.
What you will do
🚀 You will help scale one of our most important backend services, enabling us to successfully serve the next order of magnitude increase in load.
📊 You will work closely with developers and the infrastructure team, to improve the observability of the service and to make sense of incoming error-reports and metrics, using tools such as Datadog.
🧨 You will help improve the fault-tolerance of our services. For example by proposing and implementing changes to the APIs and the underlying implementation and introducing topics such as rate-limiting or work queues.
🔒 You will work with other developers, Infosec and external pen testers, on prevention and mitigation strategies to keep our customers’ data safe.
What we’re looking for
🤝 You build trusting relationships, to allow for clear and meaningful communication in a fully remote setting. You are keen to understand different cross-functional perspectives and you know how to make your case.
🏋🏽♂️ You have multiple years of experience working on backend services, that are in production and deployed under load multiple times per week. You have a good understanding of load analysis monitoring and performance scaling techniques.
🛠 You are proficient in Node.js and TypeScript, yet you see technology as a means to an end and are open to learning new tools as required.
✅ Writing automated tests is not a chore for you but a key component to building a high-quality product. You know how to write maintainable tests and you have experience with both functional as well as performance tests.
♥️ You care about the people you work with and are willing to grow together. You also care about the customer and you want to work on a product that matters.
The icing on the cake
👭🏽 You enjoy doing pair or team programming.
🧁 You have deep experience building fault-tolerant distributed systems with stateful and stateless components. You have also worked with event-based systems in the past.
🍰 You have experience in (or always wanted to learn about) some of the other tools and technologies we employ such as: Kubernetes, AWS, GitLab CI, Datadog, Gatling, Vue.js, Jest, Kotlin, Postgres, to only name a few.
📚 You like to read and have enjoyed books such as Accelerate, Continuous Delivery, Release It! and Site Reliability Engineering. You are willing to share what you learned.
Why should you apply?
- Direct impact on our product from day one
- Colleagues that care about the product and the people who build it
- We support you in your journey to become the best version of yourself. Not the least by providing challenging work, people around you who you can learn from, as well as a personal conference & training budget
- BRYTER has a product & business model that’s tried and tested and we’re in the process of scaling our impact, so your impact can scale with us
- Customers love our product which you’ll have a key role in developing
This job is not for you
If you reside outside of CET +/-2h time zones or if you have no experience at all working with Node.js and TypeScript, then this job is not for you.
Who are we?
We enable business experts to build and distribute powerful applications. Our software is intuitive and simple enough for non-IT experts to understand within minutes, yet powerful enough and enterprise-ready for industries with complex reasoning and demanding use cases. We especially cater to experts in law, finance, tax and compliance by helping them automate and standardise decision making.
How to apply?
Start a conversation by reaching out to us. Say hi, share why you’re interested in working with us and send along your CV.
What does working at BRYTER look like?
We are a remote-first Software-as-a-Service company, with people across Europe. At BRYTER, we believe in the power of self-organising teams and that everyone can be a leader. That’s why we strive for a way of working that reduces unnecessary burden and instead focuses on delivering value.
There are only two regular, mandatory meetings:
- A short 30min company-wide update meeting that happens weekly. This provides a forum for each business area of BRYTER to update the company on their progress towards their quarterly objectives.
- Our weekly Product Sync/Planning, where we revisit what we’re currently working on and what we plan to do in the upcoming week(s).
Other than that, we do a company-wide virtual-coffee session every morning. Anyone who is interested and available can join this call. The only rule is, that we don’t talk about work. It is an opportunity to laugh at what our dogs do to our shoes, share our first (or third?) coffee with each other and just try to kick-off the day in a great mood.
We do daily, written check-ins in Slack to keep everyone in the loop on what we’re working on.
👨👨👧👦 Quarterly Get-together
We are a remote-first company. At the same time, we value the face-to-face time. That’s why we get together at the same place at the beginning of each quarter. We spend the time strategizing, planning as well as just talking, having fun and getting to know each other better.
To date we have always done this in Frankfurt, Germany, where we have one of our offices. That’s why we sometimes call the time that we get together, on-sites. However, during the COVID-pandemic, these get-togethers have become virtual as well.
🎹 Processes & Tools
Our main tool for coordinating our day-to-day work is Gitlab. We not only use it as central git host, but also for our complete CI pipeline, to trigger and execute deployments with it and track our work items (and bugs 🐛) with Gitlab boards.
Developers own the development of their improvements and features and guide them until they are in production. And while some parts of the application are worked on mostly by a smaller subset of the team, we practice shared code ownership.
We practice a branch-based development workflow and do code reviews via merge requests (Gitlab-speak for pull requests). To enable quick feedback-cycles we aim for short-lived branches and provide automated means to deploy every branch to their own environment.
We put a strong emphasis on automated testing and having a test coverage that follows the testing pyramid. And as with most things, we aim to get better at these practices, which means we’re not perfect. 😇
When it comes to tools, such as an IDE or editor, you are free to use whatever you prefer. We provide JetBrains licenses, in case you like to use their tools. And of course, you’re free to choose your computer hardware and operating system.
Start a conversation with us! Just say hi, tell us why you’re interested in working with us and attach your CV and any portfolio material.