Pros
Strong product and engineering focus: As a Developer Advocate, I get to work close to both the product and engineering teams, which makes the role feel impactful.
Opportunity to shape developer experience: There is room to contribute to docs, demos, community feedback, technical content, and product messaging.
Fast learning environment: The pace is quick, and there is a lot of exposure to AI tooling, developer workflows, and emerging use cases.
Collaborative team culture: People are generally approachable and willing to help, especially when aligning across product, engineering, and go-to-market.
High ownership: There is room to take initiative, propose ideas, and build things without too much bureaucracy.
Cons
Startup pace can be intense: Priorities can change quickly, so it helps to be comfortable with ambiguity and shifting direction.
Processes are still maturing: Some workflows around planning, documentation, and cross-functional alignment may still be evolving.
Role scope can be broad: Developer advocacy can sometimes stretch across content, community, product feedback, demos, and sales support, so boundaries may need to be clarified.
More structure would help: Clearer success metrics and roadmap visibility would make it easier to prioritize the highest-impact work.