Vipkurum question cropping — the answer sits in the question's record, not a row number
The question cropping and answer key matching tool we wrote under the Vipkurum roof. The real change is where the link lives: the correct answer is no longer parked in a second file behind a row number, because Gemini and OpenAI models write it inside the record of the question it belongs to. Revise a question and its answer travels with it, so keeping a second file current stops being a step. Python and OpenCV handle the cropping, records sit in MongoDB, and the service reaches Laravel through Node.js. The scope is education material; a contract archive, version tracking or a payment product are not work we can show.
Read the case study →