We're looking for a new part-time technical editor to join the Java editorial team.
The role involves working with authors, reviewing their new article drafts, and providing helpful feedback.
The goal is to make sure that the article hits a high level of quality before it gets published. More specifically – articles should match the Baeldung formatting, code, and style guidelines.
Beyond formatting and style, articles should be code-focused, clean, and easy to understand. Sometimes an article is almost there, but not quite – and the author needs to be guided towards a better solution or a better way of explaining some technical concepts.
The Right Candidate?
First – you need to be a developer yourself, working or actively involved in the Java and Spring ecosystem. All of these articles are code-centric, so being in the trenches and able to code is instrumental.
Any experience with Scala, Kotlin, or Linux is a plus as well.
Second – and it almost goes without saying – you should have an excellent command of the English language.
Budgets and Time Commitment
You're going to be working with 6-7 authors to help them with their articles (you can choose to work with fewer or more authors depending on your availability).
An article usually takes about two rounds of review until it's ready to go. All of this usually takes about 30 to 45 minutes of work for a small to a medium article and can take 60 minutes for larger writeups.
The budget for each article is based on your editor level and the number of words.
Here are some typical budgets used by editors:
- Level 10 – 750 words – 55$
- Level 10 – 1000 words – 60$
- Level 14 – 750 words – 60$
- Level 14 – 1000 words – 65$
Your level is determined by internal metrics such as response time and feedback from the senior editors, and the max level is 20. The average earning is around 600$/month.
If you're interested in applying, please send a message to [email protected] with your details and a link to your LinkedIn profile.