A complete application in a minute
Tailored resume and cover letter, ready to send.
Neat is seeking a Technical Documentation Engineer based in Oslo to own all customer-facing technical documentation on our Support site. You will test firmware, verify behavior across environments, and work with R&D to ensure accuracy from test to publication.
You will join a hands-on team focused on turning complex engineering work into reliable, end-user guidance. This hybrid role requires proximity to R&D and a proactive mindset to shape documentation practices.
Based in Oslo, Norway.
Neat brings people together with beautifully simple, versatile video devices and experiences. By minimizing the physical and virtual divide, we enable everyone to feel more connected, present and understood, however they prefer to work. We aim to make our technologies so intuitive that terms like "in-office" and "remote" will seem obsolete in five years. Neat's pioneering portfolio addresses the needs of today's workplace and natively supports Microsoft Teams, Zoom, Google and a range of compelling business apps.
We are looking for a Technical Documentation Engineer to help build Neat's new documentation team. Sitting within Customer Experience, you will own all customer-facing technical documentation on our Support website, from first test to final publication. As one of the team's founding members, you will help shape how knowledge flows from R&D to the customers and partners who rely on our products every day.
Technical documentation at Neat is about turning complex, fast-moving engineering work into guidance people can trust. That means understanding how a feature really behaves before explaining it, anticipating the questions customers will ask, and making sure every guide, release note, and troubleshooting article is accurate on the day it goes live.
This is a hands-on role. You will test new firmware and features on real devices, across environments and connectivity conditions, and stay close to R&D: asking the questions nobody else thinks to ask, following up on unclear behaviour, and turning what you learn into documentation our customers and our own teams can rely on.