Advice for junior developers in general

Related to #8. This would be a response to this email:

I stumbled across your post on http://betabeat.com/2011/06/moving-to-new-york-city-a-software-engineers-guide/ and while it’s a few years old now I agree with many of the points you make.

It seems your post is more for established software engineers in more experienced or senior positions but perhaps you would have some advice for me as I still find much of what you said is relevant to software engineers of all levels.

As a recent Computer Science/Software Engineering graduate, with only a years worth of professional experience. I’m looking to move to NYC to pursue a career as a software engineer but am finding it quite complicated due to the lack of quality postings and lack of postings for more junior or entry-level candidates. I don’t mind entering the startup space as I’ve worked in the big slow-moving corporate environment and would like a change from that, but it seems even startups don’t often have entry-level postings.

...

P.S. I’m considering applying under Artsy’s “Student Opportunities” section, but I’m not sure if I’m the target as I’m no longer a student, which brings us full circle in the employment catch-22 of too experienced for student postings, too inexperienced for full-time postings.

Start by reading related issue #8 and the quoted email in this issue. Define the scope of the advice response for junior developers, then produce content that addresses the sender’s entry-level job-search and relocation questions; the issue does not name a file or publication entry point.