What youll do

- Own the full loop. Understand the business problem, define the solution, architect it, ship it, monitor it. No one hands you a spec.
- Build with AI as your primary tool. Claude Code, Cursor, whatever gives you the most leverage. You should be able to do in a day what used to take a team a week.
- Co-design with your AI Pod. Work directly with your pod and the business to define decision logic, risk thresholds, and success metrics. Youre building capabilities, not features.
- Build the harness before you ship. You dont call something done if you cant measure it. Evaluation frameworks arent optional theyre part of the architecture.
- Own production. Monitoring, alerting, observability these go in on day one, not after the first incident. Youre on call for what you build.
- Raise the bar. When you see a better way, say so. In design reviews, in code, in how the team works.

The DNA were looking for

- Curious. You explore current models and tools before anyone tells you to. You want to understand how things actually work, not just that they work.
- Innovative. You dont wait for best practices to exist you run the experiment and help create them. You iterate fast, share what you learn, and push the boundaries of whats possible.
- Thinks in workflows, not endpoints. You naturally decompose problems into agentic loops, skills, and orchestrated flows. CRUD with an LLM bolted on isnt a system you know the difference.
- You feel the weight of production. When youre designing, youre already thinking about 2am incidents, runaway inference costs, and edge cases that only surface when real money is moving. That instinct to stress-test your own assumptions before shipping is just how you think.
- Full-stack owner. Youre comfortable touching the prompt, the RAG pipeline, the orchestrator, and the backend.



You move up and down the stack to get the job done.
- Builders itch. When you see a repetitive task, or a problem the team has just accepted as 'too hard to fix,' you cant leave it alone. You go home thinking about it. You come back with a working prototype. Watching people do manually what a system could do makes you uncomfortable in a productive way.
- Grounded confidence. You trust your abilities. You dont need sign-off before every decision. You move forward with incomplete information, make a call, and own it. And when youre wrong, you update and move on no drama, no ego. The gap between where you are and where you want to be is what gets you out of bed.

What you bring

- Experience shipping production AI systems not just building them, but watching them run in the real world and fixing what breaks
- Real fluency with AI coding tools not 'familiar with,' genuinely fast with
- Strong eval instincts you define metrics, build test sets, and dont ship until you can measure
- Understanding of agentic architectures: orchestration, multi-step workflows, fallback and error logic
- Comfortable across any stack you go where the right solution is
- Honest communication you flag problems early, give direct feedback, and say what you actually think
- Fintech or regulated-environment experience is a bonus; what matters is understanding why 'probably fine' isnt acceptable when money is moving

We dont require

- A degree
- A specific number of years of experience
- Mastery of any particular framework

How we work and who fits here

- Act as our customers partner on the inside.

Disclaimer : This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 AI-Native Engineer, Team Lead (Gurugram)
🏢 Payoneer
📍 Gurugram