Meriam Korsan’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

Wannabe embedded engineer? Say goodbye to your worst enemy. It’s not the tech. It’s not the competition. It’s you. 🚨 Your procrastination. 🚨 Your excuses. 🚨 Your unwillingness to get your hands dirty with real projects. You can’t learn embedded systems by watching tutorials. 🎥 You can’t call yourself an engineer if you’ve never built anything. 🛠️ Here’s the truth: 📉 Reading isn’t building. 📉 Watching isn’t coding. 📉 Planning isn’t execution. Your biggest enemy is thinking you’re “learning” while doing nothing. Ready to stop being a wannabe? ✅ Start small, build something real. ✅ Fail fast, iterate faster. ✅ Write code. Burn circuits. Solve problems. Engineers are made in the trenches—not the sidelines. 🔥 Your move? And do not forget about speaking about yourself Follow me and Career Dwar - द्वार for taking your career to next level

Software Engineering: The Backbone of Modern Technology As a software engineer, I firmly believe that the field is the backbone of modern technology. From developing innovative applications to improving existing systems, software engineers play a crucial role in shaping the digital landscape. Some key aspects of software engineering that I'd like to highlight include: * **Rigorous Testing and Quality Assurance**: Ensuring that software products meet high standards of quality and reliability. * **Collaboration and Communication**: Working effectively with cross-functional teams to deliver projects on time and within budget. * **Continuous Learning**: Staying up-to-date with emerging technologies and trends to drive innovation and improvement. If you're passionate about software engineering and want to explore the latest developments in the field, let's connect and discuss! #SoftwareEngineering #Tech #Innovation #Collaboration

We're thrilled to continue our series of posts 🎙️Voices That Inspire🎙️, where we introduce exceptional professionals and their journeys! Today, we’re spotlighting Darius Draghicescu, Software Developer at PRISMA Software Switzerland. He shared his insights on today’s challenges and offered great advice for young professionals eager to grow in their careers. 1. What do you think is the future of embedded systems, and how should developers prepare for it? As a general rule, we all should adapt and evolve. It is the same everywhere in nature and embedded software development is no exception. Technology is evolving at an amazing pace and the automotive business must adapt and embrace the changes. Thus, for us developers, it's a learning game. We must learn all the new technologies if we want to be competitive and stay on top of the game. 2. What advice would you give to software developers looking to transition into the embedded systems field? If you're looking to transition into embedded systems, my advice is to start by building a strong foundation in hardware basics and low-level programming languages like C or C++. Get hands-on with microcontrollers, sensors, and development boards like Arduino or Raspberry Pi to understand the constraints and challenges of working with limited resources. From another perspective, you must have quite good soft skills, because nothing can be done without the help of your colleagues. Also, you must keep in mind that documentation is key. Automotive is a field which involves human safety and security so, everything we do is documented and tested thoroughly. 3. What soft skills have you found most valuable in your career as an embedded software developer? As I already mentioned in the previous answer, communication is key - being able to clearly explain technical concepts to other team members or collaborate effectively with hardware engineers makes a huge difference. Being able to work in a team is a must. Problem-solving and adaptability are also crucial, as you often face unique challenges that require creative solutions. Finally, patience and attention to detail are vital, since working with embedded systems means dealing with complex, low-level code where even small mistakes can have big impacts. #PRISMASoftware #VoicesThatInspire

Working on warning corrections in any project, aside to improve the quality and reduce the risk of bugs, will improve the #skills of the engineer working on the task. It’s a good way (although a bit tedious in some cases) to ramp up the skills and knowledge of less experience engineers and for those arriving to the project. These tasks will help to improve the technical skills as well as problem-solving skills, while enforcing the #communication with other team members to clarify some points and gain some deeper knowledge in design decisions. Some key skills that will be improved are: 1️⃣ 𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐨𝐟 𝐂𝐨𝐝𝐞 𝐐𝐮𝐚𝐥𝐢𝐭𝐲: Correcting warnings helps new engineers understand the importance of writing clean, maintainable, and error-free code, which is crucial for developing robust embedded systems. 2️⃣ 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠 𝐁𝐞𝐬𝐭 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬: By addressing warnings, new engineers learn industry best practices and coding standards, enhancing their ability to write high-quality code. 3️⃣ 𝐀𝐧𝐚𝐥𝐲𝐭𝐢𝐜𝐚𝐥 𝐓𝐡𝐢𝐧𝐤𝐢𝐧𝐠: It encourages analytical thinking as engineers need to analyze the warning messages, understand the context, and determine the best way to resolve them. 4️⃣ 𝐓𝐞𝐚𝐦 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧: Correcting warnings often requires #collaboration with more experienced team members, providing opportunities for mentorship and knowledge transfer. 5️⃣ 𝐎𝐰𝐧𝐞𝐫𝐬𝐡𝐢𝐩 𝐚𝐧𝐝 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐢𝐛𝐢𝐥𝐢𝐭𝐲: Taking responsibility for warning corrections instills a sense of ownership and accountability, important traits for any engineer. #Learning #SoftwareEngineering #CleanCode #KnowledgeTransfer #Development #CodeQuality #AnalyticalThinking

The journey to becoming a skilled embedded software engineer is not without its challenges. Navigating this career path demands continuous learning, adaptation to new technologies, and overcoming complex technical hurdles. Whether you're just starting out or looking to advance your career, join us as we explore the dynamic world of embedded systems and discover the exciting possibilities that await those committed to mastering this demanding yet fulfilling profession. Read more about it in our blog - https://loom.ly/SamULQ4 #embeddedsoftwareengineer #engineeringjobs #blog #redlinegroup

This is a fascinating observation! - Software Engineers are more productive by using LLM tools. - CTOs and Tech Lead don't find notable changes in output. I have so many questions. But also some insights to add. I've been running some private training sessions with O'Reilly for Engineering teams at well know Fortune 500 companies. On these exact 2 (conflicting) vectors: 1. How to increase productivity for the individual SW Engineer? 2. How to prevent that increased individual productivity from hurting the team's output? While question 1 can boil down to "what's the best way to use [whatever best tools available at each moment]? Question 2 is more nuanced, because the perception of risk is huge, from the Engineering Leader's standpoint. If most of your team's code is produced by your Engineers hitting tab a bunch of times. What exactly do you get? - It can hurt code quality - It can hurt learning and upskilling - It can break copyright laws I love the times we're living in. As a Software Engineer at core, I'm embracing and learning these new tools, but also trying to flesh out their limitations.

This is a fascinating observation! - Software Engineers are more productive by using LLM tools. - CTOs and Tech Lead don't find notable changes in output. I have so many questions. But also some insights to add. I've been running some private training sessions with O'Reilly for Engineering teams at well know Fortune 500 companies. On these exact 2 (conflicting) vectors: 1. How to increase productivity for the individual SW Engineer? 2. How to prevent that increased individual productivity from hurting the team's output? While question 1 can boil down to "what's the best way to use [whatever best tools available at each moment]? Question 2 is more nuanced, because the perception of risk is huge, from the Engineering Leader's standpoint. If most of your team's code is produced by your Engineers hitting tab a bunch of times. What exactly do you get? - It can hurt code quality - It can hurt learning and upskilling - It can break copyright laws I love the times we're living in. As a Software Engineer at core, I'm embracing and learning these new tools, but also trying to flesh out their limitations.

I'm an embedded systems engineer. The more I climb the corporate ladder, the more work I need to do. The higher you go up, the more responsibilities you have. The highest title in my embedded career is senior embedded systems engineer. As a senior, your job gets blurry. Senior engineer is still an individual contributor (IC), but is also expected to manage mid-level and junior engineers. Still coding, but also a bit of informal leadership. Not high enough to enter pure management, but high enough to review code, mentor, give guidance, and make technical decisions. Weird right? Not to mention that I'm also doing freelance work, consulting, creating content on LinkedIn, and writing books. All of those require my attention and I only have 24 hours a day. That's why I need to work less while delivering result with higher quantity and quality. Throughout my embedded career, I've developed some techniques that worked for me. They've enabled me to do more meaningful work while deliberately reducing my effective working hours. More here: https://lnkd.in/g9cr78uc

Software engineering is just a means, not an end in itself