Dating someone whose job comes first (sometimes)

There's a specific moment that decides how these relationships go. It's the second cancellation.

The first one is fine — everyone gets one. The second is where you find out whether you're dating someone with a hard schedule or someone who isn't that interested, and almost everyone reads it wrong in one direction or the other.

Getting that read right is most of the skill. The rest is logistics.

Who this is actually about

Surgeons and residents. Founders in the first three years. Litigators in trial. Anyone on call. Investment bankers, certain kinds of consultant, people running a restaurant.

What these have in common isn't hours — plenty of people work long hours predictably. It's unpredictability. The job can take the evening with four hours' notice and there's no version where it doesn't.

That's the actual thing you're dating. Not the hours, the unpredictability, and it demands a different structure than most relationships run on.

The distinction that matters

Schedule problem or priority problem. Almost every argument in these relationships is really an argument about which one is happening.

A schedule problem looks like: they cancel, they're visibly annoyed about cancelling, they propose an alternative before you've asked, and the alternative happens.

A priority problem looks like: they cancel, the apology is smooth and slightly practised, no alternative is offered, and rescheduling is left to you. Repeatedly.

The tell isn't whether they cancel. It's what happens in the ninety seconds afterwards. Someone who wants to see you starts solving for the next time immediately, because they're annoyed too. Someone who doesn't lets it drift, and drift is the answer.

The story we hear most often has the same shape. Two cancellations in three weeks, and the person on the receiving end spends a fortnight deciding whether to end it. Then a text arrives at 6.40 on a Sunday morning: the only window that existed — asking about something they'd mentioned once, ten days earlier. That message settled it, and it took eleven seconds to send. The hours were never the signal.

Read effort, not availability

This is the single most useful reframe available and it takes most people months to arrive at.

Availability is a function of their job. Effort is a function of how they feel about you. Conflating the two will make you miserable and will also make you wrong.

Effort looks like: a message at seven in the morning because that's the window they had. Remembering the thing you mentioned. Protecting a specific evening two weeks out. Telling you the schedule in advance rather than apologising after.

None of that requires much time. All of it requires attention, and attention is the resource that actually indicates something.

Someone genuinely interested with a brutal job will find fifteen minutes. Someone not interested will be busy in a way that has no fifteen minutes in it anywhere.

Structure that works

Short and frequent beats long and rare. Forty-five minutes on a Tuesday, repeated, builds more than one elaborate Saturday a month. Consistency reads as interest; scarcity reads as ambivalence whatever the intent.

Protect one recurring slot. Same evening or same morning each week, defended by both people. Having one thing that survives the chaos matters more than the total hours.

Make plans cancellable without drama. Meet near their work. Choose things that cost nothing to abandon. A tasting menu booked three weeks out turns every emergency into a crisis; a drink round the corner doesn't.

Ask for the calendar, not for reassurance. "When's your next stretch of call?" is a better question than "do you actually want to do this?". One gets you information; the other gets you a sentence that means nothing.

Some of this overlaps with dating as a busy person yourself, which we covered in dating apps when your time is the thing you have least of.

What you should actually expect

Being deprioritised sometimes, and not taking it personally, because it usually isn't personal.

When something goes wrong at work for a surgeon, a founder or a litigator, it doesn't wait. That's not a values statement about you. Treating each instance as evidence about the relationship will exhaust both of you within two months.

What you should not expect is to be deprioritised permanently. There's a difference between a hard season and a pattern, and the difference is whether it ever lets up. A trial ends. A funding round closes. A residency finishes. If nothing ever ends, you're not in a season, you're in the relationship.

What to say early

The conversation people avoid is worth having in about week three, and it's shorter than they fear.

Not "are you going to have time for me", that asks for a promise nobody can keep. Something closer to: "What does a bad week look like for you, and what do you need from someone when you're in one?"

You'll learn more from that answer than from a month of observation. Some people want to be left alone and resurface. Some want a text they don't have to answer. Some want to be dragged out of it. All three are workable and all three fail badly if you guess wrong.

The friends-and-family question

People with unpredictable jobs are frequently bad at the social calendar that surrounds a relationship, and this causes more friction than the cancellations do.

Weddings, birthdays, your friend's thing on Saturday. They will miss some, and the miss is more visible than a cancelled Tuesday because other people notice it.

The workable approach is to grade them. Some events genuinely matter and are worth them moving something for; most don't. Couples who handle this well tend to be explicit about which is which rather than expecting the other person to intuit it, and the ones who struggle treat every invitation as the same weight.

Where it goes wrong

Keeping score. Counting cancellations poisons the thing you're trying to protect, and the count is never the real question anyway.

Reading silence as a verdict. Someone in theatre for nine hours isn't sending a message with their silence. Building a narrative in the gap is the most common failure here, and it's almost always wrong.

Becoming the accommodating one permanently. Flexibility offered forever stops being warmth and becomes the structure. Occasional reciprocity — them moving something for you — is the health check.

Assuming it'll get better. Sometimes it does. Often the job is who they are rather than a phase they're in, and deciding based on a future version of them is how people lose two years.

If you're the one with the job

Worth flipping, because the same dynamic looks different from inside it.

The most useful thing you can do is give information rather than apologies. "I'm on call Thursday to Sunday, so let's do Tuesday" costs you nothing and removes the entire category of anxiety that builds in the silence. Most of the damage in these relationships comes from the other person filling gaps with guesses.

The second is to protect something small and defend it absolutely. One hour a week that never moves is worth more than four that frequently do, because reliability is the thing in short supply and it's the thing being measured.

When to stop

When effort disappears and only availability is discussed.

When rescheduling is always your job. When you've stopped mentioning things because you assume they won't happen. When the good version of the relationship exists only in the abstract, in some period after the current thing ends.

None of those are about hours. All of them are about whether the person is actually present when they are present, which is the thing that decides this rather than any calendar.

The short version

Judge effort, not availability. Watch what happens after a cancellation rather than the cancellation. Keep plans small, near and easy to move. Protect one recurring slot. Ask what a bad week looks like before you're in one.

Do that and a demanding job becomes a logistics problem, which is solvable. Get it wrong and it becomes a referendum on the relationship every single week, which isn't.

Create a free profile on Plus.

Frequently asked questions

How do you date someone with a demanding job?

Judge effort rather than availability, keep plans short and near them, and protect one recurring slot that both of you defend. Availability is a function of their job; effort is a function of how they feel about you, and conflating the two is the most common mistake.

Is cancelling a lot a red flag?

Not by itself. What matters is the ninety seconds after: someone who wants to see you proposes an alternative immediately, because they're annoyed too. Someone who lets rescheduling drift onto you, repeatedly, has answered the question.

How do you tell if they're busy or just not interested?

Interested people with brutal schedules still find fifteen minutes: a message at an odd hour, remembering something you said, an evening protected two weeks out. None of that takes much time. Someone not interested is busy in a way that has no fifteen minutes anywhere in it.

What should I ask early on?

"What does a bad week look like, and what do you need from someone when you're in one?" You'll learn more from the answer than from a month of watching. Some people want space, some want a text they needn't answer, and guessing wrong causes most of the friction.

Will their schedule get better?

Sometimes: a trial ends, a residency finishes, a round closes. Often the job is who they are rather than a phase. Deciding based on a future version of someone is how people lose years, so judge the current one.

How often should you see each other?

More often and for less time is better than rarely and elaborately. Forty-five minutes on a weeknight, repeated, builds more than a monthly production. Consistency reads as interest, and scarcity reads as ambivalence regardless of what's intended.