How to Apply to OpenText

12 min read Last updated April 20, 2026 7 open positions
Blake Crosley
Blake Crosley Researched using publicly available information, hiring data, and ATS analysis.

Key Takeaways

  • Apply through the official careers portal at careers.opentext.com; the backend is Phenom People, so a single, clean, ATS-friendly PDF resume travels well across every business unit and region.
  • Tailor the resume to the specific business cloud — Content, Business Network, Experience, Cybersecurity, Developer — and name the relevant products (Documentum, eDocs, ApplicationXtender, Magellan, Carbonite, Webroot, Fortify, ArcSight, Voltage, Aviator) plus competitor experience where you have it.
  • Expect a four-to-ten week loop: recruiter screen, hiring manager, structured technical or functional assessment, three-to-five interview panel, and (for senior and director-and-above roles) a final business-unit-leader conversation before offer.
  • Lead every story with the measurable enterprise outcome and the trade-off you made to get there; OpenText scores impact on large regulated customers, not activity or polish.
  • The culture is professional, measured, and durable — bring directness, bring ownership, bring stamina for long delivery cycles, and skip the SaaS-startup theatre; interviewers calibrate against this explicitly.
  • Have a real point of view on Aviator, agentic workflows, and how generative AI reshapes content services, B2B integration, cybersecurity, and ITOM — this is the strategic bet under Barrenechea and panels probe for it across every track.
  • Be honest about the integration context: Documentum (2017), Carbonite and Webroot (2019), and Micro Focus (2023) are real organizational realities, and candidates who can speak credibly about working inside acquired teams or through reorganizations outperform candidates who avoid the topic.
  • Global footprint is a feature, not a bug: comfort operating across Waterloo, Bangalore, Hyderabad, Mexico City, Reading, Munich, and Sydney time zones is a genuine differentiator, especially for senior cross-functional roles.
  • Plan for in-office or hybrid expectations: under Barrenechea, OpenText tightened the return-to-office mandate, and most roles are anchored to a specific office with regular on-site days; fully remote roles exist but are flagged explicitly on the posting.
  • Negotiate professionally — OpenText publishes calibrated bands aligned to public-company norms across base, target bonus, and RSU equity, with sales roles on a base-plus-variable plan; recruiters expect a calibrated conversation, not a one-shot accept.

About OpenText

OpenText Corporation (NASDAQ: OTEX, TSX: OTEX) is a Canadian enterprise information management company headquartered in Waterloo, Ontario, employing roughly 25,000 people across more than 30 countries. Founded in 1991 as a spin-out of a University of Waterloo research project that built the original full-text search engine behind the Oxford English Dictionary, OpenText has spent the last three decades assembling the most comprehensive content services and information management portfolio in the enterprise software market — almost entirely through acquisition. The company has been led since 2012 by Mark J. Barrenechea as CEO and Vice Chair, one of the longest-tenured chief executives in enterprise software, and his deal-making cadence has defined the modern OpenText: Documentum acquired from Dell EMC in 2017 for roughly $1.6 billion, the consumer and SMB cybersecurity assets of Carbonite (and Webroot, which Carbonite had bought a year earlier) acquired in 2019 for $1.42 billion, and most recently the entire Micro Focus International business acquired in August 2023 for approximately $6 billion in the largest deal in OpenText's history. The product portfolio that resulted spans five business clouds: Content Cloud (Documentum, eDocs, ApplicationXtender, OpenText Core Content), Business Network Cloud (B2B integration, supply-chain EDI), Experience Cloud (digital asset management, customer communications), Cybersecurity Cloud (Carbonite backup, Webroot endpoint, Fortify static analysis, ArcSight SIEM, Voltage data protection — the bulk of which arrived through Micro Focus), and the Developer Cloud (ALM/Quality Center, AccuRev, the Magellan analytics platform). Anchoring the entire portfolio is OpenText Aviator, the generative-AI assistant family launched in 2024, which embeds large-language-model retrieval, summarization, and workflow automation across Content, Business Network, Experience, Cybersecurity, and IT Operations — Aviator is the strategic narrative Barrenechea has placed at the center of every product roadmap and every earnings call. OpenText sells primarily to large regulated enterprises and government agencies — banks, insurers, life-sciences companies, defense and intelligence customers, central and local government — where retention schedules, audit trails, sovereignty, and on-premise deployment options still matter as much as feature velocity. Major engineering, support, and shared-services hubs sit in Waterloo and Richmond Hill (Canada), Bangalore and Hyderabad (India), Mexico City and Guadalajara (Mexico), Reading and London (United Kingdom), Munich and Grasbrunn (Germany — inherited from Micro Focus), Sydney and Melbourne (Australia), with smaller centers across the United States, Brazil, Japan, Singapore, and continental Europe. Honest framing matters here: OpenText is a stable, dividend-paying, globally distributed enterprise software company with a near-permanent customer base and a clear long-term acquisition playbook, but it is not a SaaS-native challenger. The integration of Micro Focus has been long and visible, with multiple rounds of redundancies announced through 2023, 2024, and into 2025, particularly across overlapping Micro Focus product lines and back-office functions. Glassdoor and Comparably reviews are mixed and predictable for a company of this profile: high marks for job stability, benefits, manager autonomy in regional offices, and the quality of long-tenured engineers; criticism focused on slow product release cadence relative to cloud-native competitors, leadership turnover at acquired business units, the strictness of the return-to-office mandate that Barrenechea has personally championed, and the cultural friction of layering Documentum, Carbonite, Webroot, and Micro Focus org charts onto the original OpenText spine. Candidates who go in clear-eyed about that trade-off — durable enterprise career, real product depth, large-system scale, in exchange for slower release rhythm and active integration work — are the ones who consistently report a strong experience.

Application Process

  1. 1
    Search and apply through the official OpenText careers portal at careers

    Search and apply through the official OpenText careers portal at careers.opentext.com, which is powered by Phenom People and lists every open requisition globally, filterable by country, city, function, business unit (Content, Cybersecurity, Business Network, Experience, Developer, Corporate), and remote/hybrid arrangement.

  2. 2
    Create a Phenom candidate profile, upload a tailored resume in PDF or Word forma

    Create a Phenom candidate profile, upload a tailored resume in PDF or Word format, and complete the role-specific screening questions covering work authorization, location, notice period, and — for many engineering, security, and government-facing roles — eligibility for security clearance or export-control review.

  3. 3
    Expect a recruiter screen within one to three weeks of applying for an actively

    Expect a recruiter screen within one to three weeks of applying for an actively prioritized requisition; the recruiter validates fit, salary range, geography, integration-context exposure (particularly relevant for roles touching former Micro Focus product lines), and walks you through the loop structure for that specific business unit.

  4. 4
    Move to a hiring-manager conversation focused on your relevant domain experience

    Move to a hiring-manager conversation focused on your relevant domain experience — content services, cybersecurity, B2B integration, analytics, ALM — your motivation for joining OpenText specifically rather than a SaaS-native competitor, and a deeper dive on one or two recent projects that map directly to the role's scope.

  5. 5
    Complete a structured technical or functional assessment calibrated to the role:

    Complete a structured technical or functional assessment calibrated to the role: a coding exercise plus system-design discussion for engineering, a take-home or live case for product management and product marketing, a portfolio walkthrough for design, a written strategy or solution-architecture exercise for pre-sales, and a quota and pipeline conversation for sales.

  6. 6
    Attend a panel of three to five interviews covering craft depth, cross-functiona

    Attend a panel of three to five interviews covering craft depth, cross-functional collaboration, customer or partner orientation, and an explicit values and leadership conversation; senior roles add a director or VP round, and director-and-above roles typically include a final conversation with the relevant business-unit leader.

  7. 7
    Receive a verbal offer from the recruiter followed by a written offer through th

    Receive a verbal offer from the recruiter followed by a written offer through the Phenom workflow; background checks, reference checks, and (where applicable) export-control or security-clearance verification run in parallel, and standard time from first application to written offer is roughly four to ten weeks depending on level, geography, and clearance requirements.

Resume Tips for OpenText

recommended

Lead with measurable enterprise outcomes — license revenue retained, migration p

Lead with measurable enterprise outcomes — license revenue retained, migration projects delivered, audit findings remediated, mean-time-to-detect reduced, customer-renewal rate, ARR influenced — because OpenText evaluates demonstrated impact on large regulated customers, and the Phenom parser surfaces numeric strings cleanly into the recruiter view.

recommended

Mirror the exact language of the job description, especially product names (Docu

Mirror the exact language of the job description, especially product names (Documentum, eDocs, ApplicationXtender, Magellan, Carbonite, Webroot, Fortify, ArcSight, Voltage, AccuRev, Aviator) and category terms (content services, information management, B2B integration, EDI, SIEM, endpoint protection, application security, ALM); Phenom keyword matching weights exact-phrase hits heavily, and product names are the highest-signal keywords on the platform.

recommended

If you have direct experience with comparable competitors — Box, Microsoft Share

If you have direct experience with comparable competitors — Box, Microsoft SharePoint and Purview, IBM FileNet, Hyland OnBase, Veeva Vault, ServiceNow, Splunk, CrowdStrike, SentinelOne, Veritas, Commvault, Cloudera, Tricentis, GitLab, Atlassian — name them explicitly; competitive familiarity is a strong positive signal across product, engineering, and go-to-market roles.

recommended

Use a single-column, ATS-clean PDF with standard section headings (Summary, Expe

Use a single-column, ATS-clean PDF with standard section headings (Summary, Experience, Education, Skills, Certifications) and avoid tables, multi-column layouts, text boxes, headers, footers, and embedded graphics that confuse the Phenom parser and bury your strongest content beneath formatting noise.

recommended

For engineering roles, list the production stack honestly — Java,

For engineering roles, list the production stack honestly — Java, .NET, C/C++, Python, JavaScript, TypeScript, React, Angular, Spring, Kafka, PostgreSQL, Oracle, SQL Server, AWS, Azure, Kubernetes, OpenShift — and call out scale signals such as transaction volume, tenant count, document corpus size, latency SLOs, on-call ownership, and any work crossing on-premise and cloud deployments.

recommended

Highlight any experience operating across Waterloo, Bangalore, Hyderabad, Mexico

Highlight any experience operating across Waterloo, Bangalore, Hyderabad, Mexico City, Reading, Munich, and Sydney time zones explicitly; OpenText runs follow-the-sun engineering, support, and customer-success operations, and proven multi-region collaboration is a real differentiator at every level.

recommended

Show evidence of regulated-enterprise instincts — audit, retention, eDiscovery,

Show evidence of regulated-enterprise instincts — audit, retention, eDiscovery, GDPR, HIPAA, FedRAMP, IRAP, ISO 27001, SOC 2, FIPS, Common Criteria — because OpenText sells into banks, insurers, life-sciences companies, defense, intelligence, and central government, and compliance literacy compounds across the loop.

recommended

List relevant certifications cleanly — AWS, Azure, GCP, CISSP, CISM, CISA, CEH,

List relevant certifications cleanly — AWS, Azure, GCP, CISSP, CISM, CISA, CEH, OSCP, PMP, ITIL, SAFe, Documentum, Carbonite, Webroot, Fortify, ArcSight — because Phenom indexes the certification block separately and recruiters routinely filter on it for security, content services, and pre-sales requisitions.

recommended

Keep the resume to one page for under ten years of experience and two pages maxi

Keep the resume to one page for under ten years of experience and two pages maximum for senior or principal levels; reverse-chronological format is expected, and a tight three-line summary tied to the specific OpenText business cloud you are targeting outperforms a generic objective statement every time.

ATS System: Phenom People

OpenText runs its global hiring on Phenom People, a talent-experience platform widely used by large enterprises for careers sites, candidate matching, and recruiter workflow. The careers site at careers.opentext.com is a Phenom-powered job board, and applications, screening questions, interview scheduling, scorecards, and offer letters all flow through the Phenom platform. Phenom indexes resumes for keyword and skill matching, and surfaces high-fit candidates to recruiters via its internal ranking; clean parsing matters because the parsed view is what the recruiter sees first.

  • Submit a single-column PDF resume with standard section headings (Summary, Experience, Education, Skills, Certifications) so the Phenom parser extracts every line cleanly into the recruiter view without dropping content into formatting noise.
  • Mirror the exact phrasing of skills, products (Documentum, eDocs, ApplicationXtender, Magellan, Carbonite, Webroot, Fortify, ArcSight, Voltage, AccuRev, Aviator), and category terms from the job description; Phenom keyword matching weights exact-phrase hits heavily and the job description is the canonical keyword source.
  • Answer every screening question explicitly and accurately — work authorization, location preference, notice period, salary expectations, security-clearance eligibility — because incomplete or evasive answers route applications down the recruiter queue.
  • Create a complete Phenom candidate profile with LinkedIn linked and the certifications block populated, because recruiters cross-reference the profile when shortlisting and a half-finished profile reads as low intent.
  • Apply directly through careers.opentext.com rather than through aggregators or recruitment agencies; direct applications land cleanly in the Phenom pipeline with full attribution and screening data, while aggregator submissions sometimes lose screening responses in the handoff.

Complete Phenom People Resume Guide →

Interview Culture

OpenText interviews are structured, calibrated across regions and business units, and deliberately designed to surface both deep craft signal and durable cultural fit with a 25,000-person enterprise software company that has spent a decade absorbing other 25,000-person enterprise software companies. The loop runs through Phenom, with each interviewer assigned a specific competency area and a written scorecard, so candidates should expect questions to feel non-overlapping rather than redundant — that is the panel calibrating, not duplicating. Conversations typically run 45 to 60 minutes on Microsoft Teams (the standard internal collaboration tool) for remote rounds, with onsite finals in Waterloo, Richmond Hill, Bangalore, Hyderabad, Mexico City, Reading, Munich, or Sydney where geography permits. The tone is professional, substantive, and noticeably more measured than at SaaS-native challengers; OpenText interviewers are generally long-tenured, deeply familiar with their products, and they probe for whether you can sustain quality work over years rather than whether you can sprint hard for a quarter. Engineering candidates should prepare for a coding round on a collaborative editor (CoderPad, HackerRank, or Microsoft Teams shared screen), a system-design round scaled to level — with a clear bias toward problems that touch durability, multi-tenancy, hybrid on-premise plus cloud deployment, regulated data residency, and integration across acquired product lines — and a values and behavioral round anchored in real OpenText scenarios such as a Documentum-to-Core-Content migration, a Micro Focus product-line consolidation, a Carbonite or Webroot SMB telemetry pipeline, or an Aviator AI feature shipping into a content services workflow. Product, design, marketing, and pre-sales candidates should prepare a portfolio or solution walkthrough, a regulated-customer scenario, and a cross-functional collaboration deep-dive. Sales candidates should expect a structured pipeline, quota-attainment, and territory-strategy conversation, plus a deal-cycle role play. Across every track, the panel probes for three things: clarity of thought under enterprise constraints (compliance, sovereignty, large-customer politics), evidence of having owned outcomes end-to-end through long delivery cycles rather than just shipping demos, and a credible point of view on OpenText Aviator and the broader generative-AI direction of information management. The integration narrative comes up explicitly: candidates who can speak honestly about working through reorganizations, acquired-team dynamics, and parallel product lines outperform candidates who pretend integration is invisible. Decisions are made by the hiring committee within roughly one to two weeks of the final round, and recruiters generally provide directional feedback on close calls, particularly for senior and principal-level roles where the talent pool is small and the company genuinely benefits from candidates reapplying later.

What OpenText Looks For

  • Demonstrated impact on large regulated enterprise customers — banks, insurers, life-sciences, defense, intelligence, central and local government — backed by concrete artifacts rather than vendor-deck language about digital transformation.
  • Domain depth in at least one of OpenText's five business clouds (Content, Business Network, Experience, Cybersecurity, Developer) plus a credible point of view on how Aviator and generative AI reshape that domain over the next three to five years.
  • Comfort working through long delivery cycles, multi-region coordination, and the parallel-product-line reality of a company that has acquired Documentum, Carbonite, Webroot, and Micro Focus inside the last decade.
  • Engineering and architecture craft that respects on-premise, hybrid, and cloud deployment options simultaneously, including durability, data residency, multi-tenancy, observability, and the operational realities of customers who upgrade on a multi-year cadence.
  • Compliance and security literacy — GDPR, HIPAA, FedRAMP, IRAP, ISO 27001, SOC 2, FIPS, Common Criteria — and an instinct for audit, retention, eDiscovery, and the cost of getting any of those wrong in a regulated customer environment.
  • Cross-functional collaboration across Waterloo, Bangalore, Hyderabad, Mexico City, Reading, Munich, and Sydney, including the stamina to operate across time zones and the cultural fluency to bridge legacy-acquired teams with the original OpenText spine.
  • Direct, low-ego communication style — OpenText is not a debate club and not a performance culture; the company hires people who can disagree clearly in the room, commit on the way out, and own the follow-through over the long delivery cycle.
  • Trajectory and slope of growth in the relevant domain over current title; OpenText repeatedly hires people who are about to be senior or principal in their domain rather than people who have been senior somewhere larger and stalled.
  • A clear-eyed read on the company itself: stable dividend-paying enterprise software, durable customer base, deliberate release cadence, ongoing Micro Focus integration, strict in-office expectations under Barrenechea — and genuine comfort with that trade-off rather than a quiet hope it will change.

Frequently Asked Questions

Where is OpenText headquartered and where will I work?
OpenText is headquartered in Waterloo, Ontario, Canada, with a major Canadian campus in Richmond Hill and significant global hubs in Bangalore and Hyderabad (India), Mexico City and Guadalajara (Mexico), Reading and London (United Kingdom), Munich and Grasbrunn (Germany — largely inherited from the 2023 Micro Focus acquisition), Sydney and Melbourne (Australia), with smaller centers across the United States, Brazil, Japan, Singapore, and continental Europe. Most postings list a specific office and a hybrid arrangement; fully remote roles exist but are less common and are flagged explicitly in the location field on the careers site.
What ATS does OpenText use for applications?
OpenText runs its global careers site on Phenom People. The portal at careers.opentext.com is a Phenom-powered job board, and applications, screening questions, interview scheduling, and offer paperwork all flow through the Phenom platform. The system parses PDF and Word resumes well when they are single-column, use standard section headings, and avoid tables, multi-column layouts, headers, footers, and embedded images that fragment the parsed text.
How long does the OpenText interview process take?
End-to-end the loop typically runs four to ten weeks from first application to written offer, depending on level, business unit, and geography. The recruiter screen and hiring-manager conversation generally land in the first one to three weeks, the structured assessment and panel rounds occupy weeks two through six, and the final business-unit-leader round plus offer paperwork close out the remainder. Roles that require security clearance, export-control review, or government-eligibility verification can run longer.
Does OpenText sponsor work visas in Canada, the United States, the United Kingdom, Germany, and other regions?
OpenText sponsors work authorization in markets where it has an established legal entity, including LMIA, Global Talent Stream, and permanent residence pathways in Canada, H-1B and green-card sponsorship in the United States for senior and specialized roles, Skilled Worker visas in the United Kingdom, EU Blue Card and equivalent pathways in Germany, and the regional equivalents in Australia, India, Mexico, and across the EU. Sponsorship is role-dependent and business-case driven, and the Phenom screening questions ask about your current authorization explicitly so the recruiter can route accordingly.
What does compensation look like at OpenText?
As a publicly traded company on both the Nasdaq (OTEX) and the Toronto Stock Exchange (OTEX), OpenText pays competitive market-aligned compensation with three components: base salary calibrated to role, level, and geography; an annual performance bonus (typically 10 to 25 percent of base for individual contributors, higher for sales and leadership); and restricted stock units that vest over multiple years for eligible levels. Sales roles use a base-plus-variable structure with quota-tied commission and accelerators. OpenText also pays a quarterly cash dividend, which is unusual among software companies and reflects the durable cash-flow profile of the customer base.
Is OpenText remote-friendly or in-office?
Under CEO Mark J. Barrenechea, OpenText has tightened its return-to-office expectations, and most roles are anchored to a specific office with regular on-site days — typically three or more days per week where an office exists. A subset of roles are designated remote within a specific country, and those postings call it out explicitly in the location and work-arrangement fields on the careers site. If in-office presence matters to you in either direction, confirm the specific arrangement with the recruiter during the screen rather than inferring from the title.
What is OpenText Aviator and why does it come up in interviews?
OpenText Aviator is the generative-AI assistant family launched by OpenText in 2024 and now embedded across the Content, Business Network, Experience, Cybersecurity, and IT Operations clouds. Aviator handles document summarization, retrieval-augmented generation over enterprise content, supply-chain anomaly detection, security investigation copiloting, and workflow automation, and it is the central strategic narrative under Barrenechea — featured on every earnings call and woven into every product roadmap. Interviewers across engineering, product, design, marketing, sales, and pre-sales tracks probe for a credible point of view on agentic AI in regulated enterprise information management, regardless of which role you are interviewing for.
How should I think about the Micro Focus integration when interviewing?
OpenText acquired Micro Focus in August 2023 for approximately six billion dollars — the largest acquisition in OpenText's history — bringing in Fortify, ArcSight, Voltage, AccuRev, ALM/Quality Center, COBOL, Vertica, and a substantial workforce across Reading, Munich, Bangalore, and elsewhere. Integration has been multi-year and visible, with rounds of redundancies announced through 2023, 2024, and into 2025, particularly across overlapping product lines and back-office functions. Candidates who acknowledge the integration context honestly — the upside of portfolio breadth and the friction of org-chart consolidation — outperform candidates who avoid the topic. If you are interviewing into a former Micro Focus product team, ask the recruiter and hiring manager directly about the team's stability and roadmap.
How should I prepare for the values or behavioral round?
Anchor your stories to OpenText's stated leadership behaviors: customer-first thinking, accountability, collaboration across business units and geographies, and quality at scale. Bring two or three concrete examples of each — a regulated customer you went out of your way for, an outcome you owned end-to-end across a long delivery cycle, a cross-functional initiative that bridged acquired teams, a moment you held the quality bar despite delivery pressure. Avoid abstract platitudes; the panel is calibrated to score artifacts and trade-offs, not adjectives.
Does OpenText give interview feedback to candidates who do not get offers?
OpenText recruiters generally provide directional feedback to candidates who reach the panel stage and are not selected, particularly for senior and principal-level roles where the talent pool is small and the company benefits from candidates reapplying with the gap addressed. Feedback is typically high-level and forward-looking rather than line-by-line, but it is genuinely useful for shaping a future application.
Can I reapply to OpenText after a rejection?
Yes. OpenText does not enforce a formal blackout period and explicitly encourages candidates to reapply when there is a meaningfully different role, a meaningful change in your experience, or roughly twelve months later for the same role. Phenom retains your prior application, so the next recruiter sees the previous loop and the feedback against it. Reapplications that show clear delta — a new certification, a relevant project shipped, a domain shift into one of OpenText's five business clouds, or direct experience with a competitor product the prior loop flagged as missing — convert at meaningfully higher rates than identical resubmissions, so use the intervening time to build the specific signal the prior loop called out.

Open Positions

OpenText currently has 7 open positions.

Check Your Resume Before Applying → View 7 open positions at OpenText

Related Resources

Related Articles

Sources

  1. —
  2. —
  3. —
  4. —
  5. —
  6. —
  7. —