Engineer Describes Agent-Driven Onboarding at AI-Native Company
Jean-Michel Lemieux says an AI agent set up his development environment, surfaced backlog items, and retrieved historical decision context within three days at a new AI-native company, proposing the term 'mounting' over onboarding.
Original post · 1 min read
The laptop arrived, I logged in, and an agent basically took over from there. It set up my dev env, pulled repos, fixed dependency issues, got permissions approved, pointed me at the backlog, linked the architecture docs, and surfaced the Slack debates I actually needed to read before touching production.
When I needed context on something, I asked the agent and it found the exact thread from months ago explaining why a decision was made, who owned it, the related Linear issues, and the PRs connected to it.
I’ve only been here 3 days but it honestly feels like I’ve worked here for a year because the usual friction and scavenger hunt for context just isn’t there anymore.
We should probably stop calling this “onboarding” and rename it to “mounting” because this feels a lot more like mounting a distributed filesystem called “institutional memory” than slowly getting drip-fed context over 6 months.



