I get a feeling that he is going about this the wrong way. While he lists all the things that he is not comfortable with and why it might not work out and is al

I get a feeling that he is going about this the wrong way. While he lists all the things that he is not comfortable with and why it might not work out and is also willing to throw money at someone to 'fix' this problem of finding the 'right match', he doesn't seem to be open to accepting the idea that he will not get to choose every aspect of the company unless he also is willing to participate in every aspect. For instance: > the London startups I’ve interviewed with so far, all seem to have > committed the same sins: they’re recruiting for a role to exercise > technical ownership after they’ve made their decisions about the stack > and technical strategy. and then ... > While I do use Python, Ruby, JavaScript, etc for different (non-critical) > components in the solution design, I’m mainly a Java engineer. All of > these aforementioned have their time and place, but my skills and passion > are not around using any of them as a core platform. > Since I’m a backend engineer I don’t do “full stack” when it comes to > coding. If you clearly need, but can’t afford (or don’t want) to hire > frontend or mobile developers, then we might not be compatible. So, on the one hand he expects startups to not commit to a stack until he is there and be open to changing it if he feels there's a need to, after he comes in but he is not willing to accept the responsibility that comes with deciding the stack ? If he doesn't do full stack (and that's a prefectly good thing) he should learn to interoperate with stacks that aren't decided upon by him. Also, this: > With most startups I interviewed, I found the team dynamics and technical > stack to be more challenging than the business plan or the potential the > idea has. That's just condesending.