Review a fellow trainee's CV

Open
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
content

Research direction

Open the #cyf-profile-review Slack channel and choose a CV that has not been reviewed. React to the post, then add positive and constructive feedback as comments on the file or thread, including whether you would call the person for an interview and why. Done means commenting the reviewed CV link here and adding a screenshot of your Slack reaction.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Data-Groups Submit:Issue
Learning Objectives
  • Gain exposure to other people's writing styles
  • Give constructive feedback to colleagues
Why are we doing this?

Everybody's CV will be slightly different. When you read someone else's CV you will see examples of this - some will be things you like, some will be things you don't like. In this exercise you will give both positive and constructive feedback on a colleague's CV.

Read one of the CVs that hasn't been reviewed yet on the #cyf-profile-review and give feedback on it.

Make sure you react to the post so people know you are on it (i.e. two eyes when looking, done when finished), and add the feedback as comments directly on the file or the thread.

When reading the CV, use your interviewer hat. Would you call this person for an interview? In ether answer, yes or no, make sure you give them a clear example as to why you think this way.

Maximum time in hours

1

Submission & Review
  • Add the link to the CV doc you reviewed as a comment on this issue.
  • Add a screenshot of you reacting to the message on the #cyf-profile-review Slack channel.
Dominant language
JavaScript
Stars
1
Forks
327
Avg merge
3d 7h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Data-Groups

All issues in CodeYourFuture/Module-Data-Groups

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.