Bigtable is a wrapper of Bigtable; Spanner is a wrapper of Spanner, Storage is a wrapper of Storage. Not sure why the GP thinks this is a bad thing.
Was mentioned in an onsite interview i had with them a few years back. Maybe i misunderstood but it seemed that internal teams didn't integrate with the same API as external customers. Not sure the other reply means that the "wrapper" doesn't exist or the wrapper's are just named the same as the underlying service or i just misunderstood the point.
My impression (I work at Google) is that internal interfaces to some of these services have a lot of Google-specific stuff that are hard to map to non-Google requirements.