Systems Architect

📌 Company Description Artist Venture Productions operates at the intersection of narrative, technology, and innovation, crafting strategic narrative systems for teams navigating technological and cultural transition. Founded by Gary Yong, a global creative hybrid with experience in high-stakes filmmaking and generative AI exhibitions, the company unites storytelling with systems thinking. It partners with forward-thinking organizations to offer services like strategic narrative design, AI-native frameworks, and brand evolution. Through narrative ecosystems and systems-level design, Artist Venture Productions empowers leaders to adapt to exponential change while staying rooted in their unique cultural voice and DNA.📌 About PROTO5PROTO5 is an experimental framework being designed for a legacy creative organization creating an AI-native creative team — a future ready, small, adaptive unit that integrate human intuition with machine intelligence.The team is composed of five archetypal roles — Creative Director, Systems Architect, Cultural Analyst, Operations Lead, and Project Manager — designed to operate as a living system rather than a hierarchical department.PROTO5 is both a working prototype and a philosophical experiment: a way to explore how future organizations can achieve coherence, velocity, and meaning in an age of intelligent tools.Its purpose is not just productivity — it’s co-designing the next nervous system of creative work.📌Please see Featured Posts under PROTO5 Architect Gary Yong’s profile for more material on PROTO5.⚙️ SYSTEMS ARCHITECT — QUALIFICATIONS⸻🧠 Core PurposeThe Systems Architect is the design engineer of flow — responsible for building and evolving the living architecture that allows a small AI-native team to think, move, and create at high velocity. This is not a backend or IT position. It’s a role for someone who understands that operations are choreography, and that every tool, workflow, and rhythm is part of a creative ecology.⸻🪶 Foundational Qualities • Systems thinker — sees relationships, feedback loops, and dependencies, not isolated tasks• Creative technologist — designs through tools rather than around them; understands that technology is medium, not master. • Architect of rhythm — senses timing, iteration cycles, and cognitive load; can balance automation with human intuition. • Translator between worlds — bridges code and culture, logic and emotion, precision and play. • Adaptive prototype builder — thrives in flux; iterates processes as living prototypes rather than fixed procedures. • Ethical imagination — considers the human and cultural impact of every system built.⸻🧩 Technical & Cognitive Skillset • Fluency across code / low-code / no-code environments; able to choose tools by affordance, not hierarchy. • Understanding of AI-assisted workflows (LLMs, generative video, automation stacks, creative AI tools). • Experience in systems design, product operations, or workflow engineering — ideally in startup, creative, or hybrid AI environments. • Competence in data hygiene, version control, and process mapping — but treats them as artistic constraints, not bureaucracy. • Ability to prototype cross-functional pipelines (design ↔ narrative ↔ production ↔ ops) that evolve over time. • Sensitivity to team energy and cognitive rhythm; able to detect when a system is out of sync before it breaks.⸻🧬 Meta-Intelligence Indicators • Thinks in loops, not lines.• Compresses complexity into elegant, minimal architectures. • Balances abstraction (theory of systems) with embodiment (practice of flow). • Learns new tools not for novelty, but for integration. • Communicates visually, spatially, and narratively — not just in text. • Understands that “infrastructure” is a cultural and psychological design problem as much as a technical one.⸻💡 Preferred Backgrounds (non-exclusive)• Systems Design / UX Strategy / Creative Tech / Ops Engineering / Workflow Design • Experience in hybrid creative or R&D teams (film, design, interactive media, AI start-ups, experimental labs) • Demonstrated public builds or process documentation — visible evidence of systems authorship.