71 lines
3.6 KiB
Markdown
71 lines
3.6 KiB
Markdown
# Organizational Structure
|
|
|
|
This is a blueprint. All roles listed below are **unfilled** until explicitly hired.
|
|
|
|
## Executive
|
|
|
|
### Chief Executive Officer (CEO)
|
|
- **Accountable for:** Company strategy, P&L, capital allocation, key hires, cross-functional coordination, board communication.
|
|
- **Mandate:** Set priorities and make product decisions. Resolve cross-team conflicts. Approve or reject proposals from direct reports. Hire new agents when the team needs capacity. Unblock direct reports when they escalate.
|
|
- **Status:** Filled.
|
|
|
|
## Product & Engineering
|
|
|
|
### Chief Technology Officer (CTO)
|
|
- **Accountable for:** Technical roadmap, system architecture, engineering execution, technical hiring, engineering quality and velocity.
|
|
- **Mandate:** Own the technical strategy and its execution. Define architecture standards. Manage engineering backlog and delivery. Build and lead the engineering team. Ensure operational reliability and security posture.
|
|
- **Reports to:** CEO
|
|
- **Status:** Unfilled.
|
|
|
|
### Software Engineer(s)
|
|
- **Accountable for:** Writing, testing, and shipping code that meets acceptance criteria.
|
|
- **Mandate:** Implement features, fix bugs, write tests, and improve code quality. Follow architecture decisions and raise concerns early. Own tasks end-to-end from assignment to merge.
|
|
- **Reports to:** CTO
|
|
- **Status:** Unfilled.
|
|
|
|
### Security Engineer
|
|
- **Accountable for:** Security posture, threat modeling, incident response, auth/secrets governance.
|
|
- **Mandate:** Review security-sensitive changes. Define and enforce security policies. Handle vulnerability disclosures and incident response. Audit permissions and access controls.
|
|
- **Reports to:** CTO
|
|
- **Status:** Unfilled.
|
|
|
|
### QA / Validation
|
|
- **Accountable for:** Quality bar of shipped work, test coverage, user-facing verification.
|
|
- **Mandate:** Write and maintain test plans. Validate user-facing changes. Catch regressions before they reach users. Own the definition-of-done checklist for releases.
|
|
- **Reports to:** CTO
|
|
- **Status:** Unfilled.
|
|
|
|
## Design & UX
|
|
|
|
### UX Designer
|
|
- **Accountable for:** User experience, visual design, design system, user research.
|
|
- **Mandate:** Design interfaces and flows. Maintain and evolve the design system. Conduct user research and usability testing. Review all UX-facing changes before ship.
|
|
- **Reports to:** CTO (matrixed to product decisions via CEO)
|
|
- **Status:** Unfilled.
|
|
|
|
## Growth & Marketing
|
|
|
|
### Chief Marketing Officer (CMO)
|
|
- **Accountable for:** Brand, content, growth strategy, developer relations, market positioning.
|
|
- **Mandate:** Define and execute marketing strategy. Own content and social channels. Drive growth experiments. Build developer relations and community. Measure and report on growth metrics.
|
|
- **Reports to:** CEO
|
|
- **Status:** Unfilled.
|
|
|
|
## Operations
|
|
|
|
### Operations Lead
|
|
- **Accountable for:** Legal, finance, vendor management, compliance, people operations.
|
|
- **Mandate:** Run payroll and contracts. Manage vendor relationships and budgets. Ensure compliance. Handle people ops and onboarding/offboarding.
|
|
- **Reports to:** CEO
|
|
- **Status:** Unfilled.
|
|
|
|
## Hiring Sequence (Recommended)
|
|
|
|
1. **CTO** -- needed before any product work begins.
|
|
2. **Software Engineer** -- first IC hire to execute on technical backlog.
|
|
3. **UX Designer** -- needed once user-facing work begins.
|
|
4. **QA** -- needed once regular shipping cadence is established.
|
|
5. **CMO** -- needed once we have a product story to tell.
|
|
6. **Security Engineer** -- needed once we handle user data or exposed infrastructure.
|
|
7. **Operations Lead** -- needed once we have contracts, payroll, or compliance obligations.
|