Job Description & Details
This is a heavy-duty migration gig where you'll be moving an on-prem Documentum setup over to OpenText. If you enjoy untangling legacy enterprise content management systems and modernizing them without breaking mission-critical workflows, this one's worth a look.
What You'll Should Be Doing
You'll spend your days configuring and validating the new OpenText environment, mapping out how repository structures, workflows, and custom API interactions need to translate over. Expect to spend a lot of time redesigning Java-Documentum integration points and using tools like Kiro to analyze dependencies, surface impacted API calls, and plan out remediation before things break in production.
The Core Tech Stack
You need deep, battle-tested experience with Documentum DFC, REST services, and content server internals because you'll be troubleshooting low-level behaviors daily. Strong Java skills are non-negotiable since you'll be overhauling integrations with WebMethods and CCS Java components, and having prior exposure to OpenText platforms will give you a massive head start.
Interview Expectations
They're going to grill you on your exact migration strategy, likely asking how you handle massive repository data transfers without bringing business operations to a halt. Be prepared to explain a time you troubleshot a complex DFC or REST API bottleneck under pressure; the interviewer wants to see that you can methodically isolate legacy Java integration failures without hand-waving.
Application Advice
Make sure your resume leans hard into specific Documentum migrations you've pulled off, rather than just routine daily administration. Sprinkle in keywords like DFC, REST APIs, OpenText, and Java integration so you easily clear the initial ATS keyword filters before a human engineering lead reviews your background.