I'm 22, unemployed, and feeling completely lost about what direction to take. I enjoy programming, but I keep jumping between full-stack development, Rust, cybersecurity, compilers, and agentic AI. I start tutorials and projects, but often get stuck or distracted before finishing them.
At this point, I feel like I know a little about many topics without having enough completed work or practical results to show employers. I want to find a job, but I'm unsure which skills are worth learning, what employers actually want, and how to choose an area that isn't impossibly competitive. There's also pressure at home to start earning, and I don't have many people to discuss this with.
I haven't given up on programming or on myself, but the number of possible directions feels overwhelming. How can I choose a realistic focus, create a useful study plan, finish meaningful projects, and start moving toward employment?
4 Answers
Don’t measure progress only by whether you have a technology job immediately. If necessary, work somewhere else temporarily and look for ways to build simple tools or automate repetitive tasks there. Real users, even in a small business, can give you practical experience and people who can vouch for your reliability.
Most importantly, reduce the scope of your next project until finishing it is almost unavoidable. A small completed application is more valuable for momentum and a portfolio than five ambitious projects abandoned halfway through.
Start with the job listings, not with whichever technology seems most exciting that day. Look at entry-level positions you could realistically apply for, especially in your local area, and write down the skills that appear repeatedly. Pick one language and one practical workflow, then study those consistently instead of switching topics every few days.
Build two or three small but complete projects related to those jobs. Make sure they are documented, explain your decisions, and demonstrate the kind of work employers are asking for. Once you have something presentable, apply broadly and keep improving based on the feedback you receive. You can add another skill later; your first goal is to become employable in one direction.
Curiosity is useful, but it needs to be separated from your immediate career objective. Compilers, operating systems, security research, and AI can all be fascinating, but they usually aren’t the fastest route to a first job. For now, focus on one language well enough to demonstrate competence, basic problem-solving, common development tools, and the interview format used by the jobs you want.
Choose a specific target, such as junior web developer or QA automation trainee, and make a short plan around that target. Once you have work experience, you’ll have a much better foundation for exploring the more advanced areas.
The local job market should guide your choice. Search for junior and trainee roles, note their requirements, and spend the next few months building experience in the most common technologies. Entry-level hiring can take time, so it’s completely reasonable to take a part-time or non-technical job while continuing to learn. That can reduce the financial pressure and give you enough stability to study consistently.
A useful way to do this is to list your current skills and compare them with several real job descriptions. Then choose the smallest missing skill that moves you closer to those roles. Practice it through a project that resembles actual work rather than collecting more tutorials.