Talent knows no borders, and the insurtech sector is the perfect reflection of that. Today, we bring you a very special conversation with Abu Sayeed, Senior Frontend Engineer at Weecover, who a few years ago decided to leave his homeland to make Barcelona not only his new home, but also the stage for his professional growth.
After more than three years with the team, Sayeed has become a key player at Weecover. His day-to-day work involves a massive challenge: transforming the huge technical complexity of insurance into an invisible, fluid, and simple user experience.
In this interview, we chat with him about his integration process into a multicultural team, how his technical mindset has evolved toward a more strategic product and architecture vision, and what it truly means to have autonomy and real impact in a fast-growing scale-up.
You arrived in Barcelona from Bangladesh and decided to build your software engineering career here. What made you fall in love with this city to settle down and choose it as your professional home?
When I first arrived in Barcelona, I wasn’t very sure if it would be temporary or if I would actually stay. I was coming from Bangladesh, which is a very different culture, and the first few months were a mix of excitement, adaptation, and also a bit of uncertainty.
But Barcelona won me over little by little. I liked living in an open city with people from so many different places. That helps when you come from abroad; you don’t feel like such a stranger. It also has a very interesting professional side for someone working in tech, because there are plenty of companies, opportunities, and movement to keep learning. And then there is the personal side. I met my wife here, and that changed everything—Barcelona stopped being just the city where I worked. It became the place where I was building my life. I think that’s what carried the most weight in the end.
At Weecover, we love having a team made up of people from very diverse backgrounds. How has your integration experience been, and how does this cultural variety enrich the daily life in the office?
My integration experience has been very positive. I’m not going to say everything was easy at first, because when you come from another country, there are always things that take effort. The language, certain idioms, even catching specific nuances in meetings… that takes time.
But at Weecover, I felt quite supported. I’ve had teammates who helped me, who were patient, and who made me feel like part of the team.
The cultural variety really shows in our day-to-day work. Sometimes one person sees a problem one way and another person sees it completely differently. And even though that generates debate sometimes, it’s usually positive. In tech, the first idea isn’t always the winner. More often than not, the best solution comes from listening to different perspectives.
You’ve been at Weecover for over three years. Looking back, how would you say you have evolved as a professional, and how has the company changed since your arrival?
I think I’ve changed quite a bit. When I arrived, I was eager to do a good job, learn fast, and prove that I could contribute. At first, I was more focused on solving specific tasks and making sure everything worked well.
Over time, I’ve started to look at Frontend from a different perspective. Now I don’t just think about a single screen or a specific feature. I think more about how that solution will be maintained and if another developer will be able to easily understand it. I also think about whether it fits the design system and if it will help us or cause us problems a few months down the line. I’ve also learned to connect the technical side more closely with the product. Sometimes a tiny Frontend decision can heavily impact the user experience, development time, or the ability to scale a solution for different clients.
The company has also changed a lot. Weecover has grown; there is more structure, more product focus, more design, and a bigger emphasis on building scalable solutions. But something I value a lot is that you can still speak up, propose things, and feel like your opinion matters.
For developers looking for a place where they can pitch ideas and not just ship code, what level of autonomy and real impact would you say the Weecover technical team actually has?
I would say there is quite a bit of autonomy, but it comes with responsibility. It’s not an “I do whatever I want” kind of autonomy, but rather being able to analyze a problem, propose a solution, and explain why it makes sense. In Frontend, it’s rarely just about building a interface screen. We have to think about components, states, accessibility, maintainability, UX, and also the fact that many of our solutions have to work for different clients and contexts. That forces you to think a step beyond the initial problem. Sometimes the quick fix works, but it’s not the best option if other teams need to reuse it later or if we need to scale it in a few months.
For me, that’s the exciting part about Weecover. You can have a real impact if you propose things with solid criteria. Not every single idea goes through, because there are priorities and deadlines, but that space to debate and improve things definitely exists.
Even if the end-user doesn’t notice it directly, embedded insurance requires highly sophisticated technology. How do you, from the Frontend team, make such a complex process look visually invisible, fluid, and simple for the customer?
I think this part is one of the hardest but also one of the most important. Behind the scenes, there is a lot of logic: business rules, integrations, validations, data coming from different sources, client-specific configurations, and many edge cases. From Frontend, we try to make sure that complexity never reaches the user. The user doesn’t need to understand how everything is wired up in the back. They just need to know what step to take next, understand errors if they pop up, and complete the process smoothly.
To achieve that, a good-looking UI isn’t enough. You have to carefully craft components, states, forms, copy, accessibility, and visual consistency. It’s also crucial for solutions to be reusable; if every user flow is solved differently, the product eventually becomes a nightmare to maintain. For me, a good Frontend is when there is high complexity behind the scenes, but the user feels like everything is effortless on the outside.
You share the workspace with high-caliber professionals. What stands out to you the most about the talent within the Weecover tech team, and how do you help each other keep the bar high?
What stands out the most is that people here have great technical judgment. They aren’t just people who know how to code; they are people who think about the product, the architecture, and how a decision made today might affect the team tomorrow.
You learn a lot in the day-to-day. Sometimes someone suggests a cleaner solution, someone else spots a bug you missed, or someone asks a question during a code review that forces you to rethink your approach. I value that a lot. When you work with people who care about the details, you try to level up too. I don’t see it as a competition, but as a way to improve together.
I also believe that in a healthy tech team, sharing knowledge is vital. It’s not just about solving your piece of the puzzle, but about leaving things a bit clearer for the next person who steps in.
You work with the latest tech stack. How important is it for a developer that a company like Weecover allows you to work with cutting-edge technology and keep learning new things daily?
It’s very important to me, but with a caveat. I don’t think we should use new technology just because it’s new. What matters is that it actually benefits the product, the team, and the code quality.
At Weecover, we have the opportunity to work with modern tools, modular architecture, reusable components, design systems, and Frontend best practices. That is highly motivating because you feel like you aren’t just maintaining legacy code; you are helping build a more solid technical foundation. As a Senior Frontend Developer, I also see it from another angle. Technology shouldn’t just solve today’s issue; it needs to help the team work better tomorrow. If a tool improves accessibility, reduces duplication, eases maintenance, or allows the product to scale better, then it holds massive value. And on a personal level, of course, it keeps you learning. In our field, that is fundamental.
To wrap things up, a direct message to the future engineers reading this: What would you recommend to a tech professional who is considering joining and making the career leap to a scale-up like Weecover?
I would tell them to come eager to learn, but also eager to contribute. In a scale-up, things aren’t always 100% set in stone, and while that can be a challenge at times, it’s exactly what allows you to grow. Here, you get to touch real-world problems, pitch improvements, and see that your work makes a difference. It’s not just about coding a screen and moving on. Often, you have to understand the product, sync with other teams, and design solutions that will hold up over time.
My advice would be to come with curiosity, ask a lot of questions at the beginning, and don’t be afraid to speak up when you see something that can be improved. If you love to learn and gradually take on responsibility, it’s an environment where you can grow immensely.
