|
|
@@ -25,7 +25,7 @@ Otherwise, your submission should satisfy the Backend Candidate goals.
|
|
|
|
|
|
## Django Code Assessment Criteria
|
|
|
|
|
|
-Used for Backend and Fullstack role code assessments.
|
|
|
+Used for Backend and Fullstack role code assessments. All submissions will be evaluated based on these base criteria, and specific roles might have some additional points to consider.
|
|
|
|
|
|
* Ability to run the project. Reviewers should be able to run the project locally using standard processes like `manage.py` or Foreman.
|
|
|
* Tidiness of the source code repository. No stray files like logs, virtual environments, databases, etc.
|
|
|
@@ -36,6 +36,10 @@ Used for Backend and Fullstack role code assessments.
|
|
|
* Cohesiveness of the project. No missing files, broken styles, stub features, etc.
|
|
|
* Submission process adherence. Submission should be a pull request. Commits should be atomic with clear messages.
|
|
|
|
|
|
+### Backend Engineer Focus
|
|
|
+
|
|
|
+* Admin experience of managing albums. We will be looking at how effectively someone would be able to manage albums, tracks, and playlists through the admin. Admin users will want to update details, re-order tracks, and so on.
|
|
|
+* Strength of the data model. It is important for data to be modeled in a way that supports robust APIs and useful admin views, and also enforces domain rules.
|
|
|
|
|
|
## Developing
|
|
|
|
