hirly

Sunset

Machine Learning Engineer

New York

Apply through hirly

hirly scores this role against your resume, shows its reasoning, then writes a resume and cover letter for it and fills the application with you. Free to start — no card required.

hirly's read of this role

Role family
Data & ML
Seniority
Mid level
Country
US
Work mode
Remote-friendly
First seen by hirly
2 Sept 2026

Derived automatically from the posting. Sign up to see how the role scores against your own resume.

the posting

About Sunset

At its core, Sunset was founded to help founders. We started by supporting startups through shutting down, but we have since expanded into unlocking a new revenue stream for all types of businesses.

In 2025, we had a unique insight: the data every company generates each day through collaboration, communication, and building is some of the most valuable training data in the world. Public and synthetic data can only get frontier models so far, so the next generation of model progress depends on real, proprietary data grounded in how actual businesses operate. We are a primary source of it, partnering directly with the frontier AI labs building what comes next.

Why Join Sunset Now

We have scaled from $0 to a multi-eight-figure run rate in a matter of months

We have raised from top-tier investors, including Floodgate, Afore, Ludlow, and Hustle Fund

We are small enough that you will carry outsized responsibility and grow as quickly as the company does

You will partner with and build for some of the fastest and most important companies in the world

You will help build a massive, category-defining business from the ground floor

The Role

Sunset turns sensitive internal enterprise data into de-identified datasets without destroying the structure and meaning that make the data valuable. The data does not arrive in one clean modality. It spans messages, documents, tables, files, images, metadata, and provider-specific structures, with important context distributed across all of them.

You will improve how well our system understands and protects that data. Your initial scope will be a prioritized subset of named-entity recognition, entity and identity resolution, structured extraction, classification, semantic review, or other model-backed parts of the de-identification pipeline. We do not expect one person to be an expert in every modality. The goal is measurable improvement in the areas you own: better precision, recall, F1, high-risk coverage, and preserved data utility across the failure modes that matter.

This is an applied, production-facing ML role. You will study errors, form hypotheses, build datasets and experiments, improve or replace models, and ship the result into a live pipeline. Evaluation, reproducibility, observability, and safe releases matter because they let us identify, ship, and verify meaningful model improvements in production.

What You'll Do

Own and improve NER, entity resolution, structured or tabular detection, document understanding, semantic review, or related de-identification systems

Transform model failures and capability ceilings into a prioritized improvement roadmap

Design active-learning loops that combine model sweeps, LLM-assisted review, clustering, and uncertainty signals to identify the examples most worth hand-labeling

Build representative datasets and benchmarks, and use decision-relevant metrics to reveal strengths, weaknesses, uncertainty, and failure costs

Choose and combine deterministic rules, classical ML, fine-tuning, embeddings, multimodal models, and LLM-based approaches based on the problem and evidence

Design experiments, tune thresholds, analyze precision-recall and utility tradeoffs, and explain which changes are real, uncertain, or limited to particular conditions

Productionize improvements with reproducible artifacts, evaluation evidence, runtime instrumentation, and safe rollout

Optimize inference cost, latency, and throughput without hiding regressions in quality or high-risk recall

Build high-fidelity evaluation environments with seeded failure modes and programmatic verifiers that expose subtle regressions

Build reliable model- or agent-based harnesses with bounded behavior and explicit output verification when the problem calls for them

Partner with Applied Science on measurement and calibration, Data and Product Engineering on pipeline and review systems, and Security and Quality on acceptable risk

Use AI engineering tools deeply to accelerate research, implementation, error analysis, and evaluation while verifying their output

What Success Looks Like

Model improvements generalize beyond the examples used to develop them and hold up in replay, shadow, and production evidence

Priority modalities and entity classes show credible improvements in precision, recall, F1, or other decision-relevant quality measures

High-risk misses decline without unacceptable over-redaction or loss of useful structure

New formats and modalities can be covered without relying on brittle one-off fixes

Improvements reduce meaningful delivery risk, review or rework burden, or loss of data utility rather than moving only an isolated benchmark

The team can explain why a model changed, where it improved or regressed across consequential failure modes and data segments, and whether the change should ship

The path from error discovery to a trustworthy production improvement becomes faster and more repeatable

Quality gains remain inside acceptable inference-cost, latency, and operational constraints

You Might Thrive Here If

You have 3+ years of professional machine learning or software engineering experience, including improving models in production

You have startup experience, enjoy broad ownership, and thrive when requirements are evolving or incomplete

You use modern AI tools fluently and verify their output

You have personally moved model quality through error analysis, data work, experimentation, implementation, deployment, and iteration

You have a strong grasp of precision, recall, F1, calibration, thresholding, class imbalance, imperfect labels, distribution shift, and representative evaluation

You are an applied engineer first: a strong Python and software engineer who can work inside data pipelines and production systems, not only notebooks

You have a bias toward action while maintaining scientific and engineering rigor

You are curious and stay current with relevant state-of-the-art methods

You choose techniques based on the shape of the problem and can combine deterministic, statistical, neural, and LLM-based approaches

You communicate uncertainty and tradeoffs clearly to scientists, engineers, and people making delivery or risk decisions

This Role May Not Be for You If

You want to focus on research novelty without owning measurable production improvement

You prefer optimizing one aggregate benchmark without investigating consequential failure modes, data segments, and failure costs

You want data preparation, evaluation, deployment, and production diagnosis to belong entirely to other teams

You reach for a larger model before understanding the errors, constraints, and simpler alternatives

You do not want AI tools to be part of your daily engineering and research workflow

Bonus

Experience with NER, entity resolution, information extraction, document understanding, multimodal systems, or privacy-preserving ML

Experience with hyperparameter tuning, data augmentation, model merging, ensembles, knowledge distillation, or multimodal model training

Experience fine-tuning or adapting transformer, GLiNER, embedding, vision-language, or small specialized models

Experience with active learning, uncertainty sampling, weak supervision, human-in-the-loop review, or LLM-assisted evaluation pipelines

Experience building goldens, adversarial corpora, replay systems, model bakeoffs, agentic harnesses, or programmatic evaluation environments

Experience with difficult ML or labeling problems

Experience with ONNX Runtime, TensorRT, model pruning, quantization, or other CPU/GPU inference optimization

Experience with sensitive enterprise data or other high-trust production systems

Experience with synthetic data generation and managing the synth-to-real gap

Is this role actually a fit for you?

hirly answers with a score and its reasoning, then writes the resume and cover letter if you decide to go for it.

Score it against my resume
Machine Learning Engineer at Sunset — hirly