Technical Writer

About the job:

We’re looking for a technical writer / documentation engineer.

This job involves writing technical documentation for several of our products, and this includes instructions for end users using products with a web UI, integration instructions for developers installing our SDKs (in numerous languages), as well as API documentation for our REST APIs, and everything in between.

We use a docs-as-code approach, so you’ll spend most of your time writing Markdown or MDX, hosted in a Git repository, served as a Docusaurus website.

You’ll also dive into our CI operations, write internal documentation when needed, participate in discussions around product development, and advocate for our users. Similarly, you’ll sometimes build tools, and you’ll frequently run the projects that you’re documenting, for example you’ll occasionally integrate SDK code into a mock app just so that you can go through the steps that the end user (developer) would be going through.

You’ll frequently interview developers and product managers, as well as support and solutions engineers. You’ll have maybe one to three meetings a week, and most work is async. You’ll operate within the constraints of release deadlines, so good personal time management is important.

The technical writing team is currently a team of one, so this job would involve taking ownership of a large portion of the documentation. This role is an expansion, not a backfill. There is a large backlog as well as a docs roadmap that you’ll take part in shaping.

For an overview of how the products and existing docs look, see docs.microblink.com.

What we’re looking for:

• 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).
• We’re looking for good technical skills, good writing skills, and high agency.
• 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

The process usually takes three to four weeks in total. It involves the following steps:

Screening call

• Take-home assignment
• Technical interview
• Interview with leadership

A little bit about us:

Microblink is the Identity Intelligence OS that establishes Know Your Actor: control over people and agents, how risk is assessed, and how decisions are made across digital journeys. Built for an adversarial AI era, Microblink replaces static verification with continuous identity control. As the only solution spanning IDs, biometrics, and payment cards, Microblink delivers a real-time command center where signals, policies, and decisioning can be calibrated with granular precision.

Companies use Microblink to adapt faster than fraud, optimize outcomes over time, and enforce trust at scale across onboarding, authentication, and every moment in between. In 2025, Microblink processed 2.9 billion identities across 195+ countries. Its proprietary Fraud Lab generates 100,000+ images monthly for training and testing models, achieving 100% deepfake detection in DHS-powered testing.

How can you join us?

If this role intrigues you, do not hesitate to hit the apply button and send us your resume. We are excited to meet talented people even if you don’t feel that you match 100% of the requirements.  So don’t let that discourage you, get in touch with us and we promise to get back to you.

We prohibit discrimination of any kind based on race, color, sex, religion, sexual orientation, national origin, disability, genetic information, pregnancy, or any other protected characteristic as outlined by federal, state, or local laws, as well as our internal policies and culture.

For detailed information on how we process personal data, please read our Privacy Policy https://microblink.com/privacy-policy/ or reach out to our Data Protection Officer at privacy@microblink.com.