Skip to main content
All experienceTraininpink

Building the software behind an Italian fitness product.

At Traininpink, I work on an Italian fitness product as a Senior Software Engineer, with responsibilities across dashboards, marketing, web, mobile, and system architecture.

My role
Senior Software Engineer
When
May 2026 - Present
Where
Dubai, United Arab Emirates
Explore this chapter
Traininpink fitness software engineering project overview with interface concepts
Project overview · Interface concepts

One product, several ways to use it

This role brings together several parts of my experience. The product needs software for its audience, the marketing work that introduces it, and dashboards that support the business. I work across those areas and consider how they fit into the same system.

The architectural work matters because a decision in one application can affect another. I look at what each part needs to do, how information moves between them, and where shared implementation makes sense.

Explore Traininpink (opens in a new tab)

What I worked on.

Web and mobile development

I contribute to the web and mobile applications as part of the same fitness product. The work combines feature implementation with decisions about application structure and the relationship between the interface and the systems behind it.

Dashboards and marketing

My scope also covers dashboards and the marketing side. Working across these areas keeps me close to both the customer experience and the software the business uses to support it.

System design and architecture

I contribute to architectural decisions alongside hands-on engineering. I consider responsibilities across applications, opportunities for reuse, and the consequences a change will have beyond the screen where it first appears.

How I work.

Understand the whole change

I start with the purpose of a feature and the parts of the product it touches. That context helps me connect implementation work to the wider architecture and discuss dependencies before they become separate problems.

Choose reuse deliberately

I look for common behavior across applications while keeping their different needs visible. A dashboard and a mobile application may share concepts, but their interactions need decisions that suit the people using them.

Skills I developed.

Architecture across applications

This work is deepening how I reason about a product made of several applications, particularly the boundaries between shared behavior and decisions that belong to one application.

Broader product responsibility

Working on marketing, dashboards, web, and mobile broadens the questions I bring to a feature. I consider how it fits the business as well as how it works for a user.

Keeping design close to implementation

I continue to develop my system design practice through daily engineering. Implementing features gives me a direct way to assess whether architectural choices help the team work with the product.

A place for movement.
Across your screens.

Guided training on web and mobile, with programs and nutrition brought into the same product.

See the public product (opens in a new tab)
Train.
Guided Pilates programs.
Nourish.
Nutrition alongside movement.
Connect.
Available on web and mobile.

The company, recognized.

Public milestones from Traininpink’s journey, including recognition before I joined in May 2026.

Inside the work.

Traininpink fitness product overview with web, mobile, and dashboard interface concepts.
Project overview · Interface concepts

Traininpink

Senior software engineering and system architecture for an Italian fitness product, spanning dashboards, marketing, web, and mobile applications.

Read the engineering story

The problem

The fitness product brings together customer-facing web and mobile applications, marketing, and dashboards that support the business. Decisions in one application can affect the others.

The approach

I work across these applications, connecting feature implementation with system design. I consider what each part needs to do, how information moves between them, and where shared implementation makes sense.