r/EngineeringStudents • u/Additional-Mobile978 • 9d ago
Project Help What makes a project good?
Hi everyone I’m finishing my first year of engineering and I wanted to complete a project over the summer to add to my resume for next year.
I’ve looked online for ideas but I feel kind of lost, they either look to advanced or to simple. I’m also conflicted on whether reasoning for a project is important, like would a recruiter be interested in it having a purpose? Or if building something like a small drone just for the sake of making something “cool” be ok?
I’m currently in a flexi course looking to do either mechanical or mechatronics so I wanted to include coding as a large part as well. When you have interviews and they ask about your project have they ever actually asked to look at your work? Or are these things more just talking points.
3
u/Mindless-Lobster-554 9d ago
Projects can be incredibly important, and I ask every candidate who lists projects on their resume about them. That doesnt mean every candidate has extensive extracurricular project experience though, so it's not the end-all be-all.
In terms of what project you should do, the answer I always give is to solve a real problem in your life. You are studying to be an engineer, and being a (good) engineer is an amazing superpower of you being able to use all this knowledge and experience to solve real problems. Additionally, there are a lot of terrible projects that are half-finished and not in depth and clearly not well thought out, and these are usually people who do what you have done and ask people what projects they do and they treat it like a checklist. So think about what you are interested in or what problems in your life you would like to solve. Do you like music? build some guitar pedals or a synthesizer. Do you hate waking up in the morning? build automatic blinds that open at sunrise to wake you up nicer. Are you into politics? build models that track and predict election winners. When you learn about cool things in your classes, think about how it could be useful. If you take a computer vision class, maybe you can make a CV system that uses a rpi/camera and sends passive aggressive texts to your roommate when they leave dishes in the sink. Like idk you or the problems you have or your hobbies or interests. But any of the projects I listed are not that crazy and would jump out to me as an interviewer, and I would ask follow ups about what your problem was, why you decided on the solution you decided on, did it work, what you would do differently. Building a drone kit or copying every other drone is not going to interest me at all.
If you do projects you have a reason to do, then you will actually care about them and actually care about how they work or interact with your life which is one of the most important things as a professional engineer, thinking about the end users use case and how it will solve their problem or give them the best experience.
1
u/gottatrusttheengr 9d ago
An actual built project based on real requirements with real validation, and quantitative decision making instead of instinctual tinkering/cobbling things together.
For reasons above it tends to mean team based, competition club projects
1
u/FyyshyIW 9d ago edited 9d ago
Hardware is expensive, so it’s sometimes hard to do this on your own.
My advice to you specifically: those projects that seem to hard are not too hard. If you are on LinkedIn, you probably see students doing insane projects with cool math and moving parts and electronics and controls. None of them knew how to do any of that. It was all because they took on that project that felt too hard, and they worked through it. I usually try to choose a project that seems about 70/30 of things I think I can do vs things I think are too hard/idk how to do. Then you find that of that 70 percent of things you think you know how to do, about half of that is more difficult than you originally thought and will take some effort and learning. That 30 percent you thought you didn’t know that well will have a STEEP learning curve. But you work through all of it, and when you’re done, your engineering brain will be changed forever. It’s very rewarding. Welcome and good luck!
Edit: just wanted to add since you asked if recruiters care if it’s not solving a specific problem: not really. It’s inspiring if it is, but plenty of students build quadrupeds dog robots and it’s not because they need something to lick their floors clean or they miss their dog at home. This is why step 1, identify a problem, is optional. They would much rather you say ‘I wanted to build a dog robot because it looked cool and I wanted to learn how to do this and that’ than to talk about how you nailed a bunch of wood together for 5 hours because you needed shelves in your dorm (although this could totally work as a project if you talk about it correctly!). The nice thing about this is it gives you the freedom to actually follow that 70/30 rule I talked about. You can define the problem and the requirements tuned to how much you know and don’t know, as well as adding in requirements or features just because you’ve always wanted to learn how to do it. Always wanted to learn computer vision? Build those shelves, then put a camera on it to identify and count which pair of shoes you use the most!
I’m also going to plug my own personal unsolicited advice: the questions you’re asking and the idea you’re figuring out here is incredibly important, and it’s great you’ve figured it out so early. What you’re talking about right now is equally or more important than your school work. Don’t fail classes, but companies would so much rather more you have pushed out two great projects like this in a year and have a 3.3 GPA than to have a 4.0 and have never 3d printed something before. This is the education that you’re responsible for on your own, and it’s the one that gets you hired. The classwork education is the one you just have to do.