The questions about BigO isn't about premature optimization or actual implementation. It's about understanding exactly what a particular program is doing and ho

The questions about BigO isn't about premature optimization or actual implementation. It's about understanding exactly what a particular program is doing and how it's doing it. Any sort of technical solution given at a Google interview would generally have the following questions: 1) What big O time does this algorithm run in? Why? What big O space requirements does it take. 2) If space were more/less expensive, or time more/less important, how would you change the solution and why? Understanding those tradeoffs and being able to analyze code at that level is a big part of most software engineering jobs.