Shipmind Labs

On a long project, most of the work is not writing new code, it's changing code someone else wrote years ago. So we hand candidates an unfamiliar piece of a system and ask what they'd be nervous to touch, and why. Caution in the right places is what keeps a client's system running while we're changing it.

Every product has a part nobody wants to touch, and you probably already know yours.

Was this useful?

Building something similar?

or email hello@shipmindlabs.com