What are you looking for?

Developer Relations at Camunda: Who, What, Where, Why, and How?

  • Blog
  • >
  • Developer Relations at Camunda: Who, What, Where, Why, and How?

If you’ve been part of the Camunda community for a while, you’ve likely interacted with Niall, Mauricio or Josh on the Camunda and Zeebe forums. You’ve probably met Bernd at a conference or two in the last few years. And if you’re one of our awesome Camunda meetup organizers, you’ve definitely worked with Luca to make sure your event is a smashing success. But did you know they’re all part of the larger Developer Relations (or DevRel) department at Camunda?

Escape Room

Perhaps we should start by explaining what Developer Relations is. At its foundation, the purpose of Developer Relations is to build relationships with and enable our technical communities. Still scratching your head? Here’s how it works:

To the company, we represent the community.
To the community, we represent the company.

Similar to Public Relations or Government Relations, we build relationships with a specific audience, conveying important information to them, while at the same time, accepting opinions and feedback that we then convey back to our company. (Shoutout to Yoshi Yamaguchi for the great analogy!)

So how does this translate to Camunda, and more importantly, what does it mean for you? It means that while we’ve always had your best interests at heart (and that will never change!), we now have a team officially dedicated to making sure that your feedback is heard and that you have the best experience possible as you’re using our products.

In fact, our mission sums it up nicely:

The Camunda Developer Relations team exists to serve the Camunda developer community, from internal employees to Open Source contributors, Enterprise customers, and the broader tech community.

It is our goal to provide opportunities for developers to be more successful by making them aware of our solutions, enabling them to be successful through great experiences, and fostering a culture of collaboration.

What does this mean for you going forward?

  • We’ll continue to provide awesome content for you in the form of tutorials, getting started guides, blog posts, sample applications and more.

  • We’ll be asking for your feedback on new features, as well as reaching out to see how your experience has been as you get up and running with our products.

  • We’ll be more proactive about discovering what awesome projects you’re creating in your own time that use Camunda, Camunda Cloud, and bpmn.io, and partnering with you to promote them on a variety of channels.

Most importantly, we’re 100% invested in helping you be successful in using Camunda products as well as in your overarching career as you explore new technologies and possibilities. By making you aware of the products and services we have to offer, enabling you to get the most out of those products through content and excellent experiences, and helping you to engage and collaborate with other Camunda community members, we help you be the best you can be.

Why are we so invested in this? As a team that’s driven by helping others, making sure you have a great experience with anything and everything related to Camunda is what gets us excited to come to work everyday!

So where does this work take place and who makes up the DevRel team? We’re spread out all over the world, quite literally, from Brisbane to London, Berlin, San Francisco, and Seattle.

Niall Deehan, Mauricio Salatino, and Josh Wulf are our three Developer Advocates, focused on creating content, sample applications, and demos for Camunda BPM and Zeebe. Luca Buchholz is our Community Marketing Manager, working with those of you who run Camunda meetups around the world. Danielle Andrist is our Program Manager, and a new addition to the team, concentrating on building some processes and tooling to an already great foundation.

Bernd Ruecker, as Co Founder and Chief Technologist of Camunda, is our honorary member of the team. He’s still delivering great content in the form of blog posts and conference talks around the world.

And I’m Mary Thengvall – Director of the team. I’m building a longer-term strategy and vision around Developer Experience, Developer Advocacy, and Developer Community at Camunda (keep an eye on my blog for more information about that soon!). It’s my pleasure to guide these awesome Developer Relations professionals and work across teams at Camunda to make sure we’re creating the best products for you, our community. After all, that’s what it’s all about!

Want to get in touch with us?
Great! We love hearing from you. You can reach our Developer Advocates on Twitter, browse our personal websites where we share our favorite hacks and check out our projects on GitHub:


Photo of Niall Deehan
Niall's Twitter account
Niall's GitHub account


Photo of Josh Wulf
Josh's Twitter account
Josh's GitHub account
Josh's website


Avatar for Mauricio
Mauricio's Twitter account
Mauricio's GitHub account
Mauricio's website


Photo of Mary Thengvall
Mary's Twitter account
Mary's GitHub account
Mary's website


Photo of Bernd Ruecker
Bernd's Twitter account
Bernd's GitHub account
Bernd's website

Plus you can connect with the team at CamundaCon Live this April 23rd and 24th. I’ll be moderating our panel discussion – Process Automation in 2030: Where are the humans?; and Bernd will be presenting Microservices Orchestration and Integration using Workflow Automation. It’s completely free to attend and will bring our Camunda Community together from all corners of the globe – I hope to see you there.

Interested in digging deeper into the concept of Developer Relations?

Here are a few other resources for you:

Try All Features of Camunda

Related Content

Build software that meets needs while still protecting the environment for future generations.
Want to go to CamundaCon? Here's how to convince your boss you should be in New York this October.
How green energy company Vandebron overcame complexity, the need for flexibility, and scalability issues through Camunda-powered process orchestration.