EurthTech Notes

At some point in every connected product journey, leaders face a decision that feels deceptively simple. Should we build this internally, or should we work with an external engineering partner? On the surface, the trade-off looks straightforward. Building in-house promises control, ownership, and long-term capability. Partnering promises speed, experience, and reduced upfront risk. Most discussions stop there. In reality, this decision shapes far more than cost or timelines.

Here's the rule: separate what the partnership is for from what each side contributes, and get both in writing before the excitement of the first meeting turns into an ambiguous handshake agreement nobody can execute against six months later. University-industry partnerships fail less often over bad intentions than over unstated assumptions — a hardware team assumes a research collaboration means co-development rights; the university assumes it means access to publish; nobody

Every electronics trade show floor has the same visible split: booths where the team looks relaxed and in control, and booths where someone is visibly troubleshooting a demo at 9:15am on day one. The difference is almost never talent or budget. It's a short list of specific preparation gaps that are individually easy to fix and collectively responsible for most booth-day stress — none of them require more money, just earlier attention. Here's the list, one item at a time. Dem

The Talent Gap Nobody Is Talking About Loudly Enough India is building smart cities, deploying IoT in agriculture, modernising defence electronics, pushing into semiconductor manufacturing, and developing an indigenous space programme. Every one of these initiatives requires embedded systems engineers — people who can write firmware, design PCBs, debug hardware-software interactions, and understand the physics of electronics well enough to make reliable products for harsh env

A Note Before We Begin I am writing this blog directly to you — the engineer who is thinking about joining EurthTech, or who has just joined, or who is curious about what kind of company this is and how we think about the people we bring in. Over the past several months, EurthTech has grown. New engineers have joined the team. Some came from college, bringing the energy and theoretical foundation of a fresh education. Some came from other companies, bringing habits, expectati

The Hook: Stepping Out of the Codebase You’ve mastered C/C++. You can write interrupt service routines in your sleep, and you know exactly how to squeeze that last byte of RAM out of an ARM Cortex-M4. When a hard fault occurs, you dive into the disassembly and register dumps with the confidence of a seasoned detective. You are a highly effective firmware developer. But lately, you’ve noticed a shift. The challenges that excite you aren't just about optimizing a single driver

Reading Time: 25 mins Topic: Engineering Mindset & Productization Bridging the gap between academic projects and industry reality. Indian engineering student soldering a PCB at a cluttered desk The Hook: The Great Indian Engineering Paradox India produces over 1.5 million engineering graduates every year. We have the drive, the mathematical foundation, and the hustle. Yet, ask any hiring manager at a top hardware or embedded systems company, and you'll hear the same frustrati

Author: Srihari Maddula Reading Time: 15 mins The complexity of the silicon is where real engineering happens. Photo by Unsplash. In most engineering college labs and hobbyist circles, the goal is simple: "Make the LED blink" or "Read the sensor value." If you can do it in 5 minutes using a drag-and-drop interface or a high-level abstraction library, it's considered a success. You feel productive. You feel like an engineer. You might have used tools that promise "no-code" IoT

Let's be honest. Your ECE/CS degree teaches you Ohm's Law, Laplace Transforms, and maybe some 8051 assembly. It does not teach you how to be an Embedded Systems Engineer in 2026. If you rely solely on your college syllabus, you will graduate with knowledge that is 10-15 years out of date. To get hired at a company like EurthTech (or Tesla, or Apple), you need to build a parallel curriculum for yourself. Here is the roadmap I would follow if I had to start over today. 1. Build

Author: Srihari Maddula Reading Time: 8-10 mins Tags: Compliance, Manufacturing, Documentation, Testing, Career Advice The code compiles. The LED blinks. Now the real work begins. (Photo by ThisisEngineering RAEng on Unsplash) The "Done" Illusion In college, "done" means the code compiles and the demo works for the professor. In the industry, when the code is "feature complete," you are about 40% of the way to shipping a product. Junior engineers often ask: "I finished the fi

Author: Srihari Maddula Reading Time: 8-10 mins Tags: System Design, Hardware Engineering, RF, Manufacturing, Sensors The MCU is just one component. The magic (and the failure) happens in the connections. (Photo by Michael Dziedzic on Unsplash) The "Chip-Centric" Tunnel Vision Ask a junior engineer to design a smart thermostat, and they will immediately start talking about the microcontroller. "Should we use an ESP32 or an STM32? How much RAM do we need? What clock speed?" As

Embedded engineering sits between electronics and software. This roadmap lists what to learn, roughly in order, and why each piece matters in real products. 1. Core knowledge Math: algebra, trigonometry, basic calculus and some linear algebra. You need them for signal processing, control loops and sensor calibration. Circuits and electronics: Ohm's law, Kirchhoff's laws, RC filters, diodes, transistors and op-amps. Reading a schematic is a daily skill. Computer architecture: