- We're looking for someone unusually good at figuring things out and getting things done.
- This is a hands-on, execution-oriented role sitting at the intersection of technology, data, product, GTM, research, and operations.
- You won't own a traditional department. Instead, you'll work across them—finding gaps, solving problems, creating structure where it's missing, and helping make strong specialists more effective.
A typical week might look something like this
Monday: Our outbound numbers don't make sense. Pull apart the data and determine why.
Tuesday: Research how five companies solve a product problem we're considering. Actually use the products, inspect their APIs/docs where relevant, and tell us what matters.
Wednesday: Take several ugly datasets from different systems, reconcile them, build the spreadsheet or analysis, and turn them into something humans can understand and act on.
Thursday: An important GTM automation initiative is slipping. Figure out what's blocking it, identify the gaps and dependencies, and then help drive the work required to get it moving again.
Friday: You notice something in the data nobody asked you to investigate. It looks important. Investigate it, determine what it means, and surface it before someone has to ask.
That's the job.
This is not a role where you identify problems and hand them to someone else. We want someone who gets their hands dirty. Sometimes the output is an analysis or recommendation. Sometimes it's a spreadsheet, a script, research, a process, a project plan, or a fixed workflow. Often it's some combination of them.
What We Care About
You're genuinely technical.
You should be able to write code, even if software engineering has never been your job.
Maybe you started as an engineer and moved toward product, analytics, operations, growth, strategy, or entrepreneurship.
Or maybe you've never worked as an engineer at all, but while doing those other things you taught yourself how to code because it made you dramatically better at solving problems.
Either is great.
What's not enough is having "worked closely with engineering."
You should be comfortable getting hands-on with SQL, APIs, scripts, databases, JSON, webhooks, automation systems, spreadsheets, and AI tools. You don't need to be writing production application code every day, but technology should be something you can use, not just something you can discuss.
You're a problem solver.
We don't expect every problem to arrive neatly defined.
Often, figuring out what the actual problem is will be part of the job.
You can start with an ambiguous question, break it apart, determine what information is missing, investigate it, and work your way toward an answer.
You're comfortable moving between technical and business problems and using whatever tools are appropriate to solve them.
And you don't stop at identifying the problem. You're biased toward execution and will personally do the work when that's the fastest path forward.
You're good at gap analysis.
You notice what's missing.
Missing data. Missing ownership. Missing processes. Missing instrumentation. Missing requirements. Missing follow-up. Missing connections between two teams that each think the other is handling something.
You can look at a system, project, dataset, or process and quickly start asking:
What do we have?
What do we need?
What's missing?
What's blocking us?
What should happen next?
Job description provided by ListLab.
View the original posting
