Part strategist, part engineer, part product owner — and entirely something new.
If you just graduated with a technical degree and you're browsing job boards, you've probably seen the usual suspects: software engineering roles, data analyst roles, consulting rotational programs, and a sea of "customer success" positions that sound vaguely important but suspiciously undefined.
Product Solutions at EliseAI is none of those things.
It's also not support. Not account management. Not a stepping stone to something else.
It is, genuinely, one of the most interesting entry points into an AI company that you can find right now — and the people who thrive in it tend to be the ones who couldn't quite fit themselves into a single box.
This post is for them.
.svg)
A role that didn't exist before AI made it necessary
EliseAI builds AI for essential industries — housing and healthcare. The kind of AI that answers every resident call at midnight, automates maintenance workflows, and handles the administrative complexity that burns out frontline workers.
When AI gets this embedded in operations, the traditional "support" model stops making sense. You can't run a ticket queue for a system that's actively reshaping how an entire industry functions. You need people who understand the product deeply, who can sit with a customer and figure out what's actually happening on the ground, and who can translate that back into something the engineering team can build on.
That's the role. And it's called Product Solutions.
What you'll actually spend your time doing
Forget the image of a support queue with headphones on. In Product Solutions, a single week might include:
- Leading a discovery session with a property management operator to understand how their maintenance team actually works day-to-day
- Diagnosing why an AI model is behaving unexpectedly in a specific customer environment and working with engineering to resolve it
- Designing a new workflow for how EliseAI handles a situation that the product hasn't encountered before
- Building internal tooling or writing a playbook that becomes the standard for how the team operates at scale
- Presenting a rollout strategy to a customer's leadership team
There are no scripts. There's no defined escalation path. When something isn't working, the expectation isn't to pass it up the chain — it's to fix it.
That's a significant shift from how most early-career roles work. It requires comfort with ambiguity. It rewards people who don't wait to be told what to do.
The profiles who succeed
Over time, a few distinct archetypes have emerged as the people who love this role most. You don't have to be exactly one of them — but if you recognize yourself in any of them, pay attention.
The Translator
You've always been the person who can explain technical things to non-technical people, and vice versa. In a lecture, you understood the concept and you understood why your classmate was confused by it. You've probably done this informally your whole life without naming it.
In Product Solutions, this is a core skill. The gap between what AI can do and what a housing operator or healthcare administrator understands is wide, and someone has to bridge it. That person has to be credible on both sides of the conversation. They need to speak to a CTO and a frontline leasing agent in the same week and earn the trust of both.
If this sounds like you, Product Solutions puts that skill at the center of your work — not as a nice-to-have, but as the actual job.
The Debugger Who Hates Bad Systems
You're the person who, when something is broken, cannot leave it alone. Not because you were asked to fix it, but because the brokenness bothers you. You've rebuilt your own workflows, automated things that didn't need to be automated, reorganized folders that weren't yours to reorganize.
At EliseAI, this instinct is an asset. Product Solutions is expected to build — tooling that automates troubleshooting, systems that proactively flag issues before customers notice them, internal dashboards that give the engineering team better visibility into how the AI is performing in real environments.
The team's output isn't just customer outcomes. It's infrastructure that makes the whole company smarter.
The Early Founder (Or the Person Who's Been Thinking About It)
You've thought about starting something. Maybe you did a startup project in college. Maybe you ran a small side thing. Maybe you just have a long note on your phone called "ideas."
What draws people like you to Product Solutions is the ownership model. You own a domain — not a task list, not a set of tickets, but a slice of the product in the real world. You're accountable for how it performs. You're expected to act like a product owner, which means everything from understanding the customer's problem to defining the solution to measuring whether it worked.
Many people in this team describe it as what founding a company feels like, without having to raise the money first.
What makes this role different from early-career jobs
Most early-career roles give you a narrow lane for the first year or two. You get good at the lane. Then you get a slightly wider lane.
Product Solutions at EliseAI doesn't work that way.
You'll touch product discovery, solution design, rollout, adoption measurement, and internal tooling — often all in the same week. You'll present to frontline operators and to engineering leads. You'll work in industries where the stakes are real: people's homes, people's healthcare.
The company is Series E, which means it has real resources and real customers. But the org structure still feels like an early-stage company (think Series B) — flat, fast, high-trust. If you see something that needs to change, you're expected to say so and then help change it.
For someone early in their career, this is the kind of environment that compresses learning. You don't have five years before you're doing meaningful work. You're doing meaningful work in your first month.
You’ll go deep and technical
A common hesitation for people with engineering or CS backgrounds is whether a non-engineering role will use their skills.
Here's the honest answer: it depends on what you want to use your skills for.
If you want to spend your days writing production code, this is probably not your role.
If you want your technical background to give you leverage — the ability to look at a system and understand what's happening, to work credibly alongside engineers, to build tooling that solves real problems and automate work that shouldn't be manual — then this role puts that leverage to use constantly.
The team builds. It just builds in a different direction than an engineering team does. And the proximity to customers and product means that what gets built is closely connected to what actually matters.
What we're looking for
If this resonates, here's what the role asks of you:
You need to be analytically sharp — comfortable with data, able to distinguish signal from noise when something isn't working, and willing to go deep on a problem instead of assuming you understand it.
You need to be influential without authority — able to get alignment across teams, earn trust quickly, and communicate clearly with people who have very different backgrounds and goals.
And you need to be a builder at heart. Not necessarily a coder. A builder. Someone who looks at a messy process and sees a cleaner one. Someone who finishes a customer conversation and is already thinking about what it means for the product.
Ready to see what this looks like in practice?
There are two ways in:
The Product Solutions Analyst role is designed for people early in their career — technical degree preferred, appetite for ownership required.
The Product Solutions Lead role is for people with experience leading teams who want to build and mentor product solutions analysts while still owning a good chunk of the work.
Both roles are open now.
Explore open roles in Product Solutions →
EliseAI is building AI for housing and healthcare — industries where the technology has to work, not just demo well. If you want to help bring AI into the real world, we're looking for you.