3 answers

What are some examples of actual duties at a computer science job?

3
100% of 3 Pros
Asked Viewed 311 times Translate

I am planning to work in the #computer-science sector after graduation, but I lack knowledge on what actual employees do on-site daily. When looking for this answer, I often see descriptions such as "computer engineering" or "software developing", but these doesn't paint the picture for me as to actual duties. Though I know such tasks differ greatly from job to job, some examples would allow me to place myself comfortably in that future office.

3
100% of 3 Pros

3 answers

Omer’s Answer

0
Updated Translate

From my experience, in my first software engineering job, I was tasked with building an internal iOS app that would help roughly 300 people within the company perform the duties more efficiently. This involved understanding the problem and thus coming up basic features of the app. I also helped design the user interface, and how the user would interact with the app. I then designed how I would structure my code (very important) and created a roadmap of the project. Finally, of course, I coded it up! It depends on what type of company and team you're working on. For example, a software engineers duties will reflect mine at a startup versus at a big company where you would be coding features, bug fixes, refactoring legacy code, and not involved with product development. It's a fun, flourishing, and rewarding field! If you enjoy building things and solve problems, then you picked an awesome career!

0

Jacob’s Answer

0
Updated Translate

Some examples of actual duties of a computer science job are to design software solutions, document them and then write actual code to implement your designs. Software development in a team environment may also involves design review, code review, testing, and likely integration with code from others.


Computer science jobs are to write software with little concerns of underlying hardware while computer engineering jobs may involve certain hardware instruments. Writing web applications, for instance, you don't worry about how underlying hardware works but if you are to write software to control robots you need to understand the hardware characteristics so that you can program them.


Hope this helps.

0

Glenn’s Answer

0
Updated Translate
The duties will vary greatly from job to job and position to position. I can explain how MY experience was. Of course, there was programming. But there is also a ton of overhead. Don't expect all of your tasks to be like "build X to achieve Y". They typically come in like "X is broken.. Fix it, please". Or "we'd like X, but is it doable? E.g., we'd like you to make this software do things that require access to disparate data sources.. And we have no idea where they are or what it will take.. good luck!

These are some advanced examples but that is what they pay you for. Break down barriers and make technology do amazing things.

You won't be stagnant in the field, I promise you that.
0