6 answers
1
Question
Updated
644 views
Computer Science Career Questions
Hello. I am a college student majoring in computer science.
I am currently conducting research on careers in computer programming.
I would appreciate it if anyone would be willing to answer the following questions:
Q1: Why did you choose this career?
Q2: What does a typical day look like for you?
Q3: What do you like most about this career?
Q4: What do you like least or find most challenging?
Q5: What surprised you when you first started?
Q6: How long did it take to feel established or competent?
Q7: What skills or knowledge do you wish you had learned sooner?
Q8: Knowing what you know now, would you choose this career again?
Q9: What is your job title/occupation?
Thank you in advance for your help!
Login to comment
6 answers
Updated
Sandeep’s Answer
Hello Oscar,
Great questions.
Q1: I chose this career because I enjoy problem-solving and building things that have real-world impact.
Q2: A typical day involves coding, debugging, reviewing code, and collaborating with teams to design solutions.
Q3: I like the constant learning and the ability to create something useful from scratch.
Q4: The most challenging part is dealing with complex problems and sometimes unclear requirements.
Q5: I was surprised by how much teamwork and communication is involved, not just coding.
Q6: It took about 2–3 years of real work experience to feel confident and competent.
Q7: I wish I had focused earlier on system design, real-world projects, and problem-solving skills.
Q8: Yes, I would choose this career again. it’s challenging but very rewarding.
Q9: Software Engineer.
Great questions.
Q1: I chose this career because I enjoy problem-solving and building things that have real-world impact.
Q2: A typical day involves coding, debugging, reviewing code, and collaborating with teams to design solutions.
Q3: I like the constant learning and the ability to create something useful from scratch.
Q4: The most challenging part is dealing with complex problems and sometimes unclear requirements.
Q5: I was surprised by how much teamwork and communication is involved, not just coding.
Q6: It took about 2–3 years of real work experience to feel confident and competent.
Q7: I wish I had focused earlier on system design, real-world projects, and problem-solving skills.
Q8: Yes, I would choose this career again. it’s challenging but very rewarding.
Q9: Software Engineer.
Hello Sandeep, Thank you so much for your response. After reading experiences from other websites, I found that everyone also emphasizes communication and collaboration in this field. Furthermore, I found your answer to question 7 very helpful. It is like an advisory for me to pursue this career. Your answers are very helpful as a reference for my research notes. Thank you so much for your help and time!
Oscar
Updated
Andras’s Answer
Hello, good luck with your studies, keep up the good work!
Q1: I guess this is the usual story. I had a PC as a child and quickly became a geek, partly because I loved tweaking things and do some basic programming, partly because we played together with friends. I was also good at math so applied to computer science university. Many of my class mates applied the same, it also made my decision easier.
Q2: In partly home office I develop software for a large multi. Most of the day is working in specific tasks like programming, configuring, testing - all part of a larger feature. Time to time I also fix incoming bugs. Minor part of day are meetings, mostly with team mates to arrange duties. I also spend time regularly to learn, like reading articles, doing online trainings, watching tech videos.
Q3: Never boring. Either the domain and tech stack itself is changing or the project and product you are assigned to is changing roughly in every 2-3 years. Technology is evolving superfast, including both the domain knowledge and the work environment (software tools, automation, AI). Not to mention the most companies are big enough to provide opportunities to career moves like becoming a tech or people leader after some time.
Q4: No direct impact on society, at least not in a scale like if I was a doctor or teacher. Can be frustrated if team structure or management is less optimal causing daily stress and struggle - but that is not computer science specific, can occur in any work place. Many leaders are tech based folks, not much trained for human skills, so this can still be a common issue in tech companies I think.
Q5: How large amount of development is related to already existing code base. Even if you create new software blocks, they become legacy immediately - so in most cases a daily work of software engineer is not about creating 1000 lines of new code all the time. It is not an issue though. Of course other job roles like architect or support or operations are much different.
Q6: It is a rollercoaster: every 2-3 years things are changing, see my answer to Q3 above. So any time a new project or new technology is coming, you start learning over and over again. Depending on complexity of the software you are developing, it can take 0.5 to 1 year to become comfortable. But looking at the specific code block your current task is related to, is just days normally. So the feeling of being lost and confused never lasts for more than couple of days. Especially if you are in a team where team mates help and mentor. And especially nowadays that you have AI tools that can educate you quickly any time.
Q7: There is no such I can think of. No silver bullet type of competence. Just be open to learn and adapt continuously.
Q8: Yes, definitely.
Q9: Senior software developer.
These were very clever and nice open questions! I hope my answers help.
Q1: I guess this is the usual story. I had a PC as a child and quickly became a geek, partly because I loved tweaking things and do some basic programming, partly because we played together with friends. I was also good at math so applied to computer science university. Many of my class mates applied the same, it also made my decision easier.
Q2: In partly home office I develop software for a large multi. Most of the day is working in specific tasks like programming, configuring, testing - all part of a larger feature. Time to time I also fix incoming bugs. Minor part of day are meetings, mostly with team mates to arrange duties. I also spend time regularly to learn, like reading articles, doing online trainings, watching tech videos.
Q3: Never boring. Either the domain and tech stack itself is changing or the project and product you are assigned to is changing roughly in every 2-3 years. Technology is evolving superfast, including both the domain knowledge and the work environment (software tools, automation, AI). Not to mention the most companies are big enough to provide opportunities to career moves like becoming a tech or people leader after some time.
Q4: No direct impact on society, at least not in a scale like if I was a doctor or teacher. Can be frustrated if team structure or management is less optimal causing daily stress and struggle - but that is not computer science specific, can occur in any work place. Many leaders are tech based folks, not much trained for human skills, so this can still be a common issue in tech companies I think.
Q5: How large amount of development is related to already existing code base. Even if you create new software blocks, they become legacy immediately - so in most cases a daily work of software engineer is not about creating 1000 lines of new code all the time. It is not an issue though. Of course other job roles like architect or support or operations are much different.
Q6: It is a rollercoaster: every 2-3 years things are changing, see my answer to Q3 above. So any time a new project or new technology is coming, you start learning over and over again. Depending on complexity of the software you are developing, it can take 0.5 to 1 year to become comfortable. But looking at the specific code block your current task is related to, is just days normally. So the feeling of being lost and confused never lasts for more than couple of days. Especially if you are in a team where team mates help and mentor. And especially nowadays that you have AI tools that can educate you quickly any time.
Q7: There is no such I can think of. No silver bullet type of competence. Just be open to learn and adapt continuously.
Q8: Yes, definitely.
Q9: Senior software developer.
These were very clever and nice open questions! I hope my answers help.
Hello Andras,
Thank you so much for your response.
I appreciate that you pointed out the importance of learning new things consistently. By combining it with your experiences, it changes my view of a computer programmer's career. Also, the roller coaster feeling gives me a sense of what it's like to work in the industry. Moreover, your answers are very helpful for my research paper, and they give me some tips on how to prepare for this career. In addition, I really like the roller coaster and silver bullet metaphors because I can clearly imagine them as I read.
Thank you so much for your time and help!
Oscar
Updated
Sebastian’s Answer
Q1: Why did you choose this career?
I chose this career because I enjoy solving problems and working with technology. Programming allows me to build practical solutions and continuously learn new things.
Q2: What does a typical day look like for you?
A typical day involves reviewing tasks, writing and debugging code, attending team meetings, and collaborating with others to solve issues or improve systems. There’s also time spent testing and documenting work.
Q3: What do you like most about this career?
I like the problem-solving aspect and the ability to create something useful from scratch. The constant learning and variety of challenges keep the work interesting.
Q4: What do you like least or find most challenging?
The most challenging part is dealing with complex bugs or unclear requirements, which can take time to resolve. Staying updated with new technologies can also be demanding.
Q5: What surprised you when you first started?
I was surprised by how much collaboration is involved. Programming is not just coding—it requires communication, teamwork, and understanding user needs.
Q6: How long did it take to feel established or competent?
It typically takes about 1–2 years of consistent practice and real-world experience to feel comfortable, but learning never really stops.
Q7: What skills or knowledge do you wish you had learned sooner?
I wish I had learned more about debugging techniques, version control (Git), and problem-solving strategies earlier, as they are essential in daily work.
Q8: Knowing what you know now, would you choose this career again?
Yes, I would. It offers good career opportunities, flexibility, and continuous growth.
Q9: What is your job title/occupation?
Software Support Engineer / Technical Support Specialist (related to IT and software troubleshooting environments)
I chose this career because I enjoy solving problems and working with technology. Programming allows me to build practical solutions and continuously learn new things.
Q2: What does a typical day look like for you?
A typical day involves reviewing tasks, writing and debugging code, attending team meetings, and collaborating with others to solve issues or improve systems. There’s also time spent testing and documenting work.
Q3: What do you like most about this career?
I like the problem-solving aspect and the ability to create something useful from scratch. The constant learning and variety of challenges keep the work interesting.
Q4: What do you like least or find most challenging?
The most challenging part is dealing with complex bugs or unclear requirements, which can take time to resolve. Staying updated with new technologies can also be demanding.
Q5: What surprised you when you first started?
I was surprised by how much collaboration is involved. Programming is not just coding—it requires communication, teamwork, and understanding user needs.
Q6: How long did it take to feel established or competent?
It typically takes about 1–2 years of consistent practice and real-world experience to feel comfortable, but learning never really stops.
Q7: What skills or knowledge do you wish you had learned sooner?
I wish I had learned more about debugging techniques, version control (Git), and problem-solving strategies earlier, as they are essential in daily work.
Q8: Knowing what you know now, would you choose this career again?
Yes, I would. It offers good career opportunities, flexibility, and continuous growth.
Q9: What is your job title/occupation?
Software Support Engineer / Technical Support Specialist (related to IT and software troubleshooting environments)
Updated
Matthew’s Answer
Q1: Why did you choose this career?
Because I love solving problems. I didn't seek it out, I was presented with an opportunity to work alongside some software engineers and loved it.
Q2: What does a typical day look like for you?
Well im a director now, so about 50% of my team is making sure my teams have what they need to do their jobs, the rest is primarily strategy and architecture. If i'm lucky i'll have some time to write some code!
Q3: What do you like most about this career?
Whilst the core activities are similiar, you can work for a whole variety of different companies and industries. You are directly and meaningfully contributing to the success of a business, as well as an opportunity to create your own business without really getting siloed into an area.
Q4: What do you like least or find most challenging?
It can be a demanding job and I can find it hard to shut off.
Q5: What surprised you when you first started?
Software engineers aren't un-relatable geniuses but friendly normal people that love solving problems by using technology.
Q6: How long did it take to feel established or competent?
the first year of my job to feel established as a software engineer and competent enough that i'm providing value. The technology you work with can be incredibly deep - the feeling of competency is a relative thing!
Q7: What skills or knowledge do you wish you had learned sooner?
How to communicate effectively and how to listen more effectively.
Q8: Knowing what you know now, would you choose this career again?
100%. I get to do a job i love, get paid well to do it and get to be around my family by working from home - there's few industries like this!
Q9: What is your job title/occupation?
Director of Software Engineering
Because I love solving problems. I didn't seek it out, I was presented with an opportunity to work alongside some software engineers and loved it.
Q2: What does a typical day look like for you?
Well im a director now, so about 50% of my team is making sure my teams have what they need to do their jobs, the rest is primarily strategy and architecture. If i'm lucky i'll have some time to write some code!
Q3: What do you like most about this career?
Whilst the core activities are similiar, you can work for a whole variety of different companies and industries. You are directly and meaningfully contributing to the success of a business, as well as an opportunity to create your own business without really getting siloed into an area.
Q4: What do you like least or find most challenging?
It can be a demanding job and I can find it hard to shut off.
Q5: What surprised you when you first started?
Software engineers aren't un-relatable geniuses but friendly normal people that love solving problems by using technology.
Q6: How long did it take to feel established or competent?
the first year of my job to feel established as a software engineer and competent enough that i'm providing value. The technology you work with can be incredibly deep - the feeling of competency is a relative thing!
Q7: What skills or knowledge do you wish you had learned sooner?
How to communicate effectively and how to listen more effectively.
Q8: Knowing what you know now, would you choose this career again?
100%. I get to do a job i love, get paid well to do it and get to be around my family by working from home - there's few industries like this!
Q9: What is your job title/occupation?
Director of Software Engineering
Updated
Ryun’s Answer
Q1: I had a programming class starting in middle school and again in high school. It was the one class where I wasn't constantly looking at the clock to see how much more time was left in class. I know its sometimes over used but I do believe that if you do something that interests you and you like to do, it makes your career enjoyable and not a chore.
Q2: Initially, I was involved in the actual development of the software so coding, debugging, documenting, etc. I moved from there to more leadership roles like Team Lead, Architect, and Product Manager. I found that I was most effective when working through other people and leading them to accomplish more than I could do by myself.
Q3: I like seeing people using a product that I helped develop. It makes you feel like you have had an impact. I love problem solving and helping people do things they couldn't do easily before.
Q4: I like working for large companies but it can be really challenging because sometimes there is a lot of people that want to be able to say 'No' so it is hard to get everyone say 'Yes'. The bureaucracy sometimes slows the innovation but I always encourage you to drive forward with a project you believe in.
Q5: When I was in school, you would get a project and when your code worked and you submitted it you were done. That is not the real world. In the real world when your code works, it is just the beginning. The feedback loop between your users and your development is critical. Engineers don't always think like their users. Listen to how people use your product and take that feedback to heart. Make things easy to use and you will be successful.
Q6: Good question! That's hard to answer. I liked changing roles every couple of years because when I got where I felt I was the expert in an area, I wanted to go learn something new. It always takes sometime to find your role and where you can contribute but I would estimate it takes 3-6 months to where you feel like you are a competent contributor.
Q7: How to present for impact is a big one! If you want your ideas accepted, you have to learn how to influence management to invest in your idea. I highly recommend taking presentation courses and learning how to be comfortable pitching your ideas in front of people
Q8: Absolutely! I feel like I stumbled upon what I was meant to do very early in my educational career which is rare.
Q9: Chief Software Engineer
Q2: Initially, I was involved in the actual development of the software so coding, debugging, documenting, etc. I moved from there to more leadership roles like Team Lead, Architect, and Product Manager. I found that I was most effective when working through other people and leading them to accomplish more than I could do by myself.
Q3: I like seeing people using a product that I helped develop. It makes you feel like you have had an impact. I love problem solving and helping people do things they couldn't do easily before.
Q4: I like working for large companies but it can be really challenging because sometimes there is a lot of people that want to be able to say 'No' so it is hard to get everyone say 'Yes'. The bureaucracy sometimes slows the innovation but I always encourage you to drive forward with a project you believe in.
Q5: When I was in school, you would get a project and when your code worked and you submitted it you were done. That is not the real world. In the real world when your code works, it is just the beginning. The feedback loop between your users and your development is critical. Engineers don't always think like their users. Listen to how people use your product and take that feedback to heart. Make things easy to use and you will be successful.
Q6: Good question! That's hard to answer. I liked changing roles every couple of years because when I got where I felt I was the expert in an area, I wanted to go learn something new. It always takes sometime to find your role and where you can contribute but I would estimate it takes 3-6 months to where you feel like you are a competent contributor.
Q7: How to present for impact is a big one! If you want your ideas accepted, you have to learn how to influence management to invest in your idea. I highly recommend taking presentation courses and learning how to be comfortable pitching your ideas in front of people
Q8: Absolutely! I feel like I stumbled upon what I was meant to do very early in my educational career which is rare.
Q9: Chief Software Engineer
Updated
Robert’s Answer
Q1: Why did you choose this career?
I started as a high school chemistry teacher, but it wasn't the right fit for me. So, I went back to school for a computer science degree. Now, as a software developer, I find great satisfaction in my work.
Q2: What does a typical day look like for you?
I usually have meetings in the morning due to time zone differences, which leaves my afternoons free for development work.
Q3: What do you like most about this career?
I love solving problems and troubleshooting. Analyzing logic and improving processes is exciting. This career is both technical and creative, which keeps my mind engaged.
Q4: What do you like least or find most challenging?
I'm not great at handling emails and administrative tasks. They take me away from coding, which I enjoy more. These tasks are necessary, but they're not my favorite part.
Q5: What surprised you when you first started?
I was surprised by how well I fit in. At first, I was intimidated by more experienced developers, but my training and skills helped me contribute meaningfully and learn quickly.
Q6: How long did it take to feel established or competent?
I felt competent in testing and fixing bugs within my first year. After a couple of years, I gained confidence in taking on new development tasks.
Q7: What skills or knowledge do you wish you had learned sooner?
I wish I had improved my communication skills earlier. I often tried to solve problems on my own, but asking for help sooner could have saved time and effort.
Q8: Knowing what you know now, would you choose this career again?
Absolutely! Being a programmer feels like the perfect fit for me.
Q9: What is your job title/occupation?
Senior Software Application Developer
Great questions! Best of luck with your journey.
I started as a high school chemistry teacher, but it wasn't the right fit for me. So, I went back to school for a computer science degree. Now, as a software developer, I find great satisfaction in my work.
Q2: What does a typical day look like for you?
I usually have meetings in the morning due to time zone differences, which leaves my afternoons free for development work.
Q3: What do you like most about this career?
I love solving problems and troubleshooting. Analyzing logic and improving processes is exciting. This career is both technical and creative, which keeps my mind engaged.
Q4: What do you like least or find most challenging?
I'm not great at handling emails and administrative tasks. They take me away from coding, which I enjoy more. These tasks are necessary, but they're not my favorite part.
Q5: What surprised you when you first started?
I was surprised by how well I fit in. At first, I was intimidated by more experienced developers, but my training and skills helped me contribute meaningfully and learn quickly.
Q6: How long did it take to feel established or competent?
I felt competent in testing and fixing bugs within my first year. After a couple of years, I gained confidence in taking on new development tasks.
Q7: What skills or knowledge do you wish you had learned sooner?
I wish I had improved my communication skills earlier. I often tried to solve problems on my own, but asking for help sooner could have saved time and effort.
Q8: Knowing what you know now, would you choose this career again?
Absolutely! Being a programmer feels like the perfect fit for me.
Q9: What is your job title/occupation?
Senior Software Application Developer
Great questions! Best of luck with your journey.