Skip to main content

Command Palette

Search for a command to run...

the unsexy habits that actually get you hired

no shortcuts. no secrets. just patterns from people who did it.

Published
4 min read
the unsexy habits that actually get you hired
A
a TypeScript full stack developer shipping scalable web apps and adding AI powered workflows on top.

i've spent time around people who got placed at good companies. not because they got lucky. not because they had some secret. just patterns. you hang out with enough people who got the same outcome and you start noticing things. here are seven of them.

one: actually know your fundamentals

this sounds obvious but most people skip it. they want to build the shiny thing first. but if you don't understand first principles, you hit a wall later.

take schema design. give someone a problem like "design a social network's database" and you'll quickly see who gets it. the friendship graph. how do you store that? how do you query it? basic crud is easy. the hard stuff is what separates people.

the ones who got placed went deeper than they needed to. they didn't just copy projects. they understood why things were built the way they were.

two: actually like coding

sounds stupid to say but most people don't. they want the job, the salary, the title. but coding itself? they'll drop it in 5 years for management.

the people who got placed see themselves doing this for decades. they cross-question in class. they catch things you missed. they read documentation for fun. they build simple apps themselves instead of asking ai to do it.

can you learn to love it? maybe. i hated coding when i started college. wanted to make films. but somewhere it clicked. i've seen people from completely different backgrounds become great engineers. the interest can grow if you let it.

three: ability to sit for long hours

not healthy. just real.

talk to any good developer. they've done the 4-5 hour sprints. the 20-hour days before deadlines. i'd see the same faces in coworking spaces at 4am. not because they had to. because they were deep in something.

spend 6 months putting in real hours on one stack. 10-12 hours a day. you build familiarity. most jobs are the same stuff anyway - backends, frontends, deployments. the business logic changes but the foundation doesn't.

and here's the thing - if you put in those hours and nothing clicks, that's useful information too. at least you know.

four: the right peer group

saw this pattern constantly. one person in a group of four gets placed, the other three follow within a month.

someone gets placed at a good company. their roommate helped them prep. immediately asked for a referral for the friend. two weeks later, same company. both at good packages.

same story in other groups. when smart people cluster, everyone gets smarter. you pick up momentum. healthy competition kicks in. it's like competitive exam days - compete with friends on the leaderboard, everyone ends up with good ranks.

coding feels unpredictable but it's not. four people outperforming everyone else in a cohort? all four probably get jobs. compensation varies but the outcome doesn't.

five: ignore the market noise

market's weird right now. some hiring, some layoffs. easy to blame the market. easy to consume negative content and convince yourself nothing's possible.

but once you stop believing, you stop trying. then you definitely don't get placed.

smart engineers who can actually build things will be hireable for a long time. the role might change. the tools will change. but the core skill - clear fundamentals, first principles thinking, ability to contribute - that stays valuable.

even if you're in a low paying job or just graduated, there are vectors. friend's startup. freelance work. something. the core belief has to stay: put in the work, get the outcome. lose that and you're done.

six: own your placement

friends help. mentors help. but it's on you.

some people got jobs themselves. no referrals. they reached out directly to founders, hiring managers, technical leads. showed their work. got interviews.

one person built a blockchain indexer. tweeted about it. went semi-viral. job offer next day.

another built a memory library. tweeted, applied, interviewed, got hired.

another had a complex ai project, went viral, cold message from founder.

the pattern: one ambitious project that aligns with what a company needs. then reach out with something real. not ai-generated spam. not mass emails. one good project, one meaningful message.

three ways to get hired as an early engineer: great college pedigree, referral from someone who trusts you, or build something impressive that matches what the company wants. that's it.

seven: there is no shortcut

look at all six points. nothing revolutionary. fundamentals. interest. hours. friends. optimism. outreach.

the people looking for magic pills don't get placed. the ones who go deep on one thing, who actually understand what they're building, who surround themselves with people pushing forward - they do.

focus less on shortcuts. more on depth. opportunities follow automatically.