Good Engineer Reputation: How to Build One

Engineers sharing projects, illustrating how to build a good engineer reputation

A veteran software engineer has published a two-step plan for building a good engineer reputation: do work that is hard and unusual, then tell people about it. The advice comes from a post on the blog Approach with Alacrity, written after a younger engineer asked over drinks how to get the kind of standing the author has.

The author says that standing has a practical payoff. They know people at strong companies who would refer or vouch for them, so a good job is within reach if they ever want one.

Pick one community to impress

The post argues that the average person’s opinion doesn’t matter in engineering. What counts is what other good engineers think of you.

Which engineers? That depends on your interests. The author lists a few options: AI enthusiasts on X, art-tech circles in Brooklyn, old-school open-source hackers, or the principal engineers at your own mid-sized company. The choice matters less than you’d expect, since impressing one group tends to carry over to the others.

The advice is to choose a community you admire on technical grounds and want to learn from. Then ask what you can give it, not what it can do for you. A good engineer reputation grows from contributions, not self-promotion.

What counts as good work

The author’s view is that earnestness and persistence matter most, assuming you’re already smart. They are skeptical of the idea that every candidate needs a side project. Some people game it by putting something impressive-sounding on a resume, such as fine-tuning a YOLO model or pushing a thin research paper into NeurIPS. Real experts, the author says, can usually tell whether a project was hard and original.

A strong project, in their definition, takes weeks or months and teaches you something most of your peers haven’t learned. It could be a video game. It could be a work project that stretches your abilities. It shouldn’t be a standard assignment or homework, because by definition your peers are doing those too.

The post leans on Paul Graham for support. He has argued that working on your own projects teaches programming faster than a class does.

Employees can ask for better work, too. The author suggests telling your manager you want an interesting project. Managers rarely hand those out by default, but many will go find one if you show interest. Then you have to deliver.

How to talk about it

Good work alone isn’t enough. The author knows engineers at well-run companies and in school whose strong work went unnoticed.

The post offers a few ways to get it seen:

  • Show up. Go to internal talks and happy hours at your company. Engineers like hearing about cool projects.
  • Pick small meetups. Skip events with 100 or more people. A niche group of 10 to 20 is better, even if the topic is unfashionable. The author recalls one of their best AI meetups starting from a Discord post and drawing just three or four people who demoed projects to each other.
  • Join online communities if you’re far from a tech hub. Contribute real work instead of dropping a link and leaving.
  • Write or give talks. Writing scales the way software does, and it lets you explain why you built something a certain way.

Publishing isn’t the finish line. The author says you need to submit your post to places like Hacker News, relevant subreddits and lobste.rs, and accept that it can feel like shouting into the void. Sending it directly to friends and mentors in your community can bring feedback and a boost.

Writing as proof of skill

The post argues that clear writing is itself engineering work. It cites Ben Kuhn’s essay “In defense of blub studies,” which draws a general pattern from many projects. It also quotes Grant Slatton’s view that a good design doc lays out the problem so clearly that a solution which took two weeks to invent looks obvious by the end.

The author’s case study is a friend named Nolen, who makes viral games at eieio.games. Colleagues knew him for solid infrastructure work and a steady stream of internal blog posts. After he left to build games, he wrote a long post about nearly every project. His first few games didn’t spread widely, but he improved at both the games and the writing, and his best one ended up in the New York Times.

Why bother with a network

The author admits this advice doesn’t come naturally to someone who’d rather write code all day. Their argument is that it also makes you better. The best engineers aren’t lone wolves, they say. They have a network of experts to work with and ask for advice, and a bigger network supports better work.

There are material perks. People the author knows who are well known don’t apply for jobs. Recruiters and peers reach out with a role already in mind.

What readers can do this week

The takeaway is concrete if you want a good engineer reputation of your own. Choose one community. Start a project that will take weeks and teach you something your peers don’t know. Then write about it and submit the post wherever it fits. The author calls the plan simple but not easy.

It’s one engineer’s opinion, not research. But it matches what hiring managers say they miss in a flood of near-identical, AI-written applications: evidence that someone is actually trying. The post was shared in the TLDR Tech newsletter on November 18, 2026.

Source: approachwithalacrity.com

Written by

Saksham Bhargava

Saksham Bhargava runs Alteroid and has been writing about consumer technology for over five years, covering iPhone, Android, Windows, AI tools and gaming. With an MCA and six years of hands-on web development experience, he tests the features he writes about on his own devices and focuses on clear, practical guides that solve real problems. Away from the screen, he enjoys travelling to places most tourists skip.