What Would Be a Valuable 15-Day Internship Project in Embedded Systems?
Asked by
MellowCedar47
I've just started a 20-day summer internship in an R&D department focused mainly on embedded systems, although my team works on the software side rather than electrical circuits. My mentor explained that AI tools are shortening many development tasks, and he suggested I find a topic or combination of topics that could become a worthwhile project in roughly 15 days. He wasn't very enthusiastic about a web-design project.
I'm entering my third year and currently know Java, Bash scripting, C, some Python, and am beginning to learn C# and the .NET framework. I also considered a cybersecurity-related project, but I'm not sure how interested my mentor was. What kind of project could be useful to the company, challenging enough for two weeks, and still realistic for an internโeven with AI assistance?
Answers
Try to solve a real problem for the team rather than choosing a technology first. A small developer utility, test automation tool, log analyzer, documentation search tool, or security checker for existing projects could all fit an embedded-software environment. Ask what repetitive or frustrating task the engineers wish they had automated.
Reply to this answer
A practical option would be a small C#/.NET service with authentication, authorization, logging, and a useful internal feature. Even with AI helping write code, understanding the requirements, handling edge cases, testing it, and reviewing the generated code will take time. Just avoid making it mission-critical during a short internship.
Reply to this answer
Your mentor may simply not have prepared a specific intern project. Talk with developers on the team about what theyโre currently working on and look for a small, well-defined task you can contribute to. Once you find something useful, confirm the scope with your mentor. That will probably produce a more relevant project than inventing one from scratch.
Reply to this answer
A security-focused code or configuration scanner could be interesting, especially if it targets the companyโs own projects and follows their rules. Keep the scope narrowโsuch as detecting common issues, checking dependencies, or reviewing insecure configurationsโand make the result a safe prototype rather than claiming it can find every vulnerability.
Reply to this answer
If the company has recurring internal dataโtest results, build reports, defect records, or weekly status filesโyou could prototype an analytics tool that processes it and generates a clear report or dashboard. That gives you a concrete deliverable while letting you practice scripting, data handling, testing, and possibly integration with existing tools.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions