No Stupid Questions

I am a project manager for an automotive part maker.

My job is emails, tickets and meetings on the computer all day every day.

My job is to make sure the engineers work on the correct tasks at the right time. I am responsible for the planning and delivering on time (delivery is a part with mechanical, electronic and software working together correctly). I am responsible to keep the project within the budget. I decide on priorities, what the team needs to be working on first, second and third. I am responsible for making the team work according to the quality process, which means they must follow to correct steps, design rules, reviews and create the appropriate documentation.

I can tell you, sitting in front of the screen all day, is harmful to health (in a different way than a physical job is). For example, almost everyone I work with is wearing glasses, my own vision has degraded a lot.

I'm a pet product specialist for a pet food manufacturer. I respond to customer emails, calls, and chats about our products. This could mean assisting pet owners in selecting products based on their pets' unique medical or physiological needs, answering nutritional questions, handling complaints, and more. In my downtime I work on reference materials for the rest of the team, continuing education on animal nutrition (my last class was on avian flu in pet foods), and prepare promotional materials for expos and trade shows.

On light days we do a lot of sharing memes, shit talking in group chat, dicking around on the Internet, and finding other creative ways to fuck off.

Lots of microsoft excel and bullshitting

I’ll just give some examples.

We know that construction workers build things, but many office workers are behind them. When you hear “office worker,” think “information worker” as that will help.

What information?

Someone has to pay the construction workers. This involves accounting and payroll tasks best done at a computer.

Architects design the project being constructed and this is done in an office.

There are permits, inspections, regulations, taxes, real estate licensing etc to clear the project and this is done through computers and telephones.

Coordination of the different work crews must be planned - we don’t just ask concrete, civil engineers, plumbers, electrical, and landscaping to all show up on the same day and just figure things out. These things are scheduled out and arranged with many different companies / subcontractors and this is mapped out on a computer and agreed to over the phone.

The new apartments being constructed will need tenants to rent them. Billboard space is going to be rented near the building. A graphic designer is designing the billboard on a computer in an office. Someone else is calling the billboard company to arrange the large scale printing of it and to purchase the time it will be displayed.

I’ll stop. This is off the top of my head. If construction workers, with their obviously valuable and easy to understand work have this many office workers behind them, you can imagine how it’s even more complex for things like tech companies.

Hour by hour, my job evolved from taking calls from clients who owed us money, to then answering questions from agents who weren't as skilled at it as I was.

In the process of being promoted, I was asked to join a daily meeting of over 100 people talking about the issues affecting our department.

Once in a great while, something came up in that meeting that gave me the heads up to prevent chaos in our department and stress to members.

There's a whole shitload of cogs turning in modern corporations. There's also a huge danger of people leaving and nobody understanding why the cogs are there.

I do IT governance. When someone builds a server or a firewall rule or a database in a way that could leak patient data to somewhere it shouldn't be I find it and make them fix it. Generally people don't want to redo something that they've done so there is a whole process around who you tell so that everyone know the problem and who has to fix it.

I work for a consulting firm, so a project is whatever our client has contracted us to do, for the objectives and timeline we've agreed to in the contract. We do workforce readiness, largely. So the client might be adopting a new software and wants us to create the employee training on it.

We contract with them for training to help their leaders deliver workshops, maybe some e-learning modules and assessments, and to have it done in a certain number of weeks. That's an example of a project, and typically we'll have a small team on the deliverables for it: the modules and the workshops. Meetings are to check in on progress, fix any issues, meet with the client or their subject matter experts. So that's my office job, though luckily it's been remote for me since covid.

Just look up the movie “Office Space” it pretty well summarizes it all.

Let me take a liberty to answer for everyone.

Most of human activities now generate a lot of data, or require a lot of data to happen.

It can be anything from construction blueprints and software, to more subtle things like goods distributions on the shelves or schedules or whatever.

Behind everything you see in the world there is a data management, and behind this data management there are layers of people making those decisions from top to bottom.

Some of those people managed to create spaces where all they have to do is to say "nothing on my side" during the meeting.

Others are the opposite, have to take the toll and process the massive amounts of this data.

This is what the office job is nowadays.

Recently finished university and got my first job in basic accounting. All I do is well, watch videos on phone, messages people and a bit of accounting here and there. Boring, relaxing and that’s about it. Going to stick with it for a year and then prolly find new work.

I'm a translator. I translate everything you can possibly think of. HSE documents, emails to illicit lovers, websites, I'm your person.

Here's my office work:

Since 2005 I worked as a TV news producer. We started the day with a morning meeting where reporters pitched stories and it was decided what they covered that day. Then as a producer I organized the stories in the newscast and found other stories which I was responsible for. That ranges from finding a worthwhile press release to interviewing people myself (usually by phone, and someone's video chat,) or just finding info by going through data. I would write those, then decide what visuals, audio elements, camera shots, graphics, and anchor reads went with it.

Then during the live newscast I timed it, and made adjustments on the fly when necessary. (Killing stories, finding ones to insert, and adding breaking news.)

I let my contract end almost two months ago, choosing not to stay in news. I've been applying to mostly other non-TV news office jobs. That's including producing other video projects, but also technical writing and marketing positions.

It really varies too much between industries to give a single answer. Someone at an insurance company is going to be doing something vastly different than an accountant, and they'll be different from an architect (though only part of what architects do is in the office).

That being said, office work for the average worker, as in a salaried or hourly worker with a fairly rigidly defined job description, is usually going to be paperwork, even though there's not always paper involved.

It's taking information and moving it around, in one way or another.

As an example, one of my exes worked for a company that handles employee benefits, investments, and other services to other companies. Lets say a worker has an IRA, gets a nice insurance policy, and there's a pension fund.

Her job is to take data from the company that contracted with the company she worked for, enter that data into the system in an properly formatted way, run calculations, then trigger the appropriate funds being moved from one account to another. No meetings unless something goes wrong. It's all day data entry and management.

Now, before that job, she worked at a tax service under a CPA. She would get actual paper back then. Receipts, forms, and look for deductions for the client, then print out the church correct tax form, have the client sign it, then send it off. She would finish one, then start the next, all day long during tax season. Off season, she would be receiving accounting records from clients and entering them into the system of the company she worked for, and process things like withholding.

Pretty much, neither of those jobs required leaving the desk her entire shift.

Now, my best friend runs a department at a community college. He leaves the actual desk frequently. There's meeting with his superiors, meetings with his underlings, meetings with vendors, budgeting work, orders, policy decisions, disciplinary decisions, and the list keeps on going.

My best friend's husband was a flunky at architectural firm. When he was on a project, his job was drafting designs per specifications given to him. It required doing some oh the work, meeting with the architect, then changing anything per their decisions, or finalizing those plans. From there, once plans were ready to be used by someone to build something, he would essentially coordinate between contractors and his office to troubleshoot any snags with things like permits, supply issues, etc. So it was usually a lot of desk with work over a few weeks or months, then weeks or months barely at a desk, but still mostly in office.

Myself, I never had a long term office job. But, during recovery from a work related injury, I was pulled into the office of the home health company I worked for. My injury precluded patient care, but I was okay for light duty.

I was placed in staffing. I would roll in early, about 6 AM, and check for any call-ins. That would be employees needing to have their case covered by someone else for whatever reason. I would call other caregivers based on availability, proximity to the patient, and hours already worked. The last one was to avoid overtime unless absolutely necessary.

The software used, I would type in the name, and their details would pop up with their address, phone number, and current schedule. Same with the patient.

The first step for me was always to check the patient's location, because that let me filter out people on the list as available by proximity before anything else, since I would have to just go down the list. I'd enter a name, check the location, and decide who to short list. Once I had the short list, I'd verify they were not going into OT, and start calling, with priority given to employees that had requested more hours.

Most of the time, a call-in would take fifteen to twenty minutes to resolve.

Once the morning run was over, it would be time for a quick coffee and come back to handle any afternoon call-ins in the same way. Have lunch, then repeat for evening/night call-ins.

During the few months I was doing it, most of the time, that was handled by maybe 2 or 3 in the afternoon. Some days it was all handled before lunch, and very occasionally by the time the coffee break was available. Very variable because there are days when folks just didn't call in as much. And there were days it was crazy, particularly when there'd be something like a bad flu run through local schools and the parents would either catch it, or need to take care of their kids.

But, usually, the afternoons were either straight up bullshitting with the ladies in the office (not flirting or messing with, just swapping healthcare war stories), or helping with sorting out patient intake and/or prioritizing staffing for new patients. A new patient means you either shuffle staff around, hire new caregivers, or break it to the bosslady that someone is going to need overtime until the other options could happen. Since I knew pretty much everyone, I was good at figuring out who would be a good pick for a patient's needs.

A few times, I did some of the initial onboarding for new caregivers. Get them the employee handbook, introduce them around, talk about expectations, that kind of happy horseshit.

Tbh, I liked it most days, but not as much as patient care. Don't think I could have done it for years or anything, but as a temporary thing, it was nice.

See? Totally different daily routines and work between industries.

Account Manager at a marketing agency, I run ~5 marketing departments with a mix of my own staff, outsourced contractors and employees at my clients' businesses.

We create marketing campaigns that consist of a set of emails, social posts, ads, thought leadership articles, blogs, landing pages, downloadable PDF reports and the attendant reporting on how they performed, plus finding and targeting the audiences in various segments. It's a mix of database management, creative writing and design, project planning and communication meetings.

I generally spend about a 1-2 hours a day on each client, plus meetings. We make and send the collateral, get approval, execute, track, measure, compare, make a strategic conclusion, repeat

I work in an office as a network administrator. Largely my day to day is a meeting every morning to go over what everyone is doing for the day, then looking through and responding to all the alerts that came up from all the servers I manage(things like failing backups, unexpected reboots, stopped services, strange login behavior, etc)

Then, if I still have time in the day, I put time towards some of the long term projects I have which largely consists of finding things that can be automated and scripting up solutions to that

I help our customers make their business processes less stupid, time consuming and riddled with errors. Practically speaking it means I go to meetings, documentation process changes, build out business process automations, and attempt to convince an unwilling workforce that no, 17 spreadsheets is not the only or best way to run a business (change management).

Today I have...

• spoken to a team member under my supervision about their workflow (30m)
• reviewed applicants for a role on my team (15m)
• prepared some financial reports for a client (1h)
• prepared some financial forms for that client (1h)
• figured out the right methodology for a complex letter for that client (30m)
• drafted a complex financial / legal letter for that client (1h)
• felt stressed about this client's situation (45m)
• applied a check list to this client's project (30m)
• reviewed and attended to some emails (30m)

It's time for lunch now.

In my case, I work IT for a healthcare company. Current major projects of mine include trying to migrate servers from our data centers to the cloud and setting up Disaster Recovery options. These are 2 of my 22 current projects.

On the day to day, I'll determine what it takes for an application to run and how does it communicate to find the most optimal way we can build it within vendor and enterprise specifications. An example might be...

• Application is a hosted Web Page
• It stores all of its data a SQL Database
• Is used by locations outside of our network, so this will require
  • A Public Endpoint to be accessible outside of our network
  • DMZ'd Network Security Group or Application Security Group to manage exactly what and be accessed from where
• Is a low-tier application that does not require low latencies

In this case, I can decide to use a PaaS Web Server and PaaS SQL Server, so that I don't have to manage security and updates of the Operating System in the future. After deciding this, I might diagram how everything will connect and communicate, then build the infrastructure to fulfill this design. Lets say that means going to Azure (the cloud provider), building the Web Server and SQL Server, creating the DMZ rules (443 inbound from anywhere to WebServer and 1433 only from WebServer to SQLserver) I set up a backup system for both of these to take daily backups in case anything goes sour, then determine what steps are necessary to make sure that I can minimize the downtime for the migration, since it will take time to restore a backup from the data center's version into the Azure version.

I'm trying to keep things simple-ish for this example because there's a wide variety of tools, environments, and processes that come into play for any one of these builds. Most of the time is spent not in actively moving things, but in determining best courses of action and minimizing downtime, especially being a healthcare environment where an application could be actively impacting a patient's care.

Of course there's all the other stuff you might expect, like emails about a server not working right and meetings about how management wants to use more AI while needing to cut costs to the organization because we're "not currently economically sustainable."

While by no means a comprehensive view into the work, I hope it grants some insight into the role!

I worked in software development as a QA engineer. Every day I'd load the current build of the OS and test for bugs, check that fixed bugs are truly fixed, and write bug reports. Once a week it was on me to come in early and do a quick rundown to see how usable the build was and then send a report to the entire org so people knew if it was too problematic to install and remain productive.

I worked in IT at a place that was perpetually under water. I spent all day troubleshooting either end-user computers or servers. We never had a break from tickets, so there was always work to be done unless the holidays were in season and users were taking time off.

I worked IT Exec Support for a high-up individual. It required being on-call and meeting them at their office in different cities and being the personal IT for their staff. It was pretty unpleasant in that the exec never communicated effectively and was insulated by their staff such that they had unrealistic expectations about how things should work. I was proud to land the job, but I'm glad to be done with it.

I now work in IT at a place that is super organized. I mostly wait for someone to call with an issue. Most things are pretty easy to fix. Some days I have to administer our inbox and direct users or create tickets. During that time, I'm always busy. On the days when it's not that, I surf Lemmy (on wfh days) or read a book (on in-office days) between calls. I also configure devices for people and the like (think upgrades and new employees). I'll probably stay here until retirement cause it's the easiest job I've ever had.

They do the work in the office. Just like work from home works in the home.

And a florist works in the.....floor.

Does finance count? I'm usually studying something in the alternative data space (that is, using non-financial data to make decisions on investments) so I can, in the end, make a presentation or deliver a product to someone. For example, an analyst decides to study a clothing company and asks me to scrape their prices in the main Latin American markets (because he thinks they can grow there or something). So I do that for a while and report back to him what I found. If it is interesting, I may be tasked with implementing something in our Excel add-in so he can plug that information into his own models, or I'll need to develop a model myself.
Lots of spacing out, browsing lemmy and playing bullet chess on my phone, too

I work as Adminstrator and Developer for Medical Software in a Hospital.
Most of my days are either spend preparing for future planned Software deployments, checking if they can meet our needs. Fomulating out the requirements and data imports and exports to various existing systems. On others like today I'm a bit more hands on and actually fix a bug in an application, laid out a plan for QA testing and eventual deployment of the new release and wrote some documentation so that should I vanish from the face of the earth, the stuff I do can be picked up by someone else.

I largely analyze data and create software to automate business tasks. This allows people in my company to make informed decisions about the business, how money is or should be spent, who & where to hire, helping non-techical people automate repetitive tasks. I also present/interpret data and influence decision-making.

This might mean creating forecasts. Automating data analysis with reports. Building data sources (gathering and manipulating data from different places and compiling it). Building interactive software or excel sheets for non-technical users. Creating white papers or presentations on analysis I've done. Etc.

I use excel, google sheets, google app script (basically javascript), tableau, python, and SQL.

In Office Space the main character seems like some kind of analyst, maybe a project manager who makes sure things are getting done as planned and addresses. The other two guys from the office were software developers if I remember correctly. The annoyimg lady answering phones was a receptionist.

So it varies widely depending on what needs to be done and who it is assigned to. I have worked in the same IT department for over 15 years and had four different positions working with the same large software systems doing very different work (help desk, testing, requirements, project management). I interact with security people, administrative assistants, and even directors as part of the work.

'Office work' is more of a description of the location and setting than the work itself.

there's a billing dept in my company. i assume they handle billing. they have an office. they sit at desks a lot. they make calls and verify insurance and process payments and whatnot.

I have a friend who is a software dude. i dunno what he does but I'm assuming it involves offices, desks, and software.

I’d totally like to share what I do at my office job at the equivalent of the IRS in my country, but that’s classified :(