Notes on hiring, security, and how we build Kit.
Plan a first-manager trial with clear authority, less engineering work, useful evidence and an agreed route back to an individual contributor role.
Ernest Bursa
Founder
An impressive track record can hide a dependence on the old team. Use a first-principles interview to see how a candidate handles your company's constraints.
Check AI agent sandbox security beyond the microVM: verify shared files, network access, credentials, external tools, and how your team accepts results.
Check whether the Alpine OpenSSH password bypass applies to your servers, distinguish PAM and container cases, and verify the fix reached the running daemon.
Compare Greenhouse, Ashby and Lever with Kit for a small hiring team. Plan CV imports, archived history and live-role handoffs before switching your ATS.
Write a clear part-time job ad salary: show actual pay, weekly hours and the full-time reference, then explain contract terms and on-call pay separately.
Build a solo founder incident response plan before your first security report: name contacts, record evidence, rehearse decisions, and check recovery access.
Build a fuzz testing crash report another engineer can reproduce, with the exact build, input, command, failure evidence, owner, and fix verification.
Use a feature-combination matrix to test shared previews, document privilege crossings, triage vulnerability reports, and verify the complete fix.
Use this database evaluation checklist to assess PostgreSQL compatibility, transaction isolation, durability and the limits of correctness test results.
Displaying items 1-9 of 236 in total