> Markdown version of [/jobs/ext/2601311-fullstack-software-engineer](https://www.wearedevelopers.com/jobs/ext/2601311-fullstack-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Fullstack Software Engineer - **Company:** Samba TV - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Salary:** $180,000.0 - $235,000.0 - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Microsoft Azure, Code Review, Computer Engineering, Continuous Integration, Relational Databases, Software Debugging, Software Design Documents, Web Development, Python (Programming Language), PostgreSQL, Node.Js, OAuth, OpenID, Microsoft PowerPoint, Prometheus, Next.js, Service Layer, Software Engineering, SQL Databases, Data Streaming, TypeScript, Web Platforms, WebSocket, Working Model 2D, Datadog, Network Routers, Scripting, ReactJS, Large Language Models, Grafana, Multi-Agent Systems, Backend, Git, Webpack, Information Technology, Sentry, Live Streaming, Graphql, Front End Software Development, Api Management - **Published:** August 10, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=42f17515af04acb3 ## About the Role * Deep in JavaScript/TypeScript and Node. This is the center of the role. You write clean, type-safe code and lean on the type system rather than fight it, and you're comfortable owning backend services and APIs and reasoning about data flowing over REST and SSE. * Genuinely full-stack, with real front-end depth where it counts. You have meaningful, hands-on React experience and a solid grasp of the web platform. What matters most here isn't breadth of UI work - it's judgment on the hard parts: streaming and asynchronous state, reconnection and mid-flight failure, rendering performance under long-running token streams, and accessibility. You can reach for AI tools to move fast, but you own the correctness of what ships rather than trusting generated code to get these edge cases right. You can lead front-end work when the team needs coverage, without needing it to be the bulk of your work. * An architectural thinker. You can weigh trade-offs, write a clear design doc, and explain the "why" so others can build on it. You've helped shape the technical direction of a team, not just your own tickets. * Fundamentals. Solid with relational databases (PostgreSQL) and SQL, Git, and CI/CD. You understand how applications get deployed to the cloud (AWS, GCP, or Azure) and how to operate what you ship. * A multiplier. You explain technical ideas clearly, give constructive review, and raise the people and code around you. You're open to feedback and you disagree well. * Education / experience. A Bachelor's degree in Computer Science, Computer Engineering, or a related technical field, or equivalent practical experience. Typically 6+ years of professional full stack / web application development, including experience providing technical leadership on a team., * Experience with a modern SSR/full-stack React framework (Next.js, Remix, or TanStack Start) and the surrounding ecosystem (Query, Form, Router). * Familiarity with AI / LLM application development - streaming chat UIs, tool-calling, or agentic/multi-agent patterns. Depth here is a strong plus at this level. * Experience building real-time or streaming interfaces (SSE, WebSockets) and the UX patterns that go with them. * Familiarity with type-safe API contracts (tRPC, Hono RPC, or GraphQL) shared across a monorepo. * Comfort with modern tooling: pnpm monorepos, Vite, and a TypeScript-first workflow. * Experience with auth flows (Auth0, OAuth/OIDC, JWTs) in a single-page or SSR app. * Familiarity with observability tooling - Sentry, OpenTelemetry, Prometheus/Grafana, or similar - for debugging and operating production systems. * Experience in AdTech, MediaTech, or data-heavy product environments. * Knowledge of scripting (Python, Go, or shell) for automation and testing. ## Description * Design across the whole system. Make and document the architectural calls that span the AI/backend engine, the service layer, and the UI - orchestration boundaries, streaming protocols, the type-safe client-to-server contract, artifact and file-delivery flows, persistence, and error/reconnection strategy. Turn ambiguous product goals into designs the team can build against. * Build on the backend and AI layer. Work in the engine that powers the product - extending backend services and their capabilities, wiring model interactions and structured outputs, handling streaming, and managing state and persistence. Reason about latency, cost, and failure modes across the system. * Own the service layer. Extend the Node backend-for-frontend between the UI and core services - building endpoints, streaming responses (SSE) to the browser, enforcing auth, and keeping the client-to-server contract type-safe end to end. * Ship UI, and provide front-end coverage. Build a streaming, chat-style interface in React on a modern SSR framework - live token streams, progress indicators, and inline interactive content - and turn structured data into interactive charts, tables, and the download/preview experience for generated documents (e.g., PPTX, PDF). Be someone the team can rely on to carry meaningful front-end work when needed. * Provide technical guidance to the team. Set the bar in code review, weigh in on design docs, and help other engineers navigate a fast-moving AI-native codebase. Spot risk early - performance, complexity, streaming-state edge cases - and steer around it before it ships. * Get streaming and async right. Handle the realities of long-running, asynchronous work end to end: partial/streaming state, loading and "generating" transitions, reconnection, large-payload handling, and graceful behavior when a request fails mid-flight. * Raise quality. Write unit, integration, and end-to-end tests, instrument what you ship, and use logs, traces, and error tracking to debug issues that span the UI and the services behind it. * Understand the context you're working in. Build a working model of how the system and its downstream dependencies behave, and use it to make good product and implementation calls rather than waiting for fully-specced tickets. * Collaborate and mentor. Partner with product, design, and platform/backend engineers, and level up the engineers around you through review, pairing, and clear technical writing., * Senior full-stack engineer. You've owned significant features and systems end to end across the stack - services, APIs, and UI - and operate with autonomy. You default to action, but you also think about the second-order effects of a design. ## Related Videos - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Keeping applications secure by evolving OAuth 2.0 and OpenID Connect](https://www.wearedevelopers.com/videos/100152-keeping-applications-secure-by-evolving-oauth-2-0-and-openid-connect) - [From Doubt to Confidence: How Sentry Uses Verdaccio to Bulletproof SDK Releases](https://www.wearedevelopers.com/videos/739-from-doubt-to-confidence-how-sentry-uses-verdaccio-to-bulletproof-sdk-releases) - [Build and Deploy a Fullstack App with Open Source Tooling](https://www.wearedevelopers.com/videos/775-build-and-deploy-a-fullstack-app-with-open-source-tooling) - [Debugging in the Dark](https://www.wearedevelopers.com/videos/1658-debugging-in-the-dark) - [Delay the AI Overlords: How OAuth and OpenFGA Can Keep Your AI Agents from Going Rogue](https://www.wearedevelopers.com/videos/1637-delay-the-ai-overlords-how-oauth-and-openfga-can-keep-your-ai-agents-from-going-rogue) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss) - [Dev Digest 130 - The Diablo is in the details](https://www.wearedevelopers.com/magazine/470-dev-digest-130-the-diablo-is-in-the-details) - [Web Development Best Practices: What The Data Tells us](https://www.wearedevelopers.com/magazine/84-web-development-best-practices-what-the-data-tells-us)