Freelance developer projects and remote developer jobs
Browse freelance developer projects and remote developer jobs. Read the brief for the requested change, existing system and delivery requirements.
See live developer work →What lands here
Nabbly reads developer briefs and roles from job boards and hiring communities. Arrival times vary by source. A gig reaches this page when it talks about work like this:
- developer
- software engineer
- backend
- full stack
- solutions architect
- devops
- solutions engineer
- python
Recent gigs
Board snapshot: 2 November 2026. Open one, or open the board. It carries far more and changes through the day, so some of these will already have been filled.
- Trading Bot Developer Needed – Crypto Arbitrage Strategy
- Staff Software Engineer - R37
- python client app to interact with linuxcnc server - Quotation Request
- Python developer - Quotation Request
- Senior System Software Engineer - Datacenter Power Management
- Staff Software Engineer
- Build Python FastAPI Backend - Quotation Request
- ServiceNow Developer SME
- Godot Game Developer
- Senior Salesforce Developer
- Java Developer
- AI Solutions Engineer
- Principal of backend — SchemeServe Limited
- Head of backend — SchemeServe Limited
- Embedded Linux Senior Software Engineer - Optimisation — Canonical
- Forward Deployed AI Solutions Engineer — Natera
Snapshot: 2 November 2026
- 5,733 English-language gigs in the snapshot of 2 November 2026.
- Posts using urgent wording, such as ASAP or today: 82 of 5,733 gigs (1%).
- Stating a budget in the posting, in the snapshot: 1,309 of 5,733 gigs (23%).
- Budget bands in the snapshot, of the 1,309 that state one: Under $100 438 (33%); $100-500 378 (29%); $500-2k 408 (31%); $2k+ 85 (6%).
- 539 further gigs name an amount above $20,000 and are left out of the bands.
- Freelancer.com offers clients a dropdown of budget ranges, so many of its posts share the same range; the midpoint is what is counted.
- Work type recorded in these listings: project 1,307 (23%); contract 36 (1%); other 335 (6%); not stated 4,055 (71%).
- Listings labeled remote: 5,579 of 5,733 gigs (97%); on-site 25 (0%); not stated 129 (2%).
- Listings by source: Himalayas 3,901, 68% of the snapshot; Freelancer.com 1,263, 22% of the snapshot; Jobicy 282, 5% of the snapshot; Jobspresso 102; Arbeitnow 75; PeoplePerHour 44; We Work Remotely 29; Realworkfromanywhere 8; RemoteOK 7; Threejs 5; Pythonjobs 3; Workingnomads 3; Wpjobs 3; Bubble 2; Larajobs 2; Remotive 2; Entcareers 1; Soundlister 1.
- Common words in listing titles: developer (985 gigs); software engineer (936 gigs); backend (257 gigs).
- Posting dates in this snapshot: 23 Oct 2026–2 Nov 2026 (10 days; dates read for 5,733 of 5,733 gigs).
How to read this snapshot. Sample size: 5,733 English-language gigs as of 2 November 2026. Unknown: budget not stated or not parseable in 3,885; work type not stated in 4,055; remote/on-site not stated in 129. Budgets are parsed from posting text (currencies not converted, hourly and project figures not separated); field membership is the board's own classifier, which is not perfect. Budgets are amounts stated in postings.
Choose a developer brief by scope, not just stack
A familiar language is a useful starting point, but it does not tell you whether the engagement fits. Separate a defined feature or bug fix from an ongoing engineering position. A mobile app request needs a different scope conversation from a technical lead role, even when both involve tools you know. Check the deliverable and expected commitment before judging your fit.
A development brief might describe mobile app work, subscription setup or an engineering role. The field label can also need classification review. Treat the developer category as a route into relevant postings, then verify each brief. A title cannot establish that a project is correctly categorized or that its scope is complete.
Look for the dependencies behind the request
Read what the client says about the existing system. Is this a new application, a feature inside an established codebase or a fault they need diagnosed? Repository access, test environments, integrations and data migration can affect the work as much as the interface described in the post.
Check whether the client wants implementation only or also planning, tests, deployment and documentation. If the brief mentions an external service, establish who provides the account and who approves changes. An estimate should make those assumptions visible rather than absorb them into an undefined promise to finish everything.
Ask how the client will accept the work. A working demonstration, a reviewed pull request and a deployed feature are different completion points. Clarify the handover and support expectations, particularly if another developer will maintain the code after delivery.
For a bug report, request the steps that trigger the fault and the behavior the client expected. A screenshot may show the symptom without explaining the cause. Ask whether it occurs in a test environment and whether recent changes are known. You can describe the investigation you would perform without claiming to have diagnosed a system you have not seen.
A migration needs more than a working new screen. Establish which records move, what must stay linked and who checks the transferred results. Discuss a backup and a recovery plan before any production change is agreed. If another team owns the database, their review and access arrangements belong in the proposed schedule rather than being treated as incidental administration.
For subscriptions or other external integrations, clarify what should happen when a request fails or an event arrives again. Ask who owns the service account and where the behavior can be tested. Your sample can explain how you handled those cases without exposing client credentials. In the proposal, distinguish building the integration from approving the account setup and operating it after handover.
Distinguish location from engagement type
Remote work can still require a particular country, time zone or overlap with a team. It can also be an employee role rather than a freelance project. Check those conditions in the posting itself. If work type is unstated in the snapshot, that is missing information rather than evidence of flexibility.
Interpret the budget alongside the deliverable
Budget information in the snapshot is parsed from posting text. Currency amounts are not converted, and hourly and project figures are not separated. Dropdown ranges can also be represented by a midpoint. That makes the combined bands unsuitable for comparing the cost of unrelated engineering tasks.
Use the individual posting to confirm the currency, unit, payment schedule and included work. If the requested change depends on a codebase you haven't inspected, explain what you need to review before giving a supported estimate.
The general reply guide explains how to turn a missing dependency into a focused question.
Start with the brief
A good share of developer work here is posted at the larger end. Read what the client actually needs, pick a relevant piece of your work, and say how you would approach it. Free includes editable reply templates; Pro adds reply drafts based on the job description. Review your reply before sending.
Replying to developer briefs: the developer guide → · what to put in the first two lines →