2

Freelance Remote Research Engineer Jobs (NOW HIRING)

MovieWeb: Movies & TV Reporter

Atlanta, GA · Remote

$25 - $34/hr

This is a paid freelance remote position. The editorial team at MovieWeb.com is looking for a ... Should possess a general understanding of the culture and strong research skill ​Responsibilities:

Aerostar, a business unit of TCOM, is seeking a Staff Research Engineer to help lead the ... Remote candidates will not be prioritized. Physical Requirements & Working Conditions: * Physical ...

Approval of remote and hybrid work is not guaranteed regardless of work location.For additional ... POSITION SPECIFICS We are seeking an experienced Research and Development Engineer to manage ...

DTEX is seeking a highly skilled and mission-driven Threat Intel Research Engineer to join our ... Flexibility - Work in a hybrid or remote environment that balances collaboration with autonomy.

next page

Showing results 1-20

Freelance Remote Research Engineer information

See salary details

$14

$47

$132

How much do freelance remote research engineer jobs pay per hour?

As of Jul 9, 2026, the average hourly pay for freelance remote research engineer in the United States is $47.71, according to ZipRecruiter salary data. Most workers in this role earn between $24.28 and $61.78 per hour, depending on experience, location, and employer.

What is the difference between Freelance Remote Research Engineer vs Freelance Remote Data Scientist?

AspectFreelance Remote Research EngineerFreelance Remote Data Scientist
CredentialsEngineering degrees, technical certificationsStatistics, data analysis, programming skills
Work EnvironmentRemote, project-based, technical researchRemote, data analysis, modeling tasks
Industry UsageEngineering firms, R&D departmentsTech companies, analytics firms
Search & ComparisonOften compared for technical research rolesRelated but focuses on data analysis

Freelance Remote Research Engineers focus on technical research and engineering projects, often requiring engineering credentials. In contrast, Freelance Remote Data Scientists specialize in data analysis and modeling, typically with statistics and programming skills. Both roles are remote and project-based but serve different industry needs.

What are the key skills and qualifications needed to thrive as a Freelance Remote Research Engineer, and why are they important?

To thrive as a Freelance Remote Research Engineer, you need advanced analytical abilities, a strong background in mathematics or computer science, and relevant research experience, typically supported by a graduate degree. Familiarity with programming languages (such as Python or MATLAB), data analysis tools, and version control systems like Git is essential. Excellent self-management, problem-solving, and communication skills distinguish top professionals in this role. These abilities ensure you can independently drive projects, collaborate virtually, and deliver innovative solutions to complex research challenges.

How do Freelance Remote Research Engineers typically manage project communication and collaboration with distributed teams?

Freelance Remote Research Engineers often work with geographically dispersed teams, making clear communication and collaboration essential. They commonly use project management tools, version control systems, and regular video meetings to stay aligned with team objectives and timelines. Establishing clear expectations, frequent updates, and proactive problem-solving are crucial for overcoming the challenges of remote work. Additionally, they may need to adapt to different collaboration styles depending on the client or project's structure.

What is a Freelance Remote Research Engineer?

A Freelance Remote Research Engineer is a professional who conducts research and develops new technologies or solutions in fields like software, hardware, or data science, while working independently and remotely. They are typically hired on a contract or project basis by companies or academic institutions needing specialized expertise. Their work may include designing experiments, analyzing data, developing prototypes, and publishing findings. Working remotely allows them to collaborate with teams worldwide and manage their own schedules.
What cities are hiring for Freelance Remote Research Engineer jobs? Cities with the most Freelance Remote Research Engineer job openings:
What are the most commonly searched types of Remote Research Engineer jobs? The most popular types of Remote Research Engineer jobs are:
Infographic showing various Freelance Remote Research Engineer job openings in the United States as of July 2026, with employment types broken down into 95% Full Time, 2% Part Time, and 3% Contract. Highlights an 87% Physical, 4% Hybrid, and 9% Remote job distribution, with an average salary of $99,230 per year, or $47.7 per hour.

Research Engineer - Reinforcement Learning

Firecrawl

San Francisco, CA • On-site, Remote

$180K - $290K/yr

Full-time

Medical, Dental, Vision, Life, Retirement, PTO

Re-posted 22 days ago


Job description

Research Engineer - Reinforcement Learning
You'll bring reinforcement learning to Firecrawl's core product - building the training infrastructure, reward pipelines, and fine-tuning systems that make our models meaningfully better at extracting, understanding, and structuring web data. This isn't theoretical RL research. You'll build your own training infra, run fast experiments, ship models to production, and bridge the gap between classical RL approaches and modern LLM agent systems. If you care as much about training throughput as you do about reward design, this is the role.
Salary Range: $180,000 to $290,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
Equity Range: Up to 0.15%
Location: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
Job Type: Full-Time
Experience: 3+ years in applied RL, ML engineering, or model training - with production systems
Visa: US Citizenship/Visa required for SF; N/A for Remote
About Firecrawl
Firecrawl is the easiest way to extract data from the web. Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call. In just a year, we've hit 8 figures in ARR and 120k+ GitHub stars by building the fastest way for developers to get LLM-ready data.
We're a small, fast-moving, technical team building essential infrastructure superintelligence will use to gather data on the web. We ship fast and deep.
What You'll Do
Build training infrastructure and reward pipelines from scratch. Design and operate the systems that train and evaluate Firecrawl's models. You'll own the full loop - data collection, reward modeling, training runs, evaluation, and deployment. You build the infra yourself because you're the one who needs it to work.
Fine-tune models to achieve state-of-the-art results. Take foundation models and make them dramatically better at web data extraction, content understanding, and structured output generation. You know how to get from "decent fine-tune" to "best-in-class" and you have the patience and rigor to close that gap.
Bridge LLM agents and classical RL. The most interesting problems at Firecrawl sit at the intersection of modern LLM-based agents and classical RL techniques. You'll design reward signals for agent behaviors, apply RL methods to improve multi-step agent workflows, and figure out where traditional RL approaches outperform prompting - and vice versa.
Run fast experiments and iterate. You design experiments that test meaningful hypotheses, run them quickly, and make decisions based on results. You don't spend weeks on experiment infrastructure before getting a single result. Speed of iteration is a core part of how you work.
Communicate clearly to non-RL people. RL can be opaque. You translate your work into language that engineers, product people, and leadership can understand and act on. You know how to explain why a reward function matters without requiring everyone to read the paper.
Collaborate closely with the team. Work directly with the Search/IR-focused Research Engineer and the engineering team to connect RL improvements with search, ranking, and the broader product roadmap.
What We're Looking For
Builds their own training infra and reward pipelines. You don't wait for an ML platform team to set things up. You build the training loops, reward models, data pipelines, and evaluation frameworks yourself - because you understand that infra choices directly affect the quality of results. You've operated GPU clusters, managed training runs, and debugged convergence issues in production.
Can fine-tune models to SOTA. You've taken models from baseline to best-in-class on tasks that matter. You understand the full fine-tuning lifecycle - data curation, training dynamics, hyperparameter sensitivity, evaluation methodology - and you have the taste to know when a model is actually good versus when the eval is flattering.
Bridges LLM agents and classical RL. You're fluent in both worlds. You understand PPO, RLHF, reward modeling, and policy optimization - and you understand how modern LLM agents work, where they fail, and how RL techniques make them better. You see connections between these domains that most people miss.
Production-minded. You care about whether your models work in production, not just on benchmarks. You've deployed models that serve real traffic and made hard tradeoffs between model quality, latency, and cost. Research that doesn't ship isn't research that matters here.
Runs fast experiments and communicates clearly. You'd rather run three rough experiments this week than one polished one next month. When you have results, anyone on the team can understand what they mean - no decoder ring required.
Backgrounds that tend to do well: RL engineers at AI labs or applied ML teams who've shipped models to production. Researchers who've done RLHF or reward modeling for LLM systems. ML engineers who've built training infrastructure at startups and cared as much about the pipeline as the model. People who've worked at the intersection of RL and language models - whether in academic labs with a production bent or at companies building agent systems.
What We're NOT Looking For
Pure theorists. If your best RL work lives in a paper and you've never trained a model on real data at real scale, this isn't the role. We need someone who builds and ships.
Researchers who need a platform team. If you expect training infrastructure, data pipelines, and evaluation frameworks to be set up before you can be productive, you'll be frustrated here. You build the tools you need.
People who only know one paradigm. Deep in classical RL but never worked with LLMs? LLM fine-tuner who's never touched RL? You'll be missing half the picture. This role requires fluency in both.
Slow iterators. If your standard experiment cycle is measured in weeks, not days, you'll struggle with the pace. We need someone who can run a meaningful experiment, interpret results, and decide next steps within a day or two.
Black-box communicators. If your typical update is a wall of metrics only another RL researcher can parse, this isn't the right fit. We need someone who can explain what's working, what's not, and why it matters - to people without RL PhDs.
A Note On Pace
We operate at an absurd level of urgency because the window for what we're building won't stay open forever. If that excites you, keep reading. If it doesn't, no hard feelings - but this role probably isn't for you.
Benefits & Perks
Available to all employees
  • Salary that makes sense - $180,000-$290,000/year, based on impact, not tenure
  • Own a piece - Up to 0.15% equity in what you're helping build
  • Generous PTO - 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge
  • Parental leave - 12 weeks fully paid, for moms and dads
  • Wellness stipend - $100/month for the gym, therapy, massages, or whatever keeps you human
  • Learning & Development - Expense up to $1,000/year toward anything that helps you grow professionally
  • Team offsites - A change of scenery, minus the trust falls
  • Sabbatical - 3 paid months off after 4 years, do something fun and new

Available to US-based full-time employees
  • Full coverage, no red tape - Medical, dental, and vision (100% for employees, 50% for spouse/kids) - no weird loopholes, just care that works
  • Life & Disability insurance - Employer-paid short-term disability, long-term disability, and life insurance - coverage for life's curveballs
  • Supplemental options - Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind
  • Doctegrity telehealth - Talk to a doctor from your couch
  • 401(k) plan - Retirement might be a ways off, but future-you will thank you
  • Pre-tax benefits - Access to FSAs and commuter benefits (US-only) to help your wallet out a bit
  • Pet insurance - Because fur babies are family too

Available to SF-based employees
  • SF HQ perks - Snacks, drinks, team lunches, intense ping pong, and peak startup energy
  • E-Bike transportation - A loaner electric bike to get you around the city, on us

Interview Process
Application Review - Send us your work and a quick note on why this excites you. Show us what you've trained - models, reward systems, training pipelines. Published work is great; shipped production models are better.
Intro Chat (~20 min) - A quick conversation to get to know each other before we go deep. We'll talk about what you've been working on, what drew you to Firecrawl, and what you're looking for in your next role. Time for your questions too.
Technical Deep Dive (~60 min) - Go deep on RL and model training work you've done: training infrastructure decisions, reward design, fine-tuning approaches, production deployment. We'll explore a live problem - how you'd apply RL to improve an LLM agent workflow at Firecrawl. We're looking for depth across classical RL and modern LLM techniques, production instincts, and fast reasoning.
Founder Chat (~30 min) - Culture, pace, ownership, and how you like to work. Time for your questions too.
Paid Work Trial (1-2 weeks) - Tackle a real RL/fine-tuning problem with production implications. We evaluate on technical depth, experiment velocity, and how clearly you communicate results.
Decision - We move fast after the trial.
If you want to bring RL to one of the most interesting applied problems in AI - making agents smarter at understanding and extracting web data at scale - this is your shot.
Apply now.