The technical interview started with a requirement to code a simple REST call with the function name and variable name to use specified in the instructions. The next part was strangely vague with only three pieces of information provided.

1. a domain
2. an input value
3. an output value

An example of the above translated into a sentence might be "Go to 'somesite.com' to find information about sending the value 'blue-5' to some URL mentioned somewhere in the site to get back 'red-7'". There was no mention of the value type, e.g. "We are searching customer orders."

A consultant using only these requirements would be making the questionable choice of following a series of assumptions regarding the endpoints and REST calls, only to end up with a result which may be a coincidental match, and no means to verify if the implementation is correct or not. Even recognizing that this is an exercise, I found the scenario to be very unrealistic.

Question

The technical interview started with a requirement to code a simple REST call with the function name and variable name to use specified in the instructions.  The next part was strangely vague with only three pieces of information provided.

1. a domain
2. an input value
3. an output value

An example of the above translated into a sentence might be "Go to 'somesite.com' to find information about sending the value 'blue-5' to some URL mentioned somewhere in the site to get back 'red-7'".  There was no mention of the value type, e.g. "We are searching customer orders."

A consultant using only these requirements would be making the questionable choice of following a series of assumptions regarding the endpoints and REST calls, only to end up with a result which may be a coincidental match, and no means to verify if the implementation is correct or not.  Even recognizing that this is an exercise, I found the scenario to be very unrealistic.

Moveworks

Domanda di colloquio di Moveworks

Aziende seguite

Ricerche di lavoro