learning-it by example

#329 Forward deployed engineer interviews 5.3 min

Build, Configure or Vendor? Score It and Stress-Test

Configure won 40 to 34. Moving one weight at a time shows how sure that is.

1. In the build, configure or vendor scoring example, after 'configure' wins, why is each weight moved one at a time?
2. In the build, configure or vendor scoring example with made-up scores and weights, what were the totals for the three options?
3. In the build, configure or vendor scoring example, moving one weight at a time from 0 to 10 with the other weights left as set, which criteria could never change the winner?
4. In the build, configure or vendor scoring code, what does the winner function return when the top two options have the same total?
5. In the build, configure or vendor scoring example, what is said about the options, scores and weights?
6. In a weighted build, configure or vendor scoring matrix, when should the weights be set?

Practice only: nothing is saved and no score counts towards anything. Each answer comes with the reason.

  1. Check one total by hand

    Copy the code folder first. Using the SCORES and WEIGHTS in options.py, work out the total for 'build' on paper by multiplying each score by its weight and adding. Then run python run.py and compare your answer with the printed line.

    A hint

    Build's scores are 2, 2, 5, 5 and 2. The weights are 3, 2, 3, 1 and 2.

  2. Weigh everything equally

    In options.py change WEIGHTS so that every criterion has the weight 1. Predict the three totals and whether configure still wins, and whether cost and risk still never change the winner. Run python run.py to check.

    A hint

    With equal weights each total is just the sum of the five scores. I saw 16, 18 and 14.

  3. Care a lot about fit

    Put the weights back. Then change the weight of fit from 3 to 7. Predict which option wins. Run python run.py and check whether the total for build now beats the total for configure.

    A hint

    Build scores 5 on fit and configure scores 3. I saw a win for build, 54 to 52.

  4. Make the vendor cheaper

    Put the weights back. In SCORES change the vendor's cost score from 3 to 5. Predict the new total for the vendor and whether the winner changes. Run python run.py and read which flip points moved.

    A hint

    The vendor gains 2 points times the weight of cost. I saw the vendor total move to 38 while configure stayed ahead at 40.

These tasks are for you to try on your own machine. Nothing is checked or saved.

What this does not show

Made-up options, scores and weights (my opinion); one weight moved at a time from 0 to 10; ties are skipped; cost and time are scores, not estimates; the sources are vendor and prompt pages.

Up next in Forward deployed engineer interviews

More in Forward deployed engineer interviews

All Forward deployed engineer interviews videos

Related videos