Principal Applied Scientist, Humorphic Labs

Humorphic Labs builds AI systems that work as teammates rather than tools. We ship them six months or more ahead of anyone else. The Lab is small on purpose, so it can change direction in a day.

Humorphism concerns the quality of the working relationship between a person and an AI system. It asks whether the system acts proactively, adapts to the person and the situation, earns trust, manages attention, and strengthens human judgment. This role turns those behaviors into testable questions, then answers them with working systems.

You will own the scientific agenda. You will convert a fuzzy behavioral goal into an end-to-end plan that covers data, agent architecture, evaluation, and the product experiment that tests it. You will write code every week and build large parts of the experimental stack yourself, because it does not exist yet.

The first focus areas are agentic products where a domain expert holds judgment the system cannot replace. Amazon Connect places an assistant beside a person handling a live conversation. AWS Bio Discovery places one beside a scientist running experiments. Both need evaluation that measures collaboration quality rather than task completion alone.

The role changes shape as the Lab matures. It starts as hands-on science in close partnership with product and engineering. Later it moves inside a product team to carry adoption of what the Lab proved.

Key job responsibilities

• Own the scientific strategy for human-AI collaboration across agentic and multimodal systems.
• Convert desired interaction behaviors into falsifiable hypotheses, evaluation tasks, and system requirements.
• Build the evaluation system that measures teammate behavior, trust, adaptation, human contribution, and failure recovery.
• Design agent systems that use memory, tools, planning, and recovery, then test them with the people who do the work.
• Design data collection and curation for language, speech, and interaction traces.
• Build significant parts of the experimental stack yourself, because that stack does not exist yet.
• Diagnose failures across data, models, orchestration, evaluation, and product interaction.
• Define the requirements engineering needs to turn a proven method into a product capability.
• Partner with design, product, engineering, and behavioral research from problem definition through product validation.
• Run experiments with partner product teams, then report what worked, what failed, and what changed as a result.
• Set the standard for reproducible experiments, evidence, and scientific review inside the Lab.
• Mentor scientists and engineers without moving away from hands-on work.
• Represent the work in internal reviews and in appropriate external scientific venues.

A day in the life

Your week has two centers of gravity.

Most days you build. You take a claim about how a teammate should behave, design the smallest experiment that can falsify it, and run it. You read interaction traces from real sessions, then argue with the engineers about what they mean.

The rest of the week belongs to the people the work is for. You sit with a contact center agent or a bench scientist and watch where the system helps and where it intrudes. You leave with the next hypothesis. Often you leave with evidence that kills the last one.

About the team

The Lab is a lead who still writes code, an Applied Scientist, and engineers. Applied AI Solutions leadership approved it with one instruction, to explore the limits of what we can build, and one number, to ship six or more months ahead of anyone else.

You own the agenda, the hypotheses, and the evaluation. The engineers build the systems that test them, then the products that carry the ones that survive. Neither seat hands work over a wall.

We have a sunset clause. Once a capability is proven and integrated into its product, the Lab moves to the next frontier.