Ncg | Kaylee

By week six, two of her questions had led to the deprecation of a redundant microservice, saving the company an estimated $40,000 a year in cloud costs. What sets Kaylee apart isn’t her technical prowess — though her Python is clean and her system design diagrams are surprisingly elegant. It’s her embrace of the NCG identity as a lens, not a limitation.

Her internal blog series, “Things I Was Too New to Know Not to Ask,” has become required reading for onboarding cohorts. She’s been informally dubbed the . And her manager, Derek, has changed his entire approach to mentorship. ncg kaylee

And that’s a feature, not a bug. [End of feature] By week six, two of her questions had

“I cried in the supply closet,” she says with a wince. “Then I wrote a post-mortem, automated the fix, and bought donuts for the on-call team.” Her internal blog series, “Things I Was Too

That post-mortem — titled “Oops, Did I Do That? (And How to Never Do It Again)” — has since been adapted as a template for the company’s entire incident-response training. Kaylee doesn’t know if she’ll stay in infrastructure. She doesn’t know if she wants to be a manager, a principal engineer, or something else entirely. But she does know one thing: the power of a beginner’s mind in a world of experts.

“I don’t know how things ‘usually’ break,” Kaylee told me over a cafeteria oat milk latte. “So I just look at how they could break. Sometimes senior engineers have seen so many disasters that they’ve stopped imagining new ones.”