Technical Content Producer

The short version

I'm Brandon, and I run TechHut. For the last several years I've been making Linux, self-hosting, and homelab content for a community of about 280,000 people on YouTube, plus written guides on techhut.tv. I've hit the point where I can't keep up with both sides of it on my own, so I'm looking for one person to take over a big chunk of the pre and some of the post production work.

This is not a writing job where you get handed notes and turn them into paragraphs. You need to actually build the thing. If we're doing a guide on setting up Immich behind a reverse proxy, you're spinning up a clean VM, running every step yourself, finding the part where the docs are wrong, and then writing it up so nobody watching gets stuck at step 12.

What you'd actually be doing

• Building out test environments from scratch (VMs, containers, bare metal) and running through guides end to end on clean installs to make sure every step works
• Writing and editing the companion articles for videos, plus standalone written guides for techhut.tv
• Catching the gotchas. Port conflicts, permissions issues, steps that only work because something was already installed
• Capturing clean screen recordings of the process
• Helping shape which topics we cover based on what the community is asking for
• Video editing, if you have the skills for it

What you need to know

• Linux. Comfortable in the terminal, not looking things up for basic file permissions or systemd. Any distro family is fine, but you should know your way around at least Debian/Ubuntu and Fedora-adjacent systems.
• Docker and Docker Compose. You should be able to read a compose file, understand what's wrong with it, and fix it. Networking, volumes, and reverse proxies included.
• Homelab experience, hands on. You run stuff at home. Proxmox, TrueNAS, Unraid, a pile of Raspberry Pis, whatever it is. I want somebody who does this for fun already, because that's who catches the details.
• Technical writing. Clear, direct, and organized in a way that somebody newer than you can follow without getting lost. If you've written documentation, a personal blog, or even good README files, that counts.
• GitHub. The site and a number of our repos live there. Branches, pull requests, resolving a conflict without panicking, and editing markdown in a repo.
• AI tooling, at a moderate to advanced level. Building automations and working with agents, not just typing questions into a chat box. The big one here is testing: pointing an agent at a written guide, having it stand up the deployment, and surfacing broken steps before you spend an afternoon doing it by hand.

Nice to have

• DaVinci Resolve. If you can edit, that opens up a lot more work here. Cuts, b-roll assembly, on-screen callouts, basic color and audio cleanup. Fusion and heavy motion graphics are not expected.
• Self-hosted models and local inference
• Kubernetes, K3s, or similar
• Networking beyond the basics (VLANs, firewalls, VPN mesh setups)
• Your own YouTube channel or written technical content, at any size
• Experience with static site generators and MDX
• Basic scripting in Bash or Python for automating test environment setup

The logistics

• Part-time independent contract, paid per deliverable. Expect a handful of deliverables a month to start. For someone based in the US, this could develop into a full time W2 position after some time, depending on channel health.
• Remote, and open to applicants worldwide where TechHut can legally engage and pay independent contractors. North American time zones are preferred, and being close enough to the Vancouver/Portland area for occasional in-person work would be a real plus, but neither is required.
• Pay: Typical assignments pay $200 to $400 per deliverable, depending on scope. Larger projects, specialized work, and video editing may pay more. A deliverable is typically one topic taken end to end: test environment built, guide validated, written article delivered, and screen recordings captured. Scope and price get agreed up front, before you start.
• Equipment: We provide clean virtual machines or access to remote testing environments over NetBird, so you will not be responsible for sourcing hardware or routine environment setup and teardown. Having your own hardware is still a plus, but it is not required. A Resolve Studio license can be provided if editing ends up being part of your work.

How to apply

Send an email to brandon@techhut.tv with:

1. A short note about your homelab. What you run, what's broken right now, what you're proud of.
2. A link to something technical you've written. Blog post, documentation, README, forum answer, anything.
3. Your GitHub profile.
4. An automation or agent workflow you've built. Doesn't matter how small, I just want to see how you think about the problem.
5. If you edit video, a link to something you've cut. It does not need to be polished or professional. Skip this one if editing isn't your thing.
6. Your resume. This one I do need.

Please skip the cover letter. I'd rather read about your setup.

I read every one of these myself, and I'll follow up with everybody who applies.