Competitive coding signals that: * you can read (understand requirements) * visualise problem space * modify problem space * efficiently prune problem space is

Competitive coding signals that: * you can read (understand requirements) * visualise problem space * modify problem space * efficiently prune problem space is search of solution * have good understanding of DS and alorithms * command computer to help you finding solutions I would say competitive programming is much more about math than software engineering. I would say all these skills are useful to be good SE but you also need: * good code organisation * very good semantics skills (domain modeling, naming) * debugging skills (correlated to problem solving) * conversation skills (posing precise questions and answers) * beeing comfortable with ambiguity and change of requirements (especially startups) * being able to work with/fix shitty abstractions that less(sometimes "more") skilled people come up with For average job even CS degree is overskill.