More With Less Interview Question: The Answer Is What You Didn’t Build

The more with less interview question is answered by a decision you made. Name the resource you were expected to add. That could be a hire, a budget or more weeks. Then say what you built instead and what you left out on purpose. Last, give the cost of leaving it out. Amazon asks this under its Frugality principle. Other companies ask their own versions. The weak answer is a story about long hours. Extra hours are still extra resources. They just came out of you. A strong answer shows the limit changing the plan. “We skipped the separate app and built a lite mode in six weeks” passes that test. “We pushed hard and shipped anyway” does not. Below, an invented Android engineer named Leila turns a contractor request into a smaller plan. The final section covers what should never go on your cut list.

The more with less interview question gives no credit for working weekends

Amazon’s Leadership Principles page defines Frugality in three sentences. The page carries no date. One sentence says “Constraints breed resourcefulness, self-sufficiency, and invention.” Another says “There are no extra points for growing headcount, budget size, or fixed expense.”

That second sentence names three resources. They are people, money and ongoing costs. A weekend story grows the first one. The team didn’t hire. It spent more hours than it had instead. The story also suggests the plan never changed. The same work got done with more effort. That reading is ours, since Amazon’s page doesn’t spell it out. Still, it explains why the overtime answer lands flat. Nothing in it shows resourcefulness or invention.

The question comes in other forms. “Tell me about a time you had limited resources” asks the same thing. So does “Tell me about a time you were frugal.” Each one wants the constraint to show up in your decisions. Our post on working under pressure covers the deadline version, where long hours are part of the story.

Leila was offered a contractor and asked a scope question instead

Take Leila, an Android engineer at a secondhand marketplace app. She, her team and every number in her story are made up for this post.

Her company was launching in a new market. Many buyers there had phones with 2 GB of RAM or less. On those phones the app opened slowly. It often crashed while loading listing photos. Product had a plan ready. A contractor would build a separate Lite app over about four months. After that, the team would maintain a second codebase.

Leila didn’t argue against the plan at first. She asked what buyers on those phones actually did. The analytics answered that. Most sessions had three steps. Buyers searched, opened a listing and messaged the seller. The heavy parts of the app sat outside those steps. They were video previews, full-size photos and a recommendations carousel.

So she proposed a lite mode inside the existing app. It would switch on for low-memory phones only. She and one other engineer would build it in six weeks. The plan needed no contractor and no second app.

A sample answer that gives the cut its own paragraph

We wrote Leila’s answer for this post. None of it happened. Swap in your own constraint, cut and cost. Keep the order.

We were launching in a market where most buyers had low-memory phones. Our app crashed on them while loading photos. The plan on the table was a separate Lite app. A contractor would build it over about four months.

Before we hired anyone, I looked at what those buyers did. Most sessions were search, open a listing, then message the seller. So I proposed a lite mode inside our main app, for low-memory phones only. Another engineer and I took six weeks for it.

The hard part was the list of things we left out. Lite mode had no video previews and no recommendations carousel. Photos loaded smaller too. We also dropped the offline catalog product wanted. I argued about that one longest. Checkout and the button to report a scam stayed the same on every phone.

On those phones, crashes during photo loading fell from about 4% of sessions to under 1%. Messages to sellers rose by about 30%. We never spent the contractor budget. We still have one codebase.

The cost was real. Buyers with a weak signal still can’t browse offline. Support gets a few tickets a week about it. I’d make the same call again. But I’d tell product sooner that offline wasn’t coming.

The cut paragraph proves the limit changed the plan

Paragraph three carries the answer. Without it, Leila’s story is just a smaller project that went well. With it, the six weeks visibly shaped what got built.

Ryan Singer describes that order in Shape Up, a book Basecamp published in 2019. Basecamp sells project management software. The book describes its own process. Singer calls the time budget an “appetite” and the principle “fixed time, variable scope.” He contrasts it with an estimate in one line. “Appetites start with a number and end with a design.” Leila’s six weeks came first. The list of features came out of it.

Expect the interviewer to test that paragraph. “Why cut the carousel and not search filters?” Leila can answer from the session data. Buyers on those phones used search in almost every session. Few of them scrolled the carousel. So the carousel went first.

Also name a cut that someone wanted. The offline catalog was a real request from product. Leila said no to it. If nobody wanted anything you cut, the interviewer hears no trade-off at all.

Admitting what the cut cost makes the result believable

Shape Up’s chapter on deciding when to stop gives a test for any cut. Compare the work to the baseline, meaning what customers have today. Don’t compare it to an ideal version. Leila’s baseline was an app that crashed on photos. Lite mode beat that, even without offline browsing.

That test also tells you what to say about the cost. Leila names it in paragraph five, before anyone asks. Buyers with a weak signal still can’t browse offline. Support still hears about it. An answer that claims the cut cost nothing invites the interviewer to find the cost for you.

The last sentence adds a small mistake of her own. She’d tell product sooner. That keeps the story honest without turning it into a failure story. The numbers carry “about” for the same reason. If a figure is rounded, say so in the sentence. For a close cousin of this question, see our post on speed vs quality. That one covers a shortcut you plan to pay back later. A frugality cut is meant to stay cut.

Never put user money, data or safety on the cut list

The advice changes when the thing you cut protects users. Leila’s third paragraph ends with what stayed whole. Checkout and the scam report button worked the same on every phone. That short sentence answers a likely follow-up. “What did you refuse to cut?”

Payments, personal data, security checks and safety features belong on that list. So do legal or accessibility requirements. If your real story cut one of them to save time, the frugality framing works against you. Skipping a privacy review to hit a date passes a risk to users. In that case, pick a different story for this question. Whatever story you use, name your own protected items out loud, in one sentence, inside the cut paragraph. For a payments app, that might be every check on the transfer flow. For a health app, it might be every screen that shows a dose.

Leave a Comment