ZipRecruiter

Log In

1

Hourly Open Source Investigator Jobs in Delaware

Tech Impact

Data Scientist - Fellowship

Wilmington, DE · On-site

$40/hr

This is an hourly contract position. * 20 hours per week. * $40/Hour * Fellowship program runs from ... Hands-on coding experience in Python / R / Julia or any other open-source programming language

FHR

A4.9-Security Analyst 5026 Dover,DE

Dover, DE · On-site

Our direct client has an opening for a Security Analyst 5026 This position is up to 13 months with ... YOUR CURRENT RESUME YOUR HOURLY RATE Key Responsibilities Security Monitoring: Continuously monitor ...

Intermountain Health

PB Coding Coordinator

Dover, DE · On-site

$31.01 - $48.84/hr

Utilizes coding knowledge and source-based research to investigate and respond to coding requests ... Actual hourly rate dependent upon experience. $31.01 - $48.84 We care about your well-being - mind ...

Breakthru

Field Sales Manager

Middletown, DE · On-site

... source candidates, schedule interviews, conduct interviews, and manage the on-boarding process ... Undertakes analysis and investigation to solve issues. This is only a summary of the typical ...

next page

Showing results 1-20

All JobsHourly Open Source Investigator JobsHourly Open Source Investigator Jobs in Delaware

Hourly Open Source Investigator information

What is an hourly open source investigator?

An Hourly Open Source Investigator is a professional who gathers, analyzes, and verifies publicly available information—often from the internet and social media—to support investigations. They are typically paid by the hour and may work on cases involving fraud, background checks, due diligence, or cybercrime. Their expertise lies in using open source intelligence (OSINT) tools and techniques to uncover relevant data while adhering to ethical and legal standards. This role is often critical for law firms, corporations, journalists, and law enforcement agencies seeking reliable, actionable intelligence.

What are the key skills and qualifications needed to thrive as an hourly open source investigator?

To excel as an Hourly Open Source Investigator, you need strong analytical skills, a keen eye for detail, and a solid understanding of investigative research methods, often supported by relevant education or experience in intelligence or journalism. Familiarity with open source intelligence (OSINT) tools, social media platforms, and data visualization software is typically required. Excellent critical thinking, persistence, and effective written communication help distinguish top performers in this field. These skills and qualities are crucial for gathering accurate, actionable intelligence while ensuring ethical and legal compliance.

What are some common challenges hourly open source investigators face when verifying the credibility of online information?

Hourly Open Source Investigators often encounter challenges such as misinformation, manipulated media, and anonymous sources when verifying online content. Sifting through large volumes of data quickly while ensuring accuracy can be demanding, especially under tight deadlines. Investigators must use a combination of advanced search techniques, digital forensics tools, and cross-referencing multiple sources to validate findings. Staying updated on the latest verification tools and maintaining a skeptical, detail-oriented mindset are essential to overcome these obstacles and deliver reliable results.

What is the difference between Hourly Open Source Investigator vs Freelance Open Source Researcher?

AspectHourly Open Source InvestigatorFreelance Open Source Researcher
CredentialsTypically requires research, cybersecurity, or investigative certificationsOften self-taught or with similar certifications, no formal requirement
Work EnvironmentUsually employed by organizations, working on specific investigationsIndependent, working remotely on various projects
Employer & IndustryCompanies, government agencies, private investigatorsClients across industries, including journalism, security, and consulting
Search & Comparison IntentUnderstanding job scope, pay, and responsibilitiesFinding freelance opportunities, rates, and project types

The main difference is that Hourly Open Source Investigators are typically employed by organizations and work on investigations as part of a team, often with specific certifications. Freelance Open Source Researchers operate independently, offering their services to various clients without formal employment. Both roles require strong research skills, but their work settings and employment structures differ.

What cities in Delaware are hiring for Hourly Open Source Investigator jobs?

Cities in Delaware with the most Hourly Open Source Investigator job openings:

Hourly Open Source Investigator jobs near you

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Middletown, DE • On-site

$20 - $30/hr

Full-time

Posted yesterday

New

Job description

Type: Contract, hourly

Location: Remote

Hours: 20–30 per week

Pay: $20–30/hour, based on experience and language coverage

Start: Immediate

ABOUT THE ROLE

We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.

You will do two jobs, and you should expect either on any given day.

•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.

• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.

TASKS YOU'LL SEE

• Feature build — Add a working feature to a live library without breaking anything that already worked.

• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.

• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.

Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.

WHAT YOU JUDGE IN A TRAJECTORY

• Was the command right for the state the environment was actually in?

• Did the agent read the previous output correctly?

• Was the step wrong, or only inefficient — these are scored differently.

• Where did the run first go off course — usually earlier than where it visibly broke.

• Did the agent notice its own mistake and recover, or keep building on a false assumption?

• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?

WHAT WE NEED FROM YOU

• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.

• Languages — Strong in Python or Go, and able to read a language you've never used.

• Linux — Comfortable with logs, running processes, build failures, and containers.

• Workflow — Everyday Git, diffs, pull requests, and issue tracking.

• Debugging — Able to work with no test suite and no error message pointing at the cause.

• Focus — Able to hold context across a long run, because step 74 can depend on step 12.

• Writing — Clear English, since every judgement needs an explanation another engineer can check.

Apply