Tech roles beyond coding

Stage 1 of 7 · 8 lessons · ~2 weeks

The landscape of non-coding tech roles

What product managers, technical writers and developer advocates actually do, who does well in each, and the adjacent roles worth knowing about. Test your fit with small real tasks before you commit.

Start: What "beyond coding" really means

Lessons· one lesson for each topic, in this order

  1. 1What "beyond coding" really means
  2. 2Product manager: deciding what gets built and why
  3. 3Technical writer: making products usable through docs
  4. 4Developer relations: helping outside developers succeed
  5. 5Adjacent roles: project manager, business analyst, solutions engineer, customer success
  6. 6Who does well in each role
  7. 7The job market, honestly
  8. 8Testing your fit with small real tasks

Do this

  • Read ten real job postings for your target role and highlight the responsibilities and experience they ask for.
  • Write one paragraph each on product management, technical writing and DevRel in your own words.
  • List two adjacent roles, such as business analyst or support engineer, that could be a stepping stone for you.
  • Do one small real task from your chosen role this week: interviews and a problem page, a README, or a five-minute demo.
  • Talk to one person who works in your target role and ask what a normal week looks like.
  • Write down what you enjoyed and what drained you in the task you tried.

Start with

Keep handy

Before moving on: A one-page comparison of product management, technical writing and DevRel in your own words, with notes on two adjacent roles, ten real job postings reviewed, and one small real task from your chosen role completed.

Tauseef's advice
Do not pick one of these roles because you want to avoid code. Pick it because you like the actual daily work: deciding, explaining or teaching. Spend a weekend doing a small version of that work before you spend months studying for it.

Mark this stage as not done?