Not for public situations, but internally, and proactively...<p>For my startups's new engineering hiring process, I recently wrote the boilerplate part of the email I send when requesting a first Jitsi/phone technical meeting, after a prospective team member has passed the initial meeting with the CEO.<p>Part of this is to tell them the purpose and format of this meeting (e.g., no surprise coding test, start to get a sense of each others' abilities and what it'd be like to work together). But then the majority of the text is to convey the culture we're going for, and the professional mode it's safe to be in for the interview (which is different than some other places, and than some standard advice).<p>I'm shooting for the engineering&ops culture to be what I call in the boilerplate "honest and earnest". And that it's safe and encouraged in this culture to say "I don't know", "that's a problem", "I made a mistake", "I need help", etc. And that it's safe and encouraged to be in this mode in the interview, as well (and I will be, too).<p>In work (and in the interviews), I absolutely don't want people thinking they should be posturing or cultivating social media-like distorted images, avoiding pointing out system problems, getting into conflict of interest situations with personal career advancement vs. the interests of the team and our work, etc.<p>I'm sure we'll refine this over time, but I believe that an honest&earnest culture avoids a lot of problems around mistakes, including helping to avoid mistakes in the first place, and avoiding compounding them when they do happen.