What Really Defines a Developer’s Technical Strength? A Practical Evaluation Framework

The Essence of Technical Strength

There is no completely objective, quantifiable standard for judging a technologist's ability; assessments inevitably involve subjective judgment. The core principle is that technical strength equals the ability to solve problems.

Key Rules

There is no universal technology that applies everywhere; technology must be relevant to its domain.

Technology is valuable only when it solves concrete problems.

The complexity of a problem determines the required level of technical strength.

Hard vs. Soft Skills

Hard Skills are observable abilities to solve problems and can be categorized into four progressive levels:

Point : A single technique that addresses a specific issue (e.g., using JDBC to read data).

Line : A series of related points that together complete a business flow (e.g., routing, controller, JDBC, cache).

Surface : A collection of related lines within a domain (e.g., Java development includes multithreading, JDBC, file I/O, JVM tuning).

Body : Integration of multiple surfaces, such as system architecture that spans Java, databases, networking, and business knowledge.

Soft Skills go beyond hard techniques and include:

Problem Discovery : Ability to identify hidden or non‑obvious issues, often requiring experience and systematic analysis.

Technical Innovation : Generating novel solutions or improving existing processes, typically demonstrated by industry leaders.

Practical Evaluation Methodology

When assessing candidates or team members, consider both dimensions:

Verify that the candidate can apply appropriate technologies to real problems, not just recite algorithms.

Explore the depth of their knowledge: do they understand why a solution works, its trade‑offs, and performance characteristics?

Assess their ability to trace performance bottlenecks across the entire stack (e.g., database queries, concurrency design, code logic, external dependencies).

Evaluate their experience with larger‑scale issues such as architecture design, multi‑region deployment, and system resilience.

Case Study

A candidate claimed a 10× performance boost by introducing a cache layer. The interview revealed that they could not explain the underlying principles, had not measured end‑to‑end latency, and lacked awareness of capacity planning. This highlighted the gap between point‑level knowledge and line/surface‑level competence.

Conclusion

Technical strength is fundamentally about problem‑solving ability. By breaking skills into hard (point‑line‑surface‑body) and soft (discovery, innovation) categories, managers can more objectively evaluate engineers during hiring, promotion, and daily work.