Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Engineering Team Structure

At the end of June 2024, we transitioned to a component-based team model to improve ownership, clarify responsibilities, and strengthen DevOps practices. This structure helps each team focus on a specific product area and simplifies delivery.

Team Structure

  1. Cosmos Team (hh-cosmos)
    • Focus: Admin Dashboard, Booking & Inventory Management, Package Management, Marketing & Promotion, Payment Management, Restaurant & SEO Management
    • Lead: Saiqul
    • Backend: Dayu
    • QA: Bernadetta
  2. End-User Team (hh-engineering)
    • Focus: End User Product, Inventory, Package Booking Process & Checkout, User Registration & Account/Profile, Restaurant/Branches/Package/Tags/Group Landing Page Catalog & Search, Self-checkin, Personalization & Recommendation, Voucher catalog & checkout, Promo code/referral/reward & loyalty program, banners/ads and flash sale, reviews, SEO
    • Lead: Tompi
    • Backend: Odi, Firman
    • Frontend: Afif, Luthfi, Monyta, Afandi
    • Mobile: Tompi (Android), Budi (iOS)
    • QA: Bernadetta, Rina, Wiwik
  3. Syn Team (hh-syn)
    • Focus: Restaurant Staff Domain, Registration & Onboarding, Dashboard & Analytics, Booking & Inventory Management, Package Management
    • Lead: Saiqul
    • Backend: Ali
    • Frontend: Fandi
    • Mobile: Tompi
    • QA: Wiwik
  4. Vendor Team (hh-ballbot)
    • Focus: API for Third-party/Vendor app, Blogger and Influencer integration, Inventory, Web embed, Package booking process & checkout, Restaurant branches catalog & search, Reviews and tags, Registration & onboarding blogger, Dashboard & analytics for blogger, Booking management for blogger
    • Lead: Zul
    • Backend: Mian
    • Frontend: Hanggar
    • QA: Fauzi

Cross-Team Support (Kernel)

Umam and Nesya serve as the product manager and technical writer across all teams. Irfan and Budi serve as DevOps across all teams. Rafi serves as the machine learning engineer.

Transition Notes

  1. For projects nearing completion, such as group landing page admin, Search by PDT, and Checkout Page Phase 3, no handover is needed. However, Search by PDT Phase 2 will be transitioned to the End-User team.
  2. Regarding communication with third parties, Nesya will begin handing over responsibilities to Fauzi starting today. Nesya will guide Fauzi until July 5th, particularly focusing on communication with the AOA company.

Purpose of the restructuring

  1. Clear ownership and responsibility: Each team has a defined focus area, allowing better accountability and specialization.
  2. Improved DevOps practices: This structure supports better integration of development and operations, leading to more efficient and reliable delivery.
  3. Enhanced collaboration: Teams have clear focus areas, while cross-team collaboration is still encouraged to maintain a holistic product view.