So You’re Ready for Your Next Adventure

4 MIN READ
MIN READ

LogDNA is now Mezmo but the insights you know and love are here to stay.

I just celebrated my first anniversary at LogDNA, so I thought it fitting to write my first LogDNA blog post.

The year marker seems like the right time to reflect on some things that I’ve learned along the way and give a taste of our unique culture. In the tech industry, it’s not uncommon for people to seek new opportunities to grow their career, so this blog post is also meant to share a few things that I look for in new roles with the hope that it helps people who are ready for a similar change. While I’m a marketer by function, I think these tips can apply to people in any discipline in any industry. 

Everyone has their own calculus, their own checklist of the most important things that they look for in assessing a new opportunity. For me, I look for three things: team fit, organizational health fit, and career fit.

Look for team fit 

It might seem trite, but it’s true: the most important decision factor when considering a new opportunity is the team. Simply put, your team is everything. The team can make a challenging experience fun (we’re doing something big that neither of us could achieve alone) or it can make the job dreadful.

Still, assessing the team fit during an interview process is complicated. Like dating, everyone’s presenting themselves in the best possible light. The candidates. The interviewers. Everyone. Here are a few things that I looked for at LogDNA:

  • Do team members share a set of core values and a common purpose that unites them? At LogDNA, our core purpose -- why we exist -- is powerful: to empower people who build solutions that shape the world. We look through this lens with everything we choose to do. And, we have a set of values that meaningfully describe how we behave with each other. 
  • Do team members seem like fellow builders? Especially at a startup that is in scale mode, I look for a team that shares the aspiration of building something new and disruptive. This doesn’t just mean product. For instance, the marketing team at LogDNA is building a distinctive, vibrant brand and is finding new paths into a market dominated by the dinosaurs of our category. That’s a cool challenge, and it is shared by everyone on the team. 
  • Do you trust your prospective manager with your career? A former colleague once taught me that the single most important thing a candidate asks themselves when interviewing is “would I trust this person with my career?” That’s pretty weighty, but it’s 100% accurate. 

The point is to find the people who you’ll want to go to battle with for the long haul. Often when interviewing, candidates spend most of their time answering questions but interviewing is a two-way street. Interview your potential employer as if they need to convince you that their company—and your potential team and hiring manager—is the best place for you to continue building your career. 

Look for organizational health fit

I’ve got to admit, for someone who loves mission-driven, strong-culture companies, I loathe the word “culture.” It means everything and nothing at the same time. 

Recently, I’ve become familiar with the term “organizational health.” It’s meant to communicate not just the IQ of the company, but the EQ as well, which to me, speaks volumes. 

Here are a few things to look for when assessing organizational health: 

  • Does it seem like there is a low level of politics? All organizations greater than 2 people have politics, so it’s not a question of whether there is politics; rather, it’s a question of whether the politics get in the way of business results and learning. You want a balance of super smart people who are also kind, treat each other with respect, and have fun.
  • Do people seem clear on the company direction? Using this litmus test couldn’t be easier—ask all of your interviewers the same question about company direction. If you’re getting similar answers, then that’s a good sign. 

At LogDNA, our investment in organizational health is rooted in the belief that our team is one of our primary competitive advantages in the market. We believe that a team of 140 people all rowing in the same direction has the adaptability and nimbleness to beat a team of 10,000 who can barely handle their oars. And we’re constantly communicating the fundamentals—our core purpose, core values, the strategy for winning, and what matters most across the company right now—in order to keep LogDNA healthy. 

Look for career fit

I often refer to careers as adventures. They are more than individual jobs. They represent multiple jobs, and each job opportunity is measured by how it contributes to your growth and learning. Yes, other factors are important—compensation, title, and so on—but the most important factor is ongoing growth and learning. When evaluating a new opportunity, take time to understand how this new role fits into your overall career arc. 

LogDNA is my first startup. When I decided to join the team, I was looking for a company as it was beginning to scale, a phase of growth that I’d never experienced. For me, I immediately saw the career fit at LogDNA. I was eager to apply what I’d learned in my career to lead a great team and help bend the growth curve at LogDNA even more. 

Today, the company is disrupting the traditional log management category by creating what we call an observability pipeline: a platform that enables the builders of this economy—the developers, security engineers, site reliability engineers… everyone!—to get vital data in real time, without regard to source, to destination, to use case, or to scale. This is an opportunity to work on this big, complicated challenge. When you are scaling, there’s another meaningful benefit: you get to stretch your career faster by doing things that you’d never get the chance to do at a bigger company.

One last thing…

It’s been a tremendous year full of learnings (and did I mention explosive growth?). Mostly, though, I wake up psyched to work with a kick-ass group of people who are thinking about customer problems, day-in and day-out, and have fire in the belly to take on the industry Goliaths and change the world for the better.

So, that’s my 1 year reflection. I hope these tips are helpful to you as you contemplate the next step in your career adventure. PS: We’re hiring.

Table of Contents

    Share Article

    RSS Feed

    Next blog post
    You're viewing our latest blog post.
    Previous blog post
    You're viewing our oldest blog post.
    Mezmo + Catchpoint deliver observability SREs can rely on
    Mezmo’s AI-powered Site Reliability Engineering (SRE) agent for Root Cause Analysis (RCA)
    What is Active Telemetry
    Launching an agentic SRE for root cause analysis
    Paving the way for a new era: Mezmo's Active Telemetry
    The Answer to SRE Agent Failures: Context Engineering
    Empowering an MCP server with a telemetry pipeline
    The Debugging Bottleneck: A Manual Log-Sifting Expedition
    The Smartest Member of Your Developer Ecosystem: Introducing the Mezmo MCP Server
    Your New AI Assistant for a Smarter Workflow
    The Observability Problem Isn't Data Volume Anymore—It's Context
    Beyond the Pipeline: Data Isn't Oil, It's Power.
    The Platform Engineer's Playbook: Mastering OpenTelemetry & Compliance with Mezmo and Dynatrace
    From Alert to Answer in Seconds: Accelerating Incident Response in Dynatrace
    Taming Your Dynatrace Bill: How to Cut Observability Costs, Not Visibility
    Architecting for Value: A Playbook for Sustainable Observability
    How to Cut Observability Costs with Synthetic Monitoring and Responsive Pipelines
    Unlock Deeper Insights: Introducing GitLab Event Integration with Mezmo
    Introducing the New Mezmo Product Homepage
    The Inconvenient Truth About AI Ethics in Observability
    Observability's Moneyball Moment: How AI Is Changing the Game (Not Ending It)
    Do you Grok It?
    Top Five Reasons Telemetry Pipelines Should Be on Every Engineer’s Radar
    Is It a Cup or a Pot? Helping You Pinpoint the Problem—and Sleep Through the Night
    Smarter Telemetry Pipelines: The Key to Cutting Datadog Costs and Observability Chaos
    Why Datadog Falls Short for Log Management and What to Do Instead
    Telemetry for Modern Apps: Reducing MTTR with Smarter Signals
    Transforming Observability: Simpler, Smarter, and More Affordable Data Control
    Datadog: The Good, The Bad, The Costly
    Mezmo Recognized with 25 G2 Awards for Spring 2025
    Reducing Telemetry Toil with Rapid Pipelining
    Cut Costs, Not Insights:   A Practical Guide to Telemetry Data Optimization
    Webinar Recap: Telemetry Pipeline 101
    Petabyte Scale, Gigabyte Costs: Mezmo’s Evolution from ElasticSearch to Quickwit
    2024 Recap - Highlights of Mezmo’s product enhancements
    My Favorite Observability and DevOps Articles of 2024
    AWS re:Invent ‘24: Generative AI Observability, Platform Engineering, and 99.9995% Availability
    From Gartner IOCS 2024 Conference: AI, Observability Data, and Telemetry Pipelines
    Our team’s learnings from Kubecon: Use Exemplars, Configuring OTel, and OTTL cookbook
    How Mezmo Uses a Telemetry Pipeline to Handle Metrics, Part II
    Webinar Recap: 2024 DORA Report: Accelerate State of DevOps
    Kubecon ‘24 recap: Patent Trolls, OTel Lessons at Scale, and Principle Platform Abstractions
    Announcing Mezmo Flow: Build a Telemetry Pipeline in 15 minutes
    Key Takeaways from the 2024 DORA Report
    Webinar Recap | Telemetry Data Management: Tales from the Trenches
    What are SLOs/SLIs/SLAs?
    Webinar Recap | Next Gen Log Management: Maximize Log Value with Telemetry Pipelines
    Creating In-Stream Alerts for Telemetry Data
    Creating Re-Usable Components for Telemetry Pipelines
    Optimizing Data for Service Management Objective Monitoring
    More Value From Your Logs: Next Generation Log Management from Mezmo
    A Day in the Life of a Mezmo SRE
    Webinar Recap: Applying a Data Engineering Approach to Telemetry Data
    Dogfooding at Mezmo: How we used telemetry pipeline to reduce data volume
    Unlocking Business Insights with Telemetry Pipelines
    Why Your Telemetry (Observability) Pipelines Need to be Responsive
    How Data Profiling Can Reduce Burnout
    Data Optimization Technique: Route Data to Specialized Processing Chains
    Data Privacy Takeaways from Gartner Security & Risk Summit
    Mastering Telemetry Pipelines: Driving Compliance and Data Optimization
    A Recap of Gartner Security and Risk Summit: GenAI, Augmented Cybersecurity, Burnout
    Why Telemetry Pipelines Should Be A Part Of Your Compliance Strategy
    Pipeline Module: Event to Metric
    Telemetry Data Compliance Module
    OpenTelemetry: The Key To Unified Telemetry Data
    Data optimization technique: convert events to metrics
    What’s New With Mezmo: In-stream Alerting
    How Mezmo Used Telemetry Pipeline to Handle Metrics
    Webinar Recap: Mastering Telemetry Pipelines - A DevOps Lifecycle Approach to Data Management
    Open-source Telemetry Pipelines: An Overview
    SRECon Recap: Product Reliability, Burn Out, and more
    Webinar Recap: How to Manage Telemetry Data with Confidence
    Webinar Recap: Myths and Realities in Telemetry Data Handling
    Using Vector to Build a Telemetry Pipeline Solution
    Managing Telemetry Data Overflow in Kubernetes with Resource Quotas and Limits
    How To Optimize Telemetry Pipelines For Better Observability and Security
    Gartner IOCS Conference Recap: Monitoring and Observing Environments with Telemetry Pipelines
    AWS re:Invent 2023 highlights: Observability at Stripe, Capital One, and McDonald’s
    Webinar Recap: Best Practices for Observability Pipelines
    Introducing Responsive Pipelines from Mezmo
    My First KubeCon - Tales of the K8’s community, DE&I, sustainability, and OTel
    Modernize Telemetry Pipeline Management with Mezmo Pipeline as Code
    How To Profile and Optimize Telemetry Data: A Deep Dive
    Kubernetes Telemetry Data Optimization in Five Steps with Mezmo
    Introducing Mezmo Edge: A Secure Approach To Telemetry Data
    Understand Kubernetes Telemetry Data Immediately With Mezmo’s Welcome Pipeline
    Unearthing Gold: Deriving Metrics from Logs with Mezmo Telemetry Pipeline
    Webinar Recap: The Single Pane of Glass Myth
    Empower Observability Engineers: Enhance Engineering With Mezmo
    Webinar Recap: How to Get More Out of Your Log Data
    Unraveling the Log Data Explosion: New Market Research Shows Trends and Challenges
    Webinar Recap: Unlocking the Full Value of Telemetry Data
    Data-Driven Decision Making: Leveraging Metrics and Logs-to-Metrics Processors
    How To Configure The Mezmo Telemetry Pipeline
    Supercharge Elasticsearch Observability With Telemetry Pipelines
    Enhancing Grafana Observability With Telemetry Pipelines
    Optimizing Your Splunk Experience with Telemetry Pipelines
    Webinar Recap: Unlocking Business Performance with Telemetry Data
    Enhancing Datadog Observability with Telemetry Pipelines
    Transforming Your Data With Telemetry Pipelines