Julian Simon
I work in product marketing for technical B2B products. I like getting close to the detail, building a clear picture, and working out what should happen next.
I like to start by getting close to the thing itself: how the product works, what customers actually struggle with, what the market is doing, what sales is hearing, and what the product team knows that may not yet have made it into the story.
The useful part is rarely one piece of information on its own. It appears when product, market, customer, technology, and commercial reality start to line up. I enjoy building that picture, especially when the subject is unfamiliar or still taking shape.
That also means staying in touch with different teams. I like being close to product, marketing, and revenue at the same time, understanding what each is seeing, and helping useful information travel between them. Some of the most important connections are not between abstract ideas, but between people who hold different parts of the same picture.
Understanding only matters if it changes what happens next. Sometimes that means positioning or a go-to-market plan. Sometimes it is product feedback, a sales conversation, an explanation for a customer, or simply making sure the right person knows the right thing at the right time.
I’m based in Cologne, Germany. I studied English and History and, for quite a while, assumed I would become a teacher.
In hindsight, the through-line is fairly obvious. I like learning a subject properly and then finding the language that makes it clear to someone else, whether that means explaining a historical argument or figuring out how to talk about a deeply technical product.
I’ve worked in mobility technology since 2019, starting while I was still at university. Along the way, I’ve worked across technical writing, product management, and product marketing. Today, I’m a Senior Product Marketing Manager working with B2B technology across telematics, connectivity, and asset protection.
That mix suits me. The products are technical, the markets are complex, and the useful answer is rarely contained within one team.
Technical products rarely suffer from a lack of features. More often, the challenge is building a shared understanding of why those features matter. I like getting close enough to a product to explain not just what it does, but why someone should care.
I like go-to-market work when it starts well before launch and continues after it. That means spending time with product teams and early customers, helping shape what is being built, working closely with revenue teams, and staying involved when a product reaches real customers.
I’ve led substantial go-to-market motions into new markets and segments where there was no existing internal playbook to fall back on. Those tend to be the projects I enjoy most.
I absorb information quickly and genuinely enjoy unfamiliar territory. Give me a new product, market, customer problem, or technical system and my first instinct is usually to understand as much of it as I can.
The interesting part comes afterwards: seeing how the pieces affect one another and spotting connections that are easy to miss when everyone is looking only at their own part of the picture.
I work best with a lot of agency. I like taking responsibility for ambiguous work, giving it structure, and keeping the right people connected around it.
I have core responsibilities, of course, but I don’t think particularly rigidly about role boundaries. If something matters, I can contribute, and getting involved would help, I generally will.
AI has become a practical part of how I work: for learning, research, prototyping, writing, and removing some of the repetitive work around the edges.
I also enjoy helping other people understand it, particularly the difference between something that looks impressive in a demo and something that is actually useful on a Tuesday afternoon.
If you’d like to talk about a product, a market, or something else interesting, feel free to say hello.