RED AND BLUE TECHNOLOGY’s Post

🟦 What Does an Embedded Software Engineer Actually Do? 🟦 🔧 Need the Right Embedded Software Engineer for Your Team? 🔧 💡 Finding the right engineer for your project can be a challenge, especially when it comes to specialized roles like embedded software engineers. At OSI Engineering, we understand the unique skill sets needed for this position and can help guide you to the perfect fit. Whether it's technical knowledge of hardware or a passion for creating smarter devices, we match employers with engineers who have the right blend of skills and experience. 💡 👋 Let us simplify your recruitment process and find the right engineer to power your next innovation. 👋 👩💻 Check out the full article: https://lnkd.in/gbaqx_Ri 👩💻 #EngineeringRecruitment #EmbeddedSoftware #TechTalent #OSIEngineering #Hiring

Take a look at one of our latest roles! Software Project Manager - Embedded Software - #Switzerland. To find out more, please visit the link below #TechnologyCareers #Devicedriver #Python #SoftwareContractJobs#SoftwareContract#SoftwareFreelancer #Embeddedlinux #Testdevelopment #Cprogramming #Embeddedsoftwarerecruiter #Baremetal #EmbeddedSoftwareTest #Firmware #RTOS #Kerneldevelopment #Firmwareengineer #Embeddedsoftwaredevelopment #ICResources #TechnologyRecruitment #TechnologyJobs

In my experience, rushed embedded project development + inexperienced embedded engineer (usually junior) is the perfect combo to generate the maximum amount of bugs possible. Companies usually want the fastest time to market. The rationale is clear: faster delivery -> faster market capture -> faster client acquisition -> $$$. Companies also want to cut costs as much as possible. The rationale is also clear: less money burn -> longer runway -> survive longer -> success. So they pick the most 'obvious' way: hiring junior embedded engineers. But hiring juniors means they don't have the experience to develop something from idea to final product. They literally have never seen shipped products before. Combine that with rushed projects, just imagine how hackish and spaghetti the code would be. I've seen a junior used their own version of scheduler mimicking RTOS task scheduler. Originally, the project only had one loop, but because the company wanted more and more features, he added more loops. But obviously more super loops were harder to code and maintain. So he spent weeks (or months) perfecting a primitive task scheduler. I'm all in writing primitive task scheduler for educational purposes, but for commercial purpose? Time wasted was more expensive than his salary. When I reviewed the code. Oh wow, you wouldn't believe what I saw. I almost suggested the engineer open an Italian restaurant instead because the spaghetti code he produced was enough to feed 50 hungry people. PS: To be fair, in my early career my spaghetti code could compete head-to-head with a pasta factory in terms of production. Everybody has to start somewhere right?

I'm noticing more Engineering companies in the embedded software, firmware and FPGA VHDL space are thinking of getting their experienced senior engineers to RTO more often. Supposedly, Fatigue maintaining cultural cohesion, waning collaboration and less immersive onboarding in remote environments have underpinned RTO. Most of the senior engineers I know have proven to work very effectively and productively remotely, going into the office 1 day per week and even a few days a month. Candidates don't want to commute an hour each way for full on-premise working. It's a waste of their valuable time. Not every Engineering company can offer the same salaries and benefits like the FAANG/MAMAA or other Enterprise companies who are going down this route of RTO with muted resignations, so the flexibility of Remote working is a welcome Benefit especially for less well known SME's. Top Engineering Talent is Hard to Find, but it will be Harder to Keep with full on-premise RTO. Can Senior Embedded, Firmware, FPGA VHDL Engineers work very effectively and productively on a Remote basis ?

Do I know a senior embedded software engineer who has experience on functional safety ?

🌟 Attention Automotive Embedded Software Job Seekers! 🌟 The automotive industry is evolving rapidly, embracing Object-Oriented Programming (OOP), POSIX-based systems, and modern languages like RUST, while moving toward abstract hardware access. 🚀 To stand out in this competitive market, it's no longer enough to just know microcontrollers or have expertise in low-level programming. ✅ Master Software Engineering Principles: Learn how to design scalable, maintainable, and reusable software. Practice your skills using libraries and frameworks. As a SW Engineer you need to learn how to do a selection for a framework. ✅ Adopt OOP Skills: Familiarize yourself with concepts like abstraction, encapsulation, inheritance, and polymorphism. They’re becoming foundational even in embedded systems. ✅ Explore POSIX Systems: Understand multitasking, thread management, inter-process communication, and other POSIX-compliant APIs. ✅ Learn RUST: With its focus on memory safety and performance, RUST is gaining popularity in embedded and automotive software development. ✅ Think Beyond Bare Metal: The HPC being used brings alot of features to the system as availability, safety and security. SW getting complicated. ⚠️low level drivers and firmware developed had been moved to manufacturing hubs. 💡 Advice for Engineering Managers in Automotive Software Engineering 💡 For a long time ⌛️ mastering microcontroller architecture was the rule used in hiring. which is like interviewing Java developers in x86 assembly 🤔 The best investment is building your team.↩️↩️ Great teams don’t just happen—they’re built through continuous learning and growth. Invest in training programs, mentorship opportunities, and a culture of upskilling.

If you're coming from a Software Engineering or similar position in a larger corporate environment and want to jump into start-ups... Bin off the words 'Information Technology' or I.T. Seriously, eradicate it. Keep it far, far away from your CV, cover letter, LinkedIn, emails, everything. I.T is printers, routers, windows installations, monitors... Software Engineers build digital products and experiences that solve problems. I know it's small but for people looking to jump into start-ups for the first time, the perception people have of you, and whether you 'get it' is SO important. The assumption for Software peeps with 'I.T' all over their CV is that you don't.

Aha to test or not to test the algorithm...

𝗧𝗼 𝘁𝗲𝘀𝘁 𝗼𝗿 𝗻𝗼𝘁 𝘁𝗼 𝘁𝗲𝘀𝘁? That is the question. 👉 Do you always test on a model in the loop your software changes? 👉 Even when they are "low risk"? 👉 Do you run regression tests before every deployment? I'd love to hear about your best practices and experience in the comments! -------------------------------- If you find this conversation useful please repost ♻️ - you will help others. Know someone who could be interested? Tag them in the comments! Interested in control and embedded software engineering? Follow me and ring the bell 🔔 on my profile to get a notification for all my new posts.