Synthires
Technical Content Writer (Remote | $90–$140/hr)

How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Technical Writing Specialist
Position: Technical Writing Specialist
Type: Contractor
Compensation: $90–$140/hour
Location: Remote
About the Opportunity
micro1 is engaging experienced Technical Writing Specialists to contribute to a writing-intensive customer project focused on developer and product documentation. You will apply your technical writing and communication expertise to help train next-generation AI systems using high-quality, real-world documentation.
The work involves analyzing complex technical materials, creating and editing developer-focused content, structuring documentation systems, and evaluating documentation for clarity, accuracy, completeness, and usability. Experts will be expected to apply strong analytical thinking and precise communication skills to transform complex technical concepts into clear and effective documentation for varied audiences.
No prior AI experience is required—your technical writing expertise, professional judgment, and ability to synthesize complex information are what matter.
Responsibilities
- Analyze and interpret technical source materials, including API references, developer guides, release notes, and technical specifications.
- Create and edit high-quality technical documentation, including guides, tutorials, architecture documents, and developer resources.
- Translate complex technical concepts into clear, concise documentation for both technical and non-technical audiences.
- Apply information architecture principles to organize documentation for usability, discoverability, consistency, and scalability.
- Implement and maintain docs-as-code workflows and editorial standards.
- Apply established style guides and documentation guidelines consistently across deliverables.
- Evaluate existing documentation for clarity, completeness, accuracy, structure, and terminology.
- Identify gaps, inconsistencies, and areas where documentation can be improved.
- Recommend and implement documentation improvements based on audience needs and project requirements.
- Maintain consistent terminology, structure, tone, and formatting across documentation sets.
- Explain documentation decisions, trade-offs, and reasoning clearly to stakeholders and collaborators through written communication.
- Apply strong attention to detail when reviewing technical content and documentation quality.
Reasons to use Rodeo
I’m in my final year doing Economics and I don’t know whether to apply for grad schemes now or do a masters first. What do you think?
Honest answer — it depends on where you want to end up. A lot of top grad schemes (Big 4, civil service, banking) don’t need a masters. Let’s look at the ones you’d be competitive for now, and we can decide if a masters actually adds anything.
Also worth knowing: most autumn 2026 applications are open now. Timing matters more than you think.
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
Graduate Consultant — 2026 Scheme
Why you're a good match
StrongYour economics background and your summer at a regional bank line up with what PwC looks for on the consulting scheme. Applications close in four weeks.
See breakdownIt searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Why you're a good match
You’ve got the grades and the economics background, and your bank internship is exactly the experience this scheme looks for. Apply soon — deadlines close within the month.
Experience fit
Your summer at the bank plus your econometrics coursework map directly to the day-one responsibilities on this scheme — client modelling, market briefings, and deal support.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
Required Qualifications
- Minimum 3 years of experience producing developer or product documentation.
- Hands-on experience creating API documentation, integration guides, onboarding materials, tutorials, release notes, or similar technical content.
- Strong expertise in technical writing, information architecture, and editing.
- Ability to communicate complex technical concepts clearly and concisely.
- Experience writing for both technical and non-technical audiences.
- Proficiency with docs-as-code workflows, including Markdown, Git, and CI/CD.
- Experience applying established style guides such as Microsoft, Google, or custom organizational guidelines.
- Exceptional written English with strong grammar, structure, terminology, and editing skills.
- Strong attention to detail and consistency.
- Ability to synthesize information from multiple technical sources and produce coherent documentation.
- Strong professional judgment when structuring, evaluating, and refining technical content.


Get help with your application
Your very own career expert that helps elevate your application to the next level.
Preferred Qualifications
- Experience owning the structure, quality, and strategy of end-to-end documentation sets.
- Experience establishing or improving documentation information architecture.
- Experience working closely with developers, engineers, product t
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Location