From that point of view, yes, this is an interesting approach. Extremely detailed microservices can be super hard to read.

When I worked with Ruby, I struggled a lot with that, because the Ruby community is more inclined to use highly complicated patterns where you can see hundreds of different files with 10 lines of code each.

I think an engineer still needs to have at least an idea of that traditional way of doing things to be able to criticize it.

These are the ideas I'm looking for when interviewing, I would definitely hire you if you can justify your approach.