Careers
There is no junior track here, and no analyst pyramid to climb. Every person who reads code for us has at least twenty years behind them and has usually been the most senior technologist in a previous room.
A team of peers
Many roles.
Broader perspective.
Many of our team have served as CTOs, architects, engineering leaders, security leads, and tech CEOs, often holding several of these roles over a career.
The experience you bring. The way you work.
20+
Twenty years, minimum
Multiple-time CTOs, chief architects, tech CEOs, VPs of engineering and security leads. Time served is not a proxy for judgment, but there is no shortcut to having seen enough systems fail.
Polyglot by necessity
A single engagement can mean ten or more languages, firmware through cloud. The people who thrive here are curious about unfamiliar stacks rather than defensive about them.
Able to talk to anyone
You will present the same findings to a target’s engineers, an absorbing tech team, a board and a legal team in the same week. Translation is half the job.
Comfortable being decisive
Deal timelines do not wait for certainty. We form a view, say it plainly, and are clear about what we are confident in and what we are not.
Genuinely independent
Our value rests on saying the unwelcome thing to the client paying us. That requires people who are not looking for the next engagement more than the right answer.
Remote work, global deals
Based in Seattle, we assess technology for deals around the world. Most engagements are fully remote, bringing our team together around each target’s technology and the deal’s priorities.
How people join
We do not post openings
The bench grows by introduction
Tech DNA is a bench of senior engineers. There is no job board here, and we are not likely to add one. People join after a career as a CTO, chief architect or engineering leader, usually by writing to us, and we bring them onto engagements when a deal needs exactly what they have done. The work is project-based and remote, in small teams of peers, matched to the stacks and domains you know best. If that sounds like you, tell us what you have built, where you go deepest, and when you are available.