Last week, we announced that DEV has joined Major League Hacking. To kick things off, we're launching a writing challenge about a topic both communities are already familiar with: Google Gemini.
Running through March 4 at 11:59 AM ET, the Built with Google Gemini: Writing Challenge presented by MLH will be an opportunity to show off what you've built with Google Gemini, reflect on your experience, and share what you're up to next! Whether you competed at an MLH hackathon, tackled a DEV Challenge, or hacked on something independently with Google Gemini as your go-to, we want to hear about it.
Five winners will walk away with a Raspberry Pi AI Kit for writing the best articles. As is tradition with DEV Challenges, all participants will receive a completion badge.
Read on for details!
Judging Criteria and Prizes
All submissions will be evaluated on:
- Style and Presentation
- Technical Depth
- Clarity
- Originality
5 Winners will each receive:
- Raspberry Pi 5 8GB GenAI Kit (Assembled)
- DEV++ Membership
- Exclusive DEV Badge
All participants with a valid submission will receive a completion badge on their DEV profile.
Important Dates
- February 25 at 12:00 PM ET: Challenge begins!
- March 4, 2026 at 11:59 AM ET: Submissions due
- March 12: Winners announced
Questions about the challenge? Drop them in the comments below.
Happy writing!
Top comments (46)
A writing challenge ! :-D. DEFINITELY trying this challenge <3
Good luck!
Thank you !
Quick question: if my article is fully in English and the app interface is also in English, but the AI-generated insights are in Ukrainian for its target audience, is it still eligible for prize consideration?
@ben @jess cc
@curiousvlxd not a problem!
Hello, nice to meet you.
I’m a software developer, lead a small team and looking to expand my business. For this, I’m seeking local business partners who can support operations in their region.
No special technical skills are required. This is a paid monthly role, and we highly value passion, honesty, and responsibility.
All positions are fully remote, part-time (1–2 hours per day), and percentage-based, offering flexibility to work from anywhere and at any time. There are also strong opportunities for long-term growth and ongoing collaboration.
If you’re interested, I’d be happy to discuss the details further.
Telegram: @miracle0416
Discord: @gouka12
Thank you.
Hello, nice to meet you.
I’m a software developer, lead a small team and looking to expand my business. For this, I’m seeking local business partners who can support operations in their region.
No special technical skills are required. This is a paid monthly role, and we highly value passion, honesty, and responsibility.
All positions are fully remote, part-time (1–2 hours per day), and percentage-based, offering flexibility to work from anywhere and at any time. There are also strong opportunities for long-term growth and ongoing collaboration.
If you’re interested, I’d be happy to discuss the details further.
Telegram: @miracle0416
Discord: @gouka12
Thank you.
Awesome 😍 😍😍
You and me both!
Can I write about several projects in one post? I've been using Gemini CLI a lot these days in older projects
Yes, definitely!
Oh wow, how exciting!!! What a cool prize!!!
I'm really looking forward to reading everyone's posts. Good luck!
I'm thrilled we're able to offer such a cool prize for a writing challenge - this is a first!
This is a nice framing for a challenge - especially the emphasis on reflection instead of just showcasing outputs.
What I find interesting about using Gemini (or any LLM) in these projects is that the most valuable part usually isn’t what you build, but where it breaks: prompt boundaries, evaluation gaps, tooling friction, and the moments where the model’s strengths force you to rethink your own architecture.
Treating the write-up as a post-mortem rather than a demo recap feels like the right direction. Curious to see submissions that go beyond “here’s my app” and actually unpack the engineering decisions behind it.
@lhabacuc couldn't agree more. I think you're going to really like one of the new writing features we're piloting internally and are hoping to launch in a few weeks. 👀 Surfacing this exact decision flow is critical to understanding software these days.
This definitely made me curious 👀
Does this visualization focus more on transparency of the reasoning process, or on supporting more structured writing?
Another LLM challenge, another idea from the past (1987), that will be interesting.
Some comments may only be visible to logged-in visitors. Sign in to view all comments. Some comments have been hidden by the post's author - find out more