Write a general CV
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- content
Research direction
Start by reading the linked CV guide and completing its checklist. Create the general CV in a Google Doc, run it through the automated CV reviewer, and act on its feedback; ask for a review in #cyf-profile-review, clearly identifying it as a reusable base CV. Done means feedback has been addressed and the CV has been iterated until it is great.
Written by the indexing model from the issue text.
Description
When applying for jobs, you should tailor your CV to the specific job you're applying for. But you generally don't make a brand new CV from scratch for every application. It's useful to have a base CV with most of the information, which you can adjust.
Prepare a CV in a Google Doc which targets the kind of job you're hoping to apply for in the future (probably a software engineering job).
Make sure to read the CV guide and follow its instructions, including checking the checklist.
When your CV is ready:
- Run it through our automated CV reviewer and act on its feedback. If you're not sure about any of the feedback, reach out on Slack in #cyf-profile-review.
- After you've acted on that feedback, ask someone to review it on Slack in #cyf-profile-review. Make clear in your request that this is a generic CV to use as a base for future applications.
Respond to any feedback received, and keep iterating until your CV is great.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Tools
-
🏕 Priority Mandatory 📅 Sprint 4 Core Module-Tools Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 70/100
CodeYourFuture/Module-Tools#581 ·
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 📅 Sprint 4 Module-Tools Recurring Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 58/100
CodeYourFuture/Module-Tools#544 ·
-
Install a JDK Open🏕 Priority Mandatory 📅 Sprint 4 Core Module-Tools Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
CodeYourFuture/Module-Tools#480 ·
-
🏝️ Priority Stretch 🐂 Size Medium 📅 Sprint 5 Module-Tools Optional Submit:PR
Difficulty 3/5 1-3 hours Newbie friendliness 35/100
CodeYourFuture/Module-Tools#179 ·
-
Prep Exercises Open🏕 Priority Mandatory 📅 Sprint 5 🦑 Size Large Core Module-Tools Submit:PR
Difficulty 3/5 1-2 days Newbie friendliness 65/100
CodeYourFuture/Module-Tools#178 ·
All issues in CodeYourFuture/Module-Tools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#17425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·