Welcome to Behind the Flame, a series created to showcase our incidentios.
Meet Dylan Rose Muller, Business Development Representative here at incident.io.
Q: What has been your favorite incident.io memory so far?
It's hard to pick just one, but going to LeadDev Berlin was really exciting. I had just joined incident.io the week before and still had absolutely no idea what I was doing. Jumping right into it at the conference, I got to meet a bunch of people from the London office, which was really fun, and overall it was a great learning experience.
Q: What is the value that most resonates with you?
The value that resonates with me most is definitely win together. There is something very genuine about it throughout the company. We're always leaning on each other and learning from each other.
Q: What is your favorite benefit?
My favorite benefit is definitely the first Friday of the month. My commute from New Jersey to New York can be draining, so the extra time to reset is really helpful.
Q: What is your favorite Slack channel?
#random is really fun. We had a lengthy discussion about our favorite MySpace songs, which made my millennial heart very happy. I also like #cold-case-mysteries, where we analyze the team's refrigerators to figure out who's responsible for what's inside. The results are sometimes very unexpected!
Q: What advice would you give to yourself on your first day?
The advice I would give myself is to jump right in and not hold back. At my last job, everyone stayed in their own lane. It's really nice here that everyone is so willing to help out. Don't be afraid to reach out, introduce yourself, and make new friends.
Q: What advice would you give to candidates interviewing?
My advice to candidates is to bring your whole self to the interview. Show us who you are and don't hide any bit of your personality. We are very specific with who we hire here. Everyone's goofy, but also very hardworking. Having that balance is really important; show us that you care and that you're excited.
Q: How would you describe the culture in three words?
I would describe our culture as goofy, hardworking, and authentic.
Q: Why shouldn鈥檛 you work at incident.io?
I don't think incident.io would be a good fit for someone who wants to blend into the background. I've been at larger companies where it's easy to do that - you do what needs to be done and slide right by. incident.io is not like that. This is a place where your ideas will be heard, and you'll bring a lot to the table. Your impact genuinely matters, so be prepared to come in and work really hard.
Q: Which incident.io employee would you want to be stuck in a lift with?
If I were stuck in a lift, I would want to be stuck with either Adrienne or Tom. Adrienne is great at planning, stays super calm, and has really good energy. I think she would already have a plan to get us out. The polar opposite would be Tom; he is a very funny man who has a lot to say. I know that I wouldn't be bored with him until we were rescued.
Q: What does the last Friday of the month mean to you?
The first Friday of the month is a chance to reset. It's time I can spend in New Jersey, seeing friends and family, and tidying up my house, because after a week of commuting, it looks like a bomb went off! It's a much-appreciated rest and reset.
Q: What are you most looking forward to with incident.io this year and beyond?
I am most excited to see where incident.io will go. I joined at a time of great change. I got a new manager [Cameron Nagel], and we hired a ton of new people and new leadership. It's going to be really exciting to see what they roll out and what we're capable of. The roadmap looks amazing, so seeing that all come to fruition is really exciting.
Q: What is it like being part of the BDR team?
Sales is going to be stressful anywhere you go. Every month you have a quota; you hit it and then the next month it's back to zero. So you're constantly working, but I think we have a special way of doing it here. We're really collaborative and supportive of each other. We will do anything to see each other succeed. I also really love the collaboration with marketing. We work together a lot to create things, whether it be email sequences or working on events and event outreach.
Q: How would you describe the day to day as a BDR?
Day-to-day, it's a combination of prospecting into new accounts, working with my account executives and my manager, sending out a ton of emails, making a bunch of calls, and getting to connect with our customers.
Q: What is something that surprised you when you joined?
I think what surprised me was the amount of travel. I was not anticipating traveling so much, but it's been really cool. Since I started, I've been to Berlin, Vegas, and California, and we have some really exciting trips coming up, like Greece for our 2025 company offsite! While I didn't expect to be traveling this much, it's been a great perk of my role.
Q: What has been your favorite customer interaction?
My favorite customer interactions are definitely when we get to meet with them at conferences. Being able to talk with people in person and speak with engineers helps me understand their point of view and how incident.io is really helpful. Especially when we're giving them a demonstration and I see their faces light up as everything starts connecting and they're like, "Wow, this is actually really amazing and really helpful!" To understand that from their point of view makes my life a lot easier.
Q: Why do you think companies need a reliable incident management tool?
I think inevitable at any organization something is going to break and when you think about a massive organization that has things breaking all the time I mean I spoke with a prospect who literally measures their downtime in seconds because every second they are down they're losing a million dollars so the impact of that is actually really wild so in order to prevent you know trying to put out fires left and right making sure you have the right people in the right conversations at the right time so that you can handle it and get back to building products like what engineers really want to be doing. I think having a solution in place like incident.io is incredibly impactful.
