Submission guidelines for blogs across Embedded Computing Design brands

July 23, 2019 Brandon Lewis

**The blog must be original to our website, not republished from another media outlet.**

We have just a few main rules:

1) No sales pitches. Readers are turned off by promotional blogs. Any blog that is a product pitch or a company promotion will be rejected. Refrain from mentioning your product and company name unless it is at the end of the blog and without marketing language, i.e. “world’s first,” “best,” etc. In addition, omit any product status information. This type of language will be removed by the editor or sent back to the blogger for a re-write.

2) Blogs should be short and sweet, totaling just three or four paragraphs or longer in the form of a column. They need to be between 400 to 700 words.

3) Have fun. Blogs do not have to be serious dissertations on electronic designs. They can cover current events, marketing challenges in the embedded and IoT design communities, or just what one engineer would say to another over a cube wall.

4) While blogs are not as in-depth as a full technical article, we do ask that they contain a technology tie-in, preferably in the first paragraph. Remember, the Embedded Computing Design audience consists primarily of ENGINEERS, DEVELOPERS, PRODUCT MANAGERS, RESEARCHERS, SCIENTISTS, and EXECUTIVES that serve the electronics industry.

5) Crosslinks. While we would prefer you keep product mentions and pitches out of the blog, we are open to linking a key phrase like “rugged computing” back to your website. In return we ask that you post a link on your website that links back to the blog on ours. In this way, we trade crosslinks and help improve the search engine optimization (SEO) on both our websites.

6) Submit the author’s headshot (head and shoulders), in a separate file from the blog; author photos and any other provided images should be 300 dpi, at least 150 KB in size, preferably with no background and in their native file format.

Recommendations for first time bloggers

Grab the reader: Begin the blog with a catchy, succinct oneparagraph lead. Make it fun – get the reader’s attention.

Problem/Solution: We recommend the Problem/Solution blog style for beginners: Present a problem, then show a solution.

Current event tie-in: Another idea is to take a current event and tie it into the technology you have expertise in. For example, if another DDoS attack occurs but affects the automotive industry, IoT and embedded technology providers will have to provide more robust security measures across the supply chain, perhaps at the hardware, application, or network layers.

Frequency: The more you blog, the more people will know about it. Do what you are comfortable with or consult with the editor on a recommended schedule.

Social Media: We recommend pushing your blogs out on social media, both to build your company brand and the brand of the individual blogger.

Have fun blogging.

Rich Nass
Executive Vice President
Embedded Computing Design

Brandon Lewis
Embedded Computing Design

Perry Cohen
Associate Technology Editor
Embedded Computing Design


About the Author

Brandon Lewis

Brandon Lewis, Editor-in-Chief of Embedded Computing Design, is responsible for guiding the property's content strategy, editorial direction, and engineering community engagement, which includes IoT Design, Automotive Embedded Systems, the Power Page, Industrial AI & Machine Learning, and other publications. As an experienced technical journalist, editor, and reporter with an aptitude for identifying key technologies, products, and market trends in the embedded technology sector, he enjoys covering topics that range from development kits and tools to cyber security and technology business models. Brandon received a BA in English Literature from Arizona State University, where he graduated cum laude. He can be reached by email at

Follow on Twitter Follow on Linkedin Visit Website More Content by Brandon Lewis
Previous Article
Challenges Sensors Face in Overcoming Their Underrated Designation

Sensors face three challenges as they look to overcome their “underrated” designation: maturity, specificit...

Next Article
Stuck in a Loop? Why you Should Consider Moving from Bare-Metal to FreeRTOS

Why should you consider an RTOS? For most, it comes down to knowing ‘what you do best’: if you have always ...