Suggestions for tech writer role description #1392
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reference to #1376
The interview process is extensive as it is now. I think we should condense it just a tad for this role.
In my opinion, you can tell a lot about a technical writer early in the process. You'll be able to see whether they write well from looking at their resume and samples, and you'll also see indicators of attention to detail, organization, and general knowledge of/experience with the field. I don't think we need 2 assessments for this reason.
The assessment (for me) would be more about personality, listening comprehension, and seeing their approach to writing and processes. Also, not sure what the goals are for the CTO/CEO portion, but I made a general suggestion for how I think it should look.