Technical Documentation Engineer
Freelance Contract
Poland - Remote
Rates: Negotiable depending on experience
Ever walked into a codebase (or a mapping system, in this case!) where the knowledge lives in five people's heads and nowhere else and thought, "someone needs to fix this"?
We're looking for a Technical Documentation Engineer to join a team responsible for large-scale map data delivery systems. This isn't a traditional coding role; it's a knowledge architect position. You'll embed yourself across distributed engineering teams (spanning multiple European locations), talk directly to the people who understand these systems best, and turn fragmented, tribal knowledge into clear, structured, accessible documentation.
You'll need to be part investigator, part relationship-builder, and part technical writer; someone who can walk into ambiguity, figure out who to talk to, and drive the work forward without needing detailed instructions.
Responsibilities
- Investigate existing documentation and identify gaps, inconsistencies, and undocumented processes
- Conduct one-on-one discovery conversations with engineers and subject matter experts to extract and validate technical knowledge
- Map out data pipelines, delivery systems, integration flows, and architecture relationships
- Organise fragmented information into logical, standardised, easy-to-follow documentation structures
- Build trust and strong working relationships across distributed teams; this is a people-facing role as much as a technical one
- Reduce reliance on tribal knowledge by creating clear system overviews accessible to the wider organisation
Skills Required
- Strong technical understanding of software systems, data flows, and integration architectures; enough to hold meaningful conversations with engineers
- Proven experience producing high-quality technical/architecture documentation
- Excellent communication skills; confident leading discovery conversations, asking the right questions, and adapting to different audiences
- A high degree of autonomy, curiosity, and ownership; comfortable operating with minimal oversight in ambiguous environments
- A collaborative, approachable style; you'll be joining the team, not consulting from the outside
- Nice-to-have: hands-on development/prototyping experience, familiarity with Java environments, and interest in AI/LLM-assisted documentation or knowledge-extraction tooling
If this sounds like you; or you know someone who thrives on turning chaos into clarity, drop me a message or send over your CV. Let's talk.