-
Notifications
You must be signed in to change notification settings - Fork 61
Minor Tweaks based on Issue 63 #169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
vgvassilev
merged 1 commit into
compiler-research:master
from
QuillPusher:minor_tweaks_for_issue63
May 4, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
--- | ||
title: "Careers at Compiler Research Organization" | ||
layout: textlay | ||
excerpt: "Openings" | ||
sitemap: false | ||
permalink: /careers | ||
--- | ||
|
||
# Open Positions | ||
|
||
We are always looking for new group members with passion, talent, and grit! | ||
|
||
# Student Opportinuties | ||
|
||
If you are interested in working with us for a fixed period of time, there are | ||
number of programs which offer scholarships: | ||
|
||
* [Google Summer of Code](https://summerofcode.withgoogle.com/how-it-works/) | ||
* [IRIS-HEP Fellow Program](https://iris-hep.org/fellows.html) | ||
* [CERN Students Programs](https://careers.cern/students) | ||
|
||
# Just looking for a cool spare time project? | ||
|
||
Please visit our [open projects](/open_projects) page. | ||
|
||
# Candidate Guidelines | ||
|
||
If you have interest in working on the project there is a list of things to do in order to maximize your chances to get selected: | ||
|
||
1. Contact the mentors and express interest in the project. Make sure you attach your CV; | ||
2. Download the source code of the project, build it and run the demos; | ||
3. Start familiarizing yourself with the codebase; | ||
4. If you have questions you can always contact a mentor. | ||
|
||
## Candidate Evaluation | ||
|
||
The mentors are interested in working with all candidates but unfortunately not everyone can be selected. There are a few tasks which give bonus points to candidate's application: | ||
|
||
- Submit a valid bug -- demonstrates that the candidate has completed step 2 and 3 from the previous section. | ||
- Fix a bug -- demonstrates the technical skills of the candidate and shows he/she can work independently on the project. The mentors can suggest looking into these good first issues. Fixing one issue may be enough to become a successful candidate. | ||
|
||
## What not to do and will give you negative points | ||
|
||
1. Contact the mentors with very generic requests such as "Please guide me through the X". You need to show that you have spent time on the problem. Such emails prove otherwise. | ||
2. Contact each mentor individually. You should use "reply-all" feature of your email and discuss openly with your prospective mentors the project. | ||
3. Send the same email to express interest on multiple projects. If you do not invest time to write separate emails for the different projects why the mentors should? | ||
4. Comment under opened issues with generic requests as described in 1. You need to show that you can work on bugs and use bug trackers. That shows the opposite. | ||
5. Use LLM-generated content. You should prove to yourself that project is appropriate for you otherwise we will hire the LLM instead of you. | ||
6. If any of the criteria is met to some degree mentors are free to tell you so or even not respond to your requests. We understand that may seem harsh, however, you should appreciate other's time at least as much as they appreciate yours! | ||
|
||
Good luck! |
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.