Remote or Austin, Tx Our value is directly tied to the quality of our content at scale. The ... Build tooling for LLM-as-judge evaluation and regression detection. Integrate evaluation into CI so ...
Remote or Austin, Tx Our value is directly tied to the quality of our content at scale. The ... Build tooling for LLM-as-judge evaluation and regression detection. Integrate evaluation into CI so ...
Staff Data Scientist- Pricing Science
Austin, TX · On-site +1
Remote - US or Canada About the Role As our Staff Data Scientist , you will design and ship ... Build robust predictive models across classification, regression, time series, and causal inference
Staff Data Scientist- Pricing Science
Austin, TX · On-site +1
Remote - US or Canada About the Role As our Staff Data Scientist , you will design and ship ... Build robust predictive models across classification, regression, time series, and causal inference
Remote Regression Testing information
See Austin, TX salary details
$11.68 - $16.92
0% of jobs
$16.92 - $22.16
0% of jobs
$22.16 - $27.40
0% of jobs
$27.40 - $32.64
3% of jobs
$32.64 - $37.89
4% of jobs
$42.69 is the 25th percentile. Wages below this are outliers.
$37.89 - $43.13
19% of jobs
$43.13 - $48.37
14% of jobs
The median wage is $51.14 / hr.
$48.37 - $53.61
18% of jobs
$57.89 is the 75th percentile. Wages above this are outliers.
$53.61 - $58.85
20% of jobs
$58.85 - $64.10
15% of jobs
$64.10 - $69.34
6% of jobs
$11
$50
$69
How much do remote regression testing jobs pay per hour?
What is the difference between Remote Regression Testing vs Remote Test Automation Engineer?
| Aspect | Remote Regression Testing | Remote Test Automation Engineer |
|---|---|---|
| Primary Focus | Verifying that recent code changes do not break existing functionality | Designing, developing, and maintaining automated test scripts |
| Required Skills | Manual testing, understanding of software features, basic scripting | Programming, automation tools, scripting languages |
| Work Environment | Testing environments, collaboration with QA teams | Development environments, automation frameworks |
| Certifications | ISTQB, QA certifications | ISTQB, automation testing certifications |
Remote Regression Testing focuses on manual or semi-automated testing to ensure recent changes haven't introduced new issues, while Remote Test Automation Engineers develop and maintain automated testing frameworks to streamline testing processes. Both roles require testing knowledge but differ in technical depth and automation skills.
What are some typical challenges faced by remote regression testers, and how can they be overcome?
What is remote regression testing?
What are the key skills and qualifications needed to thrive as a Remote Regression Testing professional, and why are they important?

Other
Medical, Dental, Vision, Life, Retirement
Re-posted 23 days ago
Job description
At Driver, we're building systems that turn source code into human language. The tech stack includes a core compiler-like engine, a heavily asynchronous/distributed backend server, and a frontend web application that provides a rich user experience.
About DriverWe're an early-stage startup backed by Y Combinator and Google Ventures that combines first principles technical approaches and applied LLM expertise to tackle context engineering at scale. Driver builds the context layer for employees and AI agents alike to use in developing software.
Working at DriverDriver is an early-stage but fast-growing startup. As such, we take advantage of that which startups can excel: delivery speed, flexibility, and enjoying working with a small close-knit team.
Organizational and engineering values at Driver include first-principles thinking, correct by construction, writing things down, experimentation and iteration, pragmatism, commitment to effective communication and transparency, autonomy, and ambition.
Job OverviewTitle: Applied Data Scientist, LLM Evaluation
Location: Remote or Austin, Tx
Our value is directly tied to the quality of our content at scale. The platform generates technical documentation across a complex, multi-stage pipeline - producing multiple content types at different levels of abstraction, from individual code elements up to high-level summaries. Today, changes to models, context strategies, or pipeline architecture are evaluated largely through manual review and intuition. There is no systematic way to answer: "Did this change make our output better, worse, or the same - and for which languages, repo sizes, and content types?"
This is a hard problem. LLM outputs are non-deterministic - identical inputs produce different outputs across runs, and small variations at early pipeline stages compound into meaningfully different end-user content downstream. Evaluating quality requires methodology that accounts for this: statistical reasoning over multiple runs, understanding of cascade effects through the pipeline, and rubrics that balance human judgment with automated signals.
This role builds the evaluation function from scratch. You'll define what "good" means for our generated content, build the infrastructure to measure it, and create the experimental framework that lets the team ship changes with confidence.
What You'll DoYou'll own the LLM evaluation strategy at Driver - from first principles to production infrastructure. This is a foundational role: you're not joining an existing eval team, you're building it. As the function matures, you'll seed and grow a team around it.
Define quality metrics and build evaluation datasets. Establish what "good" looks like for each content type across the pipeline. Build and curate gold-standard evaluation datasets across languages and repo archetypes (monorepos, microservices, libraries, applications). Design rubrics that capture accuracy, completeness, usefulness, and readability.
Build benchmarking and experimentation infrastructure. Create automated evaluation pipelines that score output against reference datasets. Instrument the content generation pipeline to support A/B comparisons - run the same codebase through two strategies and compare results. Build tooling for LLM-as-judge evaluation and regression detection. Integrate evaluation into CI so pipeline changes come with quality evidence.
Develop automated quality signals at scale. Build quality checks that flag degraded output without requiring human review of every document. Monitor content quality trends over time. Design sampling strategies for human review that maximize signal with minimal annotation effort.
Quantify tradeoffs and inform decisions. Run experiments on model selection, context strategies, and pipeline architecture changes. Quantify cost/quality/latency tradeoffs. Partner with the engineering team to turn evaluation insights into shipped improvements.
QualificationsEducation: Bachelor's, Master's, or PhD in Statistics, Machine Learning, Data Science, Computational Linguistics, or a related quantitative field.
Experience: Minimum 3 - 5 years in applied science, ML engineering, or data science roles with a focus on evaluation, NLP, or generative AI. 7+ years experience preferred.
Required Technical Skills
- Strong statistical foundations: experimental design, hypothesis testing, confidence intervals, effect sizes, power analysis.
- Experience designing and running evaluations for LLM or NLP systems - you've thought carefully about what "better" means when outputs are open-ended text.
- Proficient in Python and the scientific/data stack (pandas, NumPy, scipy, sklearn).
- Comfortable working in Jupyter notebooks for exploration and prototyping, and turning that work into automated pipelines.
- Experience with LLM-as-judge approaches, inter-annotator agreement, and rubric design for subjective quality assessment.
- Familiarity with the practical challenges of non-deterministic systems: variance decomposition, multi-run methodology, distinguishing signal from noise at scale.
- Strong data storytelling - you can turn experiment results into clear recommendations that drive engineering and product decisions.
Preferred and Nice-to-Have Technical Skills
- Experience with LLM APIs and prompt engineering across multiple providers.
- Familiarity with evaluation frameworks (e.g., RAGAS, DeepEval, custom harnesses).
- Experience building data pipelines or ETL workflows (Airflow, Dagster, or similar).
- Comfort with SQL and working directly against production data stores.
- Experience with visualization tools (Matplotlib, Plotly, Streamlit) for building internal dashboards and reports.
- Background in code understanding, developer tools, or technical documentation.
- Experience building or managing annotation pipelines and human evaluation workflows.
- Competitive Compensation Packages - Cash & Equity
- Flexible Work Culture
- Unlimited Time Off + 12 Paid Company Holidays
- Insurance - Health, Dental, & Vision
- Life Insurance & FSA Accounts
- 401(k) Retirement Accounts - Traditional, Roth, or Both
- Quarterly Team Offsites
Driver is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.