This page lists fully remote software-engineer positions, refreshed daily, from companies that run their engineering teams async or with timezone-flexible overlap. Filter by region, seniority and tech stack — then apply directly through each employer's original posting.
Job title
Software Engineer Remote Jobs
628
active positions
392
new in 7 days
183,547 EUR
Avg. salary/year
Open positions
- No positions for this job title currently
Salary expectations
Average: 183,547 EUR per year – based on 0 job listings.
Experience
Avg. salary
Entry-level (0 yrs)
190,909 EUR
Senior (5–9 yrs)
194,136 EUR
Lead / Staff (10+ yrs)
180,083 EUR
In-demand skills
Top skills from 0 job listings
Go
0%
AWS
0%
Python
0%
Rust
0%
CI/CD
0%
Kubernetes
0%
Postgres
0%
Docker
0%
Kafka
0%
Terraform
0%
Hiring companies
Geico · 62 Sezzle · 61 Sofi · 29 Breakout (Kraken) · 29 Salesforce · 24 Datadog · 20 Aircall · 18 Gusto · 16 Xsolla · 16 Mistral · 15 Tide · 15 Perplexity · 14
Similar job titles
What does a remote software engineer actually do?
A remote software engineer designs, builds and operates software systems — with a higher bar on async communication, clear written documentation and independent prioritisation than in a co-located role. Day-to-day work covers feature delivery in a backend or frontend stack, code reviews, on-call rotation and mentoring of less senior teammates.
Compared with office work, synchronous meetings collapse to 1–2 fixed slots per day. Most of the actual work happens through pull requests, tech-design docs and async reviews. People who like that pattern usually report being more focused and shipping more remotely than they did in an office.
How to sharpen your application for a remote engineering role
- Lead with a portfolio. 2–3 documented projects (GitHub repo + README + live deployment) outweigh years of tenure on a CV.
- Add an async writing sample. A well-structured issue or an RFC shows the remote-relevant skills a cover letter cannot.
- Make your timezone overlap explicit: "CET, 4h overlap with US East" answers the recruiter's first concern up-front.
- Take the take-home seriously. Around 80% of remote engineering roles screen with a take-home task instead of live coding.
- In interviews, name concrete trade-offs instead of reciting "best practices" — remote hiring filters hard for independent thinking.
Frequently asked questions
- Do I need English to apply?
- Yes. More than 90% of roles listed here use English as the working language. Solid C1 written English is enough in most cases — accent and pronunciation matter much less than in office-based roles because so much is async.
- Can I work for a US company from Europe?
- Usually yes, but rarely as a direct employee. The three common patterns are an Employer-of-Record platform (Deel, Remote.com, Oyster), a B2B contractor relationship where you invoice the company, or full employment via the company's EU entity. Each listing usually states which model applies.
- How much experience do I need for a fully remote role?
- On average 3+ years. Junior remote roles are rare because async onboarding is harder; we tag the ones that exist as "junior friendly". At Staff and Principal levels remote is now the default.
- How fresh are these listings?
- We re-crawl every listed employer every 24 hours straight from their ATS (Greenhouse, Lever, Ashby, Workable). Closed roles disappear within 48 hours; new ones appear the day they are posted.
- Which tech stacks are most in demand right now?
- See the live skill ranking above, computed from the 542 open listings on this page. Across all roles, Python, Go and TypeScript dominate, followed by AWS, Kubernetes and Postgres. Rust is growing fast, especially among infrastructure and crypto companies.
- How is remote-job.net different from LinkedIn or Indeed?
- We only list fully remote roles — no hybrid, no "remote sometimes". We also structure region, skills and salary so you do not need to read every posting end-to-end to compare.