Everyone wants to "break into tech." Few people stop to think about how they want to be found. The market is neither easy nor impossible: it is selective. And being selective rewards people who know how to position themselves, not those who shout the loudest. Let’s look at what actually works, without any magic formula.
A portfolio that shows decision-making, not just code
Recruiters don’t read your entire portfolio. They scan it looking for one signal: does this person solve problems, or do they just follow tutorials? Three projects you understand end to end are worth more than ten half-finished screen clones. For each one, make the problem, the technical decision, and what you would do differently today clear. The README matters more than the star count. “I built a CRUD app” says nothing; “I chose Postgres because I needed X and accepted the cost of Y” shows that you think.
Build in public without becoming an influencer
Building in public isn’t about posting motivational threads. It means showing the process: the bug that blocked you for two days, the decision that went wrong, the piece that finally worked. You don’t need an audience; you need a trail. A handful of honest posts about what you’re learning creates a history that speaks for you when you’re not in the room. And no, you don’t need to become an influencer. You need to be discoverable.
Interviews: you’re not being tested, you’re having a conversation
A technical interview isn’t an exam where you either get the answer right or fail. It’s a simulation of what it’s like to work with you. Thinking out loud, admitting “I don’t know, but I would look into it this way,” and asking questions before you start coding are signs of maturity, not weakness. Prepare two or three real stories: a difficult problem, a conflict you resolved, and something you broke and fixed. Memorizing LeetCode problems only gets you so far if you don’t know how to have a conversation.
Networking without making people cringe
The kind of networking that gives the practice a bad name is when someone only shows up to ask for a referral. What works is the opposite: help before you need help. Answer a question in a group, leave a useful comment on someone’s work, or send an article to the right person. A network isn’t a contact list; it’s a group of people who remember you for a good reason. It is built slowly, and you can’t outsource it.
Specialize or generalize? It depends on where you are
“Should I specialize or become a generalist?” It depends on where you are. At the beginning, breadth wins: experiment, find out what you enjoy, and learn what the market pays for. After a few years, depth in one area makes you the person people call for that specific problem. The mature shape is usually a T: a broad foundation and one deep area of expertise. Don’t choose a label; choose your next step.
Read the market without buying into the hype
Every cycle has its hype: it was blockchain, then it became AI, and it will become something else. Reading the market honestly means separating what can get you a job tomorrow from what can get you a tweet today. Look at real job postings, not guru threads: what are the companies you want to work for actually asking for? Learning the latest hype is great as long as the fundamentals remain solid. Someone who understands systems can learn a new framework over a weekend; the reverse is not true.
Positioning yourself isn’t about pretending to be senior or inflating your LinkedIn profile. It’s about leaving a trail of what you know, communicating well, and choosing where to invest with a clear head. The market is selective, and that’s okay: selectivity is exactly where prepared people stand out. Start with your next commit.