Founding Frontend Engineer

Responsibilities

• Data transfer is unsolved – from hot storage → archive storage, cloud → cloud, camera → editor, moving high volumes of data is still flaky, unreliable and difficult.
• We are building the tooling and UI directly into our platform to make this seamless at scale.
• Version control is useful for everyone – you’re an engineer, git history is useful. We’ve built git for creatives because the same concepts are useful for media teams. We save every version and every file as a commit in our database as changes are made.
• We have the backend built but we need to build the git UI for creatives.
• Integrate with everything – project management tools, AI tools, ad generators and everything in between.
• Shade is built on Python, NodeJS, NextJS, and C++ with a Postgre
  
  SQL database.

• Keep dependencies as minimal as possible.
• You are the summation of your subprocessor’s/dependencies issues. To build a durable and reliable company you must be deliberate when you add dependencies and control the vision of all the code you ship.
• Monolith microservices. Transactional everything requires one database.
• Solve the core issue. Don’t invent a bandaid.
• Example: if a database query is slow, address it directly rather than reaching for a cache.
• The simplicity of fs.read
  
  File() always wins.
• Have you tried to access files in a Dropbox local drive in your programs? It doesn’t work. Files must be manually downloaded in their entirety to be accessed. We’ve built Shade to be accessible like a hard drive where files are streamed.
• Building an AI video editor? Works with Shade.
• Using n8n automations? Works with Shade.
• Using DaVinci Resolve? Works with Shade.

• When we hire we like to keep those hires. Because of this we offer benefits on top of salary + equity.
• Free lunch.
• Fully covered health insurance including dental and vision.
• 401(k) with match.
• Unlimited PTO.

The greatest qualification in our eyes is that you can ship and maintain high volumes of quality code. If you’ve built side projects that are used by thousands of people or worked at companies where you’ve owned features end to end then we’re probably excited about you. What (we think) this looks like in bullet points:

• 4+ years of full‑time engineering experience.
• Proven track record of owning a production frontend end to end.
• Strong React/Type Script experience, ideally including Next.js and Tan Stack‑based apps.
• Experience owning Electron applications in production, including release workflows and over‐the‐air updates.
• Experience working in large, imperfect codebases and driving technical cleanup without slowing product delivery.
• Experience shipping ambitious new product features quickly and with high quality.
• Experience building AI‑powered product experiences, such as chat, search, and content sharing workflows.
• Experience building interfaces that render and manage complex content types, including media and documents.
• Experience integrating with RESTful backend services and familiarity with Web Sockets.
• Strong understanding of frontend architecture and developer experience, and good judgment about where systems, tooling, and code quality need improvement.