Tips for moving past the elephant in the room during college career steps

Oct 20, 2026 Last reply: 5 days ago 5 Replies
Jump to replies (5)

If you are in the thick of EE classes while also dealing with a background like yours, the biggest hurdle isn't the differential equations; it's the first interview. My advice is to focus intensely on building a robust portfolio that speaks for itself. While your history is a fact, your skill level should be the undeniable highlight of your application to future roles. Show them you can build a functional circuit or write clean code, not just that you went to school.



When that conversation inevitably comes up, treat it like a matter of pure proffesional integrity. Don't over-apologize or sound defensive. Acknowledging it once, briefly, and then immediately pivoting to your track record of continuous self-improvement is the way to handle it. You've proven you can commit to something difficult and stay disciplined, and that is what they are actually looking for in a future engineer.



Keep building your project list. If you can show an employer a complex digital design you completed on your own time, they are less concerned with past mistakes and much more intersted in your capacity to deliver results.


I took the advice to build a serious portfolio and started applying for contract roles last year. I managed to land an interview with a small firm that deals mostly in custom PCB design. I made sure my resume focused entirely on my successful implementations of the digital logic gates I designed using Verilog. When they brought up my past, wich they did, I kept it brief. I just acknowledged the situation once and imediately shifted the conversation back to my personal project where I used an STM32 microcontroller to manage temperture readings. They seemed to appreciate the direct approach. The hiring manager said they were looking for discipline and follow through, and my track record of getting those complex projects done on my own time seemed to speak to that. I ended up getting the role, which was a relief. It was definitly a struggle, but it proved that a strong technical foundation and handling the difficult conversation maturely can make a difference in how a company views your potential.

Congrats on the offer. My path was similar but slower. I spent about a year fixing broken appliances and audio gear for people in my neighborhood before I ever applied anywhere. What actually made things click for me was a used bench oscilloscope I picked up cheap. Being able to see what a circuit was doing instead of guessing turned my hobby projects from messy breadboard stuff into things I could actually explain in an interview. Small shops seemed way more interested in that than the big companies, who mostly just ran the background check and stopped replying. Did you find the same thing with firm size, or did the bigger places give you a real shot too?

Congrats, that STM32 project sounds like it did exactly what a portfolio should do. One thing I'd add from my 12 years in industrial controls: smaller shops often run looser checks than the big firms, so aim there first and let the expirience stack up. I got my start at a panel shop with 30 employees, and three years of solid work there opened doors that a fresh resume never would have. By the time I applied to the larger plants, my references were doing the talking. Timing the disclosure matters too, I always saved it for after the technical interview when they allready liked me.

One thing I'd add from my own experience applying to places with a record: find out exactly what shows up on the check before the interview does. I pulled my own report thru the same consumer reporting agency a big employer would use, and there was actually an outdated entry on it that took two months of paperwork to get corrected. Had I not looked, I'd have been standing in an interview denying something that wasn't even on paper anymore. Also, keep a dated build log for every project, because in my second interview the questions were all about why I made specific design choices, and having written reasoning from months earlier made the answers sound considered rather than rehearsed.

Quick update - I started focusing on those smaller panel shops as one person suggested. Getting through the initial screening was definitely easier than I expected. Still, the technical interview rounds themselves are quite tough, and I'm spending most of my time now prepping for those deep logic and circuit questions.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required