Senior Software Engineer – Backend (Systems / Infrastructure)

Vizcom Technologies, Inc.; San Francisco (CA); On-site; USD 195,000 - 225,000; Full time

Job summary

Vizcom Technologies, Inc. is seeking a Senior Software Engineer – Backend (Systems / Infrastructure) to architect and deliver robust backend systems. You will focus on scaling Vizcom as customer demand grows, working on optimizations and integrations to ensure high performance and reliability.

Your role requires 5-8+ years of experience in production web systems, strong skills in databases and distributed systems, and familiarity with Kubernetes. The position offers an annual salary of $195,000 - $225,000 plus equity.

Qualifications

• 5-8+ years building production web systems (TypeScript/Node or similar).
• Strength in databases, performance tuning, and distributed systems.
• Experience operating Kubernetes or similar orchestration environments.
• Fluency with observability tools and debugging live systems.

Responsibilities

• Design and implement scalable APIs in TypeScript/Node with GraphQL.
• Profile and optimize slow paths — queries, resolvers, and I/O.
• Build and operate distributed systems: job queues, streaming, caching.
• Collaborate with AI engineers to integrate GPU inference pipelines.
• Improve reliability: lead incident reviews, strengthen CI/CD.

Skills

Production web systems

Databases

Performance tuning

Distributed systems

Kubernetes

Observability tools

Tools

TypeScript

Node.js

GraphQL

Postgres

Redis

Job description

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 from queueing GPU workloads to optimizing GraphQL resolvers and streaming 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 one critical 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 one observability improvement (metrics, traces, alerts).

Compensation

$195,000 - $225,000 annually + Offers Equity

What You’ll Do

• Design and implement scalable APIs in TypeScript/Node with GraphQL and Postgres
• Profile and optimize slow paths — queries, resolvers, and I/O
• Build and operate distributed systems: job queues, streaming, caching, and observability
• Collaborate with AI engineers to integrate GPU inference pipelines into user workflows
• Improve reliability: lead incident reviews, strengthen CI/CD and deployment flows
• Mentor teammates on 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.

Qualifications

• 5–8+ years building production web systems (TypeScript/Node or similar)
• Strength in databases, performance tuning, and distributed systems
• Experience operating Kubernetes or similar orchestration environments.
• Fluency with observability tools and debugging live systems.
• Bonus: GPU workloads, background job systems, or realtime architectures.

How We Work

• Small 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.