Sure, but you're looking for a programmer. :)

... and how exactly is developing code from scratch within 4 hours different from developing code a doghouse scratch within 4 hours?

Both require good thought, design and a plan to execute.

The only way to deliver a doghouse from scratch within 4 hours is to have a doghouse template that's prefabricated, ready and available.

An experienced web developer will have template in his head for various typical problems. So that should not be an issue at all. It's just typing it out for the component at hand.

Asking for using web components will of course limit the pool of candidates having a mental template quite a bit, since it's a fairly recent technology, and even then, most people probably never used the raw API, or if they do, they wrap it a bit, so it will not be something they'll remember right away.

That's the major pitfall here, to me.

> It's just typing it out for the component at hand.

You and I have very different approaches to design.

Before I type out the actual component, I will write the Enzyme via Jest test cases first to ensure I clearly understand what the actual component should be doing in the first place even if I am beyond sure I have a good grip on the requirements.

Real world experience has taught me that the ability to bang out code matters way less than the ability to ensure and verify that the code actually, in reality, behaves as expected by the customer.

That can be verified by clicking through the result, after you bang out the code. There's certainly nothing that prevents verification later, if you bang out the code first.

Automated verification may save some time (in some cases), but is not the only way to verify the component behavior.