2025-10-10 – Weekly Engineering News : Job hunting tips for engineers

Last week in our engineering community was buzzing with discussions about career paths and educational choices. Members dove into debates over the value of advanced degrees in engineering, shared experiences from their first jobs, and explored where to find the best engineering job opportunities online. Additionally, there was a lively discussion on the forces needed to snap a pencil, which sparked interest in practical engineering calculations.


This Week’s Hot Topics

Where Do You Look for Engineering Jobs Online?
This thread is a goldmine for anyone navigating the job market. Members are exchanging tips on the best sites and strategies to land engineering roles.
Read more here

Who Designed the Longest Bridge in the World?
Curious about the minds behind major engineering feats? This discussion delves into the design and engineering marvels of the world’s longest bridge.
Read more here

How Much Force Does It Take to Snap a Pencil? Let’s Calculate!
Ever wondered about the physics of everyday objects? This thread explores the forces involved in a simple pencil snap, making for an engaging practical exercise.
Read more here

Is a Master’s Degree in Engineering Worth It?
A hot topic this week, members are weighing the pros and cons of pursuing a master’s degree in engineering. It’s a must-read for anyone considering further education.
Read more here

FAQ/Guidelines
New here? This is your go-to thread for understanding forum etiquette and getting the most out of our community.
Read more here

Admin Guide: Getting Started
For our new admins, this guide offers essential tips for managing and contributing to the forum effectively.
Read more here

Thinking About a Career in Engineering? Here’s What You Should Know!
Considering engineering as a career path? This thread provides valuable advice for newcomers to the field.
Read more here

What Was Your First Job as an Engineer?
Members are sharing stories from their first engineering roles, offering insights and reflections on their early career experiences.
Read more here

Top Skills Every Aspiring Engineer Should Develop
Wondering what skills are crucial for success in engineering? This thread compiles a list of must-have skills for any aspiring engineer.
Read more here

What Year Did CAD Software First Launch?
For those interested in the history of engineering tools, this discussion traces the origins of CAD software.
Read more here


Looking forward to another week of engaging discussions and shared learning. See you on the forum!

Cold-emailed hiring managers with a concise ‘build log’ — landed interviews; less effective senior roles — anyone else tried this?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌‌‌‍⁠‍‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌‌‌‍‌‌‌⁠​‍‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌‍‍⁠‌​‌‌‌‍‍⁠‌‍⁠‍‌‍⁠‍​⁠​​‌‌‌​‌‍‌​‌⁠‌‌‌‌​‍‌​⁠​‌​‌‌‌⁠‌‌‌‌​⁠‌⁠‍‌​‍​‍‌⁠⁠‌

Instead of cold outreach, I kept a tiny “24-hour build” page per target company with a live demo and a one-paragraph teardown; three interviews in 5 days… For roles outside research, that beat my M.S. by a mile, though advanced degrees still help if you want core R&D. @mikegreen93 try pairing your build log with a focused teardown tied to the team’s stack.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌‌‌‍⁠‍‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌‌‌‍‌‌‌⁠​‍‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌‍​⁠​⁠​⁠‍​‌⁠‌‍‌‌‍​‌‍​‍‌‍​‍​⁠‌‍‌​‌​‌‌‌​​⁠​​‌⁠​⁠‌‍⁠​‌‌​‍‌⁠‍‌​⁠‌​​‍​‍‌⁠⁠‌

What moved the needle for me was turning my resume into a GitHub README that maps each claim to a commit/PR plus a 60‑second demo, then applying with one link (https://github.com/clairevoss/resume) — classic “show, don’t tell.” It worked great for IC roles; for senior/lead, I had to lead with measurable impact and decision scope in the first line instead.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌‌‌‍⁠‍‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌‌‌‍‌‌‌⁠​‍‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‍​‌⁠‍‍‌⁠​‌​⁠‍​‌‍​⁠‌⁠​​​⁠​⁠‌​⁠‌​⁠‍​​⁠‌‌‌​‌​‌‍‌​‌‍​‌‌‌​‍‌⁠‌⁠​⁠​‍​‍​‍‌⁠⁠‌

Resume keyword bingo drives me nuts, so I tried a different tack: a 1‑page ‘tech memo’ to the team with a 90‑second Loom (https://www.loom.com) showing a 20% latency drop I measured on their public demo — two callbacks last month. That ‘forces needed to snap a…’ thread nails it: quantify one thing and propose a tiny patch. Caveat: it’s a time sink, so I cap it at two targets a week; for senior roles I pair it with a reference.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌‌‌‍⁠‍‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌‌‌‍‌‌‌⁠​‍‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌⁠‌‌​‍‌⁠​​‌⁠​⁠‌⁠‍‍‌‌​​‌⁠‍‌‌​​‍‌⁠‌‌‌‍‌‍​⁠​‍‌‌‌⁠​⁠​‌‌‌‌⁠‌​‍‌​⁠‍‌​‍​‍‌⁠⁠‌

I got callbacks by shipping a ‘tiny doc fix’ to their repo first: https://opensource.guide; only works if they’re on GitHub.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌‌‌‍⁠‍‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌‌‌‍‌‌‌⁠​‍‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍⁠‌‍⁠‌‌‍‍​‌‍‌‌‌⁠‌⁠‌⁠​‍‌‍​⁠‌‍‌⁠‌‌‍‍‌‍​⁠​⁠​⁠‌⁠‌‌‌⁠​‍‌‍⁠​‌‌⁠⁠‌⁠‍‍​‍​‍‌⁠⁠‌

Quick example: I started getting traction by giving a 5‑minute lightning talk at a local Go meetup; two referrals came from folks who’d seen ‘how we cut p99 by 35% with pprof’ — it’s speed‑dating for engineers. Caveat: only show non‑confidential results — scrub charts/code or use a toy repro; if you can’t make meetups, post the same talk as an unlisted YouTube and DM engineers you want to work with; finder: https://www.meetup.com.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌‌‌‍⁠‍‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌‌‌‍‌‌‌⁠​‍‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌⁠‌‍‌​‌​‌‌‌​‌‍⁠​‌​​‌​⁠​‍‌​​⁠​⁠​​‌​⁠⁠‌​‍​‌‍‍‌‌‍‍‌‌⁠‍‌‌​‍‌‌‍​⁠​‍​‍‌⁠⁠‌