Link mobile delivery with backend engineering

A mobile-booking modernization brought design, payment, web, backend and mobile teams together around new booking journeys. I served as General/Team Lead within a distributed co-lead structure for a 14-person team, while owning the project’s single backend-for-frontend, or BFF.

My role combined hands-on engineering with the technical enablement that made integration possible: clarifying requirements, agreeing API behavior, preparing developer guidance and resolving issues across teams.

I handled the BFF’s requirements, design, implementation, mainly unit testing, integration plan and documentation. Built with Node.js, TypeScript and NestJS, it used Redis caching and had no database of its own.

I translated complex backend responses into mobile-friendly flows through orchestration, aggregation, validation and request/response transformation. Defensive handling covered missing or partial data, normalized errors and safe defaults. Price work converted the display model, decimal representation and currency labels; exchange-rate conversion belonged outside this BFF.

One detailed problem was turning irregular seat-coordinate data into a row-and-column model that mobile apps could render. The transformation handled half-cell layout increments, aisles, facility widths, grid spans and overlays, including empty, missing or malformed layouts.

I wrote targeted unit tests for normal layouts, differing row structures and conversion edge cases. The mobile teams implemented their app journeys, while I provided the API model, integration guidance and cross-team alignment around it.

I maintained structured API contracts, Swagger/OpenAPI and Confluence guidance covering integration flows, errors and testing. Compatible changes had to preserve calls made by older mobile clients; breaking changes required a new version and a migration period.

I also produced developer-run Insomnia flows, examples and JavaScript scripts to prepare test data, chain requests, reuse variables and check responses. Feedback from mobile, QA and backend developers fed into revisions of the guidance. Formal integration-document sign-off remained with the Product Owner and Mobile Team Tech Lead.

I aligned dependencies across design, payment, web, backend and mobile leads. Developers and co-leads shared progress in the same daily stand-up; I consolidated the overall view and reported status, risks and recommendations directly to the engagement’s Senior Manager.

I introduced a dashboard for UI-review requests and helped standardize code-review expectations. The team delivered on schedule.

In parallel, I supervised technical-enablement and shared-component Team Leads across the wider mobile team. Those responsibilities had their own planning and review structure, alongside this booking-delivery role.

I handled staging deployment and validation, collected integration feedback and resolved issues from QA-led load testing and UAT. The client-side iOS Lead performed the production deployment after testing and confirmation.

After launch, I provided ad hoc production support through the end of my tenure, using Firebase, Kibana and Red Hat OpenShift for monitoring, log investigation, defect fixes and integration support. The role combined direct BFF ownership with shared delivery leadership; it did not make every member of the 14-person team my direct report.