---
# System prepended metadata

title: Case

---

# Case

Imagine that you are joining as a Senior engineer at Zehitomo.

Your first mission is to develop a new functionality whose release date is set to 3 months from now. Please describe the process, system and tech architecture and collaboration with stakeholders from now to the release.

## Requirements
- Administration interface for service providers (eg. flower shop, coiffeur, etc.)
    - Create/edit/publish/disable service opening
    - Assignes budget for advertisement campaings (=> improving ranking position in service search result page)
    - Track requests/revenue and ad campaigns related to service openings
- Please imagine that you will develop an independent functionality (=> development from scratch), but the functionality might rely on existing APIs

## Organization & team structure
- Sales & Growth organization
    - Growth team
        - Strategy for growing the business
    - Success team
        - Ineracts with existing customers
- Product & engineering organization
    - Manager
        - Allocates resources & budget, hiring, people management
    - Product Owner
        - Translates product roadmap into milestones/deliverables
        - Prioritizes deliverables
    - Tech lead
        - Responsible for all tech related decisions (incl. dev process)
    - Domain expert (SEO, B2B business)
        - Gives advice/help related to domain knowledge
        - Establish 
    - Technical Product manager
        - Translate requirements
    - Engineers
        - 5 Backend and 3 Frontend engineers
        - Work in small teams (3-4 person) based on assigned KPI or project
    - QA
        - Validate release, testing


## Tech stack

- Node.js
- Mongo DB
- React
- AWS

# Solution

- Users
 -Roles required to access
    - End Service Provider
        
        - Create
        - Edit
        - publish (any additional approvals required and workflow if any take forward)
        - disable
    

## System architecture

Frontend

API layer

Service Components (business logic handler for message store)


Aggregator (Mongo DB)

Aggregator (to track revenue)





## Process/Schedule/Milestones

6 Sprints (2 week per Sprint)
Built the unit level testing for each of the components being built
Sprint 1
    basic building blocks of the componets  and built intercation
    Create event models and identify the commands and events thar are required and get the feedback
    Analyse the different tools and come up with best reporting tools to easily create the dashboarbs

Sprint 2 
    Focus on implementation of the service registaraion command handlers
    in parallel built the front end and the apis and read models

Sprint 3
    Focus on implementation of the revenue radiotor models
    and populate the data points that are required to push

Sprint 4


