Student Clubs and Organizations for UofA CS Students¶
University is more than courses and GPA. The people you meet through clubs and extracurriculars are often your future colleagues, collaborators, and references. This guide covers the main clubs and organizations relevant to CS students — what they actually do, and why you might care.
The short pitch: join at least one thing. Show up consistently. Take on responsibility. The students who do this end up with a richer university experience and stronger networks than those who only attend class.
Computing Science Club (CSC)¶
The primary student society for CS students at UofA. If you only join one thing, this is the one.
What it does: - Maintains and manages the CS student lounge (the ATH space) — a place to work, hang out, and meet other CS students between classes - Organizes social events: game nights, study sessions, end-of-term events - Runs industry panels and networking events with companies hiring CS graduates - Provides a space for students to connect informally — this is underrated
Why you should join: The CS lounge is genuinely one of the best places to build your undergraduate social network. The students who use it regularly tend to know each other, share opportunities (job postings, hackathon teams, side projects), and form study groups that persist for years. You don't have to be extroverted to benefit — just show up.
If you're interested in organizing, there are executive roles (president, VP events, VP finance, etc.) that offer real leadership experience. Running events for 50–200 people teaches logistics, sponsorship, communication, and project management — skills that most CS courses don't touch.
How to get involved: Show up. Check the CSC's Discord or social media for event announcements. Elections for executive positions happen annually — usually in the winter semester.
HackED — UofA's Annual Hackathon¶
HackED is UofA's student-organized hackathon, typically drawing 200+ participants over a weekend each January. It's one of the larger student-organized technical events in Alberta.
As a participant: A hackathon is 24–36 hours to build something from scratch with a team of 2–4. Sponsors provide prizes, API credits, and sometimes hardware. You'll work under time pressure, ship something imperfect, present it, and likely learn more in one weekend than in several weeks of coursework.
Even if you don't win, hackathons accelerate your development. You'll learn how to scope a project under constraints, debug under pressure, and present a technical project to non-technical judges. These are all real skills.
Beginners are welcome. Many participants are first-year students who barely know how to code yet. That's fine — you'll figure it out.
As an organizer: The team behind HackED runs logistics (venue, catering, AV, registration), sponsorship outreach (writing cold emails to companies for cash and prizes), marketing, and day-of operations. If you join the organizing team, you're doing real project management work — and the companies you approach for sponsorship are often the same companies you'll apply to for jobs. Organizers regularly get referrals and connections through this work.
MLH Events: UofA teams also participate in Major League Hacking (MLH) events — a global hackathon circuit with events every weekend. Check mlh.io for the schedule. These are great for getting experience at larger events with more competitive fields.
How to get involved: Watch for HackED's social media in the fall semester for participant registration and organizer applications.
Competitive Programming Club¶
For students who want to get seriously good at algorithms and problem-solving — both for its own sake and as interview prep.
What it does: - Weekly or biweekly practice sessions working through competitive programming problems (Codeforces, LeetCode hard, ICPC-style problems) - Practice contests replicating real competition formats - Selects and prepares the UofA team for ICPC (International Collegiate Programming Contest) — the most prestigious collegiate programming competition in the world, with regional qualifiers and a world finals
Why this matters for industry: Technical interviews at major tech companies (Google, Meta, Amazon, Microsoft, and many others) are based on algorithm and data structure problems. Students who practice competitive programming consistently are significantly more prepared for these interviews than students who cram LeetCode the month before an interview. The habits built over a year of practice are far more valuable than a last-minute sprint.
Beyond interviews, the mathematical thinking and problem decomposition skills from competitive programming make you a better engineer. These problems train you to reason about complexity, edge cases, and correctness in ways that typical coursework doesn't.
Do I need experience to join? No. Beginners are welcome and most clubs have problem sets at multiple difficulty levels. If you've finished CMPUT 204 (algorithms), you have enough background to start. Earlier is fine too.
How to get involved: Check the CS department event boards and Discord for meeting times. Codeforces (codeforces.com) is free — you can start practicing immediately.
AI/ML Club¶
As machine learning becomes increasingly central to software development, the AI/ML club has grown in relevance and membership.
What it does: - Paper reading circles — working through recent ML papers together (transformers, diffusion models, RL papers, etc.) - Study groups for foundational ML concepts: backprop, optimization, probability theory, model architectures - Project collaboration: teams working on ML applications, Kaggle competitions, research replications - Guest speakers from Amii researchers and industry ML engineers
Why join: ML is a field where self-study is necessary but having a structured community accelerates it dramatically. Reading papers with others forces you to actually understand them rather than skim. Working on projects with a team exposes you to different approaches and builds your portfolio.
The connections to Amii through this club also mean occasional access to events, speakers, and introductions that you wouldn't get otherwise.
How to get involved: Watch for the club's Discord or social media. The fall semester typically has an introductory meeting where new members can get oriented.
Cybersecurity Club / CTF Team¶
If you're interested in security — and you probably should be, since it's one of the highest-demand areas in tech — this is the entry point.
What it does: Plays Capture The Flag (CTF) competitions. CTFs are security challenges in jeopardy-style format: you're given a vulnerable system, a piece of encrypted data, a binary, or a web application, and your job is to find and exploit the vulnerability to retrieve a hidden "flag."
Categories typically include: - Web security: SQL injection, XSS, SSRF, authentication bypasses - Cryptography: breaking weak encryption, RSA challenges, hash collisions - Reverse engineering: analyzing compiled binaries to understand what they do - Binary exploitation: buffer overflows, format string attacks, ROP chains - Forensics: analyzing disk images, network captures, steganography
Why this is valuable: Security skills are increasingly expected of all engineers, not just dedicated security professionals. Understanding how attacks work fundamentally changes how you write code — you write more defensively, you understand what authentication and authorization actually protect, and you don't make the classic mistakes that lead to breaches.
From a career standpoint: security engineers are extremely well-compensated and consistently in high demand. CTF performance is a legitimate resume credential that security-focused companies explicitly look for.
No prior knowledge needed. CTFs are designed as learning experiences. You'll look up writeups after competitions, learn from other teams, and build skills incrementally. Most participants start knowing almost nothing about security specifically.
How to get involved: Look for the club's Discord. PicoCTF (picoctf.org) is a beginner-friendly platform to start on your own before your first competition.
Game Development Club¶
Game dev is one of the most interdisciplinary areas of CS — it touches graphics programming, physics simulation, AI, audio engineering, UI design, and systems programming.
What it does: - Participates in game jams: 48–72 hour events where teams make a game from scratch with a given theme (Global Game Jam, Ludum Dare, etc.) - Longer-form collaborative game projects - Workshops on tools and techniques (Unity, Godot, Unreal Engine, Blender, etc.)
Why join even if you don't want to work in games: Game development teaches a kind of systems integration that few other projects require. A working game needs a renderer, a game loop, input handling, audio, UI, and game logic to all work together. Building even a simple game gives you real experience with software architecture at a scale that most side projects don't reach.
Game jams specifically are excellent for portfolio pieces — you'll have a complete, playable artifact at the end of a weekend.
Relevant courses: CMPUT 250 (computers and games), CMPUT 350 (advanced game programming), CMPUT 411 (3D graphics).
How to get involved: itch.io and Global Game Jam have jam calendars. Find the club through the CS department or Discord.
Why Joining Clubs Actually Matters¶
Let's be direct about this. Beyond the skills and resume lines, clubs are how you build real relationships with other CS students — and those relationships often matter more than anything else.
Your classmates are your future colleagues and references. The people you study with, build things with, and compete with in clubs are the people who will refer you for jobs, co-found companies with you, and write strong references because they've actually watched you work. A professor who vaguely knows you from a large lecture cannot write the same kind of letter as a club exec who worked alongside you to organize an event for 200 people.
Clubs teach what courses don't. Running a sponsorship campaign, organizing a multi-day event, managing a team with no formal authority, presenting to industry partners — these are not skills courses explicitly teach, but they're skills that hiring managers notice immediately.
Leadership compounds. A first year who joins a club, takes on a small role, and works up to an exec position by third year has three years of compounding experience and relationships. A fourth year who joins the semester before graduation has neither. Start early.
It's also just more fun. Four years of only attending class and grinding assignments is a bleak way to spend your undergrad. The people who look back most positively on university are almost always people who built community through something outside the classroom.
Pick one or two things that genuinely interest you. Show up consistently. Volunteer for things. The rest follows.