Call for Problems FPCs 2025

This is the Call for Problems for the jury responsible for the Freshmen Programming Contests, organized by UvAmsterdam, VU Amsterdam, TU Delft, TU Eindhoven, RU Groningen, and potentially other universities in the Benelux. These contests will take place around May 2025, though the exact date may differ per university.

The deadline for submitting problems to this CfP is Saturday February 8th, 2025.

If you have any questions, feel free to reach out to the jury on the #cfp channel in the BAPC Organisation Slack which can be joined here.

While we encourage you to submit a problem through this CfP, it is also possible to join the jury without submitting a problem. Please do submit this form in this case.
We encourage you to submit problems even if you will not be able to join the jury.

This Call for Problems is based on the one for BAPC 2025, which can be found at https://jury.bapc.eu/.

Problems from previous years can be found in the CHipCie archive.

If your problem is not selected for the final set, you may retract it and use it for another contest instead.

Your name*

Email address*

example@example.com

Do you have time to spend ±8 hours per week in March and April to work on the implementation one or two of the problems?*

YesNoOther

Relevant experience*

Please indicate whether you have any experience relevant to programming contests (as participant, jury, or otherwise). If applicable, you may also list other programming-related experience.

If you have problem ideas for the Freshmen Programming Contests, please enter them in the fields below. We're specifically looking for the following:

Difficulties ranging from trivial/easy to medium/hard, with subjects that are known by Computer Science bachelor students (typically first-years). We'll cater mostly for first-time participants, and less for experienced competitive programmers, so we need more easy than hard problems.
The problem statement (including Input/Output sections, excluding samples) should not be much longer than one A4 page.

For every problem, please indicate:

Problem name
Problem difficulty (0% = every team will solve, 100% = no teams will solve, based on first-time participants in the first year of their bachelor)
Problem category/-ies (e.g. sorting, math, graphs, ...)
Problem description (for long descriptions, please include a one-sentence summary)
Input/output format/examples
Analysis of the intended solution
Preferably, correct solution code

If you would like to submit a problem package, you can find a template zip here. On Linux, such a zip can be created with the command zip -r [problem_directory].zip [problem_directory].

Problem idea(s) (not required)

Problem idea(s) attachment(s)

If you have a problem package, PDF, solution code, or other files relevant to your ideas, please add them here.