>> Is it terrible for my resume to work for years on a project that never sees the light of day? As a former recruiter turned engineer, I can say that you shou

>> Is it terrible for my resume to work for years on a project that never sees the light of day? As a former recruiter turned engineer, I can say that you shouldn't worry too much about it. If there were a surplus of great engineers fighting for table scraps, I might offer different advice. You may find it mildly harder to break into gigs that want more experience working on a fast paced agile team, but the reality is that you'll always have a mildly harder problem breaking into something that asks for experience you haven't been practicing recently. What I'd be more concerned about is working on tech that is too crusty. If you're programming in MUMPS, using flat files as a relational database, and hosting everything on Windows 3.0 being emulated on OS/2, you may wish to revisit your tech stack. If you can't throw any not-stale tech into the keyword soup on your resume, it'll look like you haven't been motivated enough to keep your skills sharp. Disregard this advice if you have plenty of people trying to recruit you and/or you know people who'd hire you if they could.