About the Role
We're looking for a Rust Content Engineer / Technical Writer to help us turn complex Rust topics into clear, bingeable content for experienced developers.
You'll sit at the intersection of:
- Rust engineering
- Teaching/communication
- Content creation (YouTube)
Your work will directly drive:
- Audience growth and trust with mid/senior engineers
- Demand for our Rust Live Accelerator program
- Better student outcomes (clearer mental models, fewer "stuck" points)
This is not a generic "write some docs" job. This is a key role in building our long-term Rust content engine.
About Let's Get Rusty
Let's Get Rusty helps experienced software engineers master Rust and land serious Rust roles.
Our flagship program, Rust Live Accelerator, is a cohort-based mentorship experience for mid/senior devs who are done with toy tutorials and want real projects, real feedback, and real interviews in domains like backend, infra, embedded, Web3, etc.
We're profitable, growing, and doubling down on content. Now we want someone who can own the teaching layer of that content with us.
Responsibilities
You will:
- Turn rough outlines or Loom recordings into spoken-word scripts for weekly Rust + career YouTube videos
- Propose topics based on:
- Student questions
- Discord conversations
- Common failure patterns for mid/senior devs moving into Rust
- Decide what to explain vs what to assume for an experienced audience
- Ensure technical accuracy and appropriate depth (no hand-wavy Rust)
- Collaborate with our editor to produce 2–3 Shorts per week from each long-form video
- Maintain a simple content tracker (topics, status, publish dates)
- Develop reusable patterns for intros, examples, and transitions so we move faster over time
What Success Looks Like in 90 Days
Outside launch weeks:
- We publish 1 long-form YouTube video per week
- We publish 2–3 Shorts per week pulled from that content
- Founders spend ≤ 3–5 hours/week total on scripting and technical review
- Scripts read like a human teaching out loud, not like a blog post
- There are no "this is wrong / embarrassing" mistakes for senior Rust engineers
If clear expectations and a scoreboard motivate you, this role will fit you.
Requirements
Must-haves
- Strong Rust proficiency OR strong systems background with proof you can ramp quickly into Rust
- Portfolio that shows you can explain complex technical topics clearly (2–3 examples: blog posts, docs, talks, videos, long-form threads)
- If you don't already have a portfolio, that's fine. Creating 1–3 pieces of content now that showcase your skillset also works (blog post, doc, talk outline, or short technical video). See paid test (bounty) below.
- Excellent written English
- Ability to write in a conversational, spoken style (as if you're on camera)
- High ownership and comfort with feedback/iteration
- Ability to work remotely and reliably attend recurring calls and reviews
Nice-to-haves
- Prior teaching or mentoring experience
- Experience shipping content publicly (blog, YouTube, talks, etc.)
- Familiarity with key Rust ecosystem topics (async, ownership/borrowing, lifetimes, performance, etc.)
No degree requirements. Skill > pedigree.
Compensation & Path
We're upfront about numbers:
- Initial 90-day contract, 20–25 hours/week, at $55–65/hr
- That's the equivalent of ~$57k–$84k/year at part-time hours
- If we hit the 90-day scorecard together, we convert to a full-time contractor arrangement, with:
- An agreed-upon hourly rate in the range equivalent to ~$95–110k/year at full-time hours
- Performance-based bonuses tied to:
- Videos shipped on schedule
- Founder time saved
- Technical quality
We pay for leverage and consistency, not hours for hours' sake.
This role is for someone who ultimately wants to be a long‑term, full‑time contractor with us. The first 90 days are part‑time by design so we can prove it's a great mutual fit before ramping to full‑time hours.
We're a small startup. There isn't much room for negotiation right now, even if we wanted to. Please make sure this compensation works for you.
How to Apply & Paid Test (Bounty)
- ✅ How to Apply
Fill out this short form: Application: Rust Content Engineer / Technical Writer (Remote)
Please include:
- Basic info (name, experience, availability, etc.)
- Links to 2–3 examples of your best technical explanations
- Blog post / doc / YouTube / Loom / tweet thread (any format is fine)
- We care most about clarity, structure, and technical depth
If you don’t have an existing portfolio yet, that’s okay. Creating 1–3 pieces now is totally acceptable (a blog post, short video, doc, or outline).
- ✅ Next Step: Paid Test (Bounty)
If you’re selected to participate, we’ll send you:
- A 5–10 minute Loom
- Rough notes / bullets
- Context on the intended audience + video format
You will return:
- A structured outline
- A 10–15 minute spoken-word script
- A 3-minute Loom explaining your structure and choices
- 💰 Bounty + Payouts
To respect your time, we’re compensating strong submissions:
- 1st place: $2,500
- 2nd place: $1,000
- Up to 10 additional qualified submissions: $100 each
- ("Qualified" = followed instructions, correct avatar, no major technical errors)
If this sounds like your kind of work, apply. We're looking for the person who can help us build the Rust content machine.