Skip to content

Test tasks for frontend (js in the main) developers from different companies

Notifications You must be signed in to change notification settings

vvscode/js--test-tasks

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

32 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Test tasks for frontend (js in the main) developers from different sources


Repo is not supported any more.

I recommend you to check https://github.com/Hexlet/ru-test-assignments from the Hexlet team


Fill free to add your tasks / tasks you've met in your career


Structure of the repo:

.
├── README.md
├── any-some-test-task-from-company-A
│   ├── README.md
│   └── task-dir
├── junior-some-test-task-from-company-A
│   ├── README.md
│   └── task-dir
├── middle-some-test-task-from-company-A
│   ├── README.md
│   └── task-dir
├── senior-some-test-task-from-company-A
│   ├── README.md
│   └── task-dir
├── middle-some-test-task-from-company-B
│   ├── README.txt
│   └── task-dir
└── any-some-test-task-from-company-C
    ├── README.txt
    └── task-dir

Each task placed into separate directory ( with meaningful name, starting with expected level / any word ). Inside should be placed readme file (with notes about the task, like level, source of the task, technologies stack, description for the position ) and one more directory task-dir with the task itself.

It will be nice if you translate (or/and duplicate) all descriptions in English.

There is an any-a-very-basic-example-test-task-from-company-A directory as example for adding test task.

Related links:

About

Test tasks for frontend (js in the main) developers from different companies

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •