fzysingularity
Joined 13 years ago
Joined 13 years ago
We’re building the inference platform for visual intelligence. We’re a deeply technical team of AI / computer-vision engineers (20+ years combined, MIT/CMU/NC State PhDs) who’ve shipped production ML infra across autonomous driving and LLMs.
We launched the VLM Run Gateway (https://vlm.run/gateway) in September, a unified API that serves open-weight VLMs, embodied VLAs, ViTs, served across a fleet of GPUs and clouds. That's exactly the infrastructure problem this role will own. We're already scaling to serve 100s of thousands of requests per day, so if this sounds exciting to you, read on.
Email us at [email protected] with your GitHub profile, papers, ML projects you’ve recently shipped (100+ GH stars only) - especially with Ray, k8s, GPUs, serverless. No AI text please, keep it short, shorter emails are more likely to get a response. No remote work, must be in the Bay Area (specify in email subject).
But both LLMs and Jev-like models would need to prefill, the only optimization Jev does differently is the decode which can be emulated by reading off logprobs.
We don’t know the param size of Jev, to determine the most comparable model, but if I had to guess it’s sub-100B.
This looks pretty decent: https://www.aidancooper.co.uk/constrained-decoding/
The aspect that I like the most is the typesafe API that introduces new probabilistic concepts that are more sound than json schema and constrained decoding with quasi-confidence scores. Developers were asking LLMs to also emit confidences which made absolutely no sense whatsoever.
Take a look at a snake demo with streaming image inputs: https://x.com/spillai/status/2103630735425089957
p(y = next thinking+decision token | x = question) != p(y = next decision token | x = question)
The former is what LLMs are trained for, the latter is what Jev was likely trained on (likely used thinking alignment as an auxiliary loss, but not explicitly included in the probability calibration).