Technical Decision Making in Interviews: How to Answer "Should We Build This?"

In technical interviews, one type of question often catches candidates off guard—not "how to implement," but "whether to implement."

An interviewer might ask: "If a Product Manager wants an offline mode for the app, what would you consider?" or "User feedback suggests a Dark Mode, is it worth doing?"

These questions test not your coding ability, but your technical decision-making mindset—a core competency distinguishing senior engineers from juniors.

Why Interviewers Ask This?

The 5-Dimension Decision Framework

Dimension 1: Business Value Assessment

Core Question: What value does this create?

1. User Value

• What pain point does it solve?
• How many users will benefit?

2. Commercial Value

• Direct revenue impact?
• Retention or engagement lift?

3. Strategic Value

• Aligns with product roadmap?
• Creates a competitive moat?

Dimension 2: Technical Feasibility

Core Question: Can we build it? How hard is it?

1. Implementation Path

• Available technical solutions?
• Pros/cons of each?

2. Technical Risks

• New, unproven tech involved?
• Single points of failure or bottlenecks?

Dimension 3: Cost-Benefit Analysis (ROI)

Core Question: Is the ROI reasonable?

1. Development Cost

• Man-hours? Schedule impact?

2. Operational Cost

• Server/storage resources?
• Maintenance burden?

3. Opportunity Cost

• What features are delayed by doing this?

Dimension 4: Risk Assessment

Core Question: What if things go wrong?

• Technical Risk: Bugs, performance regressions?
• Business Risk: Compliance issues?
• UX Risk: Confusion or complexity for users?

Dimension 5: Alternatives

Core Question: Is there a better way?

• Clarify Needs: What is the root problem?
• MVP: Can we validate with minimal cost?
• Substitutes: Third-party services? simpler workarounds?

Structuring Your Answer with STAR

Situation

"Before answering, I'd like to understand the context. What scenario is this feature addressing?"

Task

"The core issue here is balancing business value against technical cost."

Action

"I would analyze this from five dimensions: First, business value... Second, technical feasibility..."

Result

"Based on this analysis, my recommendation is..."

Common Mistakes

Real-World Case: "Should We Do Dark Mode?"

Question: "PM wants Dark Mode. Thoughts?"

Answer:

"That's a great question. Before recommending, I'd analyze a few dimensions.

First, Business Value: Dark mode improves UX in low-light environments. Industry data suggests it can boost evening retention by 5-10%.

Second, Feasibility: Implementation is mature (CSS variables or theme switching). Low technical risk, but requires component library adaptation.

Third, Cost/Benefit: Dev cost is ~1-2 weeks. Op cost is near zero. ROI looks good.

Risk: UI consistency across pages.

Recommendation: If we have significant evening usage, it's worth it. Suggest a phased rollout, starting with core pages."

Summary

Technical decision-making questions distinguish "coders" from "architects."

Key Takeaway: Don't rush to answer. Show your analysis process using the 5-dimension framework.

---

Want to master technical decision-making? Interview AiBox offers AI-powered mock interviews for system design and architectural thinking.

Start your journey with our Interview AiBox Features Guide. 🚀