Technical AnalystStrategy & Operations Lead

Were 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 wont own a traditional department. Instead youll work across themfinding gaps solving problems creating structure where its missing and helping make strong specialists more effective.

A typical week might look something like this:

Monday: Our outbound numbers dont make sense. Pull apart the data and determine why.

Tuesday: Research how five companies solve a product problem were 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 whats 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.

Thats 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 its a spreadsheet a script research a process a project plan or a fixed workflow. Often its some combination of them.

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 youve 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.

Whats 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 dont need to be writing production application code every day but technology should be something you can use not just something you can discuss.

We dont 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.

Youre comfortable moving between technical and business problems and using whatever tools are appropriate to solve them.

And you dont stop at identifying the problem. Youre biased toward execution and will personally do the work when thats the fastest path forward.

You notice whats 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
Whats missing
Whats blocking us
What should happen next

Then you help close those gaps.

You can take hundreds of thousands of rows of messy data and turn them into an answer.

Youre excellent with spreadsheets.

You know when an aggregate is hiding something important.

You look for patterns inconsistencies outliers and explanations rather than simply reporting numbers.

And your work doesnt end when the analysis is complete. The point of the analysis is to change what we do next.

You know how to quickly become dangerous in a subject you knew almost nothing about yesterday.

That could mean reading documentation testing products analyzing competitors digging through data reading source code interviewing people or using AI.

The methodology doesnt matter. Getting to a reliable answer does.

And were looking for product research not just market research. If were evaluating how something works we want someone willing to actually use it understand the workflow investigate the underlying technology where useful and figure out why it was built that way.

You dont just identify what should happen.

You notice when it isnt happening.

You anticipate dependencies and bottlenecks chase down loose ends and surface problems before they become emergencies.

You dont need authority over people to make things move.

Most importantly you execute. Were not looking for someone whose primary contribution is assigning work running meetings or maintaining project-management software. If a problem can be solved by opening a spreadsheet querying the database writing a script researching something testing a workflow or getting into the system yourself we expect you to do it.

Complexity goes in. Simplicity comes out.

Leadership should be able to give you a messy question and receive a concise explanation of:

What happened
Why
Why does it matter
Whats missing
What should we do

You also understand that timing matters. If you discover something important on Tuesday you dont bury it in a report scheduled for Friday.

This is not a project coordinator role.

Its not a traditional Product Manager role.

Its not a Business Analyst role where your primary responsibility is gathering requirements.

Its not a Data Analyst role where your responsibility ends after producing the analysis.

Its not a strategy role where your responsibility ends with a recommendation.

And its not a software engineering role although your ability to code and work directly with technical systems will be essential.

Its a role for someone who likes operating in the gaps between those disciplinesand personally doing the work required to close them.

Your career may look slightly strange on paper.

Thats probably a good thing.

Maybe you were a great engineer who didnt want to spend the next 20 years exclusively writing software.

Maybe youve never held an engineering title but taught yourself how to code while working in product analytics growth operations or another discipline because you kept running into problems you wanted to solve yourself.

Maybe youve bounced between startups product analytics growth technology and operations because none of those boxes completely described what youre good at.

Maybe youre the person everyone gives the weird problems to because they know youll eventually come back not only with an answer but with something built fixed analyzed organized or moving.

Thats who were looking for.

Youll work closely with company leadership and with strong leaders across engineering sales marketing and GTM systems.

We have excellent specialists.

Were looking for the technical generalist and hands-on problem solver who finds the gaps closes them and makes the specialists more effective.