How to strengthen your scholarship application

BSc Software, Data and Technology at Constructor University Bremen

With full scholarship opportunities from the JetBrains Foundation

Apply now

Via CUB website

Key elements of your application

Your application documents are how you make a first impression on the reviewers and provide an initial answer to the question “Is this candidate a good fit?”

Together, they should make your background clear and highlight what’s relevant for the program.

Curriculum vitae (CV)

A concise overview of your educational background and program-relevant experience, for example olympiads, projects, or teaching.

Avoid vague or unrelated filler, random hobbies, or anything that doesn’t show your suitability for the program

Always focus on outcomes. Don’t just tell us that you participated in something – tell us what you achieved in doing so.

Motivation statement

A focused explanation of who you are, what you’ve done, and why this program is the ideal next step for you.

Read more tips on how to present yourself in the motivation statement below.

Other documents

Anything else that helps concretely demonstrate your aptitude, for example your transcript or certification of English proficiency.

Opening: Your profile in 20 seconds

The first paragraph is not a warm-up; it’s an overview. In about 20 seconds, a reviewer should understand where you’re at, what you’re aiming for, and why this program fits your trajectory.

Use this formula: Background → Goals → Fit.

Be as specific as possible when telling us why you’re a good fit. Show how specific elements of the program match up with your learning style and goals.

Avoid low-signal openings, childhood biographies, praising the program, and vague statements of intent (“I want to be an awesome developer!”, etc.).

Opening template you can adapt:

I’m currently X (context).
Through Y (experiences), I realized Z (direction and motivation).
I’m now looking for A (next step), and this program fits
because B (specific aspects of the program that match your learning style and development goals).

Body: Claim, evidence, reflection

Reviewers can’t grade you on vibes – they need concrete evidence. Describe your program-relevant achievements, and back them up with facts.

Present each achievement using the Claim → Evidence → Reflection framework.

Cut the noise, buzzwords, filler sentences, and abstract claims.

Claim

A short statement about a capability or trait – for example, algorithmic problem solving, research-style work, or leadership.

Evidence

Proof of what you personally did, with appeals to numbers, outcomes, artifacts, or roles:

  • Rankings or medals.
  • Project scope.
  • What you built or shipped.

Reflection

What the experience taught you and why it matters:

  • How you improved.
  • What you learned about your working style.
  • Why it makes you a good fit for the program.

Claim → Evidence → Reflection template you can adapt:

Claim: I am good in ...; I have skills ...; I motivated in ... .
Evidence: I won ...; I created...; I have ... .
Reflection: It taught me ...; I like ...; I want to ...; I feel ... .

Conclusion: Your development trajectory

The conclusion is more than a polite “thank you for your time”. Use it to show who you are and what kind of progress you hope to make. Avoid empty statements like “I’m going to be the best student ever and take every extra course!” Instead, be clear and honest about where you want to go next, even if you’re not 100% sure yet.

A strong conclusion:

  • Focuses on 1 or 2 main ideas.
  • Conveys reasons (not just enthusiasm).
  • Explains why this program is the ideal next step for you.
  • Demonstrates why you’re a good match for the academic opportunities we offer.

Conclusion example (but don’t just copy this – be original!)

I’m choosing between Software Engineering and Machine Learning because I’ve tried both in projects and want deeper foundations.
I’d like to deepen my skills through coursework, projects, and a teaching assistantship.
I also hope to earn a JetBrains internship.

Motivation statement checklist

I understand the target profile and selection criteria.

My opening uses the Background → Goals → Fit formula, and doesn’t simply offer a childhood bio or praise for the program.

I removed all the noise like buzzwords, fillers, and generic phrases.

Quality test: After each sentence, ask: “If I remove this sentence, do I lose useful evidence for the committee?”. If the answer is “not really,” it’s probably noise.

My conclusion contains 1 or 2 directions, along with reasons, a connection to experience, and a next step.