Work

I run technical SEO content around the decisions developers make about databases, from managed Postgres and database branching to evaluating databases for AI agents. Alongside the briefs and editorial work, I built a reporting baseline tied to the first article’s publication and track our pages separately from Databricks’ wider site. Our English-language article programme earned over 500 search clicks and over 60,000 impressions in October 2026, more than doubling clicks and more than tripling impressions from September.

I develop technical briefs and editorial guidance around secrets management, machine identity and AI-agent security, as part of a programme with over 60 published articles by October 2026. Every brief is checked against the product docs, and every code example is checked to make sure it’s safe to copy, so the programme stays technically credible as it grows. I also keep the topic library mapped so new work extends the series rather than repeating it.

I turn the questions developers are already asking in the community into briefs that make Infisical’s approach to secrets and agent security concrete. Each brief gives writers the audience, the argument, the questions to answer for search and AI answers, and the product details to verify, so the articles in a series work together rather than repeat one another.

I researched a FinOps ebook on cloud data platform costs, built around the decisions practitioners actually struggle with rather than another list of cost-saving tips. I combined practitioner discussions, a sourced quote bank, competitor coverage and product documentation into a structure the writing team could build on.

I edit technical articles for both through Growth Plays, a B2B content agency. John-Henry Scherck, its founder, called one draft “one of the best pieces of content we’ve drafted as a company.”

I built Flutterwave’s developer content strategy from scratch, translating payments messaging into topics developers could use to understand and implement the product. The programme covers payment rails, settlement, stablecoin integration, cross-border failures and compliance, with topics mapped from education through implementation and evaluation. It gives the team a connected editorial plan rather than a collection of product announcements.

I developed search-led briefs around the practical barriers to adopting serverless Postgres, including connection pooling, free hosting and choosing a serverless stack. The wider content programme showed developers how to use Neon with tools such as Kysely, Prisma, Cloudflare Workers and pgvector, rather than explaining the database in isolation. The linked Dev.to tutorial set recorded over 30,000 views.

I turned feedback from documentation teams and Mintlify’s webinar into a content strategy around AI-readable docs, technical-writing workflows and platform evaluation. The plan moved beyond generic documentation advice into testing AI retrieval, finding gaps through search and support signals, keeping assistants aligned with changing docs and guiding migrations. I translated those themes into titles and writer-ready outlines tied to Mintlify’s search, automation and preview workflows.

I worked alongside Roadmap’s SEO team to turn search opportunities into practical learning content, including Python multithreading exercises, interview preparation and guides for new developers. My briefs specified the teaching sequence, code examples, task prompts and interactive elements, not just the keywords to include. During the engagement, estimated site-wide organic traffic grew by more than 60% between late June 2024 and March 2025, a wider team result rather than growth attributable to my articles alone.

I helped run their developer marketing strategy, organised SEO around technical topics, and wrote content that competed on crowded React keywords.

I built a content strategy around Appwrite’s product roadmap and the work developers needed to get done. That included turning new Functions capabilities into tutorial plans for GitHub deployments, multi-function repositories, subscription access with user labels and migrating between Functions versions. The result was a product-led content plan with concrete implementation examples, not broad backend-development topics disconnected from the release.

I developed briefs that connected Sourcegraph’s AI-coding capabilities to real development work: understanding unfamiliar code, debugging, generating tests and planning migrations. Each brief spelled out the reader, search intent, examples and product context, including how Cody should appear naturally in the workflow. That gave writers a concrete route from a broad AI topic to an article a developer could act on.

Cloudinary had a clear content direction but needed more capacity to turn it into useful developer material. I translated those themes into search-led briefs and outlines, with specific audiences, implementation detail and guidance on where Cloudinary belonged in the story. The work supported a dedicated writing and editorial process built around demos and real media workflows, rather than adding production work back onto Cloudinary’s team.

I ran content strategy for Mia-Platform across technical articles and whitepapers, helping an internal team that was spending too much time producing and rewriting content. Hackmamba gave them a clearer production and review process, with an outside perspective that kept the content from becoming too self-referential. Their senior technical writer, Paolo Martinoli, reported quicker reviews and better-prepared, better-targeted leads, with more time left for strategic work.

I helped turn Jozu’s product demos, briefs and roadmap updates into developer-focused content for KitOps and JozuHub. The work combined editorial direction with a repeatable delivery process, giving an early-stage team a way to explain model packaging, registries and deployment without pulling its engineers away from the product. Hackmamba delivered more than 20 articles through the programme.

I turned early topic ideas into structured briefs, tuned them for search and audience, and guided writers to a consistent voice. Their team said they were “very impressed” with the finished articles.

Docs and video support. Writing our collaboration announcement is where I developed the Halo Signal and SHARE frameworks.

I ran Bitcloud’s content strategy and reworked its messaging several times as the AI software development market shifted, tying each change to a positioning analysis and an editorial plan the team could act on.

I developed security-content briefs around the gaps between storing a secret safely and using it safely in CI/CD. The briefs specified failure scenarios, trust-boundary diagrams, code examples and the limits of vaults and static scanning, with product context grounded in Aikido’s security workflow. They gave writers an argument to develop and technical details to verify, not just a keyword and a word count.

I built a content framework around the friction in Kubernetes development: local environments that do not match production, slow testing loops and the cost of maintaining extra clusters. I separated engineering-leadership arguments from hands-on developer guides and search comparisons, then connected them through pillar topics and a publishing rotation. That gave the team a plan for explaining mirrord through specific workflow problems rather than a stream of disconnected tool posts.

I developed migration-content briefs for teams deciding whether to leave their translation-management system. The work separated the questions developers, designers, product managers and content owners needed answered, then connected the evaluation guide to platform-specific migrations and automation workflows. The briefs made switching a concrete technical decision, covering imports, translation memory, glossaries, CLI integration and the risks to check before a move.

I joined when Hackmamba was a side hustle with no roadmap and took on landing pages, ads, lead funnels and messaging. As the agency grew, I became Head of Marketing and built the editorial standards behind our client work. I now combine that discipline with agent-assisted research, client performance trackers and a content-distribution workflow that extends an article into community posts, newsletters and video. I also created Developer Adoption Architecture and led the rebrand from a technical-content agency to a full-cycle developer-growth agency. Beyond marketing, I help Hackmamba recruit. I screen and interview candidates, and the people I’ve brought on have gone on to do some of the team’s best work.

I write for a technical audience that expects evidence, practical examples and an argument worth reading. My published work includes a guide to earning developers’ trust through useful content, covering topic research, product education and how to recommend a tool without turning the article into a pitch. That same approach shapes the briefs and editorial standards I use with clients.

How to write for a technical audience How to advertise to developers

Their first and only marketing executive. I built the e-commerce site, optimised product listings to rank, secured official Schneider Electric retailer approval and ranked for ABB products across regions.

I taught React and JavaScript to women starting out in development, as the only male instructor in my cohort.