When I joined Grammarly, it could fit in a small apartment. My first task was to fix a scalability problem: the service crashed with . . . 300 online users. Ten years later, millions of users relied on Grammarly apps everywhere—in browsers, on Windows, Mac, mobile, at home, in the enterprise, and through partnerships. Our product footprint grew, and so did our team. Along the way, we realized that scaling a software company is harder than scaling servers on AWS. As we kept hiring engineers and other essential experts, we began asking ourselves: Are we really moving faster with this big team? Are we productive? Can we even measure our developers' productivity? In this meetup I’ll tell you about engineering processes, software tools, and even the computer science principles we tried on our quest to scale engineering productivity and ease the growing pains. Join our conversation and have fun guessing: What worked and what didn't?