4 answers
6
Updated 348 views

what does a typical day look like for a software engineer?

I am a junior in high school, i want to be a software engineer. I want to see what does a software engineer do in a day.

computer-science programming computer-software careeradvice coding software-engineering futureengineer careergoals javascript highschoolstudent python softwaredevelopment webdevelopment softwareengineer buildsoftware
Answer This
6

3 answers

0
Updated
Share a link to this answer
Share a link to this answer

Teklemuz Ayenew’s Answer

A software engineer writes code, designs and improves systems, fixes bugs, tests software, reviews code, and solves technical problems while collaborating with team members. They also understand requirements, discuss work, and take part in planning meetings. The work is iterative and involves continuous improvement.



Software engineering is a broad field that includes web development, mobile apps, backend systems, data, DevOps, cybersecurity, and Artificial Intelligence. If you are interested in programming fundamentals, problem-solving, AI, or data, you can start with Python. If you are interested in building websites and web applications, you can start with HTML, CSS, and JavaScript. You can also follow roadmap.sh for structured learning paths. Then, practice by building simple projects like a portfolio website, to-do list app, or quiz app, improving them step by step.
0
0
Updated
Share a link to this answer
Share a link to this answer

Sandeep’s Answer

Hello Vivi,

A typical day for a software engineer usually includes writing code, fixing bugs, attending team meetings, and collaborating with other engineers to solve problems. Depending on the project, they may also review code, design new features, or test software before it is released.

One thing that surprises many students is that software engineering involves a lot of teamwork and communication not just coding all day.
0
0
Updated
Share a link to this answer
Share a link to this answer

Andras’s Answer

You usually work in a team and the team has a list of smaller tasks that can be individually assigned. So most of the time you are working on a dedicated task, which can be coding a new functionality, fixing a bug, setting up environments etc. But many times you also need to spend some time on learning, for example getting familiar with the software components you are working with, or studying new technologies your team is using. Last but not least you are participating in meetings or calls, e.g. on short daily sync or longer team meetings. To break it down I would say at least 6-7 hours are spent on effective task work, while up to 1-2 hours on learning and meetings.
0