
About me
This story starts with Maaike at the age of 14, who decided to become an engineer.I’m still not 100% sure what convinced me so deeply about that choice, but I took the leap. When I reflect on it in this present moment, it feels like I came to understand how the world works (from a scientific and technical perspective). I was introduced to electricity, electronics, and mechanics, which fed my wide range of interests. But what really excited me was chemistry.
Four years later, I started the engineering program in Ghent. Studying was something I mastered wonderfully. My notes were highly sought after: (almost) maniacal summaries in which the essential points were neatly arranged. Colours, tables, and diagrams clarified. Little did I know that the first seed to become a technical writer had germinated.
I graduated as a Master of Chemical Engineering and started my nine-year career at Onsemiconductor (later BelGaN). As a process engineer, I learned the tricks of wafer manufacturing. My inner perfectionist celebrated the responsibility of mastering complex processes in an even more complex context. All that complexity demanded clear language and clear procedures for the people on the shop floor. And my inner technical writer continued to grow.
The BelGaN story sadly ended in 2024, and I started looking for a new challenge. My career coaches guided me toward the option of becoming a technical writer. I got to know Flow and felt at home the first time I stepped into their office. The rest is history.
The quick-fire question round
Flow: Software or hardware documentation?
With my experience as a hands-on engineer in mind, hardware documentation feels like the safe option. I’m curious about what documenting software will bring.
Flow: Internal or end-user documentation?
The way I see it, internal documentation has a shorter feedback loop, and the writing process can be more attuned to the customer. In end-user documentation, I’d value the completeness of a document
Flow: Agile or Waterfall development?
I like the flow of Agile development and the predictability of waterfall development. A real yin-yang question, if you ask me.
Flow: Time travel to the past or to the future?
To the future, please. I wouldn’t want to risk altering history, and I’m curious to witness how humanity evolves and adapts to the challenges we face today.
A glimpse of the future
I’m eager to see what this new step will bring, and I look forward to learning from the team and developing into a fully grown technical writer.