Content Guidelines

If you or someone you represent would like to appear as a guest on the Software Engineering Radio podcast, or if you have a topic that you would like us to cover, this page will give you some insight into our editorial process.

  • The show is primarily topic-driven. We first decide on the subject and then look for an appropriate guest. We research the topic to identify who is active in that area. Some content producers do it the other way around. If you have the guest in mind, then we will ask you for a topic proposal. Your topic proposal should showcase why the guest is one of the best people to discuss that topic. A case study can be a topic.
  • We focus on a single topic for each episode. We don’t have guests on to discuss multiple unrelated things about which they have expertise.
  • Most of our guests are software engineers. Guests need to be knowledgeable about hands-on work in the topic space. If your guest is an executive we will ask some additional questions to ensure that they have sufficient technical knowledge, unless they are speaking on one of our small number of episodes about management.
  • Most episodes feature one guest. We occasionally interview two guests if they are complementary—for example, co-authors of a book.
  • We talk about things that exist and how to build or leverage them. Topics such as “The Future of [topic X]” or “Trends in [topic X]” are not in our scope.
  • We focus on business and enterprise software. We have covered gaming and simulation from time to time; mobile development is within scope. We do not do embedded systems or robotics as stand-alone topics, but we do cover IoT and systems in which devices participate.
  • We aim at a generalist audience. We are a generalist software engineering podcast focusing primarily on programming. Our typical listener is a software engineer with five or more years’ experience in software development, DevOps, or managing people in those roles.
  • Some topics within areas we cover are too specialized for us. If only a specialist could understand the topic, it’s probably out of scope for us. Such topics might be suitable for a specialist podcast in that area. To give an example, we have received a number of proposals on blockchain that require a considerable background in that area to understand the problem that is being solved. These topics would be a great fit for a specialist blockchain show, but not for us.
  • We lean toward open source. There is no prohibition against topics related to commercial products, but the episode can’t come across as a promotion for a commercial product. It cannot cover features only; we must cover some internals. All episodes will include some vendor-neutral discussion of the problem domain. Although we focus more on topics that are vendor-neutral and on the Linux world, we have covered topics in the Microsoft and Apple spaces.

Our Scope

To get an idea of the topics we cover, please browse our archives.
Some core areas that we examine frequently include:

  • programming languages
  • data structures
  • compilers
  • databases
  • operating systems
  • messaging
  • APIs
  • architecture
  • design and design patterns
  • user interface
  • frameworks of all kinds
  • cryptography
  • privacy
  • browsers
  • code style
  • testing
  • concurrency and parallelism
  • test automation
  • containers
  • network protocols
  • security
  • availability
  • performance
  • scaling
  • reliability and stability
  • build tools
  • orchestration and workflow management
  • CI/CD
  • deployment and rollback
  • software configuration management
  • IoT
  • mobile development
  • configuration
  • simulation
  • gaming
  • distributed systems
  • algorithms
  • data science
  • machine learning and AI
  • blockchain and crypto
  • DevOps, DevSecOps, DevMLOps, Dev-✷-Ops
  • capacity planning
  • computer science – with practical implications
  • infrastructure as code
  • metrics and monitoring
  • log aggregation
  • observability
  • on-call and incident management
  • software bugs and debugging
  • choosing the right tool for a purpose
  • tools related to a topic that we cover
  • case studies of how a problem was solved or how something was built
  • how a product or system works under the hood

We sometimes cover topics that are in scope but secondary to our core mission, such as:

  • management
  • agile processes
  • other development processes
  • effective teams
  • career development
  • training and mentoring
  • job roles within software engineering
  • soft skills for technical careers
  • venture capital and startups
  • hiring
  • job interviews
  • software as a business
  • academic computer science
  • learning strategies
  • teaching programming

Some topics are out of scope, including:

  • e-commerce
  • how to market your website
  • a company has released the latest version of their product
  • projects not directly related to software engineering
  • the story of how the guest’s business started from nothing and became successful in spite of numerous setbacks
  • the future of [topic X]
  • trends in [topic X]

To Propose a Guest

If you or someone you represent would like to come on as a guest, please submit a topic proposal. The topic should be original to the podcast. We have published nearly 500 episodes, so please start by searching our website to see if we have already covered your topic.

Your topic proposal should consist of:

  1. Either five bullet points or a 200-word abstract.
  2. Links to any supporting materials by the guest on the topic (a book, published research, blog posts, slide shares, conference talks, open source projects, and so on).
  3. Does the guest’s employer have any content communications requirements (e.g. needs to approve the final audio)? If so, then let us know.

We will evaluate your proposal in this way:

  • Is the topic within our scope?
  • Is this topic original to us (not too close to those we’ve already covered)?
  • Is the guest the best person we could interview on this topic?
  • Is this topic compelling compared to others in our queue?

The show editor evaluates all incoming topic proposals.

Contact the show editor here.

Those proposals that the editor considers to be a good fit are passed to the hosts for consideration. The hosts are free to choose their own episode topics. The hosts in most cases prefer to come up with their own ideas.

We receive several hundred guest or topic proposals each year. We generally record 5 to 10 episodes from external proposals each year compared to 40-45 internally generated topics. External topics thus compete against not only other external proposals but also the hosts’ own ideas.

Once all the hosts have seen a topic, a successful proposal usually gets picked up within 24 hours. We can give you a response quickly when we get to that stage.

Topics with the best chance of approval by the editor and selection by a host have these qualities:

  • Within our scope.
  • Very technical guest.
  • Novel topic to the show.
  • Not too specialized.
  • Guest has written a book, articles, given conference talks, or is involved with the open source project. We have had guests who have not done any of those things, but they will increase the guest’s chance of approval.

If a host wants to do your topic, they will reach out to schedule. The development queue is generally four to six months. After recording, the pre-publication queue is about 2 to 3 months.