Should I take the first job I get, or wait for a role closer to the career I actually want?

What a first job is actually for

A first job is rarely where you end up. It is where you learn how professional software gets built: working in a real codebase, code reviews, deadlines, bugs in production, working with other people and with a manager. Almost all of that transfers, whatever the stack or company.

So the question is not "is this my dream job?" It almost never is. The question is "will this job make me meaningfully better and more hireable in a year?"

Judge the offer on the things that matter

A different stack from the one you learned is rarely a real problem. Frameworks change, and learning a second one teaches you what is general and what is specific.

The hidden cost of waiting

Holding out feels safe because nothing is committed. But waiting costs something:

• Every month without work is a month without professional experience on your CV.
• A growing gap starts to raise questions in applications.
• Financial pressure often leads to worse decisions later.
• Motivation drops with every week of rejections.

Many people who wait for the perfect role end up, six months later, accepting something worse than the offer they turned down.

When waiting makes sense

Waiting is reasonable if all of these are true:

1. You have savings or support for at least three to six more months.
2. You have a real pipeline: several applications at later stages, not just hope.
3. The offer fails one of the serious warning signs above, such as no real engineering work or an unfair contract.

If two or more of these are not true, the offer is probably worth taking.

Take it, and keep building towards what you want

Accepting a job does not end your plan. It changes the pace. Many people accept a first role, learn a great deal in the first year, keep building in their target direction on the side, and then move with far better leverage. An engineer with a year of real experience gets very different responses from employers than a fresh graduate.

Some practical ways to steer while you are there:

• Ask to work on the parts closest to your target direction.
• Volunteer for tasks that stretch you, such as deployments, APIs or performance work.
• Keep notes on what you shipped so your next CV writes itself.
• Stay reasonably committed for at least a year. Leaving after three months usually looks worse than staying.

Questions to ask before accepting

Before you sign, it is fair to ask:

Could you tell me what a typical first three months would look like for this role? Who would review my code, and what would success look like after six months?

The answers tell you a lot about whether you will actually learn there.

My usual answer

For most people who ask me this, the honest answer is: take it, learn as much as you can, and use it as a platform. A first job is a step, not a destination.

An example of both paths

Consider someone who wanted a frontend role in a product company and got an offer from a small services company working mostly on backend PHP. They were disappointed and close to turning it down.

They accepted. In the first year, they shipped features to real clients, learned how databases and deployments work, fixed production bugs, and asked to take on the small amount of frontend work the company had. They kept building a React project in the evenings. Fourteen months later, they applied for frontend roles with real experience, stories about shipping to clients and a portfolio project. The replies were completely different from their graduate search.

Compare that with someone who turned down a similar offer and was still applying eight months later, with a growing gap and shrinking savings, and eventually took a less suitable role under pressure.

Not every story ends like the first one. But the pattern is common enough that I rarely advise waiting without a strong reason.

A quick scoring exercise

Score the offer from 1 to 5 on each of these, honestly:

1. How much real code will I write and ship?
2. How much will I learn from the people around me?
3. How fair are the contract terms and pay for my situation?
4. How much of what I learn will transfer to my target direction?

A total of 12 or more is usually worth accepting. Below 10, look harder at the warning signs, and if you do decline, have a concrete plan for the next three months, not just hope.

If you are still stuck

Read Fourteen Questions Worth Answering Before You Change Jobs and What Actually Changes in Your First Two Years as an Engineer.

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.