Remote tech jobs, realistically

The debate about whether remote work is over misses what actually happened. It divided. A set of companies became genuinely remote-first and built their processes around it. A larger set returned to offices with some flexibility. A third group advertises remote roles that carry location requirements in the small print.

Most frustration in a remote job search comes from treating these as one market. The listing that seemed perfect and then required quarterly on-site weeks was never in the tier you wanted; it was the third group, and it is the largest.

The tiers are distinguishable before you apply if you look. A remote-first company says where its people are and how it runs decisions; a company that tolerates remote says "remote" and mentions an office address, a time zone requirement or a travel expectation somewhere below the fold.

The pattern is fairly consistent: work whose output is verifiable asynchronously remained remote most reliably. Where value depends on presence, real-time collaboration or physical access, it did not.

Seniority is the other major factor. Senior individual contributors who need little supervision retained remote options at far higher rates than juniors, because remote onboarding of inexperienced people is genuinely harder and most companies concluded it was not worth the cost.

The practical implication for anyone early in their career is that remote is easier to obtain as a second job than a first. Building two or three years of track record somewhere, remote or not, changes which tier of the market will consider you.

• Backend, infrastructure and platform engineering — strongly remote
• Data engineering and analytics — largely remote
• Security engineering — mostly remote outside classified environments
• Design and product — mixed, often hybrid
• Hardware, robotics and lab work — largely on-site by necessity
• Junior roles across all categories — markedly less remote

Companies take one of three positions and it is worth identifying which before investing in an application. Some pay a single global rate regardless of location. Some band pay by region. Some pay local market rate wherever you happen to be.

Each has consequences beyond the headline figure. Single-rate employers are highly competitive to join and rarely hire juniors. Banded employers are the common middle. Local-rate employers may reduce your pay if you move somewhere cheaper, which is a clause worth reading carefully before relocating.

Ask which model applies before the salary conversation rather than during it. It reframes the whole negotiation: there is little point arguing a number with an employer whose bands are fixed by location, and considerable point in knowing that before you anchor.

Working remotely for a company in another country is not simply a matter of agreement. There are tax residence questions, employer obligations in your jurisdiction, and in many places the employer needs a legal entity or an employer-of-record arrangement to hire you at all.

This is why many remote listings restrict hiring to specific countries. It is rarely arbitrary. If a company cannot legally employ someone where you live, no amount of enthusiasm changes that, and identifying it early saves considerable wasted effort.

The arrangement offered also matters to you. Being engaged as a contractor rather than an employee changes your tax position, your benefits, your notice rights and sometimes your ability to demonstrate stable employment later — so it is worth understanding what you are signing rather than assuming it mirrors local employment.

Remote roles attract far more applicants than equivalent on-site ones, so the selection bar is higher rather than lower. What differentiates candidates is evidence of working well without supervision, which is exactly what a remote employer is worried about.

Written communication is the most underrated signal. Remote work runs on writing, and a clear, well-structured application is itself a work sample. Vague or careless writing is disqualifying in a way it is not for an office role where someone can walk over and ask.

State your time zone and overlap plainly rather than leaving it to be discovered. "I can reliably overlap 2pm–7pm UK time" answers the question a hiring manager is actually holding, and it removes the main reason applications from distant time zones get set aside.

• Demonstrate asynchronous work — public writing, documentation, issue threads
• Show self-direction with a project you owned end to end
• Write applications carefully; they are a work sample
• Have overlap hours you can state plainly
• Be specific about where you are legally able to work

Ask what proportion of the team is remote, because being the only remote person on an otherwise co-located team is a materially different experience from joining a distributed one. Ask how decisions get recorded, since undocumented decisions made in a room exclude you by default.

Also ask what happens if the policy changes. Remote arrangements have been revoked with limited notice, and knowing whether yours is contractual or discretionary is worth establishing before you reorganise your life around it.

The promotion question is the sharpest one available. Ask whether a fully remote person has been promoted into a senior role recently and who — a specific name means the arrangement is real, and a statement about equal opportunity means it is not.