-
Notifications
You must be signed in to change notification settings - Fork 27
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
Initial draft of the full stack engineer job description #114
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before we merge and make this public, we will figure out the hiring process and document it in the relevant places. I scheduled some time with @lguychard and @aidaeology for this on Friday.
Co-authored-by: Tomás Senart <[email protected]>
Co-authored-by: Tomás Senart <[email protected]>
Co-authored-by: Tomás Senart <[email protected]>
Co-authored-by: Nick Snyder <[email protected]>
@aidaeology: Anything blocking merge? |
@tsenart waiting for approval from reviewers :) |
@aidaeology: Should we change the interview process defined here to match what we came up with? |
Co-authored-by: Loïc Guychard <[email protected]>
Co-authored-by: Loïc Guychard <[email protected]>
Co-authored-by: Loïc Guychard <[email protected]>
Modified to match the new full stack interview process.
|
||
## Interview process | ||
|
||
1. You [apply here](TODO). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs a link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added to TODO here: https://github.com/sourcegraph/interviews/pull/136#issue-468856668
WIP job description for a full stack engineer role. The goal is to create a balance between frontend/backend experience that does not heavily focus on a language or particular framework but instead looks to asses whether the software engineer has strong capabilities and general experience to work on any part of the stack using various types of technologies.
The interview process section has not been updated yet, coming soon.