Rifki Rosada | Platform Delivery

Multi-Surface Platform Monorepo

Consolidated admin, landing, and API delivery into a single monorepo so related product surfaces could ship together more reliably.

Monorepo Platform Engineer 4-week delivery sprint Remote contract delivery
  • Problem

    Separate repositories for related surfaces caused dependency drift and slowed coordinated releases.

  • My scope

    Structured the repository with npm workspaces and clearer package boundaries.

  • Result

    Reduced release friction and dependency drift across the platform.

Problem

Separate repositories for related surfaces caused dependency drift and slowed coordinated releases.

Constraints

  • Needed isolated app ownership with shared engineering standards
  • Contributors required a simple local setup path
  • CI tasks needed deterministic scripts

Delivery

  • Structured the repository with npm workspaces and clearer package boundaries.
  • Standardized scripts across the admin app, landing surface, and NestJS API.
  • Aligned local development and release routines around one delivery model.
  • Documented the working setup so contributors could onboard faster.

Result

  • Improved dependency consistency across related product surfaces.
  • Simplified cross-surface release coordination.
  • Made onboarding and maintenance easier for contributors.

Tech stack

  • npm workspaces
  • Next.js
  • NestJS
  • TypeScript

Related delivery proof across internal tools, automation, Android + AI, and supporting product systems.

Client Systems

Client delivery

Enterprise CRM - Sales Pipeline & Performance System

Lead Full-Stack Engineer6-week delivery sprint

Cut the weekly pipeline review cycle from ~2 days of spreadsheet reconciliation to ~15 minutes — single source of truth across sales, ops, and management.

  • Problem

    Pipeline updates and performance reporting were split across 3 separate spreadsheets, making weekly reviews take days and ownership hard to trust.

  • My scope

    Mapped sales stages, reporting rules, and operator roles before touching schema or UI.

  • Result

    Cut the weekly pipeline review cycle from ~2 days of spreadsheet reconciliation to ~15 minutes — single source of truth across sales, ops, and management.

  • Laravel
  • Next.js
  • PostgreSQL
Read case study

Automation Systems

Client delivery

Inbound Order & Lead Ops Automation

Automation Engineer2-week delivery sprint

Eliminated an estimated 60–80 hours/month of manual data entry across multi-branch operations. Booking + reporting now flow automatically into a single source of truth.

  • Problem

    Inbound orders, bookings, and chat updates were copied manually into spreadsheets across multiple branches, producing inconsistent records, delayed follow-up, and zero operational visibility for management.

  • My scope

    Implemented web-order-to-sheet automation with validation and normalization.

  • Result

    Eliminated an estimated 60–80 hours/month of manual data entry across multi-branch operations. Booking + reporting now flow automatically into a single source of truth.

  • n8n
  • Google Apps Script
  • Google Sheets
Read case study

Supporting Delivery

Client delivery

Social Feed UI Fixes and Card Polish

Frontend Engineer2-week delivery sprint

Improved feed scanability through low-risk UI fixes that fit the existing product language.

  • Problem

    Social cards had uneven spacing and weak hierarchy, which made dense feed views harder to scan.

  • My scope

    Reviewed spacing rhythm, card hierarchy, and interaction cues in the existing feed.

  • Result

    Improved feed scanability through low-risk UI fixes that fit the existing product language.

  • Frontend UI
  • Responsive CSS
  • Design QA
Read case study

Planning a similar build?

Share the workflow, delivery risk, and timeline. I will reply with the best starting scope.

Share your scope Email project brief