# 🎯 Live Coding Session: Task Scoring Guidelines and Framework ## 📋 Overview This document outlines the scoring criteria, task-specific points distribution, and scoring framework for both **junior** and **senior developers**. The aim is to evaluate participants fairly while reflecting their skill levels and seniority. The **final score** will serve as an **indicator** to assist in the **subjective assessment** at the end, ensuring a holistic evaluation of each participant. --- ## Part 1: Guidelines for Criteria ### 1. Correct Implementation (40-45% of points) - **What It Includes**: - The code meets the problem requirements and works as intended. - Handles edge cases appropriately. - Produces accurate outputs for given inputs. - **How to Score**: - Full points: If the solution is correct and handles edge cases. - Partial points: If the solution works partially or misses some edge cases. - No points: If the solution does not work at all. --- ### 2. Code Quality (20-25% of points) - **What It Includes**: - Follows best coding practices (e.g., DRY, modularity). - Code is free from bugs or logical errors. - Code is maintainable and scalable. - **How to Score**: - Full points: Adheres to best practices and is bug-free. - Partial points: Minor issues with structure or bugs. - No points: Major issues with structure or buggy code. --- ### 3. Efficiency (15-20% of points) - **What It Includes**: - Solution is optimized in terms of time and space complexity. - Avoids unnecessary computations or redundancy. - **How to Score**: - Full points: Highly efficient solution. - Partial points: Some optimization but could be improved. - No points: Inefficient or brute force solution. --- ### 4. Thinking/Thought Process (10-15% of points) - **What It Includes**: - Logical reasoning and problem decomposition. - Creativity in approach or unique solutions. - **How to Score**: - Full points: Clear and structured thought process with creative solutions. - Partial points: Basic reasoning but lacks creativity or clarity. - No points: Poor reasoning or unclear thought process. --- ### 5. Articulation of Ideas (10-15% of points) - **What It Includes**: - Clear understanding of the problem and explanation of the solution. - Ability to justify decisions and communicate ideas effectively. - **How to Score**: - Full points: Clear, logical, and concise articulation. - Partial points: Adequate explanation but missing depth or clarity. - No points: Poor or no explanation of the approach. --- ### 6. Code Readability (5-10% of points) - **What It Includes**: - Code is clean, organized, and easy to read. - Variables are named meaningfully, and comments are used appropriately. - **How to Score**: - Full points: Highly readable and well-organized code. - Partial points: Some readability issues but understandable. - No points: Messy or hard-to-read code. --- ### 7. Timely Completion (5-10% of points) - **What It Includes**: - Task is completed within the allocated time. - **How to Score**: - Full points: Completed on time or early. - Partial points: Completed slightly after the deadline. - No points: Task not completed within the time limit. --- ## Part 2: Task Points Table ### Junior Developer Tasks | **Task** | **Correct Implementation** | **Code Quality** | **Efficiency** | **Thinking/Thought Process** | **Articulation** | **Readability** | **Timely Completion** | **Total Points** | |------------------|----------------------------|------------------|----------------|-----------------------------|------------------|-----------------|-----------------------|------------------| | **Task 1 (20)** | 8 | 4 | 2 | 2 | 2 | 1 | 1 | 20 | | **Task 2 (20)** | 8 | 4 | 2 | 2 | 2 | 1 | 1 | 20 | | **Task 3 (25)** | 10 | 5 | 3 | 3 | 2 | 1 | 1 | 25 | | **Task 4 (30)** | 12 | 6 | 4 | 4 | 2 | 1 | 1 | 30 | | **Task 5 (25)** | 10 | 5 | 3 | 3 | 2 | 1 | 1 | 25 | | **Total Points** | | | | | | | | **120** | --- ### Senior Developer Tasks | **Task** | **Correct Implementation** | **Code Quality** | **Efficiency** | **Thinking/Thought Process** | **Articulation** | **Readability** | **Timely Completion** | **Total Points** | |------------------|----------------------------|------------------|----------------|-----------------------------|------------------|-----------------|-----------------------|------------------| | **Task 1 (20)** | 6 | 5 | 3 | 2 | 2 | 1 | 1 | 20 | | **Task 2 (20)** | 6 | 5 | 3 | 2 | 2 | 1 | 1 | 20 | | **Task 3 (25)** | 8 | 6 | 4 | 3 | 2 | 1 | 1 | 25 | | **Task 4 (30)** | 10 | 8 | 5 | 4 | 2 | 1 | 1 | 30 | | **Task 5 (25)** | 8 | 6 | 4 | 3 | 2 | 1 | 1 | 25 | | **Total Points** | | | | | | | | **120** | --- ## Part 3: Scoring Framework ### Junior Developer Scoring Ranges | **Total Points (Out of 120)** | **Outcome** | **Description** | |-------------------------------|-------------------|---------------------------------------------------------------------------------| | **0–40 points** | **Strong Reject** | Lacks foundational skills; needs significant improvement in coding and problem-solving. | | **41–60 points** | **Weak Reject** | Some effort shown but inconsistent understanding or execution of tasks. | | **61–80 points** | **Weak Accept** | Meets basic expectations with room for growth in quality, efficiency, and clarity. | | **81–120 points** | **Strong Accept** | Excellent grasp of foundational skills, clear articulation, and problem-solving. | --- ### Senior Developer Scoring Ranges | **Total Points (Out of 120)** | **Outcome** | **Description** | |-------------------------------|-------------------|---------------------------------------------------------------------------------| | **0–60 points** | **Strong Reject** | Major gaps in advanced coding, problem-solving, or communication skills. | | **61–80 points** | **Weak Reject** | Shows effort but falls short in critical areas like optimization or quality. | | **81–100 points** | **Weak Accept** | Meets expectations but could improve in efficiency, scalability, or clarity. | | **101–120 points** | **Strong Accept** | Exceptional performance in all areas; demonstrates senior-level expertise. | ---