Roadmap · Career
Tech roles beyond coding (Technical writer)
Opens with creditsFor students and early-career people who like technology but want a role where code is not the main output: product management, business analysis, technical writing or developer relations. By the end you understand the landscape, have the technical literacy these roles need, can do the core work of your chosen role, and have public work samples and a realistic plan to get your first role.
Curated by Tauseef Fayyaz7 stages, 50 topics~8 months at a few hours a weekBy the end, you will be able to
- Explain what product managers, business analysts, technical writers and developer advocates do day to day, and how they differ from project managers, solutions engineers and customer success
- Read an API response, a pull request, a JSON payload and a simple SQL query well enough to ask engineers precise questions
- Do the core work of your chosen role: a tested spec and prioritised plan, a requirements package with process models, a structured and reviewed docs set, or a tutorial, sample app and feedback report
- Publish three strong work samples and run a focused search through internal moves, bridge roles and targeted applications, while spotting scams
The path
7 stages, in the order to learn them. Open one to start.
1The landscape of non-coding tech rolesWhat 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.8 topics · ~2 weeks
- 1What "beyond coding" really meansA non-coding tech role sits inside a software team, but its main output is not production code.
- 2Product manager: deciding what gets built and whyA product manager, or PM, makes sure a team builds the right things.
- 3Technical writer: making products usable through docsTechnical writers create the documentation people use to succeed with a product.
- 4Developer relations: helping outside developers succeedDeveloper relations, or DevRel, helps developers outside the company succeed with a product.
- 5Adjacent roles: project manager, business analyst, solutions engineer, customer successSeveral other roles also sit close to engineering without being mainly about code.
- 6Who does well in each roleEach role rewards a different temperament.
- 7The job market, honestlyThere are fewer entry-level openings in non-coding tech roles than in junior engineering.
- 8Testing your fit with small real tasksThe cheapest way to choose is to try a small piece of each role's real work.
8 in this stageOpen this stage2Technical literacyHow software is built, how the web and APIs work, and enough Git, JSON and SQL to read what engineers produce. You will not become an engineer, but you will stop being lost in technical conversations.9 topics · ~4 weeks
- 1How software is built: the lifecycleSoftware is built in a repeating cycle, often called the software development lifecycle, or SDLC.
- 2Agile, sprints, tickets and boardsMost software teams work in short cycles.
- 3Clients, servers and how the web worksWhen you open an app, a client sends a request over the internet to a server.
- 4HTTP, APIs and status codesAn API is an agreed way for one piece of software to ask another for data or actions.
- 5Reading JSON and API responsesJSON is the text format that most APIs, configuration files and event logs use.
- 6Git, GitHub and pull requestsGit records every change to a set of files over time, so you can see who changed what and undo mistakes.
- 7Reading code without writing muchYou do not need to write production code, but you do need to follow it.
- 8Data basics and simple SQLProducts store their data in databases, and most analytics questions come down to a query, a precise question asked of the data.
- 9Environments, releases, feature flags and incidentsCode usually moves through several environments, which are separate copies of the product.
9 in this stageOpen this stage- Docs as code, structure and styleHow technical writers plan, structure and write documentation: docs as code, information architecture, Diataxis, audience analysis, style guides, procedures and a static site generator. You practise on a small real product or open source tool.7 topics · ~2 monthsOpens with credits
- API docs, review and maintenanceHow technical writers document APIs with OpenAPI, write reliable code samples, run reviews with engineers, automate checks, write release notes and measure and maintain docs over time.7 topics · ~7 weeksOpens with credits
- Your portfolioBuild a docs portfolio: three to five samples of different documentation types, at least one merged open source docs contribution, and a before-and-after rewrite that shows your editing judgement.6 topics · ~2 monthsOpens with credits
- Breaking inHonest routes into a first role: internal moves, bridge roles, targeted applications, the exercises employers set, and the scams to avoid. Expect a longer search than for junior engineering roles, and plan for it.7 topics · ~4 weeksOpens with credits
- Growing in the roleYour first months and beyond: building trust, leading without authority, making your impact visible, staying technical and choosing a longer-term path.6 topics · ~2 weeksOpens with credits
5 more stages, 33 more topics, free with an account.
You have seen the open stages of the Tech roles beyond coding roadmap. Every topic it covers is listed above, and an account opens the rest: what each topic means, a question to check yourself, the courses, the practice and Tauseef's advice for every stage. Early access is open: sign up and your account is active shortly after.
Everything here is free to learn from. A few things, like adding a roadmap, keeping a cheat sheet or asking Tauseef a question, use credits. You get 15 when you join, your first roadmap is free, and if you are learning seriously and run out, you can ask for more. Credits only make sure the platform goes to people who are actually learning.
Build a project
A finished project proves more than a certificate.
- Start with this oneintermediate6 to 8 weeks · 1 studentDocumentation Overhaul for an Open Source Project
Real, merged documentation work reviewed by maintainers, plus a before-and-after write-up for your portfolio
- Markdown or reStructuredText
- Git and GitHub or GitLab
- Docusaurus, MkDocs or Sphinx
- Vale prose linter
- Link checker (lychee or similar)
Related on Sefism
Picked from the other libraries by shared topics.
Best practices
See all- Engineering Career Growth Best PracticesCareer growth best practices for engineers: read your ladder, grow scope and impact, own outcomes, work with your manager, use feedback, build promotion evidence, pick a staff or manager path.
- Technical Writing Best Practices for EngineersTechnical writing best practices for developers: write for your audience, clear sentences, scannable structure, design docs, READMEs and docs, PR descriptions, async updates and blog posts.
- How to Learn a New Programming Language or FrameworkBest practices for learning a new language or framework fast: set a goal, start with official docs, build small projects, practise deliberately, use spacing, read real code, learn with AI wisely.
Checklists
See all- First 90 Days in a New Developer Job: ChecklistWhat to do before day one, in week one and by day 30, 60 and 90 in a new developer job: setup, codebase, first PR, your manager, questions and feedback.
- Career Switch into Tech ChecklistMove into software from another field step by step: choose a direction, follow a learning plan, build proof of skill, use your previous domain, network, plan your runway and target a first role.
- LinkedIn Profile Checklist for DevelopersCheck your LinkedIn profile section by section: photo, headline, About, Experience, Featured, Skills, custom URL, Open to Work, posting and privacy.
Career questions
See all- Which freelance skills is AI replacing, and what should I switch to?AI is squeezing basic, repetitive freelance work first: plain data entry, simple transcription and translation, generic articles, basic logos and simple product descriptions. Work that combines a skill with judgement, client context or systems is holding up better, including automation, AI integration, analytics, specialist writing and full projects that own a business outcome.
- Is a UK master's still worth it in 2026?It can be, but the maths has changed. Graduate tech jobs in the UK are harder to find, the Graduate visa drops from two years to 18 months for applications from 1 January 2027, and sponsored jobs have salary floors many junior roles miss. A UK master's is worth it if you want the degree itself, have a realistic plan for sponsorship, and can afford it without crushing debt.
- GCC, service company or product company: which is best for a fresher in India?None is best for everyone. Service companies hire the most freshers and train them at scale. Global capability centres (GCCs) are growing and hire more freshers than before, with a higher bar and more AI and data skills expected. Product companies offer ownership but hire fewer freshers. Choose on the team, the learning and the work, and know you can move after two years.
Cheat sheets
See allWork with me
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com