Technical Marketing Engineer

Join Klara as a Technical Marketing Engineer. Interview engineers, transform technical expertise into high-value content, build AI and automation workflows that scale publishing, improve search and AI visibility, and measure impact across the marketing funnel.

Remote

Full-time

Contract

Marketing

5+ years

About Klara Inc. 

Klara Systems is a FreeBSD and ZFS engineering services company. We work with enterprise customers across North America, the UK, and Europe, including defense primes, storage vendors, and operators of critical infrastructure who depend on auditable, long-lived, sovereign systems. Our team is senior, globally distributed, and operates with a high degree of autonomy.  

Role Overview 

You will be a part of the marketing team and will build and run the pipeline that turns engineering work into published material buyers can find. You pull source material from engineers and consultants, decide what is worth publishing, structure it so humans and retrieval systems can use it, and measure what it does for pipeline. You automate the repetitive parts so output does not depend on headcount. 

This is a hands-on individual contributor role. You will be the first person in this seat, and you will build most of the tooling yourself. 

What you will do 

• Interview engineers and consultants. Mine incident write-ups, support patterns, upstream PRs, mailing lists, and client-safe delivery lessons for source material. 

• Turn that material into posts, technical pages, comparisons, FAQs, and migration explainers organized around the questions buyers ask, in the language practitioners use. 

• Spot opportunities for original research and benchmark reports in recurring patterns from customer engagements. 

• Build your own extraction tooling: scripts and LLM pipelines that mine support tickets, upstream PRs, mailing list archives, and delivery notes, then flag what is worth publishing. 

• Maintain a tracked set of buyer questions and run it monthly against ChatGPT, Claude, Perplexity, and Google AI Overviews. Report where Klara appears, then close the gaps through page structure, schema markup, and new content. 

• Use AI tooling to watch forums, mailing lists, and technical communities for discussions Klara should be part of. 

• Read the funnel, run experiments across regions and channels, and cut channels that are not earning their budget. 

• Own funnel reporting, attribution, nurture flows, and the dashboards leadership reads. When a stage underperforms, say why and what you changed. 

• Automate reporting and first drafts so your time goes to interviews, technical review, and distribution. 

• Keep lightweight dashboards: retrieval coverage, funnel impact, and time from source material to published output. 

What success looks like 

• When buyers ask about FreeBSD, ZFS, storage architecture, migration, or reliability, Klara material shows up in search results and in model answers. 

• Material from consulting or development work and upstream activity gets published within days. 

• More pipeline can be traced to published technical material. 

• Engineers trust the output enough to put their names on it. 

Must Have 

• You can hold a technical conversation with an operating systems or storage expert and turn 40 minutes of discussion into something publishable.  

• A background in software development, systems administration, or a related field, through education or hands-on work.  

• You read technical docs and incident notes closely enough to catch missing context and sharpen claims, and you check before shipping rather than guessing.  

• You use AI tooling daily and know how to get accurate and usable information and assets from it.  

• You know which repetitive tasks are worth automating and which are not worth the build.  

• You understand technical buyer personas and can build content they actually want to read. 

Nice to Have 

• You have experience using and building marketing dashboards. Can work HubSpot (or similar tools) and read a dashboard without being handed a summary.  

• You are familiar with or have contributed to and/or participated in an open source project or community.  

• You have run a retrieval or AEO program before, not just SEO.  

• The second time a task shows up, you think about options to automate it or build a tool for it. 

How we work  

We are distributed and asynchronous by default. We operate as a senior team with low ceremony and high trust, and we hold ourselves to an honest engineering culture. We do not oversell, we do not obscure problems, and we expect the same standards from the people we hire.