14 answers
1
Question
Updated
756 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
14 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
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
Gregory’s Answer
Q1: I chose this career because I enjoy complex problem solving, and the ability to produce usable products that can receive immediate feedback.
Q2: A typical day varies for me, from reviewing junior engineer code, writing code myself, architecting new features and creating diagrams, meetings discussing product requirements.
Q3: It requires continuous learning and often allows for open discussion and debate on software solutions that leads to a fun collaborative process.
Q4: Often the reality is business decisions will drive technical decisions in some cases, it is not always about creating good software, but at the end of the day whats best for the business. On that note, it means you don't always get to architect software the ideal way and accept tradeoffs.
Q5: It surprised me the technical debt accumulation that can vary between projects, in other words code that is not ideal and arguably poorly written appears more often than you may think.
Q6: It took a few months, as it takes time to get bearing on the technical stack and have the confidence to speak on your specialties. But sometimes its more-so learning how to convey that with the team, you might already have the knowledge, thought a team environment is different.
Q7: I wish I had learned cloud technologies and system design sooner, undergrade doesn't typically place as much emphasis on system design which is vital to a future in Software Engineering.
Q8: I would absolutely choose it again, I love Software engineering.
Q9: Senior Backend Engineer
Q2: A typical day varies for me, from reviewing junior engineer code, writing code myself, architecting new features and creating diagrams, meetings discussing product requirements.
Q3: It requires continuous learning and often allows for open discussion and debate on software solutions that leads to a fun collaborative process.
Q4: Often the reality is business decisions will drive technical decisions in some cases, it is not always about creating good software, but at the end of the day whats best for the business. On that note, it means you don't always get to architect software the ideal way and accept tradeoffs.
Q5: It surprised me the technical debt accumulation that can vary between projects, in other words code that is not ideal and arguably poorly written appears more often than you may think.
Q6: It took a few months, as it takes time to get bearing on the technical stack and have the confidence to speak on your specialties. But sometimes its more-so learning how to convey that with the team, you might already have the knowledge, thought a team environment is different.
Q7: I wish I had learned cloud technologies and system design sooner, undergrade doesn't typically place as much emphasis on system design which is vital to a future in Software Engineering.
Q8: I would absolutely choose it again, I love Software engineering.
Q9: Senior Backend Engineer
Updated
Chris’s Answer
Q1: Why did you choose this career?
I always liked computers growing up so I wanted to work with computers and create things with computers.
Q2: What does a typical day look like for you?
I check my emails/messages and attend a standup meeting in the morning to give updates on my progress. I will then continue working on my task which usually consists of writing code and testing it.
Q3: What do you like most about this career?
I like being able to write code and seeing the stuff I am writing come to life. It's nice to have an idea in mind how you want something to work and then to actually see it happening is a good feeling.
Q4: What do you like least or find most challenging?
The thing I like least is doing documentation, it is important but can sometimes be very tedious depending on how your job wants it done.
Q5: What surprised you when you first started?
It surprised me at how much I needed to learn. There are differences between doing stuff in school and then while on the job. Lots of different technologies to learn and not just programming tools but other things like jira, Confluence, etc.
Q6: How long did it take to feel established or competent?
For me I would say it felt like maybe 6 months to a year. It takes some time to get used to how things are working. Gradually you may end up getting more complex tasks which will help with boosting your confidence in being able to do the job.
Q7: What skills or knowledge do you wish you had learned sooner?
I wish I had learned more about SQL for interfacing with databases as I didn't get much exposure to it when I was in college.
Q8: Knowing what you know now, would you choose this career again?
Yes I would still choose this career at the end of the day. I like to write code and see what I am creating come to life.
Q9: What is your job title/occupation?
Software Engineer
I always liked computers growing up so I wanted to work with computers and create things with computers.
Q2: What does a typical day look like for you?
I check my emails/messages and attend a standup meeting in the morning to give updates on my progress. I will then continue working on my task which usually consists of writing code and testing it.
Q3: What do you like most about this career?
I like being able to write code and seeing the stuff I am writing come to life. It's nice to have an idea in mind how you want something to work and then to actually see it happening is a good feeling.
Q4: What do you like least or find most challenging?
The thing I like least is doing documentation, it is important but can sometimes be very tedious depending on how your job wants it done.
Q5: What surprised you when you first started?
It surprised me at how much I needed to learn. There are differences between doing stuff in school and then while on the job. Lots of different technologies to learn and not just programming tools but other things like jira, Confluence, etc.
Q6: How long did it take to feel established or competent?
For me I would say it felt like maybe 6 months to a year. It takes some time to get used to how things are working. Gradually you may end up getting more complex tasks which will help with boosting your confidence in being able to do the job.
Q7: What skills or knowledge do you wish you had learned sooner?
I wish I had learned more about SQL for interfacing with databases as I didn't get much exposure to it when I was in college.
Q8: Knowing what you know now, would you choose this career again?
Yes I would still choose this career at the end of the day. I like to write code and see what I am creating come to life.
Q9: What is your job title/occupation?
Software Engineer
Updated
Jacob’s Answer
Hello! Happy to help with your research — these are great questions. Here are my answers:
Q1: Why did you choose this career?
It actually started with a mild curiosity sparked by YouTube and media coverage of technology. I took a computer programming class in high school on a whim, and I was immediately hooked. What kept me was the problem-solving aspect — there's something uniquely satisfying about working through a complex challenge and expressing the solution through software. That feeling hasn't gone away.
Q2: What does a typical day look like for you?
My day usually starts by scanning emails and checking my meeting schedule to get oriented, then I pull up our Agile board to review whatever tasks are currently assigned to me. From there, the day flows between focused development work, meetings about upcoming features, and collaborating with teammates on their tasks.
The biggest disruption to that routine is release day. Since our clients operate during business hours, deployments and maintenance windows happen after hours. That said, if that kind of schedule is a dealbreaker for you, there's no shortage of projects and companies out there that don't have that requirement — it's very much environment-dependent.
Q3: What do you like most about this career?
Honestly, the same thing that hooked me in high school — solving complex problems. What keeps it exciting is that the definition of "complex" keeps evolving. The challenges I face today look nothing like the ones I faced five years ago, and I find that constant evolution genuinely energizing rather than exhausting. In my current project for example, we are working on a replacement of a legacy component, while also maintain the current legacy component that is in use by our clients. This in itself causes a lot of jostling of priorities sense we don't want to fall behind on our deadlines for our upcoming "2.0" version, while also ensuing our clients are still seeing progress on the current issues facing them.
Q4: What do you like least or find most challenging?
The hardest part for me isn't technical — it's professional perception. I genuinely love developing new skills outside my immediate role. I recently completed a Master's in AI and I am planning on perusing AWS certifications in the future. The challenge is shifting how colleagues who've known you in one capacity — as "the backend guy" or "the support guy" — come to see you in light of your growth. Getting people to update their mental model of you can be surprisingly difficult, even when your skills have clearly expanded.
Finding time to keep learning is also a real challenge, but one I consider worth solving.
Q5: What surprised you when you first started?
The level of autonomy was genuinely shocking. I expected to be handed very prescriptive instructions for every task, but in practice, the how of approaching a problem is almost always left to the developer. You'll get feedback and code reviews before anything is considered done, but the latitude to design and build something from start to finish in your own way was something I wasn't prepared for — in the best possible sense.
Q6: How long did it take to feel established or competent?
I'll give you an honest answer: I try not to chase that feeling. In my experience, the moment you feel fully competent is often the moment you stop growing — and I think that's actually a warning sign, not a milestone. Having a strong foundation of reliable skills is important, but I've found my most meaningful growth by actively seeking out the areas where I don't feel competent yet and treating that discomfort as an opportunity. I'd encourage you to adopt that mindset early.
Q7: What skills or knowledge do you wish you had learned sooner?
Systems thinking, without question. My undergrad did a solid job teaching me how to build individual components, but it didn't prepare me well for thinking about how those components fit into a larger system. Learning to zoom out — to understand the context your code lives in and how it interacts with everything around it — made me a meaningfully better engineer. I'd recommend seeking out that perspective as early in your studies as you can.
Q8: Knowing what you know now, would you choose this career again?
Without hesitation, yes. Like any career, there have been projects I loved and ones that weren't the right fit. But I can honestly say I have never dreaded going to work — and after years in this field, I don't take that lightly. That's not something everyone gets to say.
Q9: Job Title
Software Engineer III
Best of luck with your research — feel free to follow up if you have more questions!
Q1: Why did you choose this career?
It actually started with a mild curiosity sparked by YouTube and media coverage of technology. I took a computer programming class in high school on a whim, and I was immediately hooked. What kept me was the problem-solving aspect — there's something uniquely satisfying about working through a complex challenge and expressing the solution through software. That feeling hasn't gone away.
Q2: What does a typical day look like for you?
My day usually starts by scanning emails and checking my meeting schedule to get oriented, then I pull up our Agile board to review whatever tasks are currently assigned to me. From there, the day flows between focused development work, meetings about upcoming features, and collaborating with teammates on their tasks.
The biggest disruption to that routine is release day. Since our clients operate during business hours, deployments and maintenance windows happen after hours. That said, if that kind of schedule is a dealbreaker for you, there's no shortage of projects and companies out there that don't have that requirement — it's very much environment-dependent.
Q3: What do you like most about this career?
Honestly, the same thing that hooked me in high school — solving complex problems. What keeps it exciting is that the definition of "complex" keeps evolving. The challenges I face today look nothing like the ones I faced five years ago, and I find that constant evolution genuinely energizing rather than exhausting. In my current project for example, we are working on a replacement of a legacy component, while also maintain the current legacy component that is in use by our clients. This in itself causes a lot of jostling of priorities sense we don't want to fall behind on our deadlines for our upcoming "2.0" version, while also ensuing our clients are still seeing progress on the current issues facing them.
Q4: What do you like least or find most challenging?
The hardest part for me isn't technical — it's professional perception. I genuinely love developing new skills outside my immediate role. I recently completed a Master's in AI and I am planning on perusing AWS certifications in the future. The challenge is shifting how colleagues who've known you in one capacity — as "the backend guy" or "the support guy" — come to see you in light of your growth. Getting people to update their mental model of you can be surprisingly difficult, even when your skills have clearly expanded.
Finding time to keep learning is also a real challenge, but one I consider worth solving.
Q5: What surprised you when you first started?
The level of autonomy was genuinely shocking. I expected to be handed very prescriptive instructions for every task, but in practice, the how of approaching a problem is almost always left to the developer. You'll get feedback and code reviews before anything is considered done, but the latitude to design and build something from start to finish in your own way was something I wasn't prepared for — in the best possible sense.
Q6: How long did it take to feel established or competent?
I'll give you an honest answer: I try not to chase that feeling. In my experience, the moment you feel fully competent is often the moment you stop growing — and I think that's actually a warning sign, not a milestone. Having a strong foundation of reliable skills is important, but I've found my most meaningful growth by actively seeking out the areas where I don't feel competent yet and treating that discomfort as an opportunity. I'd encourage you to adopt that mindset early.
Q7: What skills or knowledge do you wish you had learned sooner?
Systems thinking, without question. My undergrad did a solid job teaching me how to build individual components, but it didn't prepare me well for thinking about how those components fit into a larger system. Learning to zoom out — to understand the context your code lives in and how it interacts with everything around it — made me a meaningfully better engineer. I'd recommend seeking out that perspective as early in your studies as you can.
Q8: Knowing what you know now, would you choose this career again?
Without hesitation, yes. Like any career, there have been projects I loved and ones that weren't the right fit. But I can honestly say I have never dreaded going to work — and after years in this field, I don't take that lightly. That's not something everyone gets to say.
Q9: Job Title
Software Engineer III
Best of luck with your research — feel free to follow up if you have more questions!
Updated
Anshita’s Answer
Q1: Why did you choose this career? I enjoyed programming.
Q2: What does a typical day look like for you? I create software that helps organizations work smoothly.
Q3: What do you like most about this career? Before AI, I loved building things from scratch. Now, with AI, I have great tools to help me.
Q4: What do you like least or find most challenging? Getting different teams to agree on a decision.
Q5: What surprised you when you first started? I was amazed by how supportive my teammates were in helping me succeed.
Q6: How long did it take to feel established or competent? It took me 2 years, but it can vary for others.
Q7: What skills or knowledge do you wish you had learned sooner? I wish I was not afraid of asking questions in the beginning of my career. I felt like I would be judged but that is not the case. Your team wants you to succeed more than anyone. They cannot help you if you do not ask the questions to help you move forward in your assigned taks.
Q8: Knowing what you know now, would you choose this career again? With AI changing the job market, I might consider the medical field.
Q9: What is your job title/occupation? Senior Software Engineer
Q2: What does a typical day look like for you? I create software that helps organizations work smoothly.
Q3: What do you like most about this career? Before AI, I loved building things from scratch. Now, with AI, I have great tools to help me.
Q4: What do you like least or find most challenging? Getting different teams to agree on a decision.
Q5: What surprised you when you first started? I was amazed by how supportive my teammates were in helping me succeed.
Q6: How long did it take to feel established or competent? It took me 2 years, but it can vary for others.
Q7: What skills or knowledge do you wish you had learned sooner? I wish I was not afraid of asking questions in the beginning of my career. I felt like I would be judged but that is not the case. Your team wants you to succeed more than anyone. They cannot help you if you do not ask the questions to help you move forward in your assigned taks.
Q8: Knowing what you know now, would you choose this career again? With AI changing the job market, I might consider the medical field.
Q9: What is your job title/occupation? Senior Software Engineer
Updated
Jumanah’s Answer
Q1: I enjoy problem solving and working with computers. Once I tried programming in university, I learned that I liked doing it. To be honest, in high school I didn't know I was going to like it.
Q2: What does a typical day look like for you? I work as a front-end engineer and I code on my computer at home. Have a few meetings a day. I work alot with AI.
Q3: What do you like most about this career? It's very quick to build things, and have direct user impact!
Q4: What do you like least or find most challenging? The most challenging thing is to keep up with everything that is CONSTANTLY changing.
Q5: What surprised you when you first started? How hard it is to set up your local repo :)
Q6: How long did it take to feel established or competent? 4 years.
Q7: What skills or knowledge do you wish you had learned sooner? Everything comes in due time. Theres enough time to learn anything you need to!
Q8: Knowing what you know now, would you choose this career again? Yes!
Q9: What is your job title/occupation? Senior software engineer
Q2: What does a typical day look like for you? I work as a front-end engineer and I code on my computer at home. Have a few meetings a day. I work alot with AI.
Q3: What do you like most about this career? It's very quick to build things, and have direct user impact!
Q4: What do you like least or find most challenging? The most challenging thing is to keep up with everything that is CONSTANTLY changing.
Q5: What surprised you when you first started? How hard it is to set up your local repo :)
Q6: How long did it take to feel established or competent? 4 years.
Q7: What skills or knowledge do you wish you had learned sooner? Everything comes in due time. Theres enough time to learn anything you need to!
Q8: Knowing what you know now, would you choose this career again? Yes!
Q9: What is your job title/occupation? Senior 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.
Updated
John’s Answer
Q1: Why did you choose this career?
I like playing video games and dreamt of building one for myself. Didn't happen. But I build systems now that help the most needy citizens and children in our community. So, I think my younger self would be happy with that.
Q2: What does a typical day look like for you?
I play a senior architect role so my day includes a lot of brainstorming, whiteboarding, discussions, vibe coding, and leadership conversations.
Q3: What do you like most about this career?
The impact that I have with the community and the world in general
Q4: What do you like least or find most challenging?
Having to navigate the politics of a big company is the challenge
Q5: What surprised you when you first started?
There's a lot that I didn't know, but I learned a lot too.
Q6: How long did it take to feel established or competent?
25+ years in and I'm still trying to answer that question. =)
Q7: What skills or knowledge do you wish you had learned sooner?
how to navigate the politics of a big firm and how to build my network. Also, I wish I knew who I was and what I wanted earlier.
Q8: Knowing what you know now, would you choose this career again?
Absolutely!
Q9: What is your job title/occupation?
Associate Vice President, Software Engineering
I like playing video games and dreamt of building one for myself. Didn't happen. But I build systems now that help the most needy citizens and children in our community. So, I think my younger self would be happy with that.
Q2: What does a typical day look like for you?
I play a senior architect role so my day includes a lot of brainstorming, whiteboarding, discussions, vibe coding, and leadership conversations.
Q3: What do you like most about this career?
The impact that I have with the community and the world in general
Q4: What do you like least or find most challenging?
Having to navigate the politics of a big company is the challenge
Q5: What surprised you when you first started?
There's a lot that I didn't know, but I learned a lot too.
Q6: How long did it take to feel established or competent?
25+ years in and I'm still trying to answer that question. =)
Q7: What skills or knowledge do you wish you had learned sooner?
how to navigate the politics of a big firm and how to build my network. Also, I wish I knew who I was and what I wanted earlier.
Q8: Knowing what you know now, would you choose this career again?
Absolutely!
Q9: What is your job title/occupation?
Associate Vice President, Software Engineering
Updated
Claiton’s Answer
Welcome to the team!
Q1: Why did you choose this career?
I've always loved computers, the internet, and hardware. It's been my passion since I was a kid watching my parents work with them.
Q2: What does a typical day look like for you?
It varies depending on your area. At Deloitte, we mostly use Agile methods. Every two weeks, we have a sprint to complete user stories. We have daily stand-up calls to check progress and solve any issues. Depending on your role, there can be a lot of meetings. We also focus on grooming, development, testing, and deploying tasks.
Q3: What do you like most about this career?
It constantly challenges you. Every few months, there are new trends or certifications that push you to learn and grow.
Q4: What do you like least or find most challenging?
The timelines. They're always tight.
Q5: What surprised you when you first started?
Everything! The tools available, networking opportunities, and client challenges.
Q6: How long did it take to feel established or competent?
It really depends on your own efforts.
Q7: What skills or knowledge do you wish you had learned sooner?
Communicating with leaders.
Q8: Knowing what you know now, would you choose this career again?
Yes, definitely!
Q9: What is your job title?
Specialist Master.
Q1: Why did you choose this career?
I've always loved computers, the internet, and hardware. It's been my passion since I was a kid watching my parents work with them.
Q2: What does a typical day look like for you?
It varies depending on your area. At Deloitte, we mostly use Agile methods. Every two weeks, we have a sprint to complete user stories. We have daily stand-up calls to check progress and solve any issues. Depending on your role, there can be a lot of meetings. We also focus on grooming, development, testing, and deploying tasks.
Q3: What do you like most about this career?
It constantly challenges you. Every few months, there are new trends or certifications that push you to learn and grow.
Q4: What do you like least or find most challenging?
The timelines. They're always tight.
Q5: What surprised you when you first started?
Everything! The tools available, networking opportunities, and client challenges.
Q6: How long did it take to feel established or competent?
It really depends on your own efforts.
Q7: What skills or knowledge do you wish you had learned sooner?
Communicating with leaders.
Q8: Knowing what you know now, would you choose this career again?
Yes, definitely!
Q9: What is your job title?
Specialist Master.
Updated
Francesco’s Answer
Q1: Why did you choose this career?
I chose this career because I love solving problems and fixing issues. I've been good at it since high school.
Q2: What does a typical day look like for you?
I wake up, log in to my laptop, join a standup call, and work on my tasks for the day. Sometimes I work late to prepare for the next day. Then, I relax for a few hours before going to bed.
Q3: What do you like most about this career?
Working from home is great because it gives me flexibility. I can handle appointments and make up the hours later. I also like working on big systems that help millions of people.
Q4: What do you like least or find most challenging?
The hardest part is the long hours and tight deadlines, but it's not always like that.
Q5: What surprised you when you first started?
I was surprised by how much my work helps people by giving them access to important benefits.
Q6: How long did it take to feel established or competent?
It took about two years. I had the basics from college, but I didn't feel confident until I gained more experience and learned from my teammates. Now, I help new team members.
Q7: What skills or knowledge do you wish you had learned sooner?
Enjoy what you do. If you're not happy with your work and its impact, you'll struggle with burnout and frustration.
Q8: Knowing what you know now, would you choose this career again?
Yes, but I might focus more on databases or IT to better prepare for AI's impact on our field.
Q9: What is your job title/occupation?
Delivery Analyst, Software Engineering Solutions, Deloitte USDC
I chose this career because I love solving problems and fixing issues. I've been good at it since high school.
Q2: What does a typical day look like for you?
I wake up, log in to my laptop, join a standup call, and work on my tasks for the day. Sometimes I work late to prepare for the next day. Then, I relax for a few hours before going to bed.
Q3: What do you like most about this career?
Working from home is great because it gives me flexibility. I can handle appointments and make up the hours later. I also like working on big systems that help millions of people.
Q4: What do you like least or find most challenging?
The hardest part is the long hours and tight deadlines, but it's not always like that.
Q5: What surprised you when you first started?
I was surprised by how much my work helps people by giving them access to important benefits.
Q6: How long did it take to feel established or competent?
It took about two years. I had the basics from college, but I didn't feel confident until I gained more experience and learned from my teammates. Now, I help new team members.
Q7: What skills or knowledge do you wish you had learned sooner?
Enjoy what you do. If you're not happy with your work and its impact, you'll struggle with burnout and frustration.
Q8: Knowing what you know now, would you choose this career again?
Yes, but I might focus more on databases or IT to better prepare for AI's impact on our field.
Q9: What is your job title/occupation?
Delivery Analyst, Software Engineering Solutions, Deloitte USDC
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