Work About People Contact
Accurat Dataschool Dataschool for Business In Sight Old journal

Ex–Interns of Accurat

Chatting with three interns turned full–time, full–stack developers.

Jun 10, 2021 Accurat

Many Accurat interns graduate to full–time status. In a new series, we interview colleagues who began working at Accurat as students. First up are developers Stefano Gallo (who joined May 2018), Ilaria Venturini (September, 2018) and Ivan Rossi (February, 2019). All came to Accurat from the University of Milan.

Interested in becoming an Accurat intern? We’re currently hiring developers. Visit our website to learn more and apply.

Q: What does a full–stack developer do at Accurat?

Ilaria Venturini: We develop data visualizations and web apps with a focus on usability and aesthetics. The exchange of ideas with designers is continuous — we make decisions together to come up with the best solutions for customers.

Stefano Gallo: For projects with unusual components and/or time constraints, we have to strike the right balance between functionality and sleekness. During development, we’re in constant communication with designers.

Ivan Rossi: Accurat’s projects are mainly front–end dataviz. A full-stack developer spends most of his or her time creating crazy visualizations and interactive animations.

Q: What do you think makes Accurat’s internship program unique?

SG: The unconventional working environment. At first, I couldn’t even tell who’s boss was whose.

IV: From the beginning, I had the opportunity to work on real projects and had actual responsibilities. I got to work with designers as well as developers and gained a huge amount of knowledge. I always felt that my opinions and ideas were being heard and that I could make a difference.

Q: What’s the most valuable thing you learned as an intern, and how did you learn it?

IR: To work in a team. I had never worked with other people in a professional setting, and Accurat projects are mostly short–term, so changing teams happens often. This helped me get to know most of my colleagues quickly and adapt to the different ways groups functioned.

SG: Not a technical skill, but a different approach to development. I’ve learned how to problem–solve by breaking a situation down and solving little pieces individually, without losing sight of the broader end–goal.

IV: Probably thinking before writing code. Considering the pros and cons of possible paths, choosing the right data structure, making plans, assigning priorities — simplifying a problem before beginning to code. Initially, I was mistaken in thinking that the sooner you start to develop, the better. I eventually realized — with the help of more experienced colleagues — that it saves time and effort to plan first.