Introducing Abnormal Engineering Stories - Episode #1 - Abnormal Security

Introducing Abnormal Engineering Stories - Episode #1

As VP of Engineering here at Abnormal Security, I’ve had numerous conversations with our team, VCs, and external engineering leaders about the challenges of building and leading engineering teams. Building applied machine learning products at scale requires solving a wide range of challenges: hiring great engineers, getting customer feedback, building & iterating on machine learning data pipelines… the list goes on and on. I’ve had the privilege to be part of engineering leadership teams at established mature companies like Twitter, as well as startups like Abnormal Security that are rapidly evolving & adapting. Strategies and tactics that are effective at one type of company frequently don’t work or apply to others. After mutually sharing stories and tips of what’s working for startup engineering teams, we realized that many of these conversations could be interesting to the broader community, and aimed to start a podcast series to share.

In Abnormal Engineering Stories, we will interview engineering leaders from a variety of companies to share our stories, perspectives, and strategies on how we operate our teams, products, and engineering systems. We’ll focus on how we’ve translated engineering principles and ideas into pragmatic solutions & processes at our companies.

We hope you’ll enjoy the series of conversations! Please do subscribe on Apple, Spotify, or Google Podcasts.

To launch the series first up is a conversation with Dobromir Montauk, Head of Engineering at Doxel. As an ex-Twitter engineering leader, moving to a leadership role at an early-stage startup required an adaptation of leadership principles and strategies.

I hope you enjoy hearing Dobromir and I expand on some of our lessons joining a startup, including:

  • Focusing & identifying the real work to be done
  • Rolling up your sleeves and getting to work.
  • Implementing a customer-driven product discovery and product development lifecycle.
  • And most importantly, how to learn from your mistakes — come hear us share about some of the mistakes we’ve made along the way.

Related content