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. Join Swan and you'll be pushed to reach the highest standards of quality and precision.
Technologies and tools
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.
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.
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
Engineers at Swan are not here to take orders and just start coding, they're here to co-build and be heavily involved with the product.
Swan's devs collaborate heavily with the product team and are always proposing ideas and challenging what's doable. We follow a methodology that's similar to "Shape up": 3-week cycles: Co-building is central to how we work. Each month, the product and engineering teams work together to plan goals and develop specifications for the next 3 weeks.
During these weeks, we do our best to reach goals, all while planning and designing projects for the next cycle. 1-week cooldown: After a cycle of building, it's cooldown week.
We use this time to handle any remaining tasks and improve tools and processes.
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