Technical Founders Associate

Role: Technical Founder’s Associate / Engineering Chief of Staff Location: Sunnyvale, CA (Mostly remote but opportunity to work F2F with CTO) Compensation: Academic Co-op (UC Berkeley/Stanford) OR Base + Potential startup Equity The Reality: At Juice, we are making every second count. The platform authenticates vehicles at the edge using existing site cameras. Zero new hardware, instant M2M payments. As a lean, VC-backed team of three, Juice is already processing millions of transactions globally. The CTO (ex-Google, Microsoft, 2x IoT exits) is building the deep-tech architecture connecting today's $5 Trillion mobility market to tomorrow’s $13 Trillion autonomous economy. Because the company is scaling at an unreasonable velocity, the CTO needs a high-leverage technical force multiplier. We are not looking for a standard software engineer who wants to be spoon-fed Jira tickets. Juice is looking for an absolute powerhouse to step into the role of Technical Founder’s Associate. In Silicon Valley, this is the engineering equivalent of a Chief of Staff. You will operate as the CTO’s technical proxy and right hand. You are a technical Swiss Army knife—you have the hardcore computer science chops to ship production code, but you also possess the systems-thinking required to map out massive enterprise integrations, read dense API documentation from legacy vendors, and ruthlessly unblock the core engineering pipeline. If you want a traditional FAANG internship where you spend three months changing a button color, close this page. If you want a masterclass in edge computing, computer vision, and building massive technical moats from the ground up alongside a 2x-exited founder—read on. What you will execute: Force-Multiply the CTO: Take high-level, ambiguous architectural directives from the CTO, break them down using strict first principles, and build the initial prototypes and integration frameworks before they hit the core engineering pipeline. Wrangle Legacy Infrastructure: The mobility industry runs on messy, legacy hardware APIs (parking barriers, 15-year-old EV chargers, wash systems). You will elegantly integrate bleeding-edge AI with decades-old tech infrastructure, forcing them into the 21st century. Technical Operations: Evaluate hardware vendors, build internal God-mode telemetry dashboards to track the latency of thousands of edge cameras, and act as the technical translator in tier-1 partnership meetings. Ship Real Code: Push code to active US sites processing real financial transactions. There is no massive QA team to catch mistakes. You build it, you ship it, you own it. >> HOW TO APPLY Proof of Work (Do not send a resume): Submit your GitHub profile and a 1-page Notion link to my LinkedIn DMs containing: The AI Architecture: Using first principles, how would you optimize an AI computer vision model running on constrained edge hardware to consistently identify a dirty, angled license plate at night with >99% accuracy, while minimizing cloud compute latency to make every second count? The Integration: You are on a call with a multi-billion dollar parking network running on legacy, 15-year-old on-premise boom gates. In 3 bullet points, what is your exact technical approach to bridging their legacy hardware with our modern cloud billing API in under 1 second?

Created: 2026-03-12