How should I spend my time looking for my first computer engineering job?

I’d put most of your effort into one or two substantial projects, not a pile of small tutorial copies. Pick something you actually care about, finish it, and make it easy to assess: a clear README, sensible setup instructions, and a demo if the project can be deployed. Be ready to explain what you built, what choices you made, and what you would change next.

Keep some interview practice in the mix, but scale it to the roles you want. Regular problem-solving practice can help with companies that use coding tests. For other roles, technical fundamentals and being able to discuss your work may matter more.

Before sending more applications, pick a few kinds of roles you would genuinely consider, such as backend, embedded, or junior web development. Compare several job descriptions and note which skills come up repeatedly. Then use that list to guide what you learn and to make relevant parts of your CV easy to spot.

Apply consistently, but tailor the CV rather than sending the same version everywhere. A short, specific note to someone on the team or at the company can also help you understand the role and get your application noticed. Meetups, university contacts, and professional groups are all reasonable places to start making those connections.

Don’t treat every job ad asking for experience as a hard no. Some postings describe an ideal candidate, not the only person they will interview. If you meet a good share of the actual requirements, apply and show evidence of relevant skills through projects, coursework, internships, or other practical work.

Also consider internships, trainee openings, and adjacent roles that could build experience toward the work you want. Keep a simple record of where you applied and when, so you can follow up when appropriate and notice whether a particular kind of application is getting better results.

Set a routine you can repeat instead of making the job search your whole day. For example, reserve focused time for applications, project work, and interview prep, then stop at a set time. A modest daily target you can sustain is more useful than a burst of applications followed by exhaustion.

Getting ignored is rough, but it is not a clean measure of your ability. Keep notes on interview questions and application outcomes, and adjust one thing at a time. Make room for sleep, exercise, and people outside the search too.