Not a software-house for sure, not a product company either. We try to take the best from both of these approaches. We build deep, long-last relationships based on mutual trust. Our clients have insight into the smallest details of our work and direct communication channels create a feeling of sitting next to the team. We foster a spirit of collaboration and try to work as one team with one goal.
On job boards, you can often see that having an impact is advertised as a benefit. Well, we think that this is a good start. For us, your impact is actually desirable and required. We believe that mutual and honest feedback will allow us to build a better team, better product and is a great opportunity for personal growth.
We work, succeed and fail as a team. We are eager to help each other in difficult moments. In terms of teamwork, let's talk about another, often mentioned perk - code review. Of course, we also do it on a daily basis, but again this is only a starting point. We often work collectively on a matter with such tools as pair-programming or Event Storming. In such conditions, obligatory code review becomes redundant, it's just a tool.
We foster a culture of learning and experimentation. You will be able to validate your ideas on the production from day one. Do you think that tuning that query will reduce page load time by 50%? Or maybe changing the placement of that button will boost product conversion rates vastly? No problem, let's check and measure that!
Of course, everyone makes bad calls sometimes. This is natural and there is nothing wrong with that. The worst thing would be not learning those lessons and keeping that knowledge for yourself.
- Fluent knowledge of Linux,
- Familiarity with GCP products (Cloud SQL, networking, managed clusters),
- Knowledge about maintaining PostgreSQL instances,
- Experience in supporting production environments,
- production experience in Message Brokers (preferably Kafka),
- Experience with running production workloads operating on k8s and Docker,
- experience in building CI/CD pipelines (we use GitHub),
- Understanding of security best practices,
- Understanding of deploying and running highly available, fault-tolerant systems,
- Being an open-minded, curious and pragmatic person. Go-get-it attitude,
- Working knowledge of site reliability like SLA, risk management, health checks, monitoring, alerting.
Nice to have
- DevOps mindset (have you read Accelerate ? Let's talk about it!),
- IaC approach.
- Identify and anticipate system-level risks,
- Tweak monitoring and alerting tools also provide dev team guidance on how to leverage them to make code observable,
- Support a large application based on Docker and k8s, written in Elixir,
- Design and deploy disaster recovery policy,
- Enable engineers to use infrastructure,
- Be a part of our on-call schedule rotation.