Senior Staff Engineer (Technical Lead) - Full Stack (C#, React, AWS & AI)

Job Description

Location: Remote

\n

Level: L6 Senior Staff Engineer

\n

\n

About ViewNexa

\n

ViewNexa is a streaming and app development platform for broadcasters, publishers, and media companies. We give them one workflow to ingest, manage, distribute, and monetize live, VOD, and FAST content across web, mobile, and connected TV experiences, including Roku, Fire TV, Apple TV, Samsung, iOS, and Android.

\n

\n

We are a product-engineering company: live encoding and transcoding, a high-scale backend platform on AWS, a React-based CMS, and native/CTV applications that have to work on real devices, not just in a browser.

\n

\n

The Role

\n

This is a hands-on role. 60-80% of your week is writing production code: C#/.NET on the backend, React/TypeScript on the frontend. You write the code yourself. What you ship is how other teams move: reference implementations, the hard problems, and the standards they actually follow.

\n

The remaining 20-40% is architecture, review, and mentoring across teams. You set cross-team technical direction by shipping, not by running a meeting calendar. This is not a people-manager job.

\n

AI is part of the job, not the whole job. We want someone who has put LLMs into real product workflows (APIs, RAG, agents, or production integrations), not a research scientist and not someone whose only AI experience is ChatGPT.

\n

\n

What You Will Do

\n

\n
• Ship the work other teams cannot or should not take on: gnarly C#/.NET services, React/TypeScript hotspots, production AI integrations. You write a large share of that code, including the challenging bits.
\n
• Take problems from concept to production without needing course correction from leadership. You operate what you ship: AWS services, events, messaging, data stores, caching, CI/CD, and observability.
\n
• Set technical direction across teams by landing the pattern they adopt: APIs, UI architecture, data, and cloud. Standards live in code and review, not in a wiki nobody follows.
\n
• Raise frontend quality in a large web app in a way multiple teams can reuse: React/TypeScript component architecture, state management, performance, testing, and API integration.
\n
• Identify where generative AI actually helps (internal tools, CMS workflows, support, agent-assisted development) and ship those integrations with production constraints: eval, cost, latency, safety, and fallbacks. Then help other teams use the same approach.
\n
• Lead through architecture, code review, and mentoring across teams, not through status meetings. Reviews and design docs are the 20-40%, not a substitute for writing code.
\n

\n

\n

Required Experience

\n

\n
• Full-stack ownership. Deep C#/.NET plus strong, recent, hands-on React and TypeScript. You should be credible in both layers in a design review, not a backend engineer who "also touches CSS."
\n
• You have written and shipped production code yourself in the last 6-12 months, in both layers. We will go deep on code you wrote, not only systems you directed.
\n
• Typically 8-12 years of experience, including at least ~2 years as the technical lead for an area: architecture, mentorship, and shipping without being steered through the work. Then evidence you stepped up: teams outside your group took your direction.
\n
• Distributed systems on AWS: APIs, event-driven services, messaging, data stores, caching, CI/CD, observability, and infrastructure. You have designed and built systems that other teams now depend on, not only consumed them.
\n
• Cross-team technical leadership, not only tech lead of one group. Architecture ownership, standards other teams adopted, code reviews, mentoring, and still writing a large share of the code. Title alone is not enough. We will ask which teams followed you, what you personally built, and what changed because of it.
\n
• Advanced React/TypeScript: component architecture, state management, API integration, performance, testing, and large-scale SPA development.
\n
• Hands-on production exposure to AI/ML or generative AI in at least one of: LLM APIs, model inference, RAG, vector databases/embeddings, AI agents, or shipping an AI feature used by real users or internal operators.
\n

\n

\n

Strongly Preferred

\n

\n
• Multi-tenant SaaS or CMS/admin product experience.
\n
• Media, OTT, or publishing domain familiarity.
\n
• A track record of introducing AI in a way that reduced cycle time or operating cost, with a clear view of failure modes (hallucination, eval, prompt/version control), and of spreading that pattern beyond one team.
\n
• Experience inheriting a large React codebase and improving it without a rewrite.
\n
• A clear step up from leading one area to having impact across teams, while still writing production code.
\n
• Native or CTV app exposure (this role is web + backend first).
\n
• CloudFormation/Terraform and a close working relationship with DevOps.
\n

\n

\n

This role IS a fit if..

\n

You want most of your week in the editor, and that work is how multiple teams move. You have already been a technical lead for an area (architecture and mentorship) and you can point to teams that adopted your direction. You still write production code yourself, and you have at least one AI integration you can demo, including what you would not put in production yet.

\n

\n

This role IS NOT a fit if..

\n

You want a people-manager job, or a role where coding is "when I have time." Also not a fit if you have only led one area and have not set direction across teams, or if you want an ML research role or a frontend-only React position.