Forward Deployed Engineer

About Genrise

Genrise builds agentic software for the digital shelf. Our customers are large global consumer brands, and our platform decides what their products should say on retailer sites like Amazon and Walmart as well as on Agentic surfaces like Rufus, Meta Muse, ChatGPT etc - writes it, and then measures whether it worked. That includes how products show up when shoppers ask AI assistants what to buy, which is changing faster than most brands can keep up with.

We are a small team and growing quickly across the US and UK. Every person here owns something real.

The role

This is one role with two halves, and you need to want both.

You build. You will own one part of the Genrise product end to end: design it, ship it, run it in production, and decide what it should become next.

You deploy. You will be the lead contact for one or more of our customers in the US and UK. You will sit in their working sessions, understand how their teams and processes actually work, get our system running on their data, and drive the engagement forward week to week. When something looks wrong on a customer's data, you are the one who figures out why.

The two halves feed each other. What you learn in a customer's account becomes the next thing you build. What you build is what you put in front of the customer.

You will travel to the US and UK a few times a year to present results to customer stakeholders and take part in their quarterly reviews: what happened, why it happened, and what we do next. You lead those conversations. You do not sit behind someone else who presents your work.

What you will do

• Own a product area from design through production
• Ship working software quickly, with AI coding tools as a core part of how you build
• Lead day-to-day engagement with one or more enterprise customers across US and UK time zones
• Translate messy customer problems into clear technical work, and say plainly when a request is the wrong one
• Diagnose problems on live customer data and fix the root cause, not the symptom
• Present findings to senior customer stakeholders, including results they did not hope for

What we are looking for

• A strong computer science foundation. Most of the people we hire studied CS at the IITs, NITs, or programs of similar rigor. What matters is that your fundamentals are deep: data structures, systems, databases, and the ability to reason about a problem before you code it.
• 1 to 2 years of real engineering experience where you shipped things people used.
• Exposure to e-commerce or retail, ideally. If you have worked on catalogs, marketplaces, search, pricing, or product content, tell us about it. It is a strong plus, not a requirement.
• Ownership. You finish things without being chased. You notice problems nobody assigned to you.
• Clear communication with people who are not engineers. You can explain a technical tradeoff to a brand manager in two minutes, in writing or in a room.
• Judgment about what you know and what you do not. You say "I don't know yet" when that is the honest answer, and then you go find out.
• Strong Python and SQL. Comfort working with LLMs and agent workflows in production is a plus.

What we are not looking for

• People who want to build only and hand the customer to someone else
• People who want to manage customers only and hand the building to someone else
• Long lists of frameworks and certifications. We care about what you built and why it worked

Why this role

• Ownership from your first month: a product area and a customer, not a backlog
• Direct exposure to some of the largest consumer brands in the world, at a stage where most engineers never get in the room
• Work at the edge of AI and commerce, on problems that do not have a playbook yet
• A small team where your judgment shapes the product and the company

How to apply

We are deliberately selective, and we read every application properly.

Send us your CV along with a short note (no more than 200 words) answering this: Tell us about something you built that real users depended on. What broke, how did you find out, and what did you change?

Applications without the note will not be reviewed. We would rather hear from 20 people who took this seriously than 2,000 who clicked apply.