How haensel-ams/recruitment_challenge works
Main Components Organization
• Data & Analytics Track
• Business Intelligence (BI_201805, BI_IHC_202109, Account_Manager_BI_202006)
• Data Science (DataScience_202209)
• Machine Learning (ML_201609, ML_201703, ML_201802)
• Engineering Track
• Data Engineering (Data_Engineering_202309)
• Data Quality (Data_Quality_202108)
• DevOps (DevOps_201709, DevOps_201909, DevOps_202006)
• Frontend (FrontEnd_202006)
• Management Track
• Business Development (Business_Development_202310)
• Project Management (Project_Manager_202310)
Component Relationships
a) Use a hierarchical structure:
• Top Level: Overall Recruitment Challenge System
• Second Level: Technical Tracks
• Third Level: Specific Challenge Areas
• Fourth Level: Individual Challenges with their artifacts
b) For each challenge, represent:
• Input artifacts (test data, requirements)
• Expected deliverables
• Technical tools/frameworks involved
Specific Components
For each challenge type, highlight:
Data & Analytics:
• Data flow from source files (.csv, .json) to expected analysis outputs
• PDF documentation connections
Engineering:
• Database components (using challenge_db_create.sql)
• Script execution flow (step1.sh → step2.py)
• Infrastructure components for DevOps challenges
Management:
• Link documentation and presentation materials
• Project lifecycle elements
Interconnections
• Dependencies between challenges where applicable
• Data flow between components
• Relationship between documentation and implementation
Notes for Implementation
• Use clear labeling for all components
• Version numbers from folder names
• Timestamps to show challenge evolution
• Dependencies between challenges
• Input/output relationships
Technical Details
For each challenge type, include:
• Required technical stack (based on README files)
• Data formats (.csv, .json, .sql)
• Infrastructure components (for DevOps)
• Testing requirements