Generalist — Potpie AI

Location: Bangalore
Type: Full-time, In-office

About Potpie

Potpie AI is building the AI-native engineering stack for enterprises.

Large engineering teams have enormous amounts of context spread across codebases, documentation, product requirements, tickets, internal systems, and the people who built them. AI coding tools are powerful, but without this context, their ability to work reliably on complex enterprise systems is limited.

Potpie solves this by building a unified context layer across an organization's engineering ecosystem and using it to power AI agents for software development—from understanding and debugging large codebases to impact analysis, testing, system design, documentation, and implementation.

We work closely with large enterprises and engineering teams to deploy these systems in real-world environments.

We are venture-backed, growing quickly, and still a small enough team that every person has significant ownership over what we build and how we build it.

The Role

We’re looking for a Generalist to work across some of the highest-priority problems at Potpie.

There is intentionally no narrow job description.

You might work on a product problem one week, help structure an enterprise engagement the next, research a new market or technology, build an internal process, prepare an important customer proposal, or take an ambiguous problem from the founders and figure out how to solve it.

The common thread is ownership.

You should be someone who can take a loosely defined problem, understand it quickly, bring structure to it, and drive it to completion without needing someone to tell you every next step.

This role will work closely with the founders and across product, engineering, customers, GTM, and operations.

What You’ll Work On

Product & Strategy

Work with the founders and product/engineering teams on new product initiatives.

Talk to customers, understand problems, synthesize feedback, research markets and competitors, help structure product requirements, and turn ambiguous ideas into something the team can execute.

Customers & Enterprise Projects

Work directly with enterprise customers to understand their requirements and make sure projects move forward.

This could mean helping structure an engagement, coordinating across customer and internal teams, identifying blockers, tracking deliverables, or helping turn customer problems into product requirements.

You may spend time working directly from customer offices when required.

GTM

Support strategic enterprise opportunities across research, proposals, RFPs, demos, partnerships, and customer conversations.

You’ll learn how complex enterprise software gets evaluated, purchased, deployed, and expanded.

Operations

As the company grows, things will inevitably break.

You’ll identify operational gaps, create processes where necessary, automate things that shouldn't be manual, and help make the organization run better.

The goal isn't to create process for the sake of process. It is to remove friction and help the company move faster.

Special Projects

Some of the most important things you work on won't fit neatly into any function.

If something matters to Potpie and doesn't have an obvious owner, you may be the person who figures it out.

What We're Looking For

We care much more about how you think and operate than your previous job title.

You’ll probably thrive here if you:

• Are extremely high-agency and naturally take ownership.

• Can take an ambiguous problem and turn it into a concrete plan.

• Learn new domains unusually quickly.

• Have strong analytical and problem-solving skills.

• Communicate clearly and concisely, both verbally and in writing.

• Are comfortable talking to customers and senior stakeholders.

• Can work effectively with technical teams even if you aren't an engineer.

• Are organized and can manage multiple moving pieces without losing sight of the outcome.

• Can switch between strategic thinking and hands-on execution.

• Are resourceful and figure things out rather than waiting for perfect information.

• Care about quality and have a high bar for your own work.

• Are comfortable operating in a fast-moving environment where priorities can change.

You do not need to be an engineer, but you should be genuinely curious about technology and AI. You should be comfortable learning enough about technical systems to have meaningful conversations with engineers and customers.

What Success Looks Like

Initially, you'll work closely with the founders to understand how Potpie operates and take ownership of specific projects.

Very quickly, we should be able to give you an important but poorly defined problem and trust you to figure out what needs to happen.

Eventually, we expect you to identify those problems yourself.

Success means becoming someone who can understand a problem, bring the right people together, make good decisions, and drive an initiative from “we should probably do something about this” to “done.”

There isn't a predefined career track for this role.

Depending on where you create the most leverage, you could eventually grow into leadership across product, strategy, GTM, operations, customer success, or another function that doesn't exist at Potpie yet.

Culture

We are a small, tight-knit team. People genuinely like working with each other. There is trust, directness, and very little noise.

We work closely with our customers, often from their offices. You’ll see firsthand how large enterprises operate, where things break, and how products get adopted in the real world. Feedback loops are fast and expectations are high.

No two days look the same. One day you might be working on a customer problem, another on product strategy, and another on an entirely new initiative with the founders.

You need to enjoy that mix.

We care deeply about ownership. If something is broken, we fix it. If something is unclear, we bring clarity. There is no “someone else will handle it.”

We keep things simple: direct communication, low ego, high accountability.

You also get the upside of joining an early-stage company while the team is still small enough for you to meaningfully shape the product, the team, and how the company operates.

Why Potpie?

Strong customer pull

We are already seeing real demand from enterprise customers. This isn't speculative. We are working with Fortune 500s and public companies that are actively trying to figure out how AI changes the way their engineering organizations operate.

You'll be in the middle of those conversations.

Build for the real world

Our technology is being deployed in real enterprise environments.

You won't spend months building something in isolation and wondering whether anyone needs it. You'll see customers use what we build, tell us what doesn't work, and push us to make it better.

Join at an inflection point

We have early validation, a growing enterprise pipeline, and clear momentum.

The next phase of Potpie is about scaling execution and capturing the opportunity in front of us.

Joining now means being early enough to meaningfully influence what the company becomes.

Get unusually broad exposure

Very few roles give you visibility across product, engineering, customers, GTM, hiring, operations, and company strategy at the same time.

You'll work directly with the founders and gradually take increasingly important problems off their plate.

If you want to eventually build a company, lead a function, or simply understand how startups actually get built, this is a very high-learning environment.

Help define a foundational layer for engineering

AI is fundamentally changing software development, but making it work inside large organizations requires much more than putting a coding agent in front of developers.

If we get this right, Potpie can become a foundational layer for how modern engineering systems are built and operated inside enterprises globally.

Meaningful upside

You’ll join while the company is still early enough for individual contributions to materially affect its trajectory.

The role comes with competitive compensation and meaningful ESOP ownership, giving early team members the opportunity to participate in the value they help create.

Who Should Not Join

This role probably isn't for you if you want a predictable job with a clearly defined set of responsibilities.

If you prefer waiting for requirements, working exclusively within one function, or saying “that's not my job,” you will probably find Potpie frustrating.

But if you like being handed difficult, ambiguous problems and being trusted to figure them out, you'll have a lot of room here.

We’re looking for people who want scope, ownership, and steep learning curves—not narrowly defined jobs.