Applied Scientist I

Job Summary

Before an agent can reliably operate software on a users behalf, it needs to understand what should happen next and why: the underlying process, its steps, decision points and governing logic, branches, variations, dependencies, and long-tail edge cases.

In practice, this knowledge is rarely represented explicitly. It is distributed across messy event logs, unstructured documents, screen recordings, UI interaction traces, historical executions, and the tacit knowledge of domain experts.

As an Applied Scientist on this team, you will work across teams to develop process-agnostic, scalable learning systems that recover the latent structure, decision logic, and dynamics underlying complex process execution trajectories from sparse, noisy, highly correlated observations spanning substantial behavioral heterogeneity and organizational scale.

You will take heterogeneous data such as action logs, noisy screen traces, semi-structured documents, and variant-heavy workflows, and build systems that recover canonical process structure, meaningful variations, decision rules, dependencies, exceptions, and provenance. These representations are consumed by downstream agentic execution systems and must preserve enough detail for an agent to act correctly while remaining structured, compact, transparent, and auditable.

The same observational data and learned representations also contribute directly to our work on computer-use models for last-mile interaction with enterprise software.

The problems here rarely arrive with clean formulations. You may begin with a branch the system consistently fails to recover, two superficially different execution paths that should collapse into the same process, or an algorithm that works across thousands of traces but fails at millions.

Your job is to turn those failures into tractable research problems: identify the right abstraction, formulate hypotheses, design evaluations that isolate the problem, and develop methods that solve it. Depending on the problem, this may draw from process and decision mining, graph algorithms, structured prediction, representation learning, information retrieval, program synthesis, model post-training and distillation, or agentic systems.

We care less about allegiance to a particular technique than about finding the simplest method that reliably recovers the underlying structure and scales.

Responsibilities

Process discovery and representation

• Build pipelines that discover, extract, and formalize end-to-end business processes from event logs, UI interaction traces, screen recordings, and unstructured documents.
• Develop algorithms for process variant detection, noise removal, and trace consolidation, turning noisy, high-cardinality action sequences into clean canonical representations.
• Design representations that preserve the information downstream agents need while collapsing irrelevant execution-level variation.
• Study the tradeoff between abstraction and fidelity: determine when superficially different trajectories represent the same underlying behavior and when small differences encode materially different decisions.
• Build retrieval and grounding systems that incorporate SOPs, documents, and domain knowledge when process understanding requires evidence beyond execution traces.

Evaluation and reliability

• Develop rigorous evaluation frameworks for process discovery and extraction, including LLM-as-Judge pipelines, conformance checking against ground-truth processes, and regression suites that catch subtle degradation.
• Develop evaluation methods for settings where there may not be a single canonical ground truth, including behaviorally equivalent process representations.
• Enumerate and systematically test exception paths, conditional branches, loops, rare variants, and the failure modes that naive extraction approaches miss.
• Make deliberate algorithmic tradeoffs so systems remain tractable across millions of traces and thousands of variants, including choices around data structures, approximation, indexing, and level of abstraction.
• Diagnose failures in production and turn recurring failure patterns into new algorithmic or research directions.

Collaboration

• Work closely with the computer-use agents team so the representations you produce are expressed at the right level of abstraction, contain the necessary execution context, and are robust enough for downstream autonomous execution.
• Work across research, engineering, and product to move promising methods from prototype to production and measure their effect on downstream agent behavior.

Requirements

• Ambitious and Hungry. Far and away the best prize that life offers is the chance to work hard at work worth doing. - Theodore Roosevelt
• We screen for comparable experience and strong fundamentals, not exact tool matches. Equivalent technologies are welcome.
• Problem Decomposition and Algorithmic Thinking. You can take a loosely defined problem, such as recovering a reliable process from messy action logs, decompose it into tractable sub-problems, reason carefully about edge cases, and arrive at an approach. You are comfortable reasoning from first principles about data structures, graph algorithms, approximation, indexing, and time and space complexity when algorithms must operate over millions of executions.
• ML / DL Breadth. Strong working knowledge across representation learning, sequence modeling, clustering, structured prediction, information retrieval, generative modeling, and modern foundation-model adaptation. You have the judgment to recognize when a problem calls for a learned model, an algorithmic solution, an LLM-based system, or some combination of the three.
• Cross-Domain Research Translation. You read research from adjacent areas including frontier AI, computer vision, language modelling, process mining, program synthesis, information retrieval, graph learning, and knowledge representation, and can judge whether it applies. You can identify the core idea inside a method, understand the assumptions that make it work, determine whether those assumptions hold in your setting, and adapt the idea into a working prototype.

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.