Indu Learning Platform
Course/Unit 7 · Capstone and career
Lesson 7-2

Telling your story

Reframe ten years of migration, MDG and testing work as the foundation of an AI-native technical profile, without inventing anything.

Watch firstTell Me About Yourself - Structure a Strong Answer · Jeff SuOpen on YouTube ↗

Reframe, don't rewrite

You need the vocabulary technical hiring managers scan for, not a new story. Five ECC to S/4HANA migrations, fifteen source systems and a post-replication issue rate below 5% read as delivery on a functional CV, and as engineering when described as pipelines, rules and metrics. Test each bullet: could you discuss it for ten minutes at whiteboard level without exaggerating?

Functional framingSupported data migrationWorked with business on mappingsTested workflowsCoordinated go-liveTechnical framingDesigned extract-transform-load for 5migrationsSpecified mapping and cleansing rulesBuilt and executed FUT/UAT for rule-basedworkflowOwned replication quality metric atgo-livevs
Same work, described by what you designed, built and measured.

From CV bullet to reframed bullet

The verb moves to 'designed' or 'built' only where true, the artifact becomes concrete, and the number stays exactly as it was. Generic phrases like 'worked closely with stakeholders' move into STAR stories.

On your CV todayReframedLed five end-to-end MDG datamigrations ECC→S/4HANASource-to-target mapping andMDG configurationData profiling, cleansing andvalidationCustom LSMW programs; MigrationCockpit, Data ServicesTwo go-lives, 15 sources, issuerate below 5%Designed migration pipelinesfor 5 ECC→S/4HANA programmesSpecified mapping,value-mapping and validationrules for BP/materialBuilt profiling and rule-basedcleansing checks before loadBuilt load programs acrossLSMW, Migration Cockpit and SAPData ServicesOwned replication quality: 15sources, under 5%post-replication issuesscope → designname the rule typeschecks, not chorestools as a stackmetric owner
The facts stay identical; the vocabulary becomes technical.

Try it: what does your older work prove?

Your Cognizant and PGDM years count too, if you name what they show.

Try it · Match

Match each piece of past work to the technical signal it gives.

Pick an item on the left, then its match on the right.

A formula for technical bullets

Verb + artifact + scale + tool + result. Use a verb you can defend, a concrete artifact, a number, the stack, and an outcome.

VerbArtifactScaleToolResultDesignedmigration pipelines5 programmesMigration Cockpit, SAP DataServicestwo go-lives on planSpecifiedWRICEF functional specsBP and materialMDG, BRFplusbuilt by dev teamAutomatedregression scriptscore MM flowsUFTrepeatable releasesBuiltduplicate supplier assistant2,000 synthetic recordsPython, rapidfuzz, LLMdemo + MDG design
The last row is the capstone: add it only once it exists.
Try it · Fill the blanks

Complete the bullet using the formula, choosing only defensible words.

  across , keeping post-replication issues .

Where each skill comes from

Every technical keyword needs a source: real project work or a specific lab. If it maps to nothing, remove it. Be clear about depth: 'configured on client projects' and 'wrote in a personal lab' are both valid, but different.

Skill on the new CVEvidenceMDG data model and CR workflowBAdI validations andderivationsCDS views and BP/CVIPython profiling and matchingLLM prompting, RAG, guardrailsDuplicate supplier assistantClient projects + Unit 1Unit 2 labs (2-2, 2-3)Unit 3 labs (3-1, 3-2)Unit 4 labs (4-1, 4-2)Units 5 and 6Capstone 7-1 on GitHub
Every keyword has a source you can point to.

Your 60-second pitch

It answers 'tell me about yourself'. Practise with a timer until it lands in about a minute.

Step through · 1 of 6
Present roleProof in numbersTechnical layerAI layerDemoWhy this role
One sentence: SAP MDG consultant at a Big Four firm, focused on data migration and governance for large manufacturers and consumer goods companies.
Six beats, about ten seconds each.

Your story assets

Keep the same numbers, capstone and direction everywhere. LinkedIn headline names the role you want (truthfully). CV: three-line summary, then a Projects section with the capstone, then experience. GitHub: pin the capstone, with a README that opens with the problem, one diagram and the demo link.

Your storyCVTechnical bulletsProjects sectionSkills withevidenceLinkedInHeadlineAbout (pitch text)Featured: demovideoGitHubCapstone repoLab reposPinned READMESpoken60-second pitchSTAR storiesWhy technical?
One story, told the same way everywhere.

Try it: the hard questions

Expect 'why technical?', 'what have you built?' and 'why the two-year gap?'. The PGDM years (2020 to 2022) gave you product and business skills, and you returned straight into MDG at Deloitte: a coherent story, not a gap. Keep each answer to about four sentences.

Try it · What would you do?

The interviewer asks: 'Why move from functional to technical?' Which opening is strongest?

Remember

  • Keep every fact and number; change the vocabulary to designed, built, specified, owned.
  • Every technical keyword needs a source: project work, a lab or the capstone.
  • One pitch, one capstone, one direction, repeated on CV, LinkedIn and GitHub.

Check yourself

What is the strongest proof of AI-native skills in an interview?
Which reframed bullet is acceptable?
In the 60-second pitch, what comes right after your present role?
An interviewer asks what you built. Your MDG integration is only designed. What do you say?