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.

Effective: July 1, 2024

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 and Checkout
     • User Registration and Account/Profile
     • Restaurant/Branches/Package/Tags/Group Landing Page Catalog and Search
     • Search by Product Detail Template (PDT)
     • Self-checkin
     • Personalization and Recommendation
     • Voucher catalog and checkout
     • Promo code/referral/reward and 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 Product Detail Template (PDT), and Checkout Page Phase 3, no handover was needed to the Cosmos or Syn teams. However, Search by PDT Phase 2 was transitioned to the End-User team.
2. Regarding communication with third parties, Nesya began handing over responsibilities to Fauzi starting in June 2024 and guided Fauzi until July 5, 2024, 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.