Why Vizcom
Our mission is to reshape design by streamlining the path from concept to creation, bringing more impactful ideas into the physical world.
We’re well-funded (Series B $51m to date), growing double-digits MoM, and expanding the core engineering team in SF. The surface area is big: realtime collaboration, GPU inference at scale, a modern TypeScript stack, and serving real enterprise customers.
The Role
Take end to end ownership of critical product areas, from architecture through launch, and set the technical direction for how we build at scale. You will drive design reviews, ship prototypes that push our product forward, and establish pragmatic engineering standards that balance speed and quality. Beyond your own contributions, you will mentor teammates into future tech leads and help us grow a world class engineering culture as Vizcom scales.
Interview Process (fast; no leetcode)
Intro (30m): mutual fit, role/impact.
Architectural deep-dive (60–75m): a real Vizcom problem; you drive the trade-offs.
Hands-on working session (90m): pair on a small, realistic slice.
Cross-functional chat (30m): product/design collaboration.
Founder/CTO conversation (30–45m): values, scope, expectations.
References & offer.
(Optional paid work sample if preferred to a take-home.)
Set the architecture roadmap to keep Vizcom reliable, scalable, and a joy to develop in as usage, models, and data grow.
Ship hands-on: jump into code for critical paths, rapid prototypes, and hairy debugging (latency, memory, race conditions, WebGL/WASM quirks).
Install quality guardrails that scale: test strategy, code-review norms, perf budgets, observability baselines.
Mentor and multiply: develop senior engineers into tech leads; model clear written design and crisp decision-making.
Partner cross-functionally: represent engineering trade-offs with Product/Design/Go-To-Market and act as the CTO’s delegate when needed.
90-Day Outcomes
Reliability & perf: land an observability-driven plan for our top-5 critical flows. Reduce p95 for at least one user-visible flow by ~30% through targeted fixes (query plans, caching, batching, streaming, GPU/CPU boundaries).
Architecture: author one substantial RFC (e.g., realtime doc model, rendering pipeline boundaries, or background job topology) and lead it to adoption.
Team health: mentor two engineers with measurable growth (scope, design quality, or incident handling).
Developer experience: remove one persistent friction (local env speed, CI flakiness, or flaky e2e surface) and document the standard.
The Problems You’ll Tackle
High-fanout realtime collaboration (WebSockets/CRDT-style data models).
GPU-backed image generation pipelines and queueing with bursty workloads.
Performance across the stack: React/Vite bundles, GraphQL n+1s, Postgres query plans, caching at the right layer.
Enterprise-grade SSO/SAML/SCIM, auditability, and secure multi-tenant boundaries.
A design-forward UX that must still feel instant under load.
8–12+ years building distributed web systems (TypeScript/Node preferred) with 2+ years at Staff scope.
Depth with Postgres and performance/observability (profiling, traces, query tuning).
Experience with container orchestration and production ops (K8s or equivalent).
Bonus: realtime collaboration models, WebGL/WASM, GPU workloads, or enterprise identity (SSO/SAML/SCIM).
How We Work
Small team, high ownership. Fewer people, more leverage.
Design-centric. We obsess over speed and feel; “fast enough” usually isn’t.
Write it down. RFCs, crisp decisions, living docs.
Operate what you build. Everyone on call support; incidents drive improvement, not blame.