I’ve never had an office job and I’ve always wondered what it is a typical cubicle worker actually does in their day-to-day. When your boss assigns you a “project”, what kind of stuff might it entail? Is it usually putting together some kind of report or presentation? I hear it’s a lot of responding to emails and attending meetings, but emails and meetings about what, finances?
I know it’ll probably be largely dependent on what department you work in and that there are specific office jobs like data-entry where you’re inputting information into a computer system all day long, HR handles internal affairs, and managers are supposed to delegate tasks and ensure they’re being completed on time. But if your job is basically what we see in Office Space, what does that actually look like hour-by-hour?
I work in data refinement. I stare at numbers until I find some that feel scary. Than I put those in a bin.
It’s all mysterious and important, I assume?
Typey type, typity type type.
I just check email all day. Like that’s 80% of my job. My entire job could be done from anywhere. I don’t do as single thing that isn’t in my laptop. But I still sit at a stupid cubicle.
Be engineer, draw pictures with numbers next to it that mean that your picture is important. Give picture to someone who agrees that your picture is important and presses on your picture with a stamp. Then give your picture to people that don’t work at desks to make a thing that looks like your important picture.
The best part there is that you’re not responsible for any damage your drawing causes if you’re not the one with the stamp!
I’ve never really had a “desk job” where my job was to sit at a desk 9 to 5. But a few of my past occupations included at least some desk time, such as:
- Flight instructor. Most of my day was spent either in the classroom briefing/instructing, or in the plane instructing/overseeing. I spent a significant portion at a desk creating lesson plans, updating logbooks, communicating with students, grading assignments, communicating with other instructors, communicating with our Designated Pilot Examiner, filling out FAA paperwork, that sort of thing.
- Aviation mechanic. This is more of an administrative job than the posters at your local trade school would lead you to believe. An owner/operator/pilot/plane haver guy brings you a plane for an annual inspection, now you have a research project. What exact make and model is this thing? What modifications has it had during the 50 years it’s existed? Under what authority were those modifications made? Is it still in original or correctly modified condition? Are there any manufacturer service bulletins or FAA airworthiness directives issued for this aircraft, and I mean THIS aircraft, or its components? Like, they’ll call out ranges of hull numbers in these things. Then there’s recording all the shit YOU did to the plane while it’s here.
- Project manager of a short-run job shop. First up: Meet with the customer and massage the idea they have out of their brain. 3 times out of 10 tell them which aisle in Wal-Mart they can find what they want, 1 time out of 10 explain why what they want isn’t physically or technologically possible. Once I’ve got a good idea of what the customer wants, it’s time to do some preliminary design work, research materials and prepare an estimate, deliver this to the customer. 7 in 10 times we hear back from that, get the okay to build, now it’s time to order materials, do any of the design work which may include CAD design, electrical design, computer programming, whatever. Scheduling and directing my team, contracting with any talent I don’t have in-house, the all important staring at a wall visualizing fourteen different variations on some little yet pivotal detail, and then I’d end up in the shop running laser cutters or lathes or table saws or whatever to get it built. Then the most important part: Invoicing the customer.
I rapid-fire solve technical problems all day.
I also place orders. But that’s the easy stuff.
Just look up the movie “Office Space” it pretty well summarizes it all.
Well, I generally come in about 15 minutes late. I use the side door; that way, my boss can’t see me. And after that, I just sorta spaced out for about an hour. I stare at my desk but it looks like I’m working. I do that for probably another hour after lunch, too.
I’d probably say in a given week I probably do about 15 minutes of real, actual work.
I’m a chemical engineer at a plastics company. When I’m in the office I’m looking at data and making decisions based on that, like whether to stop or increase production rates, whether to shut something down for maintenance, or finding what piece of equipment is broken and causing a problem. I also design improvements to the process like finding better ways to run the machinery, new equipment that gets us more capacity, or new ways to control the equipment. I would say about 80% of my time is in the office and 20% is in the manufacturing area.
you spend most of your time “hopping on a quick call,” replying to an email reiterating what you said last time, and doing the needful
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.
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.
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 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).