R3PI is the innovation hub of Solera, a global leader in intelligent data and software as a service. It’s not your typical office. At R3PI, we have a passion for the unknown and the yet-to-be-imagined. Every day, we create new forms of intelligence, shape smarter diagnostics and challenge what’s possible in technology. You’ll get your hands dirty in our garage-style offices and experiment with data and diagnostics to build the future of industry. Today, we’re hearing from one of our developers from Zürich. Ophelie and her team code and build solutions for the safety and security of today’s cars. Read on to get to know a little bit more about Ophelie and R3PI.   

  1. How long have you been working for R3PI, and what do you do there? 

I started with R3PI one year ago. I’m a developer working in the data engineering team. My team develops backend features for different automotive products. We are ingesting and processing data in real time at a large scale. We also work closely with data scientists to industrialize machine learning solutions. 

  1. What does a typical day in R3PI look like? 

We are involved in different projects. Most of the time we are developing new features and often testing different technologies. A lot of the projects we work on involve several different teams—the hardware team, mobile development, QA and data engineering. It’s important to have a good idea of what everyone is contributing and understand the blockers they might have on the project.  

  1. How did you hear about R3PI?

A former colleague actually suggested I check out R3PI. And I don’t regret it! 

  1. What’s unique about working in automotive tech?  

The data we work with is really interesting. You can create a lot of solutions using car data and you can extract loads of information, especially for insurance purposes. By harnessing this data, our solutions can determine if a vehicle is a total loss upon notice of an accident or if it’s repairable. When you work with vehicles, you need often to process that data in real time. It’s challenging but important. And you have to consider the design of the solution you’re working on when you process that data. You have to think about the resiliency, the strength and security of your servers. There are a lot of components to think about before you even start coding. That’s why we work closely with architects to help us get it right. 

  1. What has been your proudest moment at R3PI so far?

I’m proud when I finish a product. When I complete something, it’s cool to think about people actually using it out there. 

  1. What’s the most difficult part about your job?

Changing between different projects and learning new technologies can be hard but is also rewarding. Aligning with all teams involved in a project can be also challenging. We have a strong QA team who makes sure our components are working well with every other component. 

  1. What are your favorite things about working at R3PI?

I work with strong engineers—that’s my favorite part about my job. It’s nice to be surrounded by good people. The engineers know their stuff and they care about the quality of our projects. For complex problems it is very important to have different point of view. When I add a piece of code, I know a colleague will carefully review it to keep the product clean. When you make mistakes, you learn. It’s the best way to improve. We have quite challenging, uncommon projects here. But you always know someone has your back. 

  1. Which of R3PI’s values do you connect with the most, and why?

We’re all responsible for what we do. That’s the 90/10 mentality. You’re responsible for the 90, your team is responsible for the 10. When there’s a problem, a bug in the code maybe, we don’t complain or point fingers. We just try to find a good solution and fix it. And I love the diversity of R3PI.  

  1. What has your experience as a female developer been like?

You can be undervalued. You feel you have to prove you’re legit. But if you’re working with good people, they see what you do and your work speaks for itself.  

  1. What advice would you give to someone who’s starting out their career as a developer?

I think the best advice I can give is to start with the basics and master them. Make sure you have good technical skills and understand the tools you’re using. People will appreciate that you’ve mastered a subject and that naturally leads to you enjoying it, which makes you want to get even better at it!  

  1. What do you like to do outside of work?

I love hiking in the summer. And in the winter, I ski and eat a lot of fondue.

12. Do you like cars? What’s your favorite model?

To be honest, I wasn’t into cars before starting here. It’s definitely not criteria to work at R3PI. But I’m happy to work with that kind of data. You’re learning coding, but you’re also learning new information that happens to be about cars!    

Thanks for sharing, Ophelie!