Technical Analyst/Strategy & Operations Lead

About the role

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: Investigate why outbound numbers don’t make sense by pulling apart the data.
• Tuesday: Research how five companies solve a product problem we're considering by using their products, inspecting APIs/docs, and identifying what matters.
• Wednesday: Reconcile several ugly datasets from different systems, build the analysis, and turn them into something humans can understand and act on.
• Thursday: Diagnose why an important GTM automation initiative is slipping, identify gaps and dependencies, and help drive the work to get it moving again.
• Friday: Spot something in the data nobody asked you to investigate, determine its importance, and surface it before someone has to ask.

This is not a role where you identify problems and hand them to someone else. We want someone who gets their hands dirty. The output may be an analysis, recommendation, spreadsheet, script, research, process, project plan, or fixed workflow—often a combination.

Responsibilities

• Work across technology, data, product, GTM, research, and operations to find and close gaps.
• Solve ambiguous problems by breaking them apart, gathering missing information, and driving toward answers.
• Turn messy datasets into actionable insights using spreadsheets, SQL, or scripts.
• Research products, competitors, or technical solutions by testing systems, reading documentation, or analyzing data.
• Identify missing data, ownership, processes, or connections between teams and help close those gaps.
• Execute—whether that means writing a script, building a spreadsheet, fixing a workflow, or unblocking a project.
• Communicate complex findings clearly: what happened, why it matters, what’s missing, and what should be done next.

Requirements

• You’re genuinely technical. You can write code, even if software engineering hasn’t been your primary role. Comfort with SQL, APIs, scripts, databases, JSON, webhooks, automation systems, spreadsheets, and AI tools is essential.
• You’re a problem solver. You can start with an ambiguous question, break it apart, and work toward an answer without waiting for perfect information.
• You’re analytical. You can turn large, messy datasets into answers, spot patterns, inconsistencies, and outliers, and ensure analysis leads to action.
• You’re a great researcher. You can quickly become dangerous in a new subject—whether through documentation, product testing, data analysis, or interviews.
• You’re operational. You notice when things aren’t happening, anticipate bottlenecks, and drive execution without needing formal authority.
• You communicate exceptionally well. You distill complexity into clear, actionable insights and surface important findings promptly.

Qualifications

Your career may look unconventional, and that’s a good thing. We’re looking for someone who:

• Has a technical background—whether as an engineer who moved into product/analytics/operations or someone who taught themselves to code to solve problems.
• Has worked in startups, product, analytics, growth, or operations, often in roles that didn’t fit neatly into one box.
• Is the person others give weird problems to because they know you’ll return with answers—and something built, fixed, or moving.

You’ll work closely with company leadership and specialists across engineering, sales, marketing, and GTM systems to make them more effective.