Skip to content

RoseBludd/technical-assessment

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Technical Assessment Repository

Welcome to our technical assessment! This repository contains role-specific assessments for various positions. Please follow the instructions below to complete your assessment.

TIME CONSTRAINTS ARE NOT STRICT

Getting Started

  1. Fork this Repository

    • Click the "Fork" button at the top right of this repository
    • This creates your own copy of the assessment repository
  2. Clone Your Fork

    git clone https://github.com/your-username/assessment-repo.git
    cd assessment-repo
  3. Create Your Assessment Branch

    # Replace [role] with: frontend, backend, integration, infrastructure, or qa
    # Replace [your-name] with your name (e.g., john-doe)
    git checkout -b assessment/[role]/[your-name]
  4. Navigate to Your Role's Directory

    • Frontend Specialist: /frontend
    • Backend Specialist: /backend
    • Integration Specialist: /integration
    • DevOps Engineer: /infrastructure
    • QA Engineer: /qa
  5. Read Role-Specific Instructions

    • Each role directory contains a README.md with specific requirements
    • Follow the instructions carefully
    • Complete all required tasks
    • Ensure all tests pass locally before submitting
  6. Submit Your Assessment

    git add .
    git commit -m "Complete [role] assessment"
    git push origin assessment/[role]/[your-name]
  7. Create a Pull Request

    • Go to the original repository
    • Click "New Pull Request"
    • Select your fork and branch
    • Fill out the PR template completely
    • Important: Include your application email in the PR description

Assessment Guidelines

  • Time Limit: 2-4 hours

    • Focus on completing core requirements first
    • Document any additional improvements you would make given more time
  • Code Quality:

    • Write clean, maintainable code
    • Include appropriate comments and documentation
    • Follow best practices for your role
    • Include tests where applicable
  • Submission Review:

    • Automated tests will run when you create the PR
    • Our team will review your code
    • You'll receive feedback through the PR comments
    • Final results will be sent to your application email

Need Help?

  • Check the role-specific README for detailed requirements
  • Use the Issues tab to ask questions (templates provided)
  • Keep questions focused and include relevant context
  • Do not share complete solutions in questions

Assessment Criteria

Your submission will be evaluated on:

  1. Functionality (40%)

    • Completion of required features
    • Passing automated tests
    • Meeting acceptance criteria
  2. Code Quality (30%)

    • Clean, maintainable code
    • Best practices and patterns
    • Error handling
    • Documentation
  3. Technical Decisions (30%)

    • Architecture choices
    • Technology usage
    • Problem-solving approach
    • Performance considerations

Important Notes

  • Ensure your application email matches the one in your PR
  • Keep commits clear and well-organized
  • Document any setup steps or special instructions
  • Don't hesitate to ask clarifying questions
  • Focus on quality over quantity

Good luck with your assessment! We look forward to reviewing your submission.

About

Technical assessment for developer positions

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors