Solution Engineer
Posted 8 days ago
The role in short
Embed with the deployment team to build, test, and ship physical AI agents and supporting software integrations for high-profile customer venues.
This Isn’t Your Typical Engineering Job
Imagine this: you’re backstage at the NFL Super Bowl, making sure a physical AI agent is ready to go live in front of millions—and NFL Commissioner Roger Goodell walks by to check it out. A few weeks later, you’re at San Jose International Airport deploying AI alongside City Mayor Matt Mahan. Then you’re at NVIDIA GTC, the world’s biggest AI conference, and you bump into Jensen Huang himself.
That’s not a hypothetical. That’s what our team actually did.
At LiveX AI, we build physical AI agents—intelligent, embodied systems that interact with people in the real world. Not chatbots on a screen. Real AI that lives in airports, stadiums, conference halls, and beyond. We’re looking for a bold, driven Solution Engineer to join our core team full-time and help us deploy these systems on the world stage.
About LiveX AI
LiveX AI is a fast-growing startup headquartered in the San Francisco Bay Area, building the next generation of physical AI agents. Our technology combines advanced large language models, multimodal AI, and purpose-built hardware to create AI experiences that people interact with face-to-face. We’re backed by leading investors and trusted by enterprises, cities, and major event organizers worldwide.
What You’ll Do
You’ll be embedded in our core deployment team—the people who take our AI from the lab to the real world. Here’s what the role looks like:
- Ship Physical AI Agents: Build, test, and deploy AI-powered hardware systems to real venues—airports, stadiums, conference centers, retail spaces. You’ll own deployments end to end and see your work in action, not just in a staging environment.
- Get Your Hands Dirty with Hardware: Set up screens, sensors, networking gear, and edge compute devices. Debug on-site. Make AI work in the physical world where Wi-Fi drops, power flickers, and thousands of people walk by.
- Write Real Code: Build software that powers our AI agents—Python, TypeScript, APIs, integrations. Contribute to the same codebase the rest of engineering works in. Your commits go to production.
- Work the World’s Biggest Stages: Lead and support deployments at marquee events and high-profile locations. Previous team deployments include the NFL Super Bowl, San Jose Airport, and NVIDIA GTC. You could be next.
- Talk to Real Humans: Present demos to customers, partners, and VIPs. Explain how our AI works to both technical and non-technical audiences. Your communication skills matter as much as your code.
- Shape the Product: Feed real-world observations back to engineering and product. When you notice something in the field, your input directly influences what we build next.
Where Our Team Has Been
NFL Super Bowl
Physical AI agent deployed at the biggest sporting event in America. Commissioner Roger Goodell experienced the demo firsthand.
San Jose International Airport
AI agent deployed in a live airport environment, unveiled alongside San Jose Mayor Matt Mahan.
NVIDIA GTC
Live deployment at the world’s premier AI conference. Our team had an encounter with NVIDIA CEO Jensen Huang.
How We Evaluate Candidates
We hire for the traits that make someone thrive in fast-moving, high-stakes deployments. Every candidate is evaluated on four things:
- Responsibility & Dedication. You take full ownership of your work and follow through. When a deployment is on the line, you do whatever it takes to get it right—and you can be counted on.
- Speed of Learning. Our stack, our hardware, and our customers change fast. You pick up new tools, technologies, and contexts quickly and turn them into results without hand-holding.
- Multi-Tasking Capability. You juggle code, hardware, customers, and live events at once—often in the same day—and keep all of them moving without dropping the ball.
- Communication Skills. You explain technical concepts clearly to anyone—a mayor, a CEO, a teammate, or a curious bystander—and you keep the team aligned under pressure.
Who You Are
- Ideally, you’ve delivered enterprise software at a startup, or run enterprise projects at a consulting firm—you know how to ship for demanding customers and manage delivery end to end.
- You code. Python, JavaScript/TypeScript, or both. You’ve built and shipped things that went beyond the spec.
- You’re genuinely excited about AI—not just the hype, but how LLMs, computer vision, and multimodal models actually work under the hood.
- Hardware doesn’t scare you (or it does, but you want to learn anyway). You’re willing to carry a monitor, run cables, and troubleshoot on-site.
- You communicate clearly—to a mayor, a CEO, or a curious bystander at a trade show.
- You thrive in chaos. Startups are messy. Deployments have surprises. You stay calm, figure it out, and keep going.
- You’re a team player who brings energy, not ego.
Bonus Points
- Experience with LLM frameworks (LangChain, LlamaIndex), prompt engineering, or RAG pipelines.
- Familiarity with edge computing, IoT, AV systems, or robotics.
- Prior startup or hackathon experience where you shipped something under pressure.
- Background in CS, EE, information systems, or a related technical field.
Why You’ll Love This
- World-Stage Experiences: Your LinkedIn won’t say “updated Jira tickets.” It’ll say “deployed AI at the Super Bowl.”
- Full-Stack, Full-Real: AI + software + hardware + customer-facing—you’ll build a skill set most engineers don’t reach until years into their careers.
- Silicon Valley, Front Row: You’ll work at the center of the physical AI movement, with the connections and momentum that come with it.
- Mentorship That Matters: You’ll work directly with founders and senior engineers who want to see you grow—not hand you busywork.
- Real Ownership & Growth: Top performers take on more scope fast—leading deployments, owning customers, and shaping the product.
Prep for this interview
4 questions likely to come up at LiveX AI, each matched to a line in this posting.
- 1LLMs, RAG and agents
They wrote: “Experience with LLM frameworks (LangChain, LlamaIndex), prompt engineering, or RAG pipelines.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
- 2Integrations and APIs
They wrote: “Write Real Code: Build software that powers our AI agents—Python, TypeScript, APIs, integrations. Contribute to the same codebase the rest of engineering works in. Your commits go to production.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 3Coding
They wrote: “You code. Python, JavaScript/TypeScript, or both. You’ve built and shipped things that went beyond the spec.”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 4Ownership and working with customers
They wrote: “1. Responsibility & Dedication. You take full ownership of your work and follow through. When a deployment is on the line, you do whatever it takes to get it right—and you can be counted on.”
Tell me about something you shipped that broke in production.
How to answer
Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.
- What broke and who it affected
- How you found out and what you did in the first hour
- The root cause, said plainly
- What you changed so it can't happen the same way again
Tip: Pick a real one with a cost. Spend most of the answer on what you changed.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.
