Refold AI
Refold AI

Forward Deployed Engineer

Bengaluru, IndiaHybridMidFull-time

Posted yesterday

The role in short

Build and deploy production-grade agentic AI integrations and workflows directly with enterprise customers to solve complex system connectivity problems.

About Refold

Refold is building the next-generation AI platform that replaces enterprise integration and consultants. We’re pioneering autonomous AI agents that understand complex enterprise systems, generate production-ready code, and operate at a scale no consulting firm can match. Today, we’re starting with integrations—a $50B market. Tomorrow, we’re building towards a world where AI agents handle any complex cognitive work.

Traction: Serving 20+ enterprise customers with Fortune 500 deployments, processing 10M+ API calls/day. Refold was founded by Jugal Anchalia & Abhishek Kumar, who sold their previous startup to Netmeds; they have also been featured in Forbes 30 Under 30. They have experience at organisations such as Nomura, JioMart, InstaMojo, IIT Kharagpur, and IIT Roorkee. We are funded by marquee investors, including Eniac Ventures, Tidal Ventures, Karman Ventures, Ahead VC & Better Capital.

The Role:

As a forward-deployed engineer, you turn the hardest enterprise integration problems into production-grade systems on our agentic platform. You’ll take ambiguous, real-world requirements; messy APIs; undocumented systems; and edge cases nobody anticipated and reason from first principles to ship production-grade integrations.

You’re a curious, hands-on builder with a customer-first mindset and a real passion for AI already on the frontier of agentic tooling and vibe coding and eager to point that energy at real customer problems. You think like a solutions engineer: the goal isn’t to build; it’s to solve. Mostly delivery, with time as the technical engine behind our highest-stakes POCs — and the patterns you uncover shape the platform itself.

  • Team: Small, high-calibre technical team working directly with architects, product, and founders.
  • Building: Agentic AI workflows, connectors, and high-throughput integration pipelines.
  • You’ll work with integration leaders and engineering teams at high-growth SaaS companies and Fortune 500 enterprises.

Key Responsibilities:

  • Solve hard integration problems. Take ambiguous, real-world enterprise requirements and reason from first principles to design integrations that work, including the problems for which no playbook exists yet.
  • Build agentic workflows end-to-end. Implement complete integrations on Refold’s AI-native integration platform, orchestration logic, agentic decision-making, data transformations, and system connectivity against live enterprise systems.
  • Drive product direction from the field. You’re one of our highest-signal sources of product truth. Surface gaps, friction, and missing capabilities you hit while building and validate new platform features through real customer workflows.
  • Power high-stakes POCs. Partner with the pre-sales team to execute the technical work behind proofs-of-concept, building and validating integrations that prove value during the sales cycle.
  • Codify what works. Turn hard-won learnings into reference architectures, integration patterns, and runbooks that scale across the delivery team and feed the support knowledge base.
  • Evolve agentic capabilities. Contribute to the evolution of Refold's agentic workflows — decision-making logic, tool invocation, and autonomous execution within integrations — and feed every implementation back into the skills/graph layer so the platform's agents get measurably smarter with each integration you ship.

Required Skills & Abilities:

  • 2-4 years in solutions engineering, integration engineering, product engineering, or a similar hands-on technical role.
  • A curious, hands-on builder, you reason about systems from first principles, love getting your hands dirty, and are energised by ambiguity.
  • Genuine passion for AI: you already build with cutting-edge tools (LLMs, agentic frameworks, and vibe coding) for fun, not just at work, and you stay on the frontier as it moves.
  • With a customer-first, solutions-engineering mindset, you measure yourself by the problem solved and the outcome delivered, not the code shipped.
  • Strong foundation in APIs, distributed systems, and common integration patterns.
  • Hands-on proficiency in Python and/or JavaScript / TypeScript (Node.js).

Nice to Have:

  • Experience with enterprise systems such as Salesforce, SAP, Oracle, Workday, NetSuite, or ServiceNow.
  • Familiarity with iPaaS or workflow automation platforms (Workato, Boomi, MuleSoft, Zapier, Merge).
  • Experience with cloud infrastructure (AWS, GCP, and Azure) and containerised environments (Docker and Kubernetes).
  • Hands-on experience building with LLMs and agentic frameworks (OpenAI, Anthropic, open-source models, agent orchestration).
  • Background at an early-stage startup where product and engineering responsibilities were tightly coupled.

Why Join Refold AI?

  • Fast-growing seed-stage company (raised $6.5M from Eniac Ventures & Tidal Ventures)
  • Founding team opportunity to shape engineering culture and technical direction from day one
  • Cutting-edge AI + infrastructure tech solving complex, high-value enterprise problems
  • Early traction with Fortune 500 clients and high-growth software companies
  • Direct line of sight to leadership and future engineering management path
  • Work with a small, exceptional team that ships fast and celebrates bold ideas

Prep for this interview

5 questions likely to come up at Refold AI, each matched to a line in this posting.

  1. 1Cloud, deployment and security
    They wrote: “Experience with cloud infrastructure (AWS, GCP, and Azure) and containerised environments (Docker and Kubernetes).”

    How would you debug a deployment that works in staging but fails at the customer's site?

    How to answer

    Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.

    1. Compare versions, config and environment variables
    2. Check network rules, proxies and certificates (common in enterprise)
    3. Look at resource limits and permissions
    4. Add the missing check to your install steps afterwards

    Tip: List the usual suspects and how you'd check each without full access.

  2. 2Integrations and APIs
    They wrote: “Solve hard integration problems. Take ambiguous, real-world enterprise requirements and reason from first principles to design integrations that work, including the problems for which no playbook exists yet.”

    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.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. 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.

  3. 3LLMs, RAG and agents
    They wrote: “Genuine passion for AI: you already build with cutting-edge tools (LLMs, agentic frameworks, and vibe coding) for fun, not just at work, and you stay on the frontier as it moves.”

    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.

    1. Collect and clean the documents; handle permissions per user
    2. Split them into chunks, embed, and store with source links
    3. Retrieve, then answer with citations; say “I don't know” when retrieval is weak
    4. 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.

  4. 4Coding
    They wrote: “Hands-on proficiency in Python and/or JavaScript / TypeScript (Node.js).”

    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.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  5. 5Ownership and working with customers
    They wrote: “A curious, hands-on builder, you reason about systems from first principles, love getting your hands dirty, and are energised by ambiguity.”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

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.

Similar roles at other companies

Refold AI

Hybrid

Apply