How we think about titles

The problem with titles

Large organizations use titles to signal status and authority. Useful in some contexts, but excessive title ladders can create hierarchy-first behavior.

As a small company, we aim to keep idea quality above title gravity.

Our approach to titles

We keep title structure intentionally flat and simple. Titles exist, but we limit complexity and avoid stacked seniority labels where possible.

The intent is to preserve autonomy and make contribution quality the primary signal.

The reality of the outside world

External contexts may require role framing. Public titles are acceptable if they are accurate and not misleading.

Good examples

• Experienced DevOps engineer using "Senior Cloud Engineer".
• Deliverability-focused specialist using "Postmaster".

Bad examples

• Individual contributor using "VP/Head of Engineering" without management scope.
• Admin-focused role using "Chief of Staff" without role substance.

When unsure, align with your manager.

The future

If organizational scale eventually requires more structure, this policy can be revisited. Until then, simplicity is preferred.