Most people have a vague sense that deep work is important. Fewer can say, with any precision, what it actually looks like in their own job. That vagueness matters — because if you can’t identify deep work clearly, you can’t protect time for it.
This article gives you concrete examples across seven professions, a way to distinguish deep from shallow in each, and an honest account of what deep work feels like when it’s actually happening.
Examples of deep work by profession:
- Software developer — writing a complex algorithm without interruption
- Writer — drafting a chapter with no tabs open
- Researcher — reading and synthesising multiple papers to form an original argument
- Designer — working through visual problem-solving without breaking to check messages
- Lawyer — drafting a contract that requires holding many precedents in mind simultaneously
- Consultant — building a financial model that requires sustained analytical thinking
- Student — studying one subject intensively using active recall
What makes something “deep work”
Cal Newport’s definition is precise: deep work consists of cognitively demanding tasks performed in a state of distraction-free concentration that push your cognitive capabilities to their limit. The output is something that is hard to replicate and creates real value.
That’s the filter. Apply it to any task. If the task doesn’t push your cognitive capabilities — if it could be done adequately while half-distracted — it’s not deep work, regardless of how long it takes or how serious it feels.
The defining characteristic isn’t the profession or the task type. It’s the combination of cognitive intensity and the absence of distraction. A novelist staring at a blank page is not doing deep work if they’re refreshing their inbox every four minutes. A developer pushing trivial bug fixes to meet a ticket quota is not doing deep work. The same person, fully absorbed in designing a system architecture they’ve never solved before, is.
To understand this fully, it helps to read what is deep work before going further.
Deep work vs. shallow work — the contrast
The table below makes the distinction concrete across each profession. Note that shallow work is not valueless — it’s simply not cognitively demanding in the way that produces exceptional output.
| Profession | Deep work example | Shallow work example |
|---|---|---|
| Developer | Writing an algorithm, debugging complex code | Responding to Slack, updating Jira tickets |
| Writer | Drafting a chapter, revising an argument | Formatting, responding to editorial emails |
| Researcher | Reading and synthesising papers | Scheduling interviews, literature search admin |
| Designer | Visual problem-solving, concept development | Exporting assets, client status updates |
| Lawyer | Drafting contracts, constructing arguments | Admin, billing, email correspondence |
| Finance | Building financial models, scenario analysis | Formatting reports, meeting prep |
| Student | Active recall, working problem sets | Re-reading notes, highlighting |
For a deeper treatment of this distinction, see the full guide on deep work vs. shallow work.
Examples by profession
Software development
Deep work in software development is writing code that requires you to hold a large, interconnected problem in mind — designing a new system architecture, debugging a subtle concurrency issue, implementing an algorithm you’ve had to think through from first principles. These are tasks where interruption doesn’t just slow you down; it forces you to rebuild an entire cognitive structure from scratch.
Shallow work looks like updating tickets, reviewing a three-line pull request, attending a standup, or responding to Slack messages. These tasks are necessary. They are not deep.
The journalist angle applies here too: a developer who writes clean, complex code for three uninterrupted hours will outproduce one who “works” for eight hours with Slack open. The output isn’t proportional to hours logged. It’s proportional to the depth of the blocks.
Writing and journalism
A writer doing deep work is drafting — head down, no tabs open, working through the argument or the scene with nothing pulling attention away. Cal Newport’s own deep work includes writing his books in this manner: scheduled blocks, no internet, full engagement with the problem of what to say and how to say it.
Shallow work for a writer includes formatting documents, responding to editorial emails, pitching stories, updating a website. All legitimate tasks. None of them are deep.
The contrast is visible in output quality. A journalist who writes 1,000 polished words in a two-hour block without interruption will consistently outperform one who spends eight hours nominally writing but never enters a state of real absorption. The time on the clock isn’t the variable.
Research and academia
Academic deep work is synthesis — reading multiple papers and building an original argument that didn’t exist before you started. It’s working through a proof. It’s sitting with a data set and thinking, without reaching for easy conclusions.
The shallow version of research is often mistaken for deep work because it looks serious. Conducting a literature search by Googling terms, filing references, scheduling interviews, formatting citations — these are necessary but shallow. The cognitive load is low. You could do most of it while half-asleep.
Real research thinking is effortful in a specific way. It resists easy completion. That resistance is the signal.
Design (graphic, UX, product)
Design deep work is concept development and visual problem-solving — the phase where you’re working through whether something actually functions, whether the hierarchy communicates, whether the system holds together. It requires holding multiple constraints in mind simultaneously: user need, visual logic, technical constraint, brand consistency.
Shallow design work includes exporting assets, resizing files for different platforms, sending client status updates, sitting in review calls where decisions have already been made. Necessary. Not deep.
Law and consulting
A lawyer drafting a contract is doing deep work when the task requires holding multiple precedents, clauses, and potential failure modes in mind at once — constructing an argument that must be airtight before it reaches paper. The cognitive load is high. Interruption is expensive.
Billing, email correspondence, admin, and scheduling are the shallow counterparts. Valuable to the firm’s operations. Not the work that differentiates a good lawyer from an exceptional one.
For consultants, deep work typically means building a financial model, running scenario analysis, or stress-testing an argument before a client presentation. The shallow equivalent is formatting the slides after the thinking is done.
Finance and analysis
Financial modelling is a clear example of deep work: structuring a model that doesn’t yet exist, making decisions about assumptions, identifying where the analysis could fail. It requires sustained analytical focus with no shortcuts.
Formatting reports, attending pre-meeting briefings, and preparing summary slides are shallow work — important for communication, but not where the analytical value is created.
Students
For students, deep work is active recall and working through problem sets — genuinely testing comprehension rather than simulating it. Studying one subject intensively, without switching between topics, is how cognitive consolidation happens.
Shallow study is re-reading notes, highlighting text, and passive review. These feel like work. They produce limited retention. The cognitive demand is low enough that the brain doesn’t encode the material with any durability.
If you want to know how to do deep work as a student, the answer is mostly about replacing re-reading with retrieval practice.
What deep work actually feels like
Most descriptions of deep work focus on output and method. Fewer describe the phenomenology — what it actually feels like to be in it. That matters, because recognising the experience helps you distinguish real deep work from its simulacra.
The initial friction
The first ten to fifteen minutes of a deep work session rarely feel good. There’s resistance — a pull toward distraction, a sense that the task is harder than you’d like, a temptation to check something first. This friction is normal and expected. It’s not a sign that you’re doing it wrong. It’s the cognitive cost of shifting from shallow engagement to genuine depth.
Most people interpret this friction as a reason to delay. Productive people push through it.
Absorption — when it’s working
When deep work is working, the task starts to pull you in rather than push you away. Time passes without being noticed. The problem has your full attention not through discipline but through genuine engagement. This is what flow states describe, though deep work doesn’t require flow — sustained effort without flow still counts.
Productive fatigue — the sign you’ve done real work
After a genuine deep work session, you feel tired in a specific way. Not the hollow, drained feeling of a day full of meetings. Not the restlessness of a day spent context-switching. A particular cognitive tiredness — satisfied, locatable, the sense that something was actually spent.
If you finish a work session and feel vaguely tired without knowing what you did, that’s the shallow work feeling. Productive fatigue is different. You know what you built.
What is NOT deep work (common misconceptions)
Several things are routinely mislabelled as deep work.
Long meetings — even technical ones — are not deep work. Discussion is shallow cognitive engagement. The depth comes in the preparation and follow-through, not the meeting itself.
Thoughtful email responses are not deep work. Even if you’re choosing words carefully, the cognitive demand is too low and the interruption structure is built in.
Code review of trivial changes is not deep work. It may be careful, but careful isn’t deep.
Research that is mostly Googling is not deep work. Browsing is shallow regardless of what you’re browsing for.
The common mistake is calling anything “focused” deep work. Concentration is necessary but not sufficient. The task itself must be cognitively demanding at a level that pushes your capabilities. Without that, you have focus without depth.
This applies across jobs that require deep work — even in roles that seem inherently complex, most hours are spent on shallow tasks.
FAQ
What is an example of deep work?
A software developer writing a complex algorithm without interruption is a clear example of deep work. The task is cognitively demanding, requires sustained concentration, and the output — clean, working, well-designed code — is difficult to produce in a distracted state. Other examples include a lawyer drafting a contract that requires holding multiple precedents in mind simultaneously, or a researcher synthesising several academic papers into an original argument.
Is writing deep work?
Writing can be deep work, but not all writing is. Drafting — working through an argument or narrative from a blank page — is deep work when done without interruption and with genuine cognitive engagement. Editing, formatting, responding to editorial emails, and writing routine correspondence are not deep work. The distinction is whether the task pushes your cognitive capabilities. First-draft writing usually does. Administrative writing usually doesn’t.
Can meetings ever be deep work?
Almost never. Even technically demanding meetings — code reviews, research discussions, strategic planning sessions — are shallow cognitive engagement because they involve frequent switching between speaking, listening, and reacting. The depth of thinking, if it happens at all, occurs in the preparation beforehand or the synthesis afterwards. The meeting itself is the shallow part. Newport’s framework classifies meetings as shallow work regardless of their importance.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is an example of deep work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A software developer writing a complex algorithm without interruption is a clear example of deep work. The task is cognitively demanding, requires sustained concentration, and the output is difficult to produce in a distracted state. Other examples include a lawyer drafting a contract that requires holding multiple precedents in mind simultaneously, or a researcher synthesising several academic papers into an original argument."
}
},
{
"@type": "Question",
"name": "Is writing deep work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Writing can be deep work, but not all writing is. Drafting — working through an argument or narrative from a blank page — is deep work when done without interruption and with genuine cognitive engagement. Editing, formatting, responding to editorial emails, and writing routine correspondence are not deep work. The distinction is whether the task pushes your cognitive capabilities."
}
},
{
"@type": "Question",
"name": "Can meetings ever be deep work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Almost never. Even technically demanding meetings are shallow cognitive engagement because they involve frequent switching between speaking, listening, and reacting. The depth of thinking, if it happens at all, occurs in the preparation beforehand or the synthesis afterwards. Newport's framework classifies meetings as shallow work regardless of their importance."
}
}
]
}
</script>