Meet Alix Baggio, Software Engineer
Swan
Tech team
Swan has a diverse team of engineers from all over the place. Co-building is at the heart of the way we work. We believe in challenging each other. Being frank, but empathetic is the best way to get things done! It’s also more fun.
Swan makes it extremely easy for anyone to embed banking features, whether they're a dev or an entrepreneur (or both). It's exciting to build a bank that can be integrated by anyone! We'd love for Swan to become the reflex for European engineers who want to build something with banking and payments.
The banking domain is a fascinating and challenging place to grow your skills. It's state-of-the-art and covers everything you've learned at school: security, consistency, and scalability, but building a "bank" is a lot different from building another type of startup. In banking, you can't afford to have little bugs (imagine messing up someone’s account statement). That's why Swan puts security and robustness first and foremost.
Breakdown of expertise
Frontend engineers
10%
Backend engineers
73%
DevOps
17%
Technologies and tools
SequelizeL'équipe souhaite s'en passer en 2021
100%Scala
100%Protocol Buffers
100%PostgreSQL
100%Node.js
100%Nest JS
100%Kafka
100%GraphQLAPI
100%Akka
100%Elasticsearch
25%TypeScript
100%Terraform
100%Prometheus
100%Kubernetes
100%Istio
100%GitLab
100%AWS
100%argoCD
100%
Backend
Frontend
Devops
GraphQL API
It’s an edgy and modern choice, and incredible for our customers because they can pick and choose exactly which parts of the API they want to use.
Event-driven architecture
Great for the challenges of an internationally scaling BaaS, as events can come from any source at any time and our model has to be designed to simplify and handle that.
Functional programming
We use many different languages at Swan and this helps us create a unified environment so that we're all on the same page.
Organization and methodologies
At Swan, our product is primarily tailored for consumption by other engineers. Therefore, we encourage engineers to actively participate in co-building the product by proposing ideas and questioning feasibility.
To facilitate collaboration, engineers are organized into independent squads comprising 4 to 8 members, each working closely with dedicated Product Managers. Together, they develop the roadmap on a quarterly basis and iterate on it in cycles of 2 to 4 weeks.
Given the importance of system stability, we encourage engineers to propose technical projects aimed at scalability, which are incorporated into the roadmap alongside other features.
Recruitment process
-
A 30-min video call with our Talent Acquisition Manager, to get to know you, understand your career expectations and answer your questions
-
A technical test (45 minutes) and a technical interview with a Lead Software Engineer (1 hour)
-
A pair programming or a Design system with a Lead Software Engineer (1 hour)
-
An offer within 48 hours