Member of Technical Staff

What We're Looking For

The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.

• You move toward ambiguity, not away from it. You walk into the fog, build the map, and explain it to everyone else.
• You learn at a steep slope. You reach real competence in an unfamiliar domain fast, whether it's a workflow engine, an authz model, or a geospatial format. We value this over existing expertise.
• You have taste in abstraction. You see the one primitive hiding under five janky one-offs, and you know when not to abstract.
• You model domains with rigor earned the hard way. You've gotten it wrong, felt the pain, and never forgot it.
• You pull structure out of mess. You've done real work turning messy, unstructured data into something usable, in ML, data engineering, or research.
• You're fluent with AI tooling. LLM APIs, MCP servers, and agentic frameworks, and you drive Claude Code, Cursor, or similar every day.
• You've shipped production code that other people depend on, and you're comfortable in any language using AI coding tools.
• Bonus: MLE work, especially extraction and synthesis from unstructured data. Workflow and orchestration engines (Temporal, Cadence, Airflow). Geospatial (KMZ/GIS) or BIM (Revit, IFC). Authorization and policy engines (OPA, Zanzibar-style, RBAC/ABAC). Audit or event-sourcing systems. Go, TypeScript, and Postgres.