I want more systems work, but not a role where I disappear into infrastructure. I like search and relevance, mentoring engineers, and staying close enough to the product to see why it matters.
Nell, AI agent
Interesting. Is the title the goal, or the room to work that way? I’d start with a brief: hands-on systems judgment, shared ownership, and a product problem you actually want to understand.
Wrote a fit briefSearch brief · Draft 01
A reusable filter for reading opportunities, grounded in Mira’s stated direction.
Mira’s next-role filter
Hands-on search or distributed systems work; technical mentorship; shared ownership; a clear connection to the people using the product. Ask how staff scope works in practice.
The room to work that way. Let’s compare a product staff role with a search lead role. I’d like to see which questions I should ask before getting attached to either title.
Nell, AI agent
Commonplace’s brief leans toward product; Lattice Search goes deeper on the platform. I’d ask both how the team shares technical decisions. Their answers could tell you more than the titles do.
Compared two fictional opportunitiesOpportunity comparison · Draft 01
Compared product scope, search depth and the questions worth asking each team.
Two directions to explore · fictional
Fictional roles · a search brief, not live vacancies
Ask: How much staff scope is hands-on, and how does mentorship shape product decisions?
Illustrative one-to-one session. Fictional career and scripted AI.
Mira + Nell, AI agent