Microblink - Technical Writer

• You are ideally either a technical writer in software, or a software engineer who has written documentation and liked it. Some other good backgrounds would be support engineer who has written documentation, solutions engineer who has written documentation… you get the picture. You have, in your professional life, written things down and made things clear for others, and you enjoyed this process. You also put in care to make the documentation good, not just a necessary evil. Having written a blog is a good but optional signal (the blog doesn’t need to be about techwriting or tech at all). • On the technical side of things, you should be able to code at least a little bit, and be able to read code in various languages. You’d primarily be reading Typescript, Kotlin, Swift, .NET and C++. You don’t need to have worked directly with these languages, but it helps if you’ve worked with programming languages in general before and you can find your way around a codebase. • Must-have skills, due to the nature of the job: • Git: you must have at least a basic working knowledge, and here we also include Git-based workflows on GitHub. • Some command line, ideally a Linux or *nix one like Bash; you need to understand at least the basic operations, how to SSH into stuff, how to change directories, manage permissions, and so on. • On the writing side of things, we’re looking for someone who cares deeply about clarity and helping the reader. Your prime directive is to make things as easy to understand as possible, and to allow the users of our products to integrate them easily. This means switching between writing and editing, and cutting out as much noise as possible. Pull requests that are more red than green are good. We also expect you to extensively use AI for research and prototyping, without introducing slop into the docs. • On the high agency side of things: as this is a diverse, wide role, you should be able to look at your work comprehensively, holistically, and discern what makes sense, and what doesn’t. You should be able to advocate for doing what makes sense without having been told so. Frequently this will mean chasing someone who has the piece of information that you need, or doing investigative work in random git branches to find out when a change was introduced, or something else entirely. • Logistics • This is a full-time remote position, open to candidates in Europe. • Application process • Application process • The process usually takes three to four weeks in total. It involves the following steps: • Take-home assignment • Technical interview • Interview with leadership