Working With Me

Over the years, I’ve learned that the right fit matters more than the right title. Whether I’m considering joining a team or thinking about who to bring onto one, I come back to the same set of questions. They help me understand what really matters: how a team thinks, grows, and builds together.

On Philosophy & Pace

What’s the philosophy here: “make it happen first” or “perfection”?

I’ve worked in both cultures. I lean toward shipping fast and iterating. Learning from real users beats theorizing in a vacuum. But I also appreciate craftsmanship. I’m curious where the balance lies.

What does a typical day actually look like?

Calendars tell one story, reality tells another. I want to know: Are there blocks of deep work? How much time goes to meetings? Is async the norm or the exception?

On Growth & Ownership

How much agency will I have? What will I truly own?

I do my best work when I own outcomes, not just tasks. I’m looking for environments where I can make real decisions and see them through.

Can I mentor and train people to eventually replace me?

This might sound counterintuitive, but it’s important to me. Building up the people around you is the mark of a healthy team. I want to know I can invest in others.

Is there a mentoring culture for engineers?

Beyond formal structures, do people actually help each other grow? Do senior engineers make time for junior ones? Culture shows up in the small moments.

On Team & Users

Can I meet everyone I’ll be working closely with?

Before committing, I’d love to spend time with the people I’ll collaborate with over the next 6 months. Chemistry matters, and it’s hard to gauge through interviews alone.

What does success look like here? Will I get to talk to users?

I care deeply about understanding the pain we’re solving. If I’m building something, I want to hear directly from the people using it, not through layers of abstraction.

On Engineering Culture

Do we value system-level thinking?

Some of the best engineering happens when you zoom out. I’m drawn to teams that appreciate understanding the whole system, not just isolated components.

How do you craft developer culture?

Culture doesn’t happen by accident. I’m curious: What’s intentional here? What rituals, norms, or practices shape how engineers work together?

If any of this resonates, or if you have your own set of questions, I’d love to hear from you. The best collaborations start with honest conversations.