u/readet covered probably the most common CS jobs but I can think of a few more. Academic: PhD, university lecturer, teaching in general. If you like research but would also like something more hands-on and better paid, you could try joining a company's R&D department. It is very rare for a company to maintain an R&D department with people on it full-time but you may be able to do this if you work for the likes of Google or Amazon. Pros: continuously learning new things, solving interesting problems in new ways. Teaching people? Cons: academic research is exhausting from a finance point of view. You're applying for grants all the time to keep going or have to do lecturing. Also, if you like building stuff and not just thinking and writing about it, it may become boring. The whole teaching aspect? I mean, it wholly depends on the person. Desktop application developer: these jobs are becoming increasingly scarce with the advent of React, Electron, etc. There's just very little need for consumer desktop applications to be around nowadays, as most stuff is done on the web now and if not, you can just package your site as an Electron app and call it a native desktop app. Users will be none the wiser. If you really want to become a traditional desktop app user, you'll probably have to apply on a product basis (get a job in a company that develop a successful, well established desktop app like MS Office or Adobe Creative Suite, for instance). Otherwise you may end up maintaing legacy desktop apps nobody would want to touch in their sane mind. Pros: if you don't like building websites, think HTML/CSS/JS is not real coding or don't like web programming languages, you can stay clear of them and use whichever language you want. Cons: difficult to find a job in this area nowadays. Embedded software developer: writing C, C++, assembly programmes for microcontrollers, embedded devices of all sorts, device drivers, etc. Pros: well paid, very cool if you're into low-level development, it's cool to see that your program has visible implications on the real world. This depends on what you're building of course. Cons: difficult, usually a background in electronics is appreciated as you'll be directly interfacing with physical devices. Prior experience is usually required in most job positions in the embedded space. Data scientist: big data, data analytics and reporting, data warehouse, perhaps some AI. Hadoop, Apache Spark, Splunk and much more which I don't know about myself. Pros: very well paid as everyone wants to do big data and AI now. Cons: requires loads of experience (even a degree of its own sometimes) Sysadmin/tech support: your friendly system administrator job! Usually involves, as its name implies, maintaining the a company's IT infrastructure: networking, server setup, sorting out people's IT issues... Pros: entry barrier is lower. Usually a degree is not required, perhaps just some certifications. Very hands-on. Cons: usually stressful, depending on how short you're on IT support personnel, you may end up spending most of your workday sorting out petty problems like antivirus, PDF's not opening, misconfigured email accounts... DevOps: DevOps people aim to bridge application development and deployment with their holistic skillset. These are people who have a extensive knowledge about best CI/CD practices, build pipelines (Jenkins, Concourse, Circle CI), provisioning (Ansible, Puppet, Chef, Foreman) and are comfortable coding to an acceptable level. Their main job is ensuring the application development process is as smooth, automated, predictable and efficient as possible. Pros: for people who prefer to be generalists rather than specialists, this is a good one. Also, the fact that your job consists of improving processes so they're more efficient and reliable feels good. Cons: can feel a bit like tech support sometimes if there's not a good DevOps culture in your company. If you're not careful, you may end up fixing developers' problems rather than improving things. "Why's the pipeline broken? DevOps guy, please fix it!", "Why's the latest version of my code not on the test environment? DevOps guyyyyy!!". Can get a bit tiresome. Site Reliability Engineer (SRE): these guys look after the healthy and efficient operation of a particular product or service. You can think of them as operations managers. They have a very broad set of responsibilities: looking after IT infrastructure, security, networking, provisioning, performance, monitoring, logs... In a nutshell, their job is to make sure a service (e.g. a website like Facebook) stays up and responsive. Pros: these jobs are in high demand at the moment and therefore companies are happy to pay big bucks for it. Cons: loads of experience and qualifications required. This is a senior-level position exclusively. Cloud architect: they design cloud-based systems. They get a set of business requirements, functional and non-functional constraints and have to turn them into a sound, cost-efficient, highly available, fault tolerant and secure cloud infrastructure. Pros: almost everyone is running their infrastructure on the cloud nowadays, or at least want to migrate to it sooner than later, so there's a lot of demand for people with strong cloud skills. Cons: very high-level and heavy in system design, little coding to do (perhaps some Lambda, Terraform, CloudFormation...). Again, a good amount of experience is required. More on reddit.com

Backend/Frontend engineering for Web applications is still #1 as most companies gravitate towards building out web applications that can be cross platform. This likely won't change for a while. I think focuses in machine learning/AI as well as security will continue to get larger, but due to the amount of expertise you need to do that kind of thing i don't think it will get as big as other types of disciplines in terms of quantity.

I recommend looking at the annual StackOverflow developer survey, it gives you a good gauge of where the industry is at / where it's headed.

https://insights.stackoverflow.com/survey/2019

More on reddit.com

To add this to, it’s not just enough to get a phd in AI/ML. You also have to publish good work to get into these top positions. We are talking about getting your work into top conferences like NIPS, ICML, ICLR.

More on reddit.com

• Go here

• Look through for entry level/ junior/new grad position.

• Send the poster a nice personal email (email id are usually included in the post).

• Keep it short. Nothing too fancy. Just tell them you're a recent grad, looking for a challenging and exciting opportunity and really want to learn and stuff like that. Be sure to mention that you saw their post on hacker rank news. Or put it on subject Eg. [HN] Application for Jr. engineer.

• Attach your resume or give them a dropbox/google drive link. I think people respond to links better.

• You can usually copy and paste the same email. If name is provided personalize it. Eg. Hi Jenny

• Depending on your resume you'll get replies some will want to move forward some will pass on you. And many will not reply at all.

I did this last week and have 2-3 phone screens lined up for this week. Good thing about this approach is it gets you directly to the person's inbox. Usually the jobs are also posted by senior engineers and if they like what they see, they will give you a reference at their company. Make sure you have your resume straightened up. You want to make most of this opportunity. Have your resume reviewed by someone. If I were you I'd send 10-15 emails first and gauge the response. If you get rejection from all the email maybe you need to work on your resume, work on some project etc(this is just my 0.02). Good luck champ, I know job search is brutal. I am on the same boat as you.

Bonus Strategy: Get mixmax on your gmail it will notify you if someone opens your email. It will help you track your applications.

More on reddit.com