What is a typical day on the job in a computer related profession

Tobe -

There are many different positions and opportunities in the computer-related field. It takes a lot of different skills and roles to create products like web or mobile applications. Depending on what you are interested in, there are many options.

Nicholas outlined several of the roles above, but many related opportunities benefit from a solid technical/computer-related understanding. Some examples are:

Product Management: Here you will work with customers and stakeholders around the company to define future versions applications, integration, and tools.

Design: Here you define what the user will experience as they use your product. From the flows and interactions to the look and feel.

An often overlooked part that most of the computer-related roles rely on communication and teamwork.

Good luck!

It all depends on what type of computer related profession you are talking about, If you care to elaborate more on your interests I would gladly, answer to the best of my knowledge.

Here is a snip it of some ideas:

Techncian(general) :

You will be perform maintenance on any gear you are responsible for. If anything goes wrong or breaks, you will have to fix it, a lot of troubleshooting. You may be the one who operates the equipment on a dialy basis.

System admin:

You could be making accounts, pushing software updates, managing security settings. Setting up new workstations, you would be in chage of any movement of equipment. You may be who they call people lose internet connectivity, You will also be the go between for any IT specialists under you and upper management.

Computer repair:

Waiting for things to break it will get brought to you to be fixed.

Ethical Hackers:

Usually hired on by companies for short term, you would go in and find any vulnerabilities in a companies security scheme. Tell them how to fix it and help make them more secure.

Helpdesk:

You would be answering phones, hearing out people's issues they may be having on both hardware and software levels and help them troubleshoot, and get what ever products they may be having issues with working again.

Hope this helps. But if it doesn't please reach out with more information and I will gladly break it down a little better.

Hi Tobe,

As others mentioned, "a typical day" in a computer or tech related profession depends on the specific role. However, I would like to add that "a typical day" would also depend on the product your company is building.

Some products, like the iPhone for example, is built for individual users like you and me. When we look at this product deeper, an iPhone is a hardware (a physical device that you can hold) with software that operates inside the hardware (softwares are apps, such as mail, calendar, games, etc). If you're in a company that's building a product like the iPhone, imagine all the different jobs and roles that were mentioned here (such as Product Manager, Designer, Technician, Software Engineer, Support Agents) all working together to build a product that you and I can enjoy using them. Below are few examples of that:

• Product Managers work with App Designers to design and create beautiful apps
• Product Managers will also work with Software Engineers to build these apps the way they were designed
• You can also have Product Managers and Designers working on the hardware side of things (physical device) to design the hardware aspect of the product.
• Hardware Technicians can work with Software Engineers to make sure all the app components are compatible between the software and hardware for example.
• You also have Support Agents who are helping individuals like you and me, whenever we have issues with the Product. Then, they report some of the big issues back to the Product Managers, who then work with Designers and Software Engineers to fix the problem. This also helps improve the product.
• and many many many more!!

In conclusion, what I want to point out is that "a typical day" is very different for every role and for every product that a company is building. However, "a typical day" for the majority of tech roles will involve working across many teams to make sure that what you're responsible for is accurately and efficiently helping to build great products.

As others have said, "computer related" is a very broad profession. To add to what others have said (as they focused more on product development), I started off with development but quickly went down the path of consulting as I enjoyed solving problems for users more than doing backend development. I found myself in professional services first before finding my way into a customer-facing role at a software product company.

Professional services is a mixed bag of consultants, developers, engineers, analysts and project managers - depends on what they deliver to the customer. They often create specific bespoke solutions to problems that software vendors don't do e.g. a deployment of some software that needs to integrate specifically with a customer's internal systems. These sorts of projects can be hard work but very rewarding and can be very busy especially just before the delivery date. Depending on your role, you will likely be doing team meetings, development/solution design, and the golden nugget, communicating with the customer. The latter is almost as important as the technical aspects and a skill that can't really be taught except through practice and exposure.

As a consultant, my days are usually filled with:

• Meetings - either internally or with customer
• Doing research on action items/questions from the customer - this is the fun bit, I get to sandbox and play depending on how much time I have
• Solution design of what the customer wants to achieve
• Responding to emails - either internally or with customer

Because I don't work with a single product, my days are usually quite interesting as there is always an interesting problem to look at and customers somehow find inventive ways to push the functional limits of the products they're using!

Hi Tobe,

So I today I work at Twilio as a Senior Solution Engineer. A Solution Engineer role is a pre-sales gig that focus on meeting with potential / existing clients and showing them how Twilio can fit in their customer success story today. I code half the time and the other half is sending emails and meeting with clients.

I like this role a lot compare to being a Senior Software Engineer. When I was in a Software Engineer I was delivering code to a clients and I have small interaction with the clients. This role was great in the beginning so I can get my confidence as a developer, but it gets old very quickly.

I hope this helps.

Yeah as stated above it depends on the job you are in.

As a Software Developer or Engineer its more around solving a problem using software skills. Coming up with a technical design, coding, testing and maintaining(incase any errors or bugs).

If you can elaborate a little more, I can answer better