If they've used a variety of frameworks and worked on a variety of different projects with varied architectures, it's pretty easy to assume they're not only wi

If they've used a variety of frameworks and worked on a variety of different projects with varied architectures, it's pretty easy to assume they're not only willing but capable of learning new things. I can pickup pretty much any framework in any language and start utilizing it, but I can assure you it will take me at least a few weeks of learning and using examples/templates to get in the groove of things and a month or so to start really getting into leveraging capabilities. If it's a terribly designed framework, API, or very oddly structured language, it may take a bit more time--or if its leveraged in a massive codebase you need to understand that's poorly documented (were no longer talking about the framework itself though). Of course if you're trying to measure how quick someone can pickup a framework or if they're capable of "hitting the ground running" on arbitrary framework X with arbitrary existing codebase Y with deliverables/output that assume no learning curves while having no desire investimg in long term talent retention, this approach isn't for you. If minimizing time to market is your main goal, this approach isn't for you. If you want to produce something different where time to market can still reasonable but a bit slower, this approach may be for you.