Apptega

Context

An enterprise SaaS platform for cybersecurity and compliance, already in production and used daily by its customers, going through a progressive modernization.

Problem

The product had to evolve — new modules, modern interfaces, better foundations — without pausing what customers were already using every day.

Constraints

• Angular legacy and new React modules coexisting inside the same product.
• A multi-repository, dockerized ecosystem with independent services, shared packages and feature flags.
• Technical debt that could not be paid off in one move, and interfaces with very high information density.

The work

• Cross-functional frontend work on the main application and on new independent modules.
• Extending and maintaining the internal design system shared across applications.
• Unit, component, integration and functional-flow testing as part of the delivery, not after it.
• Refinements, estimations, demos and troubleshooting with product, design, backend, QA and DevOps.

Decisions

• Incremental evolution over a full rewrite: new capabilities as modules with clear boundaries.
• Shared design system and private packages as the way to keep consistency across repositories.
• Feature flags to decouple delivery from release in a product that can't stop.

Result

A contribution to the transition towards modern frontend experiences inside a platform of high technical and business complexity.

Learnings

• How to evolve software that is already in production, without stopping the product and without a full rewrite.
• Seniority here meant balancing speed, maintainability and continuity — rarely all three at once.