Technical Writer

About SDK.finance

SDK.finance is a modular core banking platform used by FinTech teams in 25+ countries. The product is powerful and flexible, but this only matters when people can clearly understand how it works and how to use it.

Over the years, we’ve accumulated a mixture of legacy documentation, new articles, API references, instructional videos, and Knowledge Base entries. It all exists but not as a coherent system. Some parts are outdated, some are unclear, and some simply don’t communicate the logic behind the product.

About the Role

We’re looking for someone who can take responsibility for bringing clarity, structure, and meaning to all of this. Someone who can think through the product, ask the right questions, find the missing pieces, and turn complex logic into understandable material.

What You’ll Do

• Review everything that currently exists: Knowledge Base, API documentation, video guides, onboarding flows.
• Understand what each piece is trying to explain, where it belongs, and how it fits into the overall structure.
• Reorganize documentation into a logical, navigable system: categories, flows, concepts, and progression.
• Rewrite content where needed, remove outdated pieces, and create new explanations where gaps appear.
• Describe product features, roles, flows, configuration options, and edge cases in a clear, consistent way.
• Break down business processes into step-by-step sequences that accurately reflect how real users work.
• Define core concepts (“wallet”, “cash desk”, “role”, etc.) and ensure they are used consistently everywhere.
• Work closely with engineers, product managers, and client-facing teams to understand the logic behind decisions.
• Ask questions when something doesn’t feel clear and refine explanations until they do.
• Take ownership of the product’s language and help ensure that everything we publish is coherent and helpful.
• Learn continuously as the product evolves and keep documentation evolving with it.

Who You Are

• You think before you write and writing is your way to bring clarity to a complex idea.
• You enjoy understanding how systems work, not just describing them.
• You naturally ask questions: “What does this do?”, “Why is it built this way?”, “What does the user expect?”.
• You can take a long, multi-step workflow and simplify it without losing meaning.
• You’re comfortable reading API documentation, UI flows, user roles, and business logic.
• You think in levels of depth: high-level explanation, detailed explanation, step-by-step breakdown.
• You understand that good documentation is partly structure, partly language, and partly empathy.
• You take pride in making something easier to understand than it was before.
• Experience with Markdown, Notion, Git, Swagger, or basic video scripting is a plus but your brain matters more.

Why This Role Matters

Documentation is not an afterthought for us; it’s how the product becomes usable. Your work will directly influence how quickly clients onboard, how independently they operate, and how confidently they build on top of the platform. You’ll help create order from years of accumulated content and establish a long-term foundation for clarity. Over time, you’ll develop a deep understanding of how the product works and how it is used, and this understanding will make you an important contributor in discussions about product logic and design.

Why SDK.finance

• You’ll work with a real product, not hypothetical features.
• The system is complex, so your work will be meaningful and visible.
• No promotional fluff, just honest, practical explanations for real users.
• You’ll have autonomy to define standards, structure, and writing quality.
• You’ll be collaborating directly with founders, engineers, and PMs.
• You’ll see the impact of your work as clients understand the product better.

How to Apply

• An example of something you’ve explained well (a system, interface, process).
• A short note on what you believe makes documentation truly helpful.
• What you would improve first if you were to look at a system like ours.
• A brief outline of how you would structure a flow such as “cashier top-up via API and web portal”.

We care more about how you think, how you ask questions, and how you make sense of complexity than about formal credentials.