Skip to content

20. Career and community

Time: Ongoing · Prerequisites: a capstone, or the will to build one

Why this matters

Embedded is a small field with a long memory. The people who will hire you, help you, and teach you the rest are reachable: on podcasts, in forums, at conferences, and in the comment sections of the blogs you have been reading for nineteen modules. This module is about getting hired and then getting better for the next twenty years.

Getting hired

The portfolio

One finished capstone with a README, tests, a design doc, and a demo video is worth more than ten half-built projects. Put it at the top of your GitHub profile. Pin it. Your Phase 1 and 2 checkpoint repository is the second pin: it shows the fundamentals, and the commit history shows you did the work.

A short blog, even three posts, changes how you are perceived. Write up one bug you solved with a logic analyzer, one design decision from your capstone, and one thing this guide got you stuck on. Engineers who can write get promoted.

What interviews ask

Embedded interviews are more predictable than most. Expect:

  • C fundamentals: pointers, volatile, static, const, bit manipulation, struct padding, integer promotion, undefined behavior. Modules 2 and 5. Be ready to write code on a whiteboard or in a shared editor without a compiler.
  • Hardware concepts: what happens at reset, interrupts vs polling, ISR rules, memory map, the difference between SPI and I2C, how a UART frame looks, what a watchdog is for. Modules 3 to 7.
  • Systems: RTOS primitives, priority inversion, deadlock, when to use an RTOS at all, how a bootloader works. Modules 9 and 10.
  • Debugging stories: "Tell me about the hardest bug you found." Have three, with what you measured. Module 11.
  • Design: "Design a battery-powered sensor that reports every hour." They want your reasoning about power, radio, storage, and failure modes. Modules 12 to 16.

  • Behavior: how you handle being wrong, working with hardware engineers, and shipping under a deadline.

  • Article Cracking the (Embedded) Coding Interview by Manasi Rajan ~30 min
    What to expect and how to prepare, from someone who has sat on both sides.

  • Article Embedded Artistry: Interviews by Phillip Johnston ~1 h
    How a thoughtful firmware shop interviews, including their favorite open-ended C question. Practice the questions.

Job titles decoded

"Firmware engineer," "embedded software engineer," and "embedded systems engineer" mostly mean the same thing. "Embedded Linux engineer" means Module 15. "BSP engineer" means bringing up new boards, often Linux. "Systems engineer" varies wildly; read the description. "DSP engineer" and "controls engineer" are Module 17 as a career. Look at the parts and tools named in the posting: STM32, Zephyr, FreeRTOS, Yocto, CAN, BLE. Each is a module here.

Getting better

Read and listen

  • Community Interrupt by Memfault Ongoing
    The best embedded blog running, plus a monthly "what we've been reading" roundup that keeps you current.
  • Community Embedded Artistry Ongoing
    Architecture, process, and craftsmanship, with a big free archive and a beginner's page.
  • Podcast Embedded.fm by Elecia and Christopher White Weekly, ~1 h
    Interviews with engineers across the field since 2013. Browse the episode list by topic.
  • Podcast The Amp Hour Weekly, ~1 h
    Electronics and hardware industry conversation. The hardware side of your job.
  • Community Beningo Embedded Group by Jacob Beningo Ongoing
    Practical articles on process, architecture, and tooling for firmware teams.
  • Community The Embedded Muse archive by Jack Ganssle Browse
    Ganssle retired the newsletter with issue 500 in October 2024 after 27 years. The archive is a career's worth of wisdom, tool reviews, and reader war stories.
  • Community Hackaday Daily
    What people are building. Not always industrial, always inspiring.

Ask and answer

  • Community r/embedded and its wiki Ongoing
    Active, generally kind, and the wiki's FAQ answers the questions everyone asks. Search before posting.
  • Community EEVblog forum Ongoing
    Deep hardware expertise and honest reviews of tools. Thicker skin required.
  • Community ST Community, the FreeRTOS forums, and your other vendors' forums As needed
    Where the people who made the chip and the RTOS answer questions.

Show up

  • Community Embedded Online Conference Yearly, online
    Talks from the people whose blogs you have been reading. Recorded, affordable, and student discounts exist.
  • Community Embedded World (Nuremberg, and now Austin) Yearly
    The industry's big trade show. Every vendor, every tool, free exhibition passes if you register early.
  • Community Embedded Open Source Summit Yearly
    Zephyr, embedded Linux, and open hardware under one roof, run by the Linux Foundation.
  • Community Hackaday Supercon Yearly
    The hardware hacker conference. Small, friendly, and the badge is a project.

Local hackerspaces and university IEEE chapters are where you meet people in person and borrow an oscilloscope. Find one.

Do

  • Pin your two repositories and write a two-paragraph GitHub profile README that says what you can do and links your capstone demo.
  • Write one blog post about a bug you solved with measurement. Post the link in a community and ask for feedback.
  • Answer three questions in a forum where you know the answer. Teaching is the fastest way to find your own gaps.
  • Subscribe to two sources from the list and read them for a month. Unsubscribe from the ones you skip.
  • Do one mock interview with a friend using the topics above. Record it. Watch it. Wince. Improve.

Check yourself

  • What are the three bugs you would tell an interviewer about, and what did you measure in each?
  • If a posting says "Zephyr, nRF52, BLE, low power," which modules did you do and which would you brush up?
  • Who are three engineers whose writing you would recognize by style? That is how you know you are in the field.