I recently got drinks with a younger engineer, who remarked something like: “I want what you have — I want people to know that I’m a good engineer. How do I do that?”
I don’t feel particularly famous. I’m happy doing what I’m doing, but it’s nice to know that if I wanted a job I could get a pretty good one. And the same is true for many of my friends. Because I’m a somewhat established software engineer, I know a lot of people at excellent companies who would be happy to refer or vouch for me.
In today’s job market, it can feel hard for people to stand out. But as someone who also receives hundreds of resumes a month, all accompanied by the same AI-generated emails, I can also tell you that it’s harder than ever to find candidates who seem to be trying at all.
I won’t lie. Time and luck help a lot. But I would be doing a disservice to say there’s nothing you can do other than wait; and in this piece I want to go through the ways you can develop the right skills, and make them legible.
First, who do you want to impress?
I want to emphasize that, in engineering, it doesn’t matter what the average person thinks. What’s important is what other good engineers think about you.
Even ‘other good engineers’ here is a little bit tricky to define though. There are lots of audiences you might want to be known to, depending on your interests. If you’re excited about AI, maybe you want to impress the AI-pilled tech influencers on X. If you like making silly games, maybe you want to impress the Brooklyn art-tech scene. Maybe you love systems and you want to impress the old-school open-source hackers. Maybe you want to get promoted and get better projects, and so you want to impress the principal engineers at your mid-sized company.
To be honest, I don’t think it matters what audience you pick. If you can impress one, that usually goes a long way with the others.
What I would say is that you should find one community that you admire, technically, and truly want to spend more time around and learning from. And then, as you go forward, think not about how they can help you, but what you can contribute that will benefit that community.
Do good work, then talk about it
I feel a bit bad giving this advice because it’s often said and seems simple. But few people follow these steps, and they work:
Do good work
Talk about it
1. What is good work?
I can’t emphasize enough how important it is to do good work. There are many factors that go into it, but — assuming you’re smart — the most important things you can do are to be earnest and persistent.
I think there’s a meme going around that you need a good side-project to be hired, and I can understand why. But as a result, I see people trying to ‘hack’ having a side-project all the time, by listing on their resume something that sounds impressive, like fine-tuning a YOLO model or hustling to get a paper with marginal research value into NeurIPS.
That can work on some people. But real experts can pretty often tell whether something was hard and unique or not. And those are the people whose judgement usually matters.
In general, I would say that a good project should take you a lot of work — like weeks, or months — and teach you something that most of your peers don’t know or haven’t done. It can be something fun like implementing a video game, or as straightforward as doing a project at work that stretches your technical abilities. But it should probably be something you genuinely think is cool. If you think it’s cool, it probably is!
However it can’t be a standard work project or a homework assignment. Because, by definition, that is something your peers are already doing. The best way to find unique projects like this is to follow your interests into topics you’re passionate about. Doing these projects, as Paul Graham points out, can often make you a better engineer too:
If you really want to learn to program, you have to work on your own projects. You learn so much faster that way. Imagine you're writing a game and there's something you want to do in it, and you don't know how. You're going to figure out how a lot faster than you'd learn anything in a class.
(If you work at a company, you might ask: how do you get great work projects and not standard ones? Usually, by explicitly asking your manager. Most managers might not assign cool work by default, but can put in some work to find one if you indicate interest. I can’t emphasize enough how important it is to actually ask, though; and you then have to keep up your side of the bargain, though, by working hard on it.)
2. How do you talk about it?
It’s not sufficient to just do good work! I know many an engineer who has felt their good work was overlooked or ignored — and this can be true both at large and well-managed companies and for students in school.
Here are a few ways you can talk about your projects:
Literally showing up and talking to people.
I think this is often underestimated by engineers, but is unreasonably effective (in addition to being fun!).
If you work at a company, there are probably talks or happy hours that people go to. You should go, too! This can be a good way to meet people you don’t know, and engineers love to hear about cool projects.
If you live in a tech hub like SF, you can go to events too. But be careful. I would advise against events with 100+ people. You can sometimes get value out of them, but it takes skill.
Instead, try to find a niche meetup of 10-20 people, who care about something random and maybe even uncool. So in SF today, go to the Rust or random discord meetup, not the flashy ML meetups sponsored by large companies. One of the best AI meetups I ever went to came out of a discord post, and had just 3-4 people, and we spent the whole time demo-ing projects to each other.
If you don’t live in a tech hub, sometimes online communities can substitute for this, like joining a discord or contributing to open-source. Again, though, you have to join and contribute by doing work, rather than dropping a link to your project and then dashing off. And you should try to find a community where people care, and even volunteer time to participate.
Writing, and/or giving talks
Literally showing up can often get you a long way. If you want to take it one step further, though, I recommend writing (or giving talks, if that’s more natural to you).
Writing is one of the few forms of communication that, like software, scales. It gives you another level on which to share your skills, beyond simply putting a project up on Github. When you write or give a talk, you get to go into why you built a thing a certain way, or what twists and turns you encountered while getting there. It gives you space to express your ingenuity.
Frustratingly, you cannot simply write a post and then publish it and hope it gets found. You should write it, then submit it wherever you can: Hacker News, relevant Reddit subreddits, even lobste.rs if it’s appropriate.
I won’t lie, sometimes this can feel like shouting into the void. But this is where working within a niche and community can help. You might not get to the front page of Hacker News, but once you write a cool post you can send it by DM or email to friends and mentors in your community, who can give useful feedback or help signal-boost it.
Good communication is a superpower
If you are good enough at writing, you have more options than to write about your projects. One of my favorite engineering blog posts is “In defense of blub studies” by Ben Kuhn, where he argues that a lot of excellent software engineering is about understanding computer esoterica in greater depth than you ever imagined necessary. This post isn’t about a specific project, but it’s the result of him putting together many, many different projects and analyzing a general pattern out of it.
This sort of writing itself can often demonstrate technical skill. One common sign of a great engineer is their ability to take something that seems complicated and reduce it to a few simple parts. For instance, the best design docs are deceptively simple, or as Grant Slatton put it:
[A] good doc will lay out the problem and mental models in a way that the solution that took 2 weeks of hard thought to invent will be clear to the reader by the time the doc presents it.
Writing clearly is often, itself, good engineering work, and doing so about a more general topic is often one of the best ways to demonstrate it.
Case study: Nolen (eieio.games)
One person I think has done this well is my friend Nolen, who makes silly and viral games on the internet. I first met Nolen when we were colleagues and he worked on internal infrastructure. This was not a super-glamorous part of the company, but Nolen was well known because he both did great work, and wrote many good internal tech blog posts. He was also a friendly person, someone who almost everyone knew!
When he left, he started to make silly video games. His first few didn’t spread super widely, but he wrote an in-depth blog post for almost every project he worked on. Over time, he got a lot better at both making viral games and writing about them, and his best game eventually ended up in the New York Times!
Why might you want this?
Maybe you’re looking at this and going to yourself, ‘gosh, this seems hard.’ And I agree, a lot of these steps aren’t very natural to someone who wants to write code all day.
But they are actually a big part of making you a better engineer. The best engineers aren’t lone wolves; they’re part of a network of experts who they can work together with or ask advice from. The larger your network, the better the work you’ll be able to do.
There are material benefits too. Folks I know who are well known don’t apply for jobs; people constantly reach out to them, having already thought through the best role for them. It’s not only jobs; other strong technical people reach out, to be friends. It’s a good way to live!
If there’s one thing I hope you take away, it’s that I think this is within reach for many people. It just requires doing the right kind of directed work. There are only two steps. It’s not easy, but it’s simple.
Thanks to Ben Kuhn for comments on an early outline of this post!


Yes to all this! I recently changed jobs through a friend's recommendation and now my running joke is that I only ever change jobs because someone tells me to! The only job I got on the open market, so to speak, was my first one. Also, plus one on the Ben kuhn rec. One of my all time favourite blog posts is "searching for outliers" - I recommend it to everyone I work with and I find people's reaction to it is an interesting litmus test for their general capabilities. Plus (some beautiful circularity here) one of the outlier examples he gives is jobs! Like, the best jobs often aren't just out there at a random company, they're usually the extra special ones that people back-channel because they're too important to trust to any old person.
I think there's also a point I'd make re the communication stuff. It's kind of like dating where one way to think is "man, I don't want to inconvenience this person by introducing myself to them" versus "man, I think I'm a decent person and maybe this other person's life would be better with me in it". I think you can have this mindset shift with comms where you start thinking "hey I actually built/learnt/researched something kinda cool and there might be a few people out there who genuinely like it, and imagine if I deprived them of that pleasure because I was anxious/scared/lazy rather than stoked to share my fun with the wider world". That helped me a little bit (though tbf I'm more on the extravert side and I'm fairly opinionated so I've never had a problem telling people what I think 😂)