A while ago, I was invited to join a panel organized by an engineering society. The idea was simple: a few professionals would talk about what their day-to-day really looks like. I would cover my role at Microsoft.

The event was postponed, with no new date yet. But the question stayed with me. Over my career, I've worked with many students, and with people who were not students at all. They wanted to know what this job is really like, so they could decide whether to apply if a role ever opened up.

So here it is. Everything below is what I can share publicly. It's my routine, not an official description of the role.

Not so long ago, people said that someone who stayed in the same role for many years was too comfortable and wasn't looking for challenges. I'm not sure that's true anymore.

In my field, the goals, tasks, and priorities change so fast, especially with AI, that the role itself keeps reinventing you. If I had to pick one quality you need most today, it's the ability to adapt.

Let me show you how that plays out in a normal week.

ChatGPT is insanely powerful.

But most people waste 90% of its potential by using it like Google.

These 1,000+ proven ChatGPT prompts fix that and help you work 10X faster.

Sign up for Superhuman AI and get:

Claim your free prompts

Every Monday, the first thing I do is review my calendar for the entire week. This isn't specific to my role. It's a good habit for anyone.

I go through every meeting invite and every task already scheduled, and I color-code them by group:

Why bother? Because most of my time needs to go to customers. If my week fills up with internal meetings, that's a problem. A quick look at the colors tells me right away whether the balance is off.

And yes, there are a lot of internal meetings. That's not unique to Microsoft. My customers tell me that having two or three meetings booked in the same slot is almost normal for them too.

Once the week is organized, I decline what I don't need to attend. Then I prioritize the overlaps, because I can't be in two meetings at once.

Technology helps here. Many meetings are recorded, and AI gives me a summary afterward. For almost every meeting I miss, I read the summary and check one thing: is there an action on my side?

I have customer meetings almost every day. Here's a habit that has helped me a lot: I don't spend the day thinking about today. I spend it preparing for the days ahead.

That way, I never open my calendar, see a meeting, and have no idea what it's about. When I have to speak, present, or lead, I already know what I'm bringing.

Everyone's time is valuable. My presence in a customer meeting has to add something, or it shouldn't be there.

For meetings I lead, I email the customer about a week ahead. I ask if there's a topic they'd like to discuss. If they have one, I prepare for it. If not, I bring a topic myself.

It's a small step. But it means I always know what each day and the days after it look like.

Meetings come in every shape. To be honest, not all of them are interesting. But two kinds usually are.

Customer meetings. This is where I hear what customers actually need, in their own words. Most of the real work starts here.

Product engineering meetings. Here we learn the details of a feature or something about to launch, often before it's public. That gives us time to prepare, so we're ready to help customers on day one of a new version.

If all I did was attend meetings, a big part of my job would never get done. So I use the open slots in my week for work that needs calm and attention:

Many colleagues block their calendars for this, and it works for them. I usually don't. If I have nothing scheduled, I leave the slot open. When someone needs me, I check whether what I'm doing is truly urgent. If it isn't, I make time for them.

A fully blocked calendar makes you hard to reach. I'd rather stay reachable.

Every day, several colleagues reach out with questions. I take that as a compliment. It means they see me as someone who can help.

Some of them told me why they come to me: I answer quickly. Even with a full schedule, I don't leave messages sitting for hours. Usually I reply within minutes. If I'm in the middle of something urgent, I finish my train of thought, then I answer.

I know about the cost of context switching. Every interruption means time to get back into what I was doing. For me, it hasn't been a reason to stop helping.

There's another reason too. The more senior you become, the more you're expected to help others succeed, sometimes more than doing everything yourself.

It takes time. But it's rewarding to see what happens after you introduce two people who needed to meet.

I work with some customers directly, and others indirectly. Indirect means helping the colleagues who support those customers.

For my direct customers, there's account management work too:

That last point matters most. Delivering something doesn't mean delivering value. On the Mission Critical team, customers expect a very high level of quality, and they pay for it.

For a technical person like me, admin work isn't exciting at first. For some, it never will be. But over time, I understood why it matters.

Being very good technically isn't enough if you don't understand the business. You need to know your own company's business, the customer's business, and what they actually need.

Sometimes the honest answer is that we don't have a solution for that. You don't say it bluntly, but you never lie or mislead. You look for an alternative the customer can really use. That only works if you understand their business.

It's common to get a meeting invite a day before, sometimes just hours before. Unless it's truly urgent or critical, I usually don't accept.

A week already full of work can't absorb surprises without breaking the plan. That's how many people end up feeling lost: no real plan for their day.

We have a lot of required training at Microsoft. Some of it covers the business itself: how the company works, its guidelines, and its priorities. A lot of it is technical, across many areas.

On top of that, we now take industry certifications. This year I have two to pass:

That means a lot of study time, on top of the regular work.

If you looked at my month, it would look a lot like the week I just described. The format barely changes. What changes is the work itself.

In many roles, the tasks repeat or look very similar year after year. In mine, almost nothing repeats. Sure, a customer may ask for something close to what I did for another, and I adapt what I already have.

And yes, I use AI to speed up my work, like everyone should. So creating new material doesn't take as long as it used to.

Here's the catch. If I don't know an area well, or something has changed since I last looked, it still takes real time to learn it.

You can't take a customer's question, ask AI for content, and present it ten minutes later. The customer will notice, from the way you talk and explain, that you don't really know what you're talking about.

That's why I don't think staying in one role means being comfortable anymore. When the work changes this fast, staying good at it is the challenge.

Subscribe free so you don't miss them.

If you're thinking about a career like this, or you're a student wondering what happens after graduation, reply to this email. Tell me what you'd like to know more about. I read every reply.

If you know someone who's curious about life in tech, forward this to them.

How I write: every post starts from my own notes and experience. I use AI tools to help draft and edit, and I review every word before it goes out.

Disclaimer: The views expressed in this article are those of the author and do not necessarily reflect the official policy or position of Microsoft. The author is a Microsoft employee.