Principal Engineer
Title history
- Joined as
- Senior Software Architect
- Current title
- Principal Engineer
Storyteq renamed the role following an organizational change.
Set technical direction across Storyteq's products and shared platform, working with domain leads and engineers through design and delivery. The work spans platform consolidation, global rollout, rendering and developer tooling.
Key achievements
- Designed and planned the consolidation and global rollout of three content management platforms that competed for the same market. The solution connected incompatible data models through a translation layer and used API versioning to accommodate different release patterns. Aligned twelve teams through implementation. The project was delivered in 13 months.
- Own the architecture of a rendering pipeline that turns one template into video and image variants for different platforms and markets. It handles bursts of 50k+ requests per second, with occasional peaks near 80k.
- Teams released on different schedules, and API changes were breaking products that still depended on older versions. Redrew service and data boundaries and introduced internal API versioning and deprecation, reducing release-related outages.
- Built a workflow using coding agents to investigate security findings and prepare fixes. Code controls workflow state, test execution and retry limits. A separate agent reviews changes against the original requirements before engineers approve and merge them.
- Introduced architecture decision records (ADRs), requests for comments (RFCs) and design reviews. Documented alternatives and trade-offs, then turned decisions into implementation guidance for the teams doing the work. ADRs and RFCs became an organisation-wide requirement.
Focus areas
- Work with domain leads on quarterly plans and dependencies between teams.
- Compare technical options and turn the chosen approach into designs and implementation guidance.
- Review designs and trade-offs with engineers, documenting decisions in ADRs and RFCs.
- Work through difficult technical problems in the code.
- Help teams take responsibility for their services from development through operation, using feature flags and CI/CD.
- Ran testing workshops for engineering teams.
- Built support tools to address gaps in engineers' day-to-day work.
Technologies
- Platform architecture
- Distributed systems
- TypeScript
- Node.js
- LLM orchestration
- GCP
- Docker
- Kubernetes
- Helm
- GraphQL
- PostgreSQL
- MongoDB
- React
- Vue
- Angular
- Go
- Java
- PHP