Vantaggi
I had a really great experience here. Over the course of a year I worked on very different products and features — the architecture is microservices-based with PHP, Python and TypeScript on the backend, React on the frontend — and this variety brings constant challenges and very fast professional growth. You learn a lot in a short time.
Responsibilities come quickly: you don't need to wait years to work on complex projects, which makes the job very engaging. Feedback on products and features is always welcome, and proposing new ideas is easy and encouraged.
The environment is young and international (average age around 30-35, mostly Italian colleagues but with a good share of non-Italian speakers as well), with official communication in English. My team was made up of very skilled people with a strong openness to experimenting with new frameworks and approaches — the kind of context where you genuinely grow. The onboarding was well handled: the team leader supported me through the initial setup, and together we shaped a path for what to focus on and improve over the following months, aligning it with the team's tasks and priorities. There's a lot of flexibility in building your own growth path within the day-to-day work.
On the organizational side, each Engineering team works closely with Product figures — a designer or product manager — and is led by a technical team leader who is a developer. Each team generally manages multiple products or features within ShippyPro, which adds to the variety.
Engineering is remote-first. Work is organized in Jira with time-boxed epics and tasks, with both synchronous standups on Meet and async updates on team channels. Performance reviews every six months. Time off and leave are handled very flexibly and with short notice. Benefits include meal vouchers (also when working remotely) and a welfare plan.
Svantaggi
During certain periods or on specific projects, deadlines can be tight and the workload more intense — there's a startup mindset geared towards building things fast. That said, in my team the workload was generally planned together so that it stayed reasonable and manageable.
