Guest Author Program

Write with Analog Data

We publish hands-on engineering stories: schematics, code, telemetry, edge AI, production infra, and the lessons you learned shipping them.

Pitch your idea See guidelines

Reach

1.35K+

Monthly readers across hardware, AI, and infra.

Review

2–4 days

Fast editorial feedback loop with engineers.

Showcase

Homepage

Featured placement for standout stories.

Editorial desk

How we review drafts

Applied

Response

2–4 days

Outline + asset asks.

Format

Code-first

Steps, configs, diagrams.

What we love to see

Checklist

Builds, not thinkpieces

Schematics, traces, logs, benchmarks — the artifacts that prove it works.
Code-first clarity

Snippets that compile, configs we can copy, reproducible steps.
Lessons learned

What broke, how you fixed it, and what you’d do differently next time.

What we publish

Ship Stories, not Hot Takes

Show us how you built it: diagrams, code, telemetry, design trade-offs, and the production realities that rarely make it into tutorials.

Embedded, IoT & Edge AI

Firmware bring-up, MCUs, sensor fusion, quantization, on-device ML, inference pipelines, and power/latency trade-offs.

LLMs, RAG & Agentic systems

Generative AI in production, retrieval pipelines, orchestration, MCP/agent frameworks, safety, evals, and fine-tuning results.

Infra, Data, & Reliability

Streaming, observability, deployments, CI/CD for hardware + cloud, data contracts, testing harnesses, and real SLOs.

Playbooks & Patterns

Step-by-step guides, reference architectures, teardown of mistakes, and battle-tested checklists others can reuse.

Security & Safety

Hardening, secure boot, secrets handling, threat modeling, red/blue findings, and safety guardrails for AI systems.

Testing & Tooling

Bench setups, simulators, hardware-in-loop, eval harnesses, chaos drills, and developer tooling that speeds shipping.

Telemetry & metrics Security & hardening Boards + BOM choices Edge-cloud sync LLMs & fine-tuning RAG & vector infra Agentic patterns / MCP Testing rigs

Submission checklist

Make it practical and reproducible

If a reader cannot rebuild your result, we won’t publish it. Use concrete numbers, commands, and diagrams; show configs and pitfalls.

Include the gritty bits

Commands, configs, pinouts, code blocks, diagrams, and measurements. Screenshots are great; text-only is not.

Cite results

Benchmarks, latency/power, packet captures, soak tests, and what changed after fixes.

Voice & tone

Clear, direct, and honest. No fluff, no sales copy. Share what went wrong and how you recovered.

Fast path to “publish”

2–4 days

Yes, please

Real builds & data
Original diagrams or photos
Clear prerequisites & repo links
Actionable takeaways

Skip these

AI-written filler
Link farms or product pitches
Copy-paste docs
No-code screenshots without context

Length & assets

1,200–2,500 words with 4–10 visuals (photos, diagrams, charts, or code snippets). We help polish formatting and syntax highlighting.

Process

From Pitch to Publish

A short loop with engineers and editors who care about clarity.

Pitch

Share the problem, your approach, and the main artifact (code, schematic, diagram, or dataset).

Review

We respond in 2–4 business days with scope, outline tweaks, and asset asks.

Draft & edit

You write, we edit for clarity, visuals, and safety. We handle formatting and SEO.

Publish

Featured on Analog Data, newsletter, and socials. We track and share performance.

Ready to submit

Pitch your article

Tell us what you want to build or explain. Include links to repos, diagrams, or demos if you have them. We reply in two to four business days.

Set the subject to “Guest Author” automatically
Keep it short; we’ll ask for more if needed
We never publish without your sign-off

Assets we love

Diagrams, pinouts, packet captures, dashboards, benchmarks.

Keep handy

Repo links, LinkedIn, any demo videos or screenshots.