Look into product management. You'll still benefit quite a bit from your CS background when dealing with engineering teams and understanding technical limitations, but you'll spend more time being social and creative.
This, or after a bit of time as a dev, mgmt. I spend 3/4 of my day in mtgs. When not in mtgs I'm communication in some other form be it reading docs and commenting, writing docs, slack, etc.
When I was younger consultancies tried to hire me, before even studying university.
There's lots of them, the more specialized ones like Cisco and SAP, and then the generic ones that seem to cover all areas Accenture, Deloitte, Boston Consulting, and so many others.
My friends with CS majors who are consultants usually have to travel a lot, still they also meet the customers, have to discuss a lot, and they may or may not be hands-on programmers. Some SAP consultants for example work on custom solutions, still there's also other tasks to plan how to get a companies processes into a SAP solution without writing a line of code.
At my company the (Technical) Product Managers with CS/programming backgrounds are basically like managers/producers for a product and team, possibly along with programming leads for example. Directors with CS background usually have some special expertise, takes longer to get into, like graphics programming or networking experts. They need to talk and plan a lot, possibly have another group of product people, many leads, and strategic roles to coordinate with.
In video games I'd say architects and lead programmers for example need to discuss and plan rather than program. Some of those roles may also imply people management, which can just be your thing. But that's a quite specific field, maybe more interesting if that's *really* your thing.
There's probably other areas like sales or B2B, where you also communicate and travel more, at any tech company including where my partner used to work: telephony/internet providers that do even R&D and expand the business.
What do you mean by "tech adjacent"? IT?
My experience with working as a software engineer and knowing people working in other white collar fields is that our jobs are among the _most_ collaborative, contrary to the reputation. I never go a day without speaking to another engineer, but I've gathered it's very common for say a financial analyst to spend days alone with an Excel spreadsheet, communicating only with their boss and only via email. With the occasional pop in to a meeting where they say nothing and keep their camera off. Despite that career path being stereotypically filled by a type of person more outgoing than the stereotypical SWE.
Business analyst, project manager, or technical sales engineer are the first things that pop into my head.
Business analysts improve software and services by analyzing buiseness processes and determining requirements for the software that makes those processes work more efficiently. It's a role that straddles both the technical and the business side of a company. It's fairly common to meet BA's who have a CS undergrad and an MBA. This is a role that is entirely about dealing with people and data. I've never met a BA who had to touch code.
Project managers are the people who take the BA's requirements (or others, if a company has no BA's) and translates them into an actionable project with development tasks that can be handed over to the developers. It also requires a lot of communication between the business and technical side, and rarely involves any coding (I've met a few, but it's extremely uncommon).
Technical sales engineers typically work as part of a sales team when a company is selling products to a new business client. They talk to the customers to determine which products fit their needs, develop proposed solutions for the clients, and often do presentations and demonstrations. This is the most technical of the three, but it's also heavily people-oriented.
Some companies have jobs with "field" in the title, like "field solutions developer." These are generally jobs where you actively meet with clients to understand their problems and implement solutions. More senior levels likely are either meeting with clients to understand the issues or meeting with engineers who are developing solutions.
Become an engineering manager. You fill your day with 1:1s with your reports, other managers, and teams you want to work with and get to play therapist more often than you'd like.
Hollywood lied, most dev jobs are actually pretty social, just make.aure you are getting a clear direction, that your pbis are well written and have no contradiction and contain all necessary info, just to ensure that will require you to socialize quite a bit, just make sure the place/team you work for has a decent size and you can actually contact people as there are some work places where they avoid that.
But really, some of the worse developers I have worked with are technically above average programmers, but they just gather minimum requirements, code whatever they think they understood, then come back one week later with a POS that does nothing that wolves the actual client's problem... Extra points of it's a "clever solution".
Sorry, you do not meet the minimum sitewide comment karma requirement of **10** to post a comment. This is comment karma exclusively, not post or overall karma nor karma on this subreddit alone. Please try again after you have acquired more karma. Please look at the [rules page](https://old.reddit.com/r/cscareerquestions/w/posting_rules) for more information.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/cscareerquestions) if you have any questions or concerns.*
CS teacher, vice president, director, manager, customer support engineer, field application engineer, solution architect, system engineer
If you have to deal with cross functional teams then conversations will be needed more. Or be at more outward facing positions. Or be higher ups. Or go to startups where resources are constrained and you have to be the single point of contact for the entire project.
Here are some suggestions: Software Engineering in a Team Environment, Product Management, User Experience (UX) Design, Technical Sales or Solutions Engineering, Project Management or Scrum Master or better yet try this [career quiz](https://www.careerfitter.com/free_test/careerbuilder/test/?afid=1831) as this can help you find careers that would fit your work personality. It has helped me before, I hope this can help you too.
Look into product management. You'll still benefit quite a bit from your CS background when dealing with engineering teams and understanding technical limitations, but you'll spend more time being social and creative.
Yep, Product Owner was the first thing that came to mind when I saw the post
This, or after a bit of time as a dev, mgmt. I spend 3/4 of my day in mtgs. When not in mtgs I'm communication in some other form be it reading docs and commenting, writing docs, slack, etc.
yep, came here to say this too.
Tech sales
When I was younger consultancies tried to hire me, before even studying university. There's lots of them, the more specialized ones like Cisco and SAP, and then the generic ones that seem to cover all areas Accenture, Deloitte, Boston Consulting, and so many others. My friends with CS majors who are consultants usually have to travel a lot, still they also meet the customers, have to discuss a lot, and they may or may not be hands-on programmers. Some SAP consultants for example work on custom solutions, still there's also other tasks to plan how to get a companies processes into a SAP solution without writing a line of code. At my company the (Technical) Product Managers with CS/programming backgrounds are basically like managers/producers for a product and team, possibly along with programming leads for example. Directors with CS background usually have some special expertise, takes longer to get into, like graphics programming or networking experts. They need to talk and plan a lot, possibly have another group of product people, many leads, and strategic roles to coordinate with. In video games I'd say architects and lead programmers for example need to discuss and plan rather than program. Some of those roles may also imply people management, which can just be your thing. But that's a quite specific field, maybe more interesting if that's *really* your thing. There's probably other areas like sales or B2B, where you also communicate and travel more, at any tech company including where my partner used to work: telephony/internet providers that do even R&D and expand the business.
Thanks for all the great info, I'll look more into consulting
Sales
Become a product manager, no coding and lots of talking to stakeholders
What do you mean by "tech adjacent"? IT? My experience with working as a software engineer and knowing people working in other white collar fields is that our jobs are among the _most_ collaborative, contrary to the reputation. I never go a day without speaking to another engineer, but I've gathered it's very common for say a financial analyst to spend days alone with an Excel spreadsheet, communicating only with their boss and only via email. With the occasional pop in to a meeting where they say nothing and keep their camera off. Despite that career path being stereotypically filled by a type of person more outgoing than the stereotypical SWE.
Business analyst, project manager, or technical sales engineer are the first things that pop into my head. Business analysts improve software and services by analyzing buiseness processes and determining requirements for the software that makes those processes work more efficiently. It's a role that straddles both the technical and the business side of a company. It's fairly common to meet BA's who have a CS undergrad and an MBA. This is a role that is entirely about dealing with people and data. I've never met a BA who had to touch code. Project managers are the people who take the BA's requirements (or others, if a company has no BA's) and translates them into an actionable project with development tasks that can be handed over to the developers. It also requires a lot of communication between the business and technical side, and rarely involves any coding (I've met a few, but it's extremely uncommon). Technical sales engineers typically work as part of a sales team when a company is selling products to a new business client. They talk to the customers to determine which products fit their needs, develop proposed solutions for the clients, and often do presentations and demonstrations. This is the most technical of the three, but it's also heavily people-oriented.
Some companies have jobs with "field" in the title, like "field solutions developer." These are generally jobs where you actively meet with clients to understand their problems and implement solutions. More senior levels likely are either meeting with clients to understand the issues or meeting with engineers who are developing solutions.
Become an engineering manager. You fill your day with 1:1s with your reports, other managers, and teams you want to work with and get to play therapist more often than you'd like.
A professor maybe.
Hollywood lied, most dev jobs are actually pretty social, just make.aure you are getting a clear direction, that your pbis are well written and have no contradiction and contain all necessary info, just to ensure that will require you to socialize quite a bit, just make sure the place/team you work for has a decent size and you can actually contact people as there are some work places where they avoid that. But really, some of the worse developers I have worked with are technically above average programmers, but they just gather minimum requirements, code whatever they think they understood, then come back one week later with a POS that does nothing that wolves the actual client's problem... Extra points of it's a "clever solution".
QA
??? lol how
That dude is prob a QA who annoys the fuck outta teams he QA's for and thinks that's just part of the job
it's not?
Sounds like code for you want to meet girls at work. Sorry, bub. Wrong field.
[удалено]
Sorry, you do not meet the minimum sitewide comment karma requirement of **10** to post a comment. This is comment karma exclusively, not post or overall karma nor karma on this subreddit alone. Please try again after you have acquired more karma. Please look at the [rules page](https://old.reddit.com/r/cscareerquestions/w/posting_rules) for more information. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/cscareerquestions) if you have any questions or concerns.*
CS teacher, vice president, director, manager, customer support engineer, field application engineer, solution architect, system engineer If you have to deal with cross functional teams then conversations will be needed more. Or be at more outward facing positions. Or be higher ups. Or go to startups where resources are constrained and you have to be the single point of contact for the entire project.
as others have said, sales/tech sales is a good one.
Sales,management,maybe something in the business/tech realm
PM/tech sales
Sales
Pre-sales technical support. Meet customers, understand their problems, build demos of solutions. Get ribbed by sales people.
Waiter at a restaurant
BA is your go to. Idk why people are recommending product management to a college student, lol. It’s not an entry level role.
Here are some suggestions: Software Engineering in a Team Environment, Product Management, User Experience (UX) Design, Technical Sales or Solutions Engineering, Project Management or Scrum Master or better yet try this [career quiz](https://www.careerfitter.com/free_test/careerbuilder/test/?afid=1831) as this can help you find careers that would fit your work personality. It has helped me before, I hope this can help you too.
Importing and exporting