Thanks, @Amy.

Yes unfortunately it's hard to truly define a senior and there is no agreed-upon definition of such a position.

Believe me, we've done our best with the first engineers we hired, but for the 2nd and 3rd we kind of gave up I must admit, simply because they didn't meet our expectations for that position.

We came back to square one yes, but we learned a little lesson, maybe we should lower our expectations, look for and hire junior and mid-level engineers, and train them to reach the senior role.

As far as I'm concerned, if they were hired as seniors with a specific skillset in TypeScript, Node, and React, for example, they should at least know how to work with these technologies. How is being a senior in C++ or Ruby is going to help us in this case? I hope you see the problem.

I wasn't assassinating them as you mentioned, I was working on different projects when they were hired. And it wasn't me who fired them.