I was excited to write another post for opensource.com:
It’s an extension of a twitter rant I went on a bit ago, about how important it is to know certain things about interviewing as a technical writer, but no one is teaching them, from what I can tell.
- What kind of samples should you offer?
- What is ethical to use as a sample?
- What is a reasonable (and unreasonable) writing test?
- How do you talk about team projects or work for hire?
I’m already in discussions with the team about a follow-up, based on my New Sheriff In Town talk. That one will cover how to walk into a new position and figure out what to write first.
If you’re interested in more content on interviewing, Carol Smith and I are putting the finishing touches on a workshop about all the not-code parts of a technical interview. You’ll be able to read more about that in The Recompiler soon, and of course, I’ll post about it here.
Minneapolis DevOps Meetup