Issue 52 - Run Coding Models Locally, and Why Being Overqualified is a Risk • Buttondown

Code, Content, and Career with Brian Hogan

April 30, 2026, 5:53 p.m.

Issue 52 - Run Coding Models Locally, and Why Being Overqualified is a Risk

Set up a local coding agent, and understand why you might not land roles you're overqualified for.

Code, Content, and Career with Brian Hogan

In this issue, you'll configure a coding agent to use local models, but first, you'll discover why managers view overqualified candidates as a hiring risk.

You're Too Good For This Role

If you've applied for a role that you're overqualified for, there's a good chance you won't get the job. Most jobs don't want you to be overqualified.

Some people think "overqualified" means "too old and expensive," but that's usually not the case. They are hiring for a specific role that solves a specific type of problem they have, and the role they posted comes with a budget that constrains how much they can offer.

Here are a few reasons you won't move forward if you're overqualified. None of these reasons is meant as a reflection on you or your skills. Hiring someone involves identifying and reducing risk, so managers make a lot of decisions about team fit based on that perspective.

They think you'll leave

There are legitimate reasons that a person wants to take a step back in their career. I've seen engineering managers and directors decide they miss building software and make the switch back to being an individual contributor. I've also known people who end up in staff or lead positions that they don't like, and they want to get back to roles where they just focus on the work rather than larger organizational goals. And in tough economic times, everyone needs work and is willing to take a job with lower pay at a lower level because the bills don't stop coming just because they're out of work.

So when you apply for a job that's well below your experience level but insist you're willing to do the job, the first thing the hiring manager wonders is how long you're willing to do that job for. If they bring you on and train you, will you be putting in the effort they need, or will you be spending your time looking for something that's a better fit? Because the work probably won't be very challenging for you in the long term. The role exists at that level because that's the level of work the team needs to get done. There are likely more senior members of the team who need to work on more complex things.

They think you'll have a superiority complex

Managers have to balance the roles on the team, and they're architecting the team around the role they are hiring for. Hiring someone with more experience for a junior role creates the risk that the person will come in with a "know-it-all" attitude, either intentionally or subconsciously. You have the curse of experience. You'll see things you'd like to fix. You'll see things that "should be a different way." Sometimes this attitude can bleed over into thinking they know more than the manager or team lead, which causes a whole other set of problems.

If you're in a role where you're not able to work at your experience level, frustration can come out in uncomfortable ways. You'll feel bored, unappreciated, and eventually frustrated.

I should point out that some managers are insecure and don't want to be challenged, so they hire people with less experience in an attempt to retain control.

They think you'll have unrealistic expectations about growth

If you're in a role that you're overqualified for, you might get restless and start trying to take on more work outside of your scope of responsibilities. And of course, nobody's going to stop you from doing that because they're getting your skills at a discount. But it does eventually lead to you starting to think, "Hey, I'm doing all this extra stuff. Shouldn't I get a new title and more money?" But that work wasn't what the company hired you to do or asked you to take on. It shows initiative, but coming in and doing all the extra stuff and expecting a title and pay increase right away when you were explicitly brought in to do something else is not going to be helpful. The role was most likely designed for someone to grow over time.

When a manager gets a role approved, there's a budget for the role. If they hire someone more senior, it's very hard to get the role reclassified to a more senior role. In fact, many promotions require a business reason for the promotion, and if the team already has a lot of senior people, it's hard to make the business case for one more.

There's a huge difference between what you can do and what someone needs you to do. This mismatch often causes managers to look for people in the pool who truly are a better fit for the role.

All of the things I mention here are things managers think about as they review applications and have interviews. It doesn't mean you shouldn't apply for roles, but it does mean you should be...