Do not try to pick the best field; pick the one whose daily problems you can tolerate on a bad day. Run a short, cheap experiment in two or three candidates, compare what you enjoyed doing rather than what sounded exciting, check the local job market, and commit for six to nine months.
What people tell me
I am a student and I keep jumping between areas. One week I want to do AI, the next cybersecurity, then cloud because I read it pays well. Everyone online says their field is the future. I do not have years to try all of them, and I am scared of wasting time on the wrong one. How do people actually decide?
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Choose by the daily work you can enjoy, not by the headlines about a field.
- Narrow to two or three candidates, then run a two-week hands-on experiment in each.
- Judge the experiment on what held your attention when it got hard, not on how it looked from outside.
- Check real junior listings in the places you would work. Some fields hire few juniors directly.
- Commit for six to nine months. Fields share more foundations than they seem to, so switching later is cheaper than you fear.
Stop asking which field is best
Every field has people online insisting it is the future. They are not lying, exactly. They are describing the field they chose. The question "which one is best?" has no answer that applies to you.
A more useful question is: which field's everyday problems would I still find tolerable, even interesting, on a tiring Tuesday afternoon? The headlines are about outcomes. Your job will be about the daily work.
What the daily work actually looks like
Here is a rough, honest picture of what you spend your days doing in each area:
| Field | What your days mostly look like | Tends to suit people who |
|---|---|---|
| Frontend | Building interfaces, handling state, making things work across devices, polishing details | Like visible results and care about how things feel to use |
| Backend | APIs, databases, business logic, performance, data correctness | Like systems, logic and making things reliable |
| Mobile | App screens, device features, app store releases, offline behaviour | Like building products people carry around |
| Cloud and DevOps | Infrastructure, deployments, monitoring, automation, incidents | Like keeping systems running and automating repetitive work |
| Cybersecurity | Finding weaknesses, monitoring, hardening systems, responding to incidents | Like investigating, breaking things and thinking like an attacker |
| Data | Cleaning data, pipelines, SQL, dashboards, analysis | Like finding answers in messy information |
| AI and ML | Data preparation, experiments, evaluation, integrating models into products | Like experimentation and are comfortable with maths and uncertainty |
Read that table and notice your gut reaction to the middle column, not the field name.
Narrow to two or three, quickly
You do not need to try seven fields. Cross out the ones whose daily work genuinely does not appeal to you. Most people end up with two or three candidates within a few minutes. That is your shortlist.
Run a cheap experiment in each
For each candidate, spend about two weeks doing real work in it, not watching videos about it:
- Frontend: build a small interactive page that fetches data from a public API.
- Backend: build a small API with a database, with create, read, update and delete.
- Mobile: build a two-screen app that saves data on the device.
- Cloud: deploy a simple app to a cloud provider with a pipeline and basic monitoring.
- Security: work through beginner challenges on a legal practice platform.
- Data: take a public dataset, clean it and answer three questions with SQL or Python.
- AI: call a model's API to build a small tool, then try training a simple model on a dataset.
While you do it, keep notes on one thing: when it got hard, did you want to keep going or did you want to escape? That is the most honest signal you will get.
Check the market where you will work
Enjoyment is half the decision. The other half is whether people are hired for that role at your level where you want to work. Look at twenty or thirty junior listings in your country or the remote roles you would realistically target. Some fields, like cybersecurity, AI research or cloud architecture, often hire juniors less directly and expect some general software or IT experience first. That does not rule them out. It changes the route. The Sefism company directory and internships are useful for seeing what local companies actually hire for.
Make the call and commit
After the experiments, pick the one where enjoyment and opportunity overlap best. If two are close, pick either. Then commit for six to nine months: two solid projects, the fundamentals of that field and steady applications.
Why switching later is cheaper than you think
These fields share much more than it seems. A backend engineer already knows a lot of what cloud work needs. A frontend engineer moving to mobile carries over most of their thinking. Data and AI overlap heavily. Security benefits enormously from real development experience. Your first choice is an entry point, not a wall.
The real cost is not choosing
The expensive mistake is not picking the wrong field. It is spending two years switching every few weeks and ending up with nothing deep enough to show. A reasonable choice, committed to, beats a perfect choice you never make.
If you are still stuck
Read How to Start Your Career as a Software Engineer, Getting Into Cybersecurity as a Fresh Graduate and An AI Engineering Roadmap That Puts Things in the Right Order.
If you want someone to look at your specific situation, join Sefism and, as a member, book a 1:1 session. You can also browse the other career questions people have asked.
Was this answer helpful?
Read next
- How to Start Your Career as a Software EngineerA practical route into the first software engineering job: pick one language and stop shopping, build things too big for a tutorial, learn the five fundamentals you cannot skip, get your code in front of a human, and apply earlier than you feel ready. Includes a twelve month shape to work to and an honest read on what the current entry level market has changed.
- Getting Into Cybersecurity as a Fresh Graduate: Where to Actually StartA practical route into cybersecurity or IT operations for final year students and fresh graduates: whether to keep a low paid internship, SOC analyst versus operations versus application security, which certifications are worth it, hands on labs, a home lab, a portfolio of write ups, a six month roadmap and how to handle the fear of not being good enough.
- An AI Engineering Roadmap That Puts Things in the Right OrderEvery AI engineering roadmap is the same twenty topics rearranged, and the arrangement is the only part that matters. Six stages from model basics through retrieval, measurement, tool calling and agents, each with something specific to build, what to skip entirely, and the two stages people skip and later regret.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open to X and Instagram followers and university students. Prefer to talk? A free call works too.