Part Two: Five routes to paid work · Chapter 8
The job, entered sideways.
Use contracts, internal systems, adjacent roles, domain knowledge and paid project evidence to reach employment without relying entirely on the crowded junior-job queue.
The job is still a legitimate goal. Nothing in this book argues otherwise.
Employment offers structure, experienced colleagues, mentoring and money arriving on the same day each month. Those are all perfectly reasonable things to want.
The job may still be reachable—just not through the front door you have been queuing at.
If the obvious route is filtering you out before anybody sees your work, the answer is not necessarily to abandon employment. It may be to enter through a different role, employer or type of engagement.
Four side doors
Look beyond permanent jobs with “junior developer” in the title.
01
Contract and fixed-term work
These vacancies are often filled quickly, filtered less heavily and decided largely on whether somebody suitable can start on Monday.
Three months of contract work makes you a candidate with commercial experience when you apply for the next role.
02
Internal tools outside technology companies
Manufacturers, logistics firms, charities, councils, schools and insurance brokers all rely on internal systems.
Many employ only one or two developers, advertise poorly and receive far fewer applications than recognisable technology companies.
03
Adjacent roles that can convert
Technical support, implementation, solutions engineering, quality assurance, data and reporting roles can place you inside a company that already employs developers.
An internal move may involve two candidates instead of six hundred—and somebody inside the organisation has already seen how you work.
04
A junior role in an industry you know
Your previous career or sector experience can clear a bar that candidates with only technical knowledge cannot.
A developer who understands care, logistics, education, retail or finance may be more useful than a technically stronger candidate who understands none of the organisation’s work.
Where fewer developers look
Most organisations use technology. Far fewer describe themselves as technology companies.
The employer may need your skills without using the job title you have been searching for.
An operations director hiring someone to maintain an internal system may care far less about your degree than an engineering lead processing hundreds of applications for a formal graduate role.
Poorly advertised roles
The vacancy may appear only on the organisation’s own careers page or under an unfamiliar title.
Smaller applicant piles
Developers searching only for technology companies and familiar job titles never see the opportunity.
Operational value
The employer cares whether you can keep an important system working—not whether you fit a fashionable developer profile.
Why this belongs in a book about earning without a job
The other pathways make you more employable.
Each route produces the two things the front door demanded and you could not previously supply.
Before
An applicant with a certificate
You have technical training, tutorial projects and claims about what you could do if somebody gave you an opportunity.
What the pathways create
Commercial experience and references
You deliver work for real buyers, operate around actual constraints and become known by people who can vouch for you.
After
A developer with evidence
Six months of Pathway One can turn you into a candidate with client work and references rather than another name in the application pile.
Who tends to do well
People who genuinely want employment.
The structure, colleagues, mentoring and predictable salary are not consolation prizes.
This pathway suits people who want to work as part of an organisation but are willing to reach the destination through a contract, adjacent role or less obvious employer.
It also suits people whose previous industry experience gives them knowledge that a purely technical candidate cannot quickly acquire.
Contract work: weeks
A suitable contract can move quickly when your skills match an immediate requirement.
Adjacent role: apply now
You do not need to wait until you feel like a complete developer before applying for technical roles around development.
Internal move: 9–18 months
A realistic range for establishing yourself and moving into development from an adjacent role.
The numbers
The first salary may be lower. The route may still be faster.
Starting salaries in adjacent roles often sit below developer salaries.
The person who takes the support job and crosses over within a year often overtakes the person who is still applying.
The relevant comparison is not only the salary attached to the first role. It is where each route is likely to leave you twelve or eighteen months from now.
What is genuinely bad about it?
Side doors do not guarantee that you will reach the room you want.
Adjacent roles
They can become sticky
If you become excellent at technical support, your employer may prefer to keep you in technical support.
Have the progression conversation before accepting the role and continue building evidence outside work.
Contract work
Contracts end
A short contract can create commercial experience quickly, but it does not provide the stability of permanent employment.
That uncertainty is part of the agreement you are signing.
Your responsibility
Keep moving towards development
An adjacent role is a route, not the destination. Continue building, documenting and discussing the move you intend to make.
What to do this week
Search by skill and employer—not only by job title.
01
Search by technology
Search job boards for the technologies you use rather than only for “junior developer”. Examine every role that mentions them.
The jobs that need your skills are not always called developer.
02
Find five overlooked employers
Identify five employers within commuting distance that are not technology companies but clearly rely on internal systems.
03
Inspect their history
Check whether they have previously advertised technical, data, implementation, support or internal-systems roles.
Part Three: The engine
Next: Proof, not portfolio
The route you choose determines who might pay you. Chapter 9 explains how to turn what you build into evidence that makes somebody willing to do it.