Technical Content Writer

About Medblocks

Medblocks is building a developer-focused “stack for healthcare” that makes it possible for anyone to build applications that integrate directly with clinical workflows without rebuilding expensive Electronic Medical Records systems. We believe code has the potential to save more lives than doctors can by themselves.

Founded by doctors-turned-programmers, our team leverages open, vendor-neutral standards like openEHR, FHIR, SMART, and SNOMED CT to create a platform that makes healthcare data accessible, interoperable, and useful.

Our Culture

We are a team that values deep work, clear communication, and continuous learning. We are building technology that matters, and we are looking for individuals who want their code to make a difference in healthcare.

Role Overview

We are looking for a Technical Content Writer who can make complex software and healthcare data concepts genuinely interesting and accessible.

This is a hybrid developer and content role — the mix shifts depending on what’s needed. Some days you’re writing code: building integrations, demos, or sample apps that become the basis for tutorials. Other days you’re deep in research, covering a conceptual topic like clinical data modelling or a recent development in health interoperability. And sometimes you’re working closely with our engineering team to extract and translate what they’ve built into content developers can actually learn from. What ties it all together is a strong full stack foundation. You don’t need to have built everything you write about — but you need enough depth to ask the right questions, understand the answers, and write about them with confidence.

Responsibilities

1. Write long-form technical blog posts across a range of formats — hands-on tutorials, conceptual deep-dives, commentary on industry developments, and product explainers
2. Script YouTube videos covering everything from live coding walkthroughs to thought leadership pieces on health IT standards
3. Build sample apps, integrations, and code demos when the content calls for it — and publish the source code alongside
4. Work with engineers and product team members to understand what they’ve built and turn it into clear, engaging narratives
5. Author lesson articles and coding exercises for our courses
6. Stay current on developments in health interoperability (FHIR, openEHR, SMART, etc.) and identify timely topics worth covering
7. Maintain a consistent publishing cadence across blog and video with the rest of the team
8. Deliver 1-on-1 instructional sessions with learners — explaining technical concepts, walking through code, answering questions, and adapting your teaching style to the individual’s background and pace
9. Serve as a mentor and point of contact for students working through course material, providing structured feedback on assignments and guiding them past blockers
10. Design and refine curriculum based on what comes up repeatedly in teaching sessions — turning common sticking points into better lesson content or new topics worth covering

Requirements

1. At least 1 year of full stack development experience — you’ve built and shipped web applications end to end, from backend APIs to frontend interfaces
2. Proficiency in at least one backend language (Python, Node.js, Go, etc.) and comfort with a frontend framework (React, Vue, or similar)
3. Comfort reading and debugging code across the stack, even in languages or frameworks you haven’t used before
4. Strong written communication — clear, structured, and able to adapt tone across formats (conversational scripts, in-depth articles, reference docs)
5. Ability to self-study unfamiliar topics, synthesise information from multiple sources, and form your own point of view
6. Intellectual curiosity — genuine interest in how systems work, not just what they do. Comfortable in a small, fast-moving team with high ownership

Nice to Have

1. Prior experience writing developer-focused content, technical blogs, or video scripts
2. Background building or integrating with clinical systems or hospital software
3. A public portfolio: GitHub repos, published articles, video walkthroughs, or course content
4. Familiarity with developer SEO — understanding what engineers search for and how to write content that ranks