&quot;Lack of a real challenge, no deadlines, no scope for further development of my skills&quot;<p>Those are the reasons right there.<p>Without a challenge, it&#x27;s hard to feel like you&#x27;re creating something or doing something valuable. It might be valuable to someone else, but if it&#x27;s not challenging to you, it&#x27;s very difficult to feel like you&#x27;re accomplishing something that is valuable.<p>Without a deadline, there&#x27;s usually no sense of urgency. In order to be productive and efficient, you have to have deadlines.<p>I&#x27;d try to find work that has both of these. Before you decide to move on, be absolutely sure that you communicate with your current employer. I&#x27;ve heard countless stories from Recruiters and Hiring Managers saying that if an developer had only told them that something was bothering them, the company could have changed to accommodate them (saving the developer from quitting, and saving the company lots of money in trying to find a replacement).<p>After you&#x27;ve communicated very clearly and kindly, see if things change. If they don&#x27;t change, leave. Give yourself tangible outcomes (example: If X doesn&#x27;t change by this date, I&#x27;m finding a new job) and stick to those.<p>All the best.