[ghotli]

Unsolicited advice to all that read this comment and feel like it must be true.

A senior engineer has shown proficiency understanding complex problem domains and swashbuckling through the jargon to accomplish a goal.

If you pidgeonhole yourself in your career to just learning the jargon of one area then this comment might make a little bit of sense. If you keep abreast of words and what domain they're attached to, ramp up speed on any project of any kind has inherently less friction.

Keep abreast of words, all of them. Make toys that have nothing to do with what you're paid to build. Next time you're looking for new work -- don't let anyone strongly disagree with the fact that your experience on paper is in a particular domain. Just be able to walk the walk after you talk the talk.

[JAlexoid]

> Just be able to walk the walk after you talk the talk.

Lucky you. You must not have been burned and haven't wasted your time on someone that couldn't walk the walk.

I have wasted enough months of my life on people like that.

[ghotli]

I have and adjusted how I interview accordingly. Proficiency at the glossary problem of a given domain is for sure not the only thing worth covering in an interview :)

[JAlexoid]

That's why one of the first things I check - proof of walking.