Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
Since this is the 25th edition, I thought it would be a nice opportunity to have a little conversation with all of you! Whether you have questions about writing, finding ideas, building a series, engaging with the community, staying consistent, or anything else about my journey with Dev Opportunity Radar, I'd be happy to chat.
I will be around in the comments throughout the day, and I'd love to hear about your own journey too.
If you've been writing on DEV for a while, I'd love to hear any lessons, tips, or advice you've picked up along the way. And if you're thinking about starting your own series, feel free to share your questions as well.
Let's make the comments a place where we can all share our experiences and learn from each other. Looking forward to chatting with you 😀
JavaScript enthusiast with a growing passion for Python. I love exploring the world of programming, experimenting with code, and discovering new ways to turn ideas into reality.
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
Civic technologist building AI tools that help systems explain themselves. Clew Suite builder, NACM 2026 speaker. I write about hackathons, product judgment, agent readiness, and learning in public.
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
@hemapriya_kanagala Di, its great!
Thanks for the mention and well I'm again in exam prep for SEM-7 starting next week. So, I'm kinda not into any other hacks since last 2 months due to hacktoberfest, diwali, exams and all so I stopped looking out for them.
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
It's totally fine, bhai! I can understand. All the best with your exam prep, and make sure to take care of yourself too 😀
about the GIFs, I'm actually not much of a GIF person, but I had a lot of fun adding them to this article! Francis (@francistrdev) had suggested using them a long time ago, so I had tried them in a few articles before stopping. I guess I found my GIF inspiration again for this article 😄
It does bring light into the articles since I do prefer seeing pictures time to time instead of just all text. Whatever works for you and thanks for the mention. Good work! :D
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
Thanks for suggesting it in the first place and for always supporting the Radar, Francis! I'll try to find more places to add them in future articles too 😀
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
Thank you so much for always supporting the Radar, nyaomaru! I actually mentioned you in the article too; I hope you got the notification! And I'm really happy to hear that you've discovered opportunities through the Radar. That's exactly what I hoped for when I started this 😀
Congratulations on version 25!🎉 And also on the further improvement of getting a .com domain! Rome wasn't built in a day. Good luck with future improvements too!
I came across FR8 on Radar #2 and tried to apply on the same day itself.
Unfortunately they didn’t accept my application, but I would never have heard of the program if not for your list. I’ve also applied this month to the PayPal AI Hackathon.
Can you tell me how you determine whether African-based readers can apply to programs that have country limitations or on-site requirements?
Congratulations on a huge milestone, tbh devoppurtunity radar has been a revelation for me, it exposed me to oppurtunities I could only dream of thanks to Hemapriya, and I'm grateful for this. 🎉🎉🎉Cheers to the 25th Edition, next stop 50th and beyond.
Congratulations on 25 editions, Hemapriya, and on not missing a single Friday! 🎉 What stood out to me is how deliberately the Radar was built, more than the numbers themselves.
Leaving the Community Finds section empty in Edition #1 was a smart move. Most series add reader participation later, once they want engagement. You built the slot before anyone had used it, and it told readers you meant “our radar” before you said it. Reader Updates is the natural next step. It closes the loop on “what happened after you found something?”, which is the hardest part of curation to see. Daniel’s FR8 application and Anh’s OpenAI Build Week submission are the kind of evidence that numbers can’t give you.
Your curation criteria are the real product. Anyone can aggregate links, and a search engine can do that. What you add is judgment:
You check the official source for eligibility, fees, and deadlines before sharing.
You ask what the applicant gains and how much time it costs them.
You state paid costs upfront.
You’ll publish fewer items rather than pad the list.
That is what lets a reader trust a link without checking it themselves, and it’s why a “3 good opportunities” edition can be worth more than a list of 8.
The “Friday, but no fixed hour” decision is good advice for anyone starting a series. Commit to the cadence, not the clock. Your note that nobody should burn out for consistency matters too. Missing zero Fridays in 25 weeks is great, but a series that survives a bad week is better than one that is perfect for two months and then disappears.
On views vs. impact: I think you’re right to look past views, and you hint at why. Your outcomes happen off-platform, when someone bookmarks a link or applies to a program. A few ideas, if you ever want some signal without spoiling the project:
Add a “Did you apply to something from this edition?” link or a short form to the website. Reader Updates then has an easy way in beyond the comments.
If the site has privacy-friendly analytics, track which listings get outbound clicks. That is closer to “did this reach someone” than article views are.
Add a per-listing “I applied” or “this helped” button. It’s small, and it gives you a quiet outcome count.
Questions for the AMA:
With 6 hours a week of research, have you found a system for tracking opportunities by deadline and by stage (found, verifying, ready)? I’m curious how you keep that from becoming a second job.
How do you handle opportunities that go stale or get cancelled after you’ve published them? Does the website fix that better than the articles can?
Now that you have the site and the domain, are you thinking about things like email or RSS alerts for new listings, or do you want to keep Friday as the one rhythm?
Which section of an edition do you think readers use most: Community Finds, the opportunities, or the learning resources?
Also, I like that you grew the project in response to its users, like Klaudia’s suggestion to push closed opportunities to the bottom. Those small changes show readers you’re paying attention, and that tends to bring in more contributions.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
Congratulations on hitting 25 editions of the Radar and launching your dedicated website!🎉 I joined DEV on May 20. Just checked — it turns out I liked the very first issue! What a lovely coincidence, hahaha.😁
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
AMA starts here 💙
Since this is the 25th edition, I thought it would be a nice opportunity to have a little conversation with all of you! Whether you have questions about writing, finding ideas, building a series, engaging with the community, staying consistent, or anything else about my journey with Dev Opportunity Radar, I'd be happy to chat.
I will be around in the comments throughout the day, and I'd love to hear about your own journey too.
If you've been writing on DEV for a while, I'd love to hear any lessons, tips, or advice you've picked up along the way. And if you're thinking about starting your own series, feel free to share your questions as well.
Let's make the comments a place where we can all share our experiences and learn from each other. Looking forward to chatting with you 😀
How can I bag a paid internship as junior dev from Nigeria.
Congratulations didi❤️🥰🙌🏻
Congrats @francistrdev sir too!❤️🔥
Good work 🥰
Julien Avezou (@javz)
Phinn Markson (@marsonp)
La Shara Cordero (@earlgreyhot1701d)
Konark Sharma (@konark_13)
Dhruv Jani (@dj29)
Boon (@hboon)
Thank you so much, Tara 😀❤️
Thank you, Star!!
Thanks Star!
@hemapriya_kanagala Di, its great!
Thanks for the mention and well I'm again in exam prep for SEM-7 starting next week. So, I'm kinda not into any other hacks since last 2 months due to hacktoberfest, diwali, exams and all so I stopped looking out for them.
BUT ...
HEY! Somebody started using GIFs, that's great!😄
It's totally fine, bhai! I can understand. All the best with your exam prep, and make sure to take care of yourself too 😀
about the GIFs, I'm actually not much of a GIF person, but I had a lot of fun adding them to this article! Francis (@francistrdev) had suggested using them a long time ago, so I had tried them in a few articles before stopping. I guess I found my GIF inspiration again for this article 😄
It does bring light into the articles since I do prefer seeing pictures time to time instead of just all text. Whatever works for you and thanks for the mention. Good work! :D
Thanks for suggesting it in the first place and for always supporting the Radar, Francis! I'll try to find more places to add them in future articles too 😀
Thanks Di,
And Have A Great Week!
You too, bhai! Have a great week 😀
25 editions is amazing! 🎉
I really think this is such a valuable initiative, and your consistency is seriously impressive. It’s not just a list of links either.
You’re actually helping people discover opportunities they might otherwise miss, so this definitely feels worth continuing. 💚
The website looks really stylish too! 😸
And I had no idea Cursor was looking for Ambassadors. That sounds interesting!
I honestly discover opportunities like that mostly through your Radar, which is one of the reasons I always enjoy checking it out. 🙌
Congrats again on #25!
Thank you so much for always supporting the Radar, nyaomaru! I actually mentioned you in the article too; I hope you got the notification! And I'm really happy to hear that you've discovered opportunities through the Radar. That's exactly what I hoped for when I started this 😀
I saw the shoutout! 😸💙
I was really happy to see my name there!!
I didn’t actually get a notification for it though. 😹
But thank you so much for mentioning me, and keep going with the Radar! I’m looking forward to seeing where it goes next. 🙌
Congratulations on version 25!🎉 And also on the further improvement of getting a .com domain! Rome wasn't built in a day. Good luck with future improvements too!
Hi Hemapriya,
I came across FR8 on Radar #2 and tried to apply on the same day itself.
Unfortunately they didn’t accept my application, but I would never have heard of the program if not for your list. I’ve also applied this month to the PayPal AI Hackathon.
Can you tell me how you determine whether African-based readers can apply to programs that have country limitations or on-site requirements?
Congratulations on a huge milestone, tbh devoppurtunity radar has been a revelation for me, it exposed me to oppurtunities I could only dream of thanks to Hemapriya, and I'm grateful for this. 🎉🎉🎉Cheers to the 25th Edition, next stop 50th and beyond.
Congratulations on 25 editions, Hemapriya, and on not missing a single Friday! 🎉 What stood out to me is how deliberately the Radar was built, more than the numbers themselves.
Leaving the Community Finds section empty in Edition #1 was a smart move. Most series add reader participation later, once they want engagement. You built the slot before anyone had used it, and it told readers you meant “our radar” before you said it. Reader Updates is the natural next step. It closes the loop on “what happened after you found something?”, which is the hardest part of curation to see. Daniel’s FR8 application and Anh’s OpenAI Build Week submission are the kind of evidence that numbers can’t give you.
Your curation criteria are the real product. Anyone can aggregate links, and a search engine can do that. What you add is judgment:
You check the official source for eligibility, fees, and deadlines before sharing.
You ask what the applicant gains and how much time it costs them.
You state paid costs upfront.
You’ll publish fewer items rather than pad the list.
That is what lets a reader trust a link without checking it themselves, and it’s why a “3 good opportunities” edition can be worth more than a list of 8.
The “Friday, but no fixed hour” decision is good advice for anyone starting a series. Commit to the cadence, not the clock. Your note that nobody should burn out for consistency matters too. Missing zero Fridays in 25 weeks is great, but a series that survives a bad week is better than one that is perfect for two months and then disappears.
On views vs. impact: I think you’re right to look past views, and you hint at why. Your outcomes happen off-platform, when someone bookmarks a link or applies to a program. A few ideas, if you ever want some signal without spoiling the project:
Add a “Did you apply to something from this edition?” link or a short form to the website. Reader Updates then has an easy way in beyond the comments.
If the site has privacy-friendly analytics, track which listings get outbound clicks. That is closer to “did this reach someone” than article views are.
Add a per-listing “I applied” or “this helped” button. It’s small, and it gives you a quiet outcome count.
Questions for the AMA:
With 6 hours a week of research, have you found a system for tracking opportunities by deadline and by stage (found, verifying, ready)? I’m curious how you keep that from becoming a second job.
How do you handle opportunities that go stale or get cancelled after you’ve published them? Does the website fix that better than the articles can?
Now that you have the site and the domain, are you thinking about things like email or RSS alerts for new listings, or do you want to keep Friday as the one rhythm?
Which section of an edition do you think readers use most: Community Finds, the opportunities, or the learning resources?
Also, I like that you grew the project in response to its users, like Klaudia’s suggestion to push closed opportunities to the bottom. Those small changes show readers you’re paying attention, and that tends to bring in more contributions.
Looking forward to #26, and #50! 💙
Congratulations on hitting 25 editions of the Radar and launching your dedicated website!🎉 I joined DEV on May 20. Just checked — it turns out I liked the very first issue! What a lovely coincidence, hahaha.😁
Great to see how far this series has come! And very glad to have been here since the very beginning!
Thank you so much, Julien, for always being so supportive! And thanks for the Gem too 😃