“OK Andrew, we’re looking for someone for this senior developer and they’ve got to be really really great at copying and pasting between Claude and an IDE.
Now we’re going to set up a whiteboard test here and you can demonstrate to us your best copying and pasting.”
“errrr, do I do any actual coding in the job?”
“Well, yes, inasmuch as anyone does these days. It’s mostly copying and pasting though, but hey that’s what coding IS now, right?”
“OK are you ready for your coding test, here it is: what key is COPY? And what key is PASTE?”
But for about ten years, at least, the majority of Google swe rules have been talked about as "just moving protobufs", which is effectively the same. If your job is just plumbing other people's designs for existing products, how fun can it be?
It's a running joke internally. But not always far from the truth. Translating business level protobufs into solution level protobufs is indeed the job of entire teams sometimes.
Now we’re going to set up a whiteboard test here and you can demonstrate to us your best copying and pasting.”
“errrr, do I do any actual coding in the job?”
“Well, yes, inasmuch as anyone does these days. It’s mostly copying and pasting though, but hey that’s what coding IS now, right?”
“OK are you ready for your coding test, here it is: what key is COPY? And what key is PASTE?”