Technical Researcher / Writer

Why Join Us

Your work compounds. Evergreen, honest content wins search and trust for years, not days. Real autonomy. You pick what's worth researching and own it end to end. Published under our name. Your work represents the company to a technical audience. AI-native company. You'll live at the edge of new tools, testing them for real. Bootstrapped and Profitable. We answer to customers, not investors.

How You Work

• You write code to benchmark APIs and tools, not just describe them.
• You're comfortable with data: spreadsheets, simple scripts, and charts that are honest.
• You test the no-code and agent ecosystem hands-on (n8n, OpenClaw, Hermes, MCP, AI workflows).
• You improve our docs and product by actually using them.
• You use AI, you don't let it write for you. AI makes research faster, and it also produces confident nonsense. You use it to move quickly, then you verify every number and every claim. If a benchmark isn't reproducible, it doesn't ship. We will know the difference.

The Hard Parts

• Real research is slow. Coding a fair benchmark takes longer than writing an opinion. You do it anyway.
• You publish unflattering truths. Sometimes the honest result makes us look worse. You publish it.
• You build the rig, not just the prose. The code and data behind a number matter as much as the number.
• Ambiguity. You choose the questions worth answering. If you want to churn out AI-written articles, this isn't for you.

About You

• A technical writer who codes. You can stand up a benchmark and explain it clearly.
• Intellectually honest. You follow the data, even when it's inconvenient.
• You read docs, call APIs, and wire up tests without hand-holding.
• Curious about the AI tooling space. You actually enjoy trying the new thing.
• Self-directed. You don't need a content calendar handed to you.
• Native or near-native English. Writing is the whole job.

Required Experience

• A long-form technical piece you wrote, plus the code or data behind a benchmark or estimation in it.
• A blog or portfolio of evergreen technical content.
• Experience benchmarking APIs, tools, or models.
• Familiarity with the no-code and agent ecosystem.

What We Look For

• Link one technical piece you wrote and the code or dataset behind a number in it.
• In two sentences, how would we reproduce that number from scratch?
• Evidence you measure, not guess.

Signals We Look For

• A technical blog you maintain.
• A benchmark repo.
• A comparison where you published the unflattering result.

Hiring Process

• 45-minute call with CEO. Get to know each other.
• Take-home challenge. A small, real research-and-benchmark task.
• Follow-up call. Walk through your method and what you found.
• Reference check + Offer

What You Get

• Fully Remote. Work from anywhere.
• Equity share. Own a piece of what you're building.
• Profit sharing. When we win, you win.
• Learn from the founder. Understand how a real SaaS business grows.
• Annual team retreats (last one in Spain).