Member of Technical Staff, Research Engineering

Listen Labs is a Sequoia-backed company focused on building the human layer of AI, with notable clients including Anthropic and Google. They are seeking a Member of Technical Staff in Research Engineering to help develop an AI-native product that bridges the gap between AI systems and human needs, while also tackling challenges related to emotional intelligence and preference modeling.

Responsibilities:

• You solve problems end to end. The team is split vertically, so every engineer owns a part of the product and makes decisions across the LLM pipeline, infrastructure, backend, and UX
• Future or past founder. You scope your own work, think about the customers, and own your decisions
• You care about getting things right. Moving fast is essential, but a 100% solution is much more powerful than an 80% one. When something breaks, you go to root cause
• You're excited about pushing LLMs to their limits. We work directly with the frontier model labs on new releases and constantly probe where they break
• You communicate complex ideas in writing. We work independently with one meeting a week, so writing is how tradeoffs, problems, and decisions get worked through together
• You're highly technical. Most of our team started coding as teenagers and nerd out on details from language design to compilers

Requirements:

• You solve problems end to end. The team is split vertically, so every engineer owns a part of the product and makes decisions across the LLM pipeline, infrastructure, backend, and UX
• Future or past founder. You scope your own work, think about the customers, and own your decisions
• You care about getting things right. Moving fast is essential, but a 100% solution is much more powerful than an 80% one. When something breaks, you go to root cause
• You're excited about pushing LLMs to their limits. We work directly with the frontier model labs on new releases and constantly probe where they break
• You communicate complex ideas in writing. We work independently with one meeting a week, so writing is how tradeoffs, problems, and decisions get worked through together
• You're highly technical. Most of our team started coding as teenagers and nerd out on details from language design to compilers