Build a Discord Bot People Actually Use
Maps to: Software Engineer · Community Manager · DevOps Engineer · Founder
You're going to build a bot, a little program that sits in a Discord group chat and answers people, and it will do one useful thing: help your class study, swap units in a hobby chat, check the mood in your friend group. You'll get it replying fast, plug in an AI so it can understand questions, then decide what it should refuse to answer. The payoff is that it keeps running on its own and real people start counting on it. That is what software engineers actually make: something that works without anyone watching it.
You're done when: Your bot is running in a real group chat doing one useful thing with AI, with short instructions so people know how to use it, and you decided and set the rules for what it will not do. The judgment is the work: not 'it ran once,' but 'real people use it, and I chose its limits on purpose.'
How this shows up on a resume or college app
I built a Discord bot that runs on its own in a group of N people, wiring an AI into a real use case and deciding the rules for what it should refuse to do. I learned how to make a tool that real people depend on, and that deciding what a tool should NOT do is half the job.
When you finish, BuildMe drafts your Common App activity description from what you actually built.
Not sure yet? Play 5 minutes as a software engineer first and see how the work feels.
The plan
- 1
Step 1
Decide the bot's one job, and get it to say hi
Pick what your bot does in one line and whose group chat it's for. Then, before any big setup, get the empty bot answering ONE command (one word you type at it) in a test chat of your own. (Yes, you grab a token, a secret password that lets your bot log in, but that's a two-minute step on the way to the magic moment.) Seeing it reply 'hey!' is what gets you.
- 2
Step 2
Make it do the real thing
Turn 'it replies' into 'it's useful.' Build the one real command your bot exists for: change the units, look up the study word, save the mood. Keep it to the one job.
- 3
Step 3
Give it a brain, and decide what it should NOT do
Plug an AI into your bot so it can understand a question and answer it. Then do the part that matters: find where it answers badly, weirdly or unsafely, and decide what it should refuse to do. Giving your bot limits is half of making it safe to trust.
- 4
Step 4
Put it in a real chat and write the instructions
Put your bot in a real group chat, write a short 'here's what it does' for the people in it, and watch how they use it. Free, no card needed: run it on Replit while you're at your computer (free Replit switches your bot off when you stop, so it's on when you are). Want it on day and night? Fly.io is free too but asks for a card when you sign up, so that's the step up, not the starting point. Then write down how real people react.
Tools you'll use
Real examples for inspiration
Resources
See what people have done.
Finished work from people exploring Software Engineer.