Skip to main content
David Careers

Senior Software Engineer - Backend

Posted 6 days ago

vizcomMillbrae (CA)
Software DevelopersSoftware Publishers

SENIORITY

Lead

SALARY

$195,000 per year

Apply (opens in a new tab)

About the role

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
The Role: As the Senior Software Engineer – Backend (Systems / Infrastructure)you’ll architect and deliver backend systems that keep Vizcom fast, reliable, and scalable as our workload and customer base grow. You’ll work on everything fromqueueing GPU workloadstooptimizing GraphQL resolversandstreaming realtime events. You’ll have deep ownership over APIs, performance, and data integrity — while collaborating with frontend and AI teams to enable magical experiences. Within your first 90 days you will: ship onecritical backend feature(e.g., model queue, caching layer, or realtime service), reduce p95 latency in one major API path by ~30%, Author one technical RFC proposing an improvement to architecture or reliability, Implement or document oneobservability improvement(metrics, traces, alerts).Compensation $195k - $225,000K + Offers Equity
What You’ll Do:
  • Design and implement scalable APIsin TypeScript/Node with GraphQL and Postgres
  • Profile and optimizeslow paths — queries, resolvers, and I/OBuild and operate distributed systems:job queues, streaming, caching, and observability
  • Collaborate with AI engineersto integrate GPU inference pipelines into user workflows
  • Improve reliability:lead incident reviews, strengthen CI/CD and deployment flows
  • Mentor teammateson backend architecture, testing, and performance thinking
  • The Problems You’ll Tackle
  • Distributed GPU inference and queueing with bursty workloads.
  • Realtime synchronization with WebSocket and CRDT-based collaboration.
  • GraphQL performance: caching, batching, resolver optimization.
  • Secure multi-tenant data boundaries and enterprise integrations (SSO/SAML/SCIM).Our Stack (today)
Frontend: TypeScript, React, Vite, WebGL; realtime collaboration. API/Backend: TypeScript/Node, GraphQL (PostGraphile), Postgres, Redis, background workers. Infra: Kubernetes, Pulumi, CI/CD with GitHub Actions, Datadog for observability, feature flags. Security/Enterprise: SSO/SAML (WorkOS), SOC 2-minded practices. Experience with every item above is not required. What matters is that you are excited to shape it. Qualifications5–8+ years building production web systems (TypeScript/Node or similar) Strength indatabases, performance tuning, anddistributed systems Experience operating Kubernetesor similar orchestration environments. Fluency withobservabilitytools and debugging live systems.
Bonus: GPU workloads, background job systems, or realtime architectures. How We WorkSmall team, high ownership. Fewer people, more leverage. Design-centric. We obsess over speed and feel; “fast enough” usually is not. Write it down. RFCs, crisp decisions, living docs. Operate what you build. Everyone takes on-call support; incidents drive improvement, not blame.
Interview Process:
  • Intro (30m): mutual fit, role and impact.
  • Architectural deep-dive (45m): product and design collaboration.
  • Coding Session (45m):Onsite Interview (half day)
  • References and offer.
  • Ready to Build?
If you want your work to be used daily by world-class designers and you like owning problems end to end, let’s talk. Apply with links (GitHub, LinkedIn, notable projects) and a short note on something hard you shipped.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this