Requirements

Key Responsibilities:

1. Segmentation Service Development
   
   • Refactor and Expand Segmentation Capabilities: Transform the platform’s basic segmentation system into a powerful, data-driven segmentation engine. The initial segmentation will be based on profile information, but you will expand it to include user behavior, geographic location, transactional history, and other data points, allowing operators to create detailed user segments for marketing and engagement purposes.
     
   • Custom Segment Creation: Build a flexible interface to allow operators to create custom segments based on predefined criteria (e.g., user behavior such as frequent bettors, transactional history like large deposits, or GEO preferences).
     
   • Real-Time Data Integration: Integrate the segmentation engine with the data warehouse (ClickHouse) to ensure real-time updates and data processing, continuously reflecting current user behavior and preferences.
     
   • Personalized Content Delivery via CMS: Integrate the segmentation engine with the CMS to allow operators to display personalized content such as game recommendations, promotions, and payment methods. For example, users from different GEOs may see localized content, while high-value users can receive tailored offers.
     
2. Condition Builder Implementation
   
   • Flexible Condition Builder: Design a condition builder that allows operators to set up automated workflows and triggers based on user behavior, actions, and system events. The builder must support multi-condition workflows, allowing operators to define complex conditions such as "if a user deposits over $500 and places three bets within an hour, trigger a high-value bonus."
     
   • Handling Complex Conditions and Corner Cases: Design the condition builder to handle various corner cases in multi-condition workflows, ensuring that the system remains stable under complex rules and high usage. Implement UX best practices to simplify condition setup for users, minimizing errors and reducing complexity.
     
   • Backend and Frontend Event Integration: Ensure seamless integration of backend events (e.g., deposit actions, KYC updates) and frontend events (e.g., user clicks, page navigations) into the condition builder. These events will trigger personalized notifications, actions, and content delivery.
     
   • Risk Management & Scalable Rule System: Implement a scalable rule system that can handle a large number of conditions without performance degradation. Proactively address potential risks and edge cases that may arise in complex, multi-condition workflows.
     
3. Message Center Refactoring and Expansion
   
   • Omnichannel Messaging Hub: Refactor the current message center into a robust omnichannel messaging hub, supporting multiple communication channels such as SMS, email, push notifications, and third-party services (e.g., WhatsApp, Telegram). This will allow operators to engage users across their preferred channels.
     
   • Event-Driven and Scheduled Messaging: Ensure the message center supports both event-driven and scheduled messaging, with capabilities to handle high-load scenarios. Build systems that can efficiently process real-time event-based notifications (e.g., transaction completions) and handle time-sensitive scheduled messages (e.g., promotions or reminders).
     
   • High-Load Planning and Performance Optimization: Design the system to handle high loads, ensuring it can scale to support millions of users and high volumes of event-based notifications. Plan for peak usage scenarios, optimizing delivery times for both event-based and scheduled messages.
     
   • Message Template Constructor: Build a dynamic template constructor to allow operators to create reusable message templates that support personalization through dynamic fields (e.g., user names, deposit amounts, or loyalty tier).
     
   • Performance Tracking and Optimization: Develop performance tracking tools to monitor delivery rates, user engagement, and conversion metrics. Use these insights to optimize messaging strategies, ensuring high performance under all usage conditions.
     
4. Team and Product Development
   
   • Backlog Creation and MVP Definition: You will define the MVP for the CRM service and manage a detailed backlog, prioritizing key features such as segmentation, condition building, and messaging. The MVP should deliver immediate value while laying the groundwork for scalability.
     
   • Team Expansion and Leadership: As the product evolves, you will expand the CRM team, working with backend and frontend developers, UX designers, and data engineers. You will manage cross-functional teams and ensure the roadmap aligns with business objectives.
     

• Stakeholder Communication: Act as the main point of contact for internal and external stakeholders, ensuring alignment on product goals and timelines. You will work closely with engineering, marketing, and customer success teams to ensure the successful delivery of the CRM service.
  

   
  

Benefits

What we offer:

• Working hours from 09:00/10:00 to 17:00/18:00 (Mon-Fri);
  
• Possibility of remote work format;
  
• Interesting work in successful projects;
  

• Timely payment of salaries, official employment, and 24 days of
  

  vacation;
  

• Corporate training;
  
• A friendly team and a pleasant atmosphere without pressure, stress, and other harmful things.