After you get the job, here's something my old team learned through experience (failure): modular is good, but in practice, abstracting things to the theoretica

After you get the job, here's something my old team learned through experience (failure): modular is good, but in practice, abstracting things to the theoretical max results is software that none of the developers understand, is impossible to maintain, and probably doesn't perform any better than if you didn't "optimize" near as much. (Source: I was a programmer, then a tech lead, then moved into managing about 100 of them.) Another tip: it's your job to help the programmers make you look good. You do that by making them look good. It should be a virtuous cycle.