[Brazilian-Sigma]

I am starting to appreciate incremental advice. As for taking on challenging projects, it seems like, on surface level, a very trivial problem to solve. They keep talking about the hard "technical problems" (you know, what's the hardest technical problem you solved is a common interview question).

A particular question piques my interest: if this is a simple problem, what are the hard problems and can I even approach them if I fail at a simple one? Or alternatively, if this is a hard problem, why is it hard despite delivering little value to the end user, and what are the simple problems?

[psyklic]

I suggest focusing on problems that interest and challenge you, and not worry if others consider them "hard" or not. The interview question probably depends more on how you explain the problem, rather than its actual difficulty.