Most writing today focuses on how individuals use AI tools. I wrote this post to share an early attempt at a playbook for building truly AI-native engineering teams
Larridin | AI Native Software Engineer (All Levels) — Bay Area, In-Office
Larridin is the measurement layer for AI in the enterprise. We’re building AI-native systems that correlate AI behavior to business results, expose absorption bottlenecks, and enable enterprises to invest with conviction. Backed my top tier investors such as a16z, Google and Bloomberg and with early traction!
We want high-agency software builders (3–10 yrs) who think AI-first, move fast, and want ownership of large parts of product and business. This is an in-office role in the Bay Area for engineers who want to own outcomes, not just tickets.
Looks good. Curious, how is auth handled? Lot of docs have permissions etc. Can you clarify how this is handled in both indexing side and searching side of things?