The Strategic Minimalism Resume Strategy: Winning Both ATS and Human Readers

Instead of choosing between a bland ATS-safe resume and a creative one that gets auto-rejected, this strategy targets the design choices that satisfy both.

4:41 video3 min readWatch on YouTube

Why do so many resumes look exactly the same, dense with keywords, stripped of any design personality, all clearly built to survive an automated filter? Professor Bear opens this discussion by pointing out a real tension: language models can already read even a sophisticated, well-designed resume without trouble, so the pressure to produce a boring, generic, keyword-list resume increasingly comes from older automated systems, not from any real limitation in how resumes get read today.

The real constraint is legacy technology, not human preference

The research behind this video, done using Google's deep research tool, points to a specific culprit: a lot of large companies are still running on very legacy applicant tracking systems, some even relying on OCR to parse resumes, and many of those systems predate 2020. If you're applying to a large company running one of these older systems, you likely do need to think about ATS compatibility. But if you're applying to a small company, a startup with three people, there's a good chance a person is just going to look at your resume directly, the way Professor Bear describes doing himself: a quick look, and a fast rejection of anything that visibly looks like it was built for a machine rather than a person.

What strategic minimalism actually means

The strategy is built around identifying the overlap between what works for both ATS systems and human readers, rather than treating them as opposing constraints. Clear typefaces like Calibri, Arial, and Verdana are the clearest example: a typeface that's readable for a human is also readable for an ATS system parsing text. The same logic applies to layout. A clean, organized structure helps both a human skimming the page and a system trying to extract structured fields from it. The insight isn't complicated, but it reframes the problem: instead of asking "what does the ATS want," the better question is "what's actually readable," because readability turns out to satisfy both audiences at once.

Know your target before you commit to a format

The strategy doesn't stop at typeface and layout. Professor Bear recommends researching which system a specific target company is likely using before finalizing a resume's design. Large, established corporations tend to resist changing their internal tooling, which means some of them may still be running a system that's five, ten, or even fifteen years old, purely out of institutional inertia rather than any technical necessity. For companies like Microsoft, Amazon, or Tesla, it's often possible to find out which platform they use, Workday is named as one common example, and tailor formatting choices to what that specific system handles well. Startups, by contrast, are far more likely to review resumes manually, and may actively prefer a resume that stands out visually rather than one obviously optimized for a filter.

What's coming next

Professor Bear describes plans to build a tool that applies strategic minimalism principles automatically to a resume, offering concrete suggestions based on this framework. He also hints at a "step two" beyond the current strategy: adding small, subtle design elements that make a resume stand out to a human reader without triggering rejection by an ATS system, a refinement he plans to think through further from a design perspective.

Key takeaways

  • The core problem isn't that language models can't read well-designed resumes, it's that many large companies still run outdated ATS or even OCR-based systems.
  • Strategic minimalism means choosing design elements, like clear typefaces (Calibri, Arial, Verdana) and clean layouts, that satisfy both ATS parsing and human readability at once.
  • Legacy ATS use correlates with company age and size, not with technical necessity, so it's worth researching a specific employer's system before assuming you need a heavily keyword-optimized format.
  • Startups and small companies are more likely to review resumes manually and may prefer a resume that visually stands out.
  • A planned "step two" would add subtle design touches that appeal to human readers without risking ATS rejection.

Who this is for

This is aimed at job seekers trying to navigate the gap between ATS-driven corporate hiring pipelines and startups that review resumes by hand, and it comes out of a discussion in Professor Bear's branding and AI class at Humanitarians AI.

Full transcript(auto-generated, with timestamps)

[0:01]Okay, Professor Bear here. Uh, in the branding and AI class, we're having a discussion about sort of ré strategies. I get about 30 rs a day which look all exactly the same. So I'm wondering in the day and age of language models why people and the reason I hear people do that is for these ATS systems that is so they can pass these little automated systems and but just upload your resume to any language model and ask it to read it even if it's sophisticated resume the language models can read it. The question is why do we need these boring generic basically keyword list résumés?

[0:42]So I had uh the Google deep research to uh tool do a bunch of research on this issue and say the biggest issue here is unfortunately there are a lot of big companies that are still using very legacy some even OCR systems. So if it's a big company using a very dated system i.e. 2020 and before then you probably need some sort of ATS stuff and so it's one is important to know but if you're like applying to a small company like a startup with three people they're probably reading it. They probably do what I do which is quickly look at them and just reject anything

[1:31]That looks like it was made for ATS just from the way it looks. So what I came up with is what what I call the strategic minimalism strategy. So what does this mean? So what this means is there's some things that work for both ATS and for humans. For example, clear type faces collabor. So if it's readable for humans, it's also readable for these ATS systems. a layout having clear layout f that helps both humans and ATS systems. So here's a bunch of suggestions and there are serore things that work for both humans and for ATS. The other thing you're going to want to do is you're going to run a research

[2:24]Like who you're sending it to and what kind of system they use. If they're using a very antiquated system, then you have to go with an antiquated resume. But if it's Google or Tesla, whatever, they have no excuse whatever for using some data system. I don't know what they actually use, but there is a tendency for very large corporations to resist any kind of change. So they might have a 5, 10, 15 year old system that they're still using even though it's terrible because they just don't want any change. So that will involve some research. But if it's a big company, you know, Microsoft and Amazon and Tesla,

[3:03]Whatever, you could probably easily find what they're using. Work day or whatever it's called, work a day, workday, whatever it's called, they handle a lot of stuff. So things that work for work a day, probably, you know, research whatever they use and and do that. And then I'm going to probably design a little tool, maybe not now, whenever I get a spare half an hour or so, where you can just upload your your resume and it'll apply the strategic minimalism principles to it and make some concrete suggestions. So that's it. This is my research. This was written in class, by the way, uh during the discussion about this. Um,

[3:46]And so it makes sense to me. It makes sense to me that to use type faces that work for both humans and nattos, but also to have some things, some small things which make it stand out a bit. I'll think about more what those are from a design perspective, things that won't cause problems with the ATS system, but will make it stand out to human. So, it's sort of step two in strategic minimalism. But this is what I've learned in my hour of research on this subject. It's that sort of the problem is, and this is a problem that makes sense because I see it all the time in big business, is that

[4:22]They don't make change. So, it's not that a language model can't handle a better looking, more sophisticated, better designed resume. It's that the company is using some data system, which makes total sense. Okay, so that's it for this. Um, I'll continue this a bit, uh, you know, as I build more tools sword.

More videos

Humanitarians AI Lyrical Literacy Project