Delivery Manager Intern, Enterprise (India/Remote)

A six-month internship inside a live enterprise implementation, converting to Associate Delivery Manager at month six against six published criteria.

At a glance

Role

Delivery Manager Intern, converting to Associate Delivery Manager

Duration

Six months. One extension to month nine is possible only if your account has not reached UAT by month six

Stipend

₹50,000/month for months 1 to 3. ₹60,000/month from month 4, subject to passing the month-3 review

Conversion

Associate Delivery Manager at [₹16 to 22L CTC], decided at the month-6 review against the six criteria below

Location

India-based, remote

Hours

08:00 to 18:00 IST, with an hour for lunch

Travel

About one week of client-site travel during the internship, on a UAT week

Education

Master's completing in 2026, or completed within the last twelve months

Experience

One to three years of full-time work before the Master's. Mandatory

Start

Immediate through [January 2027], depending on coursework completion

🚀 Who we are

Peakflo is an agentic AI company changing how global finance teams work. We are alumni of Y Combinator (W22) and the Google AI Accelerator, and have been covered by TechCrunch and PYMNTS. Our culture rewards curiosity, ownership and detail.

🎯 Why this role exists

We published a full-time Delivery Manager role to build our enterprise delivery function. That hire designs the operating model. This role exists because a function that works for one person is not a function; it is a person. The second and third enterprise accounts are coming, and we would rather grow the people who will run them inside our operating model than hire them from outside once it exists.

Our implementations involve multi-entity groups running SAP, Oracle or Microsoft Dynamics 365, third-party middleware built by the customer's own IT team, phased UAT across a dozen-plus client stakeholders, and integration surfaces (AI-OCR extraction, PO matching, approval policies, ERP posting) where one configuration change can ripple across a hundred test cases.

Enterprise delivery is not taught in any Master's programme we know of. It is learned by running a UAT tracker on a real account with real accountants on the other end, under someone who has done it before. That is what this internship is.

If you are weighing this against a consulting or systems-integrator offer, the trade is simple. Those environments give you more structured training and a well-mapped career ladder. This one gives you a live enterprise implementation from week one, a founder in the room every week, and a written conversion bar. If you want the structure and the ladder, that is a reasonable choice and this genuinely isn't the role. If you want the account, read on.

💪 What you'll own, months 1 to 6

Ownership ramps over six months. Each stage is the evidence we use to decide the next one, and the month-6 review is the conversion decision.

Months 1 to 2: the single source of truth, under supervision. You are assigned to one live enterprise implementation alongside the Delivery Manager. You attend every client call and every internal standup for that account. Your job is that nothing said on a call fails to become a row: every issue, risk, action, decision, dependency and new requirement lands in the RAID log and test tracker the same day, with a type, a severity, an owner and a date. You issue the minutes after every client session. The Delivery Manager reviews every row you write for the first month and spot-checks after that.

Months 3 to 4: engineering handover and the weekly status. You turn tracked items into engineering tickets the same day, linked from the tracker row, with enough written context that an engineer does not need to attend the call. You keep those tickets moving and flag the stalled ones. You draft the weekly executive status: what moved, what is blocked, what is at risk, what needs the customer. By the end of month four the Delivery Manager is editing your draft rather than writing it, and you are presenting it internally.

Months 5 to 6: a UAT workstream of your own. You write the test scripts for one workstream from the signed-off design document, assign cases to named client testers, chase them, and record every verdict with tester, date and document reference at the moment of testing. You run the regression set when an extraction, matching or posting rule changes, and you evidence the run. This is when you sit next to the client's testers for a week: UAT is when you travel.

Throughout, you learn the domain the only way it sticks: what a three-way match, a GRN, a company code and a credit note mean in production, because a client tester is asking you about one.

✅ How you convert

This is the part most internship postings leave vague. We will not.

Formal reviews at month 3 and month 6. The month-6 review is the conversion decision. Each is against the criteria below, in writing, with the Delivery Manager and a founder, and you see the write-up. Passing the month-3 review moves your stipend to ₹60,000 from the month-4 payroll.

Conversion is decided on the six criteria below, evidenced from the trackers and call records rather than from anyone's opinion of you. We publish them so you know from day one what evidence the decision will use.

60 consecutive working days with zero same-day logging misses on your account. A miss is any issue, risk, action, decision, dependency or requirement raised on a call, in chat or by email that is not in the tracker with a type, severity, owner and date by the time you sign off that day. An exception counts only if you documented it at the time and the Delivery Manager agreed it. Audited by reconciling the tracker against call recordings and chat history.
One full UAT workstream run end to end: scripts you wrote from the signed-off design, cases assigned to named testers, every verdict evidenced at source, exit criteria defended.
One milestone slip you called ahead of the date, with the leading indicator named and a recovery option proposed, before the customer or the Delivery Manager raised it.
Four consecutive weekly executive statuses sent under your name that the customer's sponsor could act on without asking for clarification of the status, the risks, the decisions or the asks.
One documented customer conversation in which you communicated a material problem or delay, explained the impact, proposed a recovery plan, and left with an agreed next step. Once is enough.
A Delivery Manager who says, in writing, that they would hand you an account.

Meet all six at month six and you convert. Miss them and we tell you plainly, with the evidence, and help you land somewhere the fit is better. One exception, and only one: criterion 2 depends on the account reaching UAT, which is the account's calendar rather than yours. If at month six you have met the other five and UAT has not started on your account, we extend once, to month nine at the latest, with the UAT start date written into the month-6 review. Nothing else extends the internship.

On conversion: Associate Delivery Manager, Enterprise, at [₹16 to 22L CTC]. Your first quarter as an Associate is the account with your name on it: one enterprise account carried through a phase end to end, with the Delivery Manager as escalation rather than supervisor, and you as the person the customer's finance controller messages first. The step from Associate to Delivery Manager comes at 18 to 24 months on its own published criteria: two accounts through UAT and go-live without Delivery Manager intervention, one account from discovery to hypercare, one change request refused to a customer and held, and a written playbook another Associate could run from.

🧰 Who you'll work with and what you'll have

Founders, weekly, on live accounts, from week one. One of them is a former McKinsey engagement lead who went on to found and scale this company. By month four you present your account's delivery status to the company yourself.
A Delivery Manager who owns your development. Not a buddy, not an HR check-in. Someone whose own success is measured partly by whether you convert.
A delivery pod: engineers, QA, ML engineers and forward-deployed engineers on the account, with a direct line to product and engineering leadership.
Founder air cover. When a customer pushes back on a date you have called, a founder backs you.
The operating model, written down. Tracker schema, severity definitions, regression policy, UAT script standards, escalation matrix, status template. You learn to run them, then tell us where they are wrong.

The corollary is real accountability from week one. An issue raised on a call that never becomes a tracked row is your miss, and we will say so.

📏 The operating standards you'll be held to

These are the same standards we hold the full-time Delivery Manager to. There is no intern version.

Same-day logging. Anything raised on a client call is in the tracker before you sign off. "Discussed, no action agreed" is a logged outcome with a reason.
Evidence over assertion. Any claim that something is tracked, tested, fixed or delivered can be answered immediately with a row number, ticket ID, test case or link.
Same-day engineering handover. Items needing engineering become tickets the same day, linked from the tracker row.
Test evidence at source. Every verdict carries tester, date and document reference, recorded when the test runs, never reconstructed later from chat.
Regression discipline. Any change to an extraction, matching or posting rule triggers the agreed regression set, and the run is evidenced.
Dependencies are first-class. Client-side and third-party items carry a named owner on their side, a date and a chase cadence. "Waiting on the customer" is a tracked state, not an excuse.
Slippage is forecast, not reported. Risk to a milestone is raised when the leading indicators move, not when the date arrives.
Dates are communicated before they slip. If a commitment is going to move, the customer hears it from you before the deadline, with a revised date.
Coverage is arranged, not assumed. Planned absence comes with a written handover and a named cover.

🕵️ Who we're looking for

This role suits someone with one to three years in consulting, systems integration, SaaS implementation, QA, enterprise technology or finance operations, who then did a Master's and now wants to move into customer-facing enterprise delivery.

Eligibility. We screen on these before anyone meets the hiring manager:

A Master's completing in 2026 (MBA, MiM, MS in Information Systems, M.Tech, MSc Finance or similar), or completed within the last twelve months.
One to three years of full-time work before the Master's. Full-time salaried or full-time contract roles count. Summer internships, live projects, part-time work, apprenticeships and teaching assistantships do not. Candidates who went into a Master's directly from a Bachelor's without this are not eligible, however strong the programme.
Exceptional written English. Short, precise, unambiguous. You can turn a rambling forty-minute conversation into eight lines that someone who was not there can act on. We test this in the working session. It is the single most predictive skill for this job.
India-based, and able to work 08:00 to 18:00 IST as your normal day, with one week of client-site travel during the internship.

What we are actually looking for beyond that, because none of it shows on a transcript:

You have run something with a date on it that other people depended on. A workstream in your pre-Master's job, a client deliverable, a system change with a go-live. It was yours, it had a deadline, other people sat on the critical path, and you can say honestly what slipped and what you should have seen earlier.
You are already detail-obsessive, and can prove it. Bring the tracker you kept for something nobody asked you to track.
You are comfortable with technical material without being an engineer. You can read a JSON payload and say what it contains, and look at a field mapping and spot where it is wrong. You do not need to code.
You have told someone a hard truth about a deadline and kept the relationship. A manager, a client, a teammate. We will ask.

Where the pre-Master's years were spent matters, in this order:

A systems integrator or Big 4 (TCS, Infosys, Wipro, HCL, Accenture, Deloitte, EY, KPMG, PwC, Capgemini, LTIMindtree, Cognizant or similar), even in a technical, testing or support stream. Time inside an SAP, Oracle or Dynamics environment for any reason is the strongest single signal on a CV for this role.
A B2B SaaS company in implementation, onboarding, QA or customer-facing delivery.
A finance, accounting or procurement function where you touched AP, AR or a three-way match.

Working pattern: India-based, remote. 08:00 to 18:00 IST with an hour for lunch, which keeps you live through the close of the Singapore working day, when our enterprise customers need us. Enterprise implementations run on the customer's clock, not ours.

🚫 What this role is not

Not a research or analyst internship. No market sizing, no competitor decks, no slides for someone else's meeting.
Not a shadowing programme. You own things from week one. Small at first, real always.
Not a product management internship. You feed hard delivery evidence into the roadmap. You do not own it.
Not a guaranteed conversion, and not a fast track to the full Delivery Manager band. Conversion is to Associate Delivery Manager, on the six criteria above. The Delivery Manager step comes after, on its own criteria.
Not a role where escalating a problem counts as solving it. That applies at intern level too.

🙂 Compensation & benefits

Stipend: ₹50,000 per month for months 1 to 3. ₹60,000 per month from the month-4 payroll, subject to passing the month-3 review. We publish the numbers so nobody spends three rounds guessing.
Conversion: Associate Delivery Manager at [₹16 to 22L total CTC]. No equity is attached to the internship or to conversion.
Founder access weekly, and a Delivery Manager whose job includes getting you converted.
Comprehensive health insurance from day one.
Remote work within the client-coverage commitment above.

Interview Process

🧭 How we'll interview

A short screening call, then three conversations, under two and a half hours in total, no unpaid homework.

Screening call (20 min): the practical terms above, your pre-Master's work experience, and the one thing you ran with a date on it.
Working session (60 min, live): a realistic but entirely fictional implementation in trouble: a meeting summary, a messy tracker and a milestone plan with a date at risk. You talk us through what you'd log, what you'd chase and what you'd tell the customer. We are watching how you read, how you write, and whether you notice what does not add up. Nothing to prepare.
Founder conversation (30 min): why delivery, why now, and whether you actually want the conversion bar above.

We also speak to one reference from your pre-Master's employer, and we ask them about follow-through rather than for a character reference.

Remote Senior Fullstack Software Engineer Remote Jobs

Find Your Next Role

467 Open Positions

Remote Senior Fullstack Software Engineer Remote Salary Ranges

Companies Hiring for Remote Senior Fullstack Software Engineer Remote Roles

Common Remote Senior Fullstack Software Engineer Remote Job Titles

Remote Senior Fullstack Software Engineer Remote Salary Ranges1901

Companies Hiring for Remote Senior Fullstack Software Engineer Remote Roles8

Common Remote Senior Fullstack Software Engineer Remote Job Titles8