r/OMSCS • • Nov 01 '24

I GOT OUT Took me awhile, but here's after 5 years in OMSA + OMSCS.

Post image
796 Upvotes

r/OMSCS • • Jul 14 '26

Graduation Georgia Tech OMSCS saved my life

723 Upvotes

I graduated with my bachelors in CS from a T30 school in 2024. I only had 1 internship during my undergrad and it was a startup that failed anyway.

After graduation, I could not find a job anywhere in the field. I ended up working as a hotel clerk for 2 years. This was the most depressing point in my life. I felt like a failure and a waste of my parents’ money. I was a waste of everyone’s effort in my life. I was not good enough.

In 2025, I saw a LinkedIn post about OMSCS. I don’t know why but I decided to apply. I started to do courses while working as a hotel clerk.

One year later I am currently interning at Amazon in Seattle as a software development engineer and nearing close of my term. My manager has repeatedly told me that he’s impressed with my work and will be approving the RO for full time. Even if this opportunity falls out, I know I can make it as a SWE and I have my passion again to be someone.

If anyone else was in similar shoes or is currently thinking about applying, I highly recommend it. It pulled me out of a dark place. Thank you Georgia Tech.


r/OMSCS • • Feb 20 '25

I GOT OUT Look How Big The Degree Is 🎓

Post image
694 Upvotes

r/OMSCS • • Dec 14 '24

I GOT OUT Walking today and got to meet the man himself

Post image
589 Upvotes

Thanked him for all his support and work he has done for the program. Good luck to all of those still in it and congrats to my fellow brethren who also walked today.


r/OMSCS • • Jun 12 '25 This

Dr. Joyner Says I don't know who needs to know this, but: they removed Program from transcripts.

583 Upvotes

There were a couple posts (this one and this one) a few weeks ago asking why "Program: MS in Computer Science, Online" appears on transcripts.

I've been waiting for someone to post a follow-up, but since no one has, and since a lot of people use Reddit when exploring the program, I wanted to put it out there publicly somewhere: the program no longer appears on transcripts. The office that handles that shared that it was added because they were getting lots of requests (mostly from undergraduate students) to verify what program they were in, so they added it to the transcript so that people the verification would be automatic when students got a transcript. But then when we shared how that change was getting interpreted by online students, they were amazing and reverted it. So, program (which includes the word 'Online') no longer appears on transcripts.

In a lot of ways, this is sort of emblematic of something I said about another program a few months ago. I said at the time:

I don't think it's always apparent to everyone in these programs just how big and complex universities are. There are departments at Georgia Tech that can make seemingly insignificant decisions based on relatively short meetings that have massive impacts on our students.

This was totally an example of that: including Program on transcripts seems like a really minor change until you get into some of the wrinkles of how online programs can be perceived, and especially how other universities deliberately designate Online degrees as different from their traditional degrees. It's honestly a massive credit to how much the university does value your opinions that they switched back.

Anyway. I'm mostly posting this since some people use reddit to research the program, so I wanted to make sure there's a public post emphasizing that the previous posts are no longer true. I was hoping that someone else would post this anyway, but since no one has... hi.

(And while we're on the topic of "things I was hoping someone would have posted by now", I'm still waiting on someone to point out that Charles was just appointed as the Chancellor of UIUC. That's huge.)


r/OMSCS • • Aug 08 '25

Graduation Finally done with my OMS trilogy

Post image
564 Upvotes

Time for taking some break.


r/OMSCS • • May 07 '21

I GOT OUT Believe in yourself!

Post image
525 Upvotes

r/OMSCS • • Apr 15 '21

Admissions Preparing Yourself for OMSCS

488 Upvotes

Hey everyone!

I'm posting this here because this is really targeted at prospective students, and... well, this is the only place I know of where y'all get together.

One of the most common questions we get in OMSCS is, "How can I get in?", "What should I do to prepare?", etc. It's always hard to answer these questions because (a) aside from the preferred requirements, we can't offer any general guarantees or endorse specific other schools' programs, and (b) a lot of it really does come down to your individual background.

That said, we've recently launched MOOC versions of three of our own CS courses, covering the fundamentals of programming, object-oriented programming, data structures, and algorithms. These were designed in part specifically with future OMSCS students in mind.

In order to summarize those, as well as provide some other very high-level feedback on how else you can prepare for the program (both prepare to apply and prepare to succeed), we've created a new web site page: http://omscs.gatech.edu/preparing-yourself-omscs

So, if you're preparing to apply in summer and wondering what you should do to strengthen your application, or if you're preparing to start in Fall and wondering what to do to increase your preparedness, that information is for you!


r/OMSCS • • Aug 10 '25 Popcorn

I Got Out! My OMSCS Exit Post! From middle school science teacher -> AI Engineer in 2 years.

483 Upvotes

Just finished Georgia Tech OMSCS in 2 years – Full Exit Review

I started coding at age 37 with basic Arduino, switched careers from teaching science/STEAM in California, and moved to rural Japan to study full-time. Two years later, I’ve finished OMSCS with the Machine Learning specialization, landed an internship in Tokyo, and am now a full-time AI engineer for braking systems in Japan.

Below is my full program review – including my background, application experience, networking story, and detailed reviews of every class I took (with hours/week, grades, and tips). Hopefully this helps anyone considering OMSCS or planning their course path.

My Story

I graduated with a B.S. in Mechanical Engineering from a well-known American university that’s not Ivy League in 2003. After graduating, I worked for a few years as a plumbing engineer, which I found boring. I then spent some time exploring other life directions before eventually moving into teaching.

For 13 years, I worked as a science, math, and technology teacher at private schools in California. About halfway through that period, I taught myself Arduino, which led to some small electronics contract work for artists. It wasn’t a huge part of my career, but it was my first real introduction to coding—at around age 37—and even then it was just basic Arduino programming.

Over my last three years of teaching, I transitioned into a STEAM (Science, Technology, Engineering, Arts, and Mathematics) role for middle school science. I tried to incorporate as much Python teaching as I could, but the challenges and limitations of teaching made me realize it wasn’t sustainable as a long-term career. I began planning my exit strategy—taking on as much Python tutoring as I could to build skills and income for a transition.

By October 2022, I committed fully to switching into the tech field. At that time, I planned to self-study or possibly take individual courses. My wife’s family owned an unused countryside home near where they lived, so we sold both our cars, got rid of most of our belongings, and moved there. Since we were renting, didn’t own a house, and didn’t have kids, we decided to take advantage of the freedom to make such a big change. I arranged remote Python tutoring for about seven hours a week so I could focus on learning full-time.

I only learned about Georgia Tech’s OMSCS program after we had already decided to move. Once I found out about it, I applied and decided to make it my full-time focus.

Applying

I applied to three online master’s programs:

  • The new Machine Learning/AI program at UT Austin

  • The MCS program at the University of Illinois Urbana–Champaign (UIUC)

  • Georgia Tech’s OMSCS

At the time, my Python skills were intermediate from self-study, including some of a popular Udemy course. I didn’t know algorithms and considered myself between beginner and intermediate in programming. For the UIUC application, I took a short online algorithms course but failed it; I still applied using that experience.

For Georgia Tech, I reached out to my undergraduate advisor from 20 years earlier. We had stayed loosely in touch, and he remembered me well enough to write a glowing recommendation letter, which I believe made a big difference. In my application, I emphasized my project experience.

Results: Admitted to Georgia Tech, rejected by both UT Austin and UIUC.

Preparing

After being accepted, I bought a new MacBook M2, which worked flawlessly throughout OMSCS. There were just a few cases in DL where I needed to use Google Colab instead of my mac, but it wasn't a problem.

Before moving to Japan, I joined the OMSCS community on Reddit and posted about my upcoming move. A student living Tokyo (shout out to Christian) in connected me to a Line chat group (Japan’s popular communication tool) with a dozen or so active OMSCS students in the Tokyo area who meet up a couple times a year. I had a video chat with that same student who was close to finishing, which was helpful. Even though I lived far from Tokyo, I stayed connected by occasionally posting in the group and hoped to meet them in person.

I chose the Machine Learning specialization and made sure to join the (gaming-based chat website) server for each course. Connecting with active (gaming-based chat website) communities and engaging with classmates was one of the best things I did.

Tokyo OMSCS Meetup and Internship

In August 2024, before the Fall semester began, I visited Tokyo for the first time since moving to Japan and attended an in-person Georgia Tech Tokyo OMSCS Meetup from that same Line group. Meeting classmates face-to-face strengthened those connections.

Around this time, I began applying to internships in Tokyo and was pleasantly surprised by the positive response. The U.S. job market was tough, but Tokyo’s was much more reasonable. Employers recognized Georgia Tech, and my résumé stood out—especially my Kalman Catcher project from CS 7638 and my research work from CS 8903. These drew strong interest in interviews.

A key advantage was that I was in Japan on a spousal visa, meaning I didn’t need sponsorship—a big plus for employers. After nearly landing one role but being rejected after the third interview, I mentioned it in the Tokyo OMSCS group. A fellow student (should out to Rikiya) suggested checking his company’s job board, where I found a newly posted AI/data processing internship starting within a month. The role was meant for overseas interns, but their visas would take 3–4 months to process—giving me a huge advantage. It fit my skill set perfectly.

That classmate personally handed my résumé to the hiring team. I had an interview within days, and the hiring manager told me I was their only serious candidate because of my immediate availability. I was offered the position and we moved to Tokyo near the end of Fall semester 2024. The hope was to get hired or find another job after.

This reinforced the importance of networking and staying active in OMSCS communities. It also validated my decision to take a lighter Fall load (CS 7650 and CS 6603) so I could finish most coursework before moving.

As another stroke of luck, the engineer I was working under in my internship decided to quit 2 months before the end of my internship, so they offered me a full-time job. Now, I work at a international company designing AI tools to assist auto braking engineering in their research and development. It's awesome.

Finishing the Program

I completed the program in two years, balancing part-time work, full-time study, and eventually my internship and job in Tokyo.

Course Reviews

(All hours/week are averages; all grades are final course grades.)

CS 7637 – Knowledge-Based Artificial Intelligence

I took KBAI because it was highly recommended as a first course. The coding challenges were the highlight—great practice, interesting, and appropriately challenging for my skill level. The semester project involved using computer vision to solve visual analogy problems, which was both very cool and a strong coding exercise.

The lectures were only loosely related to the activities and didn’t particularly interest me, but the hands-on work kept me engaged. We were allowed to collaborate, and I came up with a simple yet effective approach for the project that I shared with the class, receiving a lot of recognition from classmates.

At the end of the course, I was voted by peers for a special Thanksgiving “student who helped you most” prize, which also came with a recommendation to become a TA. I declined the TA role, but the TA who awarded the prize instead wrote me a recommendation letter that helped me get into CS 8903 the following semester.

I think it’s a good first course because it acclimates you to the program, but I wouldn’t necessarily recommend it if it’s not your first. It also had a very strong (gaming-based chat website) community where I connected with people I still keep in touch with.

Final grade: A
Hours per week: ~15–17

CS 7638 – Artificial Intelligence Techniques for Robotics

I took this along with KBAI in my first semester. Although it’s generally recommended to start with just one course, I was only working part-time and had the flexibility to take two.

This was an excellent first class, and I recommend it to everyone starting the program. The material was interesting, the coding challenges were engaging, and the lessons connected directly to the assignments and projects—everything was academically aligned, which is not true for all classes. The projects were fun and, because they were robotics-related, included cool simulations where you could see your code in action.

The (gaming-based chat website) community was active and helpful. Before each project, I would read through the project’s chat history to see recommendations and insights from other students. Some worked far ahead, which meant you could sometimes get helpful hints before starting a project.

There was also an optional hardware challenge for extra credit that could bump your grade up a letter if you were on the edge. Since I had Arduino experience, I knew I could complete it with a minimal project if needed, but I chose to go further. One of the algorithms we learned in the course was the Kalman filter, which I incorporated into a Raspberry Pi computer vision project that could catch ping-pong balls. This “Kalman Catcher” project took a lot of time but was valuable experience for my résumé. I submitted it to the end-of-semester showcase and won the Audience Choice Award.

You can watch the project here: Kalman Catcher – YouTube

Final grade: A
Hours per week: ~15–17

CS 8903 – Special Topics: Computer Vision Research

At the end of the previous semester, an email went out announcing that students could apply for a small number of Special Topics research opportunities that count as regular electives. Around ten projects were listed, and selection was competitive. I had recently earned a recognition award in KBAI, and the TA who gave me the award wrote me a strong letter of recommendation, which helped my application.

This project, led by a PhD student, focused on using deep learning to classify actions and objects from first-person perspective videos. At the time, I had very little deep learning experience beyond a few experiments in Google Colab, had never used a GPU cluster, had barely read research papers, and had no prior research experience. Still, I put in significant effort to learn about the topic, wrote a strong application, and was selected—getting official confirmation just a few days before the start of the semester. I dropped another class to take this and enrolled in Deep Learning (CS 7643) at the same time.

It was 100% the right decision, and I highly recommend trying hard to get into one of these research opportunities. The work was difficult, but it gave me valuable experience working under a PhD student, collaborating closely with another PhD candidate, and using Georgia Tech’s Skynet GPU cluster. I also did extensive literature review and read many research papers. Most importantly, I had the chance to work with real, contemporary deep learning computer vision code—something that’s rare in OMSCS courses.

Before this project, I assumed machine learning work was mostly about model architectures, but I learned that a large part is actually building training pipelines, managing experiments, and handling data. By examining real-world code, I gained practical knowledge of how model training systems are structured, which I still apply in my work today.

It was extremely challenging—there were moments when I felt completely defeated—but we completed the project. After the semester ended, the PhD students finalized the paper and submitted it to the ICASSP 2025 conference, showcasing advancements in action recognition and anticipation tasks. The paper was accepted and is available here: arXiv:2409.11513.

This became a strong résumé item and, when formatted appropriately, effectively reads like a Georgia Tech research internship.

Final grade: A
Hours per week: ~15–17

CS 7643 – Deep Learning

This class is really hard, but the concepts I learned are directly useful in my job today. It starts off by trying to scare you off with math: an ungraded assignment full of complex equations that can be overwhelming. I think this is intentional—it prompts those likely to drop to do so early, before instructors have to grade their first projects.

If you’re in the Machine Learning specialization, I highly recommend taking this course. The lectures are solid, but many students (myself included) also recommend supplementing them with the University of Michigan’s deep learning lectures, which do a great job of explaining concepts. I found it best to watch both.

The projects and assignments are difficult but very educational. After the initial math section, you work on implementing neural networks by hand, including gradient descent calculations. This is probably the only time in OMSCS you truly need calculus, and even then it’s basic derivatives you’d learn in first-semester calculus. Probability is also important—mine was rusty, so I reviewed with help from a friend who’s a physics professor and watched videos from the YouTube channel 3Blue1Brown, which I highly recommend. If you’ve studied calculus, linear algebra, and probability/statistics before, a targeted review is enough; if you haven’t learned them at all, you should take a proper course first. In my experience, linear algebra is more important for this class than calculus.

Quizzes are a major challenge in this class. There are five total:

  • For Quizzes 1 and 2, I studied about seven hours each, scored almost 100%, and felt well-prepared.

  • For Quiz 3, I studied the same amount but only scored around a C.

  • For Quizzes 4 and 5, even with the same level of preparation, I ended up with low grades (around D range).

Because of this, I highly recommend studying as hard as possible for the first two quizzes to lock in points and be mentally prepared to struggle on the last three.

There’s a team project at the end, which often serves as a grade curve. As long as you put in reasonable effort, it can bring your grade up. Group quality varies, so aim to find at least one other member who works hard. Take initiative: post an intro, ask interested classmates to share something about themselves, and choose carefully instead of accepting the first responders. Once in a group, keep momentum by setting meetings and proposing ideas. If possible, choose a project topic that could be eligible for the OMS showcase, and apply—you never know, it could be another strong résumé item.

We also did literature reviews during the course, which I found valuable for learning how to read and summarize research papers.

Final grade: A
Hours per week: ~18

CS 7641 – Machine Learning

I took this in Summer 2024 when my part-time tutoring work was minimal, so I could focus on the class full-time. Because of that, I can’t fully comment on how manageable it would be alongside a full-time job, but I can imagine it being challenging.

This class was excellent. Up to this point, all my previous classes prohibited the use of large language models, but here they were allowed—and I highly recommend taking advantage of that. I used my Georgia Tech student status to get GitHub Copilot for free (apply early; approval can take a couple weeks) and subscribed to a popular LLM service. Both made a huge difference, letting me focus on what needed to be done rather than how to code it.

The course focuses on classical machine learning—supervised and unsupervised techniques that don’t require GPUs—rather than deep learning. This is a huge benefit because the models train quickly and you can focus on understanding the data pipeline, training, evaluation, and concepts like cross-validation and data leakage. I used scikit-learn for almost everything in this class, and I still use it extensively in my work today.

One of the most valuable skills I learned here was building reusable, modular code for experiments and tracking exactly how and where data is processed and normalized. This understanding of pipelines and validation has been one of the most useful takeaways from the entire program.

The class covers around five different classical ML algorithms, both supervised and unsupervised. While you’re meant to learn to choose the right model based on the dataset, I can’t say I walked away with strong intuition there—but I did gain a solid grasp of clustering (e.g., k-means), classification, regression, and how to evaluate them. I supplemented the course lectures with the YouTube channel StatQuest, which I found extremely helpful for getting a high-level understanding of the algorithms.

There’s a lot of writing in this class—project reports can be lengthy, and the rubrics aren’t always as clear as they could be. The (gaming-based chat website) community was invaluable here; I connected with someone who had taken the course before and created a project template outlining the recommended sections and structure, which saved a lot of time. The projects also reinforced concepts like generating validation plots and interpreting clustering metrics.

This is a required course, and I understand why—it teaches you, very directly, how machine learning is actually done in practice. Even if you’re not in the Machine Learning specialization, I think it’s worth taking if you want a strong foundation in the field.

Final grade: A
Hours per week: ~17–20

CS 7650 – Natural Language Processing

This is a great course—new, highly sought after, and often hard to get into. Most people will tell you that you can’t get into it until near the end of the program, but there’s a trick worth knowing: Free-for-All Friday. On the Friday of the first week of classes, the waitlist is cleared starting at 8 or 9 AM (Eastern Time). If you try to register right after someone drops, you can grab a spot.

When I was in Japan, this meant beginning the process at 11 PM my time and staying up late, repeatedly checking and clicking. I was allowed to take an extra class that semester, so I petitioned for the overload, which let me hold multiple classes while trying to grab others. Using this method, I got into all three courses I was targeting—Graduate Algorithms, AI Ethics and Society, and NLP—but ultimately dropped GA and kept NLP and AI Ethics.

If you’re planning to take both Deep Learning and NLP, I recommend taking NLP first—it’s like “Deep Learning light” and serves as a good introduction to concepts you’ll see later in Deep Learning.

The lectures for NLP were solid and I learned a lot. This was my easiest semester by far, which gave me time to explore side projects. I used the extra bandwidth to teach myself how to make large language model agents with LangChain, culminating in a hackathon project that was shared by LangChain on LinkedIn and written up in an article. If you take NLP, I recommend using the extra time to experiment with LLMs and agent frameworks, as they may be very relevant in the future.

Final grade: A
Hours per week: ~10

CS 6603 – AI, Ethics, and Society

By this point in the program, I had been working pretty hard and wanted a lighter elective. I was also being considered for a job in Tokyo, so I needed something that wouldn’t overwhelm me if I had to move mid-semester and start working full-time. I chose this class over Reinforcement Learning because RL has a reputation for being extremely challenging and time-intensive, and I didn’t want to take on that level of workload in my situation.

In the end, this class ended up being the opposite—while RL might have been overwhelming, AI Ethics and Society was underwhelming. It was much easier than my other courses, and I mostly took it for the credit. I didn’t learn much from the material itself, but the lighter workload gave me time to work on side projects, including learning how to make language model agents—a skill that ended up being far more valuable to me.

Final grade: A
Hours per week: ~10

CS 6515 – Graduate Algorithms

I used Free-for-All Friday again to get into this course so I wouldn’t have to take it last. That’s some of the best advice I can give—do the same. Avoid taking this class last by using Free-for-All Friday.

One particular note for the Machine Learning specialization: you must get a B in this class. If you get a C and it’s your last course, you’re stuck retaking it. I planned my courses so that if I got a C here, I could switch to the Interactive Intelligence specialization (now called the AI specialization), which lets you take SDP instead of GA. In that case, GA could still count as an elective, and I could graduate without retaking it. This was my safety net.

I knew it would be hard, and this was actually the first class I took while working full-time, so I only took this one course that semester.

Preparation advice: About 2–4 weeks before the semester starts, I’d recommend focusing on the first two chapters—Dynamic Programming and Divide and Conquer. Get the textbook early, read those chapters, and watch the corresponding Georgia Tech videos (which you can find online). Even just asking LLM to explain those algorithms can help. Most of the later material is too hard to really pre-learn without the structure of the course, so I wouldn’t go much further than that.

I had never taken an algorithms course before, other than a short failed attempt at a mini one before applying to OMSCS, so this was all new to me. I’m also terrible at LeetCode. People say you need a lot of math for this class—I disagree. The only notable math-like section is near the end when you do linear programming, which is just some high school–level 2D graphing. There’s an optional summer seminar called The Language of Proof, but people I spoke with said it wasn’t necessary.

Study groups and tools: I joined two study groups—one in my Tokyo time zone and one on U.S. Eastern time—to maximize connections. I took the initiative to set up collaborative whiteboards in Zoom (via its “Project” feature), where we could save and revisit all work. Before each study session, I’d prepare by collecting and organizing screenshots of practice problems into a single whiteboard so we could hit the ground running.

Having an iPad and Apple Pencil was a huge advantage for this class. You’re constantly drawing diagrams and walking through algorithms by hand, and being able to write cleanly and quickly helped us move faster compared to everyone else using a mouse.

Homework and exams: The class recommends doing all the homework, and I agree. They’re now ungraded, so there’s no issue collaborating freely. I spent a lot of time on them, and they paid off for the tests.

One of the TAs, JOVES, gave what seemed like overly simple advice at first: essentially, “just put more time in.” It turned out to be true. This class was super hard for me, and throughout each exam cycle, I often felt like everyone else understood the material better than I did. But by relentlessly throwing more time at it—canceling plans, using vacation days, and grinding through the material—I pulled through. My success wasn’t because I was naturally gifted at algorithms; it was because I stubbornly kept working at it.

For each exam, I’d take 1–2 vacation days from work right before test week to dedicate to studying. That last stretch before the exam is when everything clicks, because you finally have a focused study guide from your group sessions.

Here’s another piece of obvious-sounding but actually very practical advice: whatever amount of time you plan to study for Test 1, study about 20–30% more than that. Do the same for Test 2. By then, you’ll know your personal range for how much time is worth putting in. The final exam is optional, and I skipped it because I was mathematically locked into a B regardless—so knowing your range early can help you make that kind of decision later.

I met with my study groups 1–2 times a week for 2.5 hours each, which was about 7–10 hours per week just in group time. On top of that, I studied heavily the weekend before each exam—around 10–17 hours—sometimes more.

Exam experience:

  • Exam 1: Studied a lot, did OK—slightly better than most in my group. Many of my group members had failed the class before and were stressed, while I had my “specialization swap” safety net.

  • Exam 2: Treated it like a must-pass moment. Took two days off work, studied ~17 hours in three days, and nearly aced it.

  • Exam 3: Very hard, but I pushed through and finished with a B overall.

This is the only class in OMSCS where I truly felt bonded with my teammates. I even met up with some in person when visiting the U.S. afterward, and I still keep in touch with one of them.

Final thoughts: If this class is required for your specialization, I understand why—it really does teach you the fundamentals. Just know the grading is harsh. My biggest recommendation: don’t take it last if you can avoid it, and be prepared to throw time at it until it sticks.

Final grade: B
Hours per week: ~17–20

CS 6457 – Video Game Design

This was my last semester, and since I’d finished Graduate Algorithms and all my requirements, I could take anything I wanted. I chose Video Game Design, and I highly recommend it if you want a creative, project-based course.

I had already learned a little Unity before the class—just part of a simple 2D tutorial—but this course was all 3D. I came in excited to learn Unity, thinking I might keep it as a hobby after graduation. I like video games, and it seemed cool to be able to make them.

The course structure was solid. There are several assignments that are essentially tutorials, and they’re very well-designed with good scaffolding. The lectures are long and wordy—watch them at 2× speed, and they’ll still feel slow. The assignments, however, are excellent practice for Unity fundamentals.

Unity itself is hard. For me, it felt like 1% creative ideas and 99% technical problem-solving just to make those ideas work.

The main draw of the course is the big team project. I initially connected with my team, pitched a game idea using a PowerPoint presentation, and got everyone on board. I also found some great AI tools for game design that aren’t well-known—like Meshy.ai, which we used to create custom characters.

I put in a huge amount of work—ridiculous amounts, really. One teammate matched my commitment, but the other three just did the minimum. That made it hard for me to do my part, and I ended up crossing the line and doing pieces of someone else’s job so I could move forward. This caused some friction with the team.

By the last third of the semester, I realized they weren’t going to change, so I pulled back and just matched their minimal effort. It would have been much better to take this course with teammates I already knew and trusted. I deliberately picked Pacific Coast–time teammates to maintain some U.S. connection, but in hindsight, I should have partnered with someone I’d met before, even if the time zone was different. Time zones are tricky, but so is team motivation.

For me personally, I left the class deciding I didn’t want to work in Unity anymore—it’s just too frustrating to constantly be stuck on technical issues. That’s a personal takeaway, not a complaint about the course.

Final grade: A
Hours per week: ~15
Recommendation: If you can, take it with teammates you know.

MGT 6311 – Digital Marketing

I took this in Summer 2025, my last semester. I could take any elective, so I sorted a popular OMSCS course review site by lowest reported hours/week and found this one. I’m not particularly interested in topics like advertising on Facebook, which this course covered, but it was fine—it was mostly just a credit I needed.

It took about 5 hours/week. Assignments were easy, but you do have to study for the tests—there’s a misconception that you don’t. I’ve seen people complain about that, but if you put in time you’ll be fine. The good news is that there are Quizlet flashcard sets made exactly for this class, and by studying those I was able to do well without spending more time than necessary.

Final grade: A
Hours per week: ~5

If you've read this far, thanks for your interest. I’d be happy to answer any questions here and best of luck to those just beginning their journey!

So how am I celebrating my free time? I’m making AI videos! https://youtube.com/@ghostpopsicleai?si=GV_4w5aJN2bIg6XI


r/OMSCS • • Aug 30 '24

This is a Meme Whenever I see a Question about Tech Jobs in this Community...

Post image
430 Upvotes

r/OMSCS • • Oct 05 '26

Social Got a 170k job from being in OMSCS! Keep going guys!

410 Upvotes

saw a similar post but also wanted to make it known that this program IS WORTH IT. After not even finishing my first semester last year I got an internship (with no referral surprisingly) at a big tech company and interned there this past summer, and got a return offer for 170k in technical support engineering. I did not from a top 20 undergrad school or anything like that and i had 3 internships from non Faang companies prior but no full time working experience. This was also this was my first paid internship since 2021. Safe to say it’s been a long journey to get here and thankful i took the leap to do this program. To whoever is reading this, keep pushing and someone will notice, trust the process


r/OMSCS • • Dec 29 '24

Meme Everybody and their mom is doing this program

404 Upvotes

Last month on the NYC subway, I was listening to GIOS lectures, a thrilling habit I maintain while grocery shopping. The train was packed, a homeless guy was napping across multiple seats, so I had to endure sitting near people.

The guy next to me noticed the lecture and said he was in the same class. Nice dude, one semester in, working a CS job but dreaming of FAANG. As someone halfway through the program, I didn’t have the heart to tell him this program’s likely a time sink—no recruiter’s ever cared about it in my experience.

Then the sleeping homeless guy woke up and joined in. Turns out, he’s in the program too, finishing his last semester. He’d given up on FAANG and was pivoting to teaching but couldn’t get interviews.

So there we were, three people at different stages of the same program, united by a prestigious degree and zero job prospects. Inspiring stuff!


r/OMSCS • • Nov 27 '24

CS 6515 GA 100% Win Rate: How We Fought and Won Against False Plagiarism Allegations in CS6515

397 Upvotes

During the fall semester, a group of us faced false plagiarism allegations in CS6515. By working together and supporting each other, we’ve now achieved 12 19 out of 20 acquittals—a perfect 100% 94.7% win rate so far.

⚠️ Important:

  • If you cheated, there’s nothing we can do—own it and move on.

  • If you didn’t cheat, we strongly encourage you to fight. The process is fair if you come prepared.

From our experience:

  • OSI judges were professional, thorough, and willing to hear us out. They reviewed all evidence carefully and ensured a fair process.

  • We submitted a petition to Professor Joyner about issues with how plagiarism cases were flagged. He listened and considered our concerns.

  • TAs remained professional throughout, continuing to grade assignments and answer questions despite the situation. Their dedication was appreciated.

💡 Advice for CS6515 Students:

  1. Don’t skip the class. It’s invaluable for mastering graph algorithms and dynamic programming—critical for coding interviews.

  2. Use tools like PyCharm to save revisions frequently. Revision histories are your strongest evidence of individual work. If you have them, they can be decisive in proving your case. (Caution: Revision histories may corrupt after power outages—always verify before submitting!)

  3. Avoid automated tools or referencing online solutions. Even accidental similarities can flag you.

  4. Make your code unique. Add your username to variable names (e.g., idx_wsmith23). While plagiarism checkers might ignore variable names, adjudicators could see this as a sign of originality.

If You’re Facing Allegations:

You’re not alone. With preparation and the right approach, you can defend yourself successfully. Here’s what helped us:

  1. Thoroughly Refute Every False Statement: Carefully review the accusations and ensure you address every false claim. In my case, the TA argued that it was "impossible" for every line of my code to match another student's unless I had cheated. However, only two seven lines and two variables matched exactly, while everything else was significantly different. By calling out this falsehood, I was able to prevent the adjudicator from making a decision based on incorrect information. Ignoring such claims could lead to unfair outcomes. (Edit: TA who accused me does not agree. His opinion is that other lines are significantly similar while mine is that lines are significantly different. See it is a matter of perspective)

  2. Challenge the Similarity Report: A similarity score from MOSS or other tools is not proof of plagiarism. As Professor Joyner notes in this research paper: While this observation typically applies to large projects, in our case*,* the flagged code was only 20–30 lines long, making overlaps far more likely due to limited variations in small assignments. This is an important distinction to highlight when defending yourself. "The projects in our class typically include several hundred lines of C code written by students. As a result, the total number of unique tokens evaluated by MOSS is quite substantial, and false positives are less likely."

  3. Present Clear Evidence: Revision histories from PyCharm or other coding tools are extremely strong evidence of individual work. If you have a history showing how your code evolved, it becomes much harder to argue that you copied someone else. Make sure to submit this as part of your defense.

  4. Don’t Be Discouraged by TAs Defending Their Allegations: TAs are expected to defend their accusations and will argue that their investigation was thorough and careful. Don’t let this discourage you. A truly thorough investigation must consider all evidence you present, not just a similarity report. Point this out if necessary and come prepared with your own evidence. Strong documentation can shift the focus away from their narrative and onto the actual facts of the case.

  5. Stay Calm and Professional: Explain your case logically and avoid emotional appeals. OSI judges are thorough and fair when reviewing evidence.

  6. Seek Support: Talk to others who’ve been through the process for guidance. You’re not alone in this.

This situation has been challenging, but our experiences prove that fighting false accusations is worth it. To anyone going through similar struggles—stay strong and don’t give up. 💪

Edits: 12/13/2024

  1. Correction for objectivity: An earlier version of this post stated that two lines were identical. Upon review, it was actually seven lines that were not identical, but very similar. This update has been made to ensure accuracy.

  2. Original post said we are 12/12, however we are 19/20 wins now; 100% 95% win rate.


r/OMSCS • • Dec 15 '24

I GOT OUT He is real! Dr Joyner congratulating students

Post image
380 Upvotes

I didn’t get a chance to take a picture with him, but I saw him standing there, congratulating all the graduates of the program.

Truly humble.

Thank you, Dr. Joyner, and the staff at Georgia Tech, for your dedication and for making this program possible.

With that note… I. AM. OUT!!!


r/OMSCS • • Sep 04 '24

I GOT OUT It's the Thing..............

374 Upvotes

You know the pain and

sacrifice for this thing to

come home. Free at last.


r/OMSCS • • Feb 07 '25

Graduation Diploma finally shipped (Dec 14th graduate)

Post image
370 Upvotes

After 3 1/2 years of slow and steady hard work, I graduated on Dec 14, 2024. I’ve been checking daily for a couple of weeks to see if parchment has changed the status for my diploma and today it finally went from processing to shipped. I don’t have a tracking number but certainly hope the empty frame I already hung on the wall will have something in it next week.

I’m 56 years old so this was quite an undertaking being so far removed from my bachelors from Clemson all those years ago.

Sorry, I’m surprisingly excited 😆.


r/OMSCS • • Nov 12 '24

CS 6515 GA I think a lot of you are missing the point of this program.

359 Upvotes

Alumni here - I’ve seen so many GA posts in the last 3 months, but I’ve not seen anyone really address the misconceptions that I see a lot of people have about the program or a Master’s degree in general.

For background - I started the program in 2018 and finished in 2022 (was working full time, so only did 1 class a semester; took some time off due to the loss of a parent and the pandemic). I’ve seen how the program has evolved over the last 6 years.

The original reason OMSCS was started was to give more people to opportunity to see if they could cut it in a high quality Comp Sci graduate program. The on-campus program is limited by physical space - which means admissions needs to be extremely selective for individuals with a high likelihood of success and that can exclude some folks who may have the skills or drive to succeed in the program but don’t have the right mix on paper. (The cost of physical coloration plus lost earnings potential in a full time on-campus program also make the opportunity cost higher for those who do not succeed).

Ultimately that means that it was intended to give people a shot a graduate CS education, but it was not a guarantee of success. Some people will not be able to cut it; and due to the low cost and relatively low time commitment failing or dropping out of OMSCS after a few semesters is much less impactful than failing/dropping out of the on-campus program.

Tangent - I also hate that we frame the completion of the degree as binary success/failure. If you are in the program doing your best, you should be learning something regardless of grade and/or diploma. That learning is valuable. (Note: before anyone comes after me, I acknowledge there may be some privilege in that position; as the degree itself can impact employment/compensation/immigration but my counter to that would be that none of those are uniquely dependent on OMSCS)

Anyway, I see too many of ya’ll treating OMSCS like an AWS cert prep course or a boot camp. You are not guaranteed to succeed. The professors generally know more than you do about pedagogy and how to run a graduate course. You are expected to teach yourself things in grad school.

I say this because I see so much of the feedback on courses like GA seemingly predicated on the idea that GA Tech should optimize OMSCS for making as many students pass as easily as possible - that’s not the point of the program! I don’t know what programs you all have been a part of where higher education is that transactional, but having been in academic spaces for a while I can tell you that is not the norm - any many programs are even harsher.

It’s okay that not every will succeed in this program. It doesn’t make you a failure. It just means this one program was not a fit. As difficult as it is for the ego, we just have to accept that not everyone is going to succeed.

Now before anyone dismisses this post as “git gud” or survivorship bias: I was in the same boat. I didn’t pass GA the first time. I didn’t have the mathematics background in my undergrad that the course somewhat presupposes and I had to remedially learn a lot. I also lost a parent midway through which let me do a retroactive withdraw. However, before I knew that was possible I was grappling with the idea that maybe I’m not cut out for this; or that I should switch from ML to II to avoid GA. I chose to continue on, with the focus of trying to learn the most I could because I knew that this was stuff that was clearly I had a lot of learning to do to master. Ultimately I managed to pass with a B and graduate with a total GPA of 3.6.

I’m sharing all of this a concerned alumni. I don’t want OMSCS to lose the rigor that attracted me to the program in the first place. If I just wanted a Master’s degree I could find a bunch of 3rd-tier schools that I could squeak through. I also think that changing one’s mindset of why they are doing this program can be helpful in putting them in a healthier position to succeed.

Bring on the downvotes! 😜


r/OMSCS • • May 04 '24

I GOT OUT Attended commencement today and officially Graduated!

Post image
355 Upvotes

r/OMSCS • • Oct 22 '24 Take My Energy

New Course Feedback on a new OMSCS course on building database systems (Spring 2025)

354 Upvotes

Hi folks 👋

We are developing a new course on Database System Implementation (CS 6422) that is going to launch in Spring 2025, and we’d love to get your thoughts!

The course dives into topics like storage management, indexing structures, and query execution, with a strong emphasis on modern C++. We gradually build an educational database system from scratch, using BuzzDB as our foundation. More course details are available here.

The hands-on programming assignments include:

  • ⚙️ A multi-threaded buffer manager

  • 🌳 An on-disk B+tre

  • 🏎️ A query execution engine

Here’s a sneak peek at some of the lessons:

  • Relational Databases

  • 🐝 BuzzDB

  • Storage Management

  • 2Q Policy

  • Thread-Safe Hash Tables

  • B+Tree

  • Query Execution

  • Query Compilation

Looking ahead, we’re planning to launch another course (CS 6423) on advanced topics in database system implementation like logging and recovery, concurrency control, and query optimization. More course details are available here.

I’m really keen to hear what you think:

  • Are there any additional topics you’d recommend to enhance these courses?

  • Any feedback on the assignments or the focus on C++?

Looking forward to hearing your thoughts and suggestions!


r/OMSCS • • Dec 03 '24

Let's Get Social 98.8% of OMS Students DON'T WANT the Athletics Fee Increase

Post image
346 Upvotes

Let's make it too big to rig everyone!


r/OMSCS • • Aug 20 '25

Social Got my OMSCS Tshirt FINALLY! 💛✨

Post image
324 Upvotes

Started the program in Spring 2024 and filled the T-shirt survey. I'm from India and I had heard it's really tough to get one of these shipped but I was like hey, let's try our luck! After a whole year of waiting (so much that I had forgotten about it), FINALLY received it today and I just caaaan't 😭💛✨


r/OMSCS • • Nov 08 '24

This is a Meme Sorry Took Me A Few Minutes to Make This.

Post image
322 Upvotes

r/OMSCS • • Aug 12 '26

I Got Out! Guess who has finally graduated

Post image
320 Upvotes

So two semesters ago I failed GA by 0.02%, and was devastated (you can see my old post about it). Fast forward to now and I just passed with an 87%, and can now graduate.

We fucking did it boyz.

time to go get needlessly drunk :)


r/OMSCS • • Nov 23 '23

Dumb Qn I’m getting pissed will all this Gen AI BS

317 Upvotes

As an OMSCS student specializing in ML, do you get pissed when you see all those charlatans with zero ideas on artificial intelligence touting on LinkedIn?

Because I get so many in my feed that it’s sickening at some point. At this point it’s like a dick measuring contest to see who is the bigger cock.