HTC Global Services
American company

HTC Global Services Inc., established in 1990 and headquartered in Troy, Michigan, United States, is a provider of information technology and business process services.
History
HTC Global Services Inc. was founded in 1990 by Indian entrepreneur Madhava Reddy, as a Michigan-based, privately owned information technology and business process outsourcing services company. Reddy is the president and CEO of the company. Currently the company has 11,000 employees globally including from Ciber and CareTech, which it has acquired in 2017 and 2014 respectively.
In 2018, the company invested ₹100 crore in a 4,500-seat development center located in Vandalur, to the south of Chennai, which will support the company's IT operations and business process outsourcing growth. In India it has centers in Chennai, Hyderabad, and Bengaluru in India, with other places of operations in Michigan (US), Singapore, Australia, the Middle East and Malaysia.
Acquisitions
In 2014, the company acquired CareTech Solutions, a US-based healthcare IT services provider. CareTech now operates as a wholly owned subsidiary of HTC and provides IT services primarily to the healthcare providers in the US.
In May 2017, HTC Global Services acquired Ciber, a global information technology consulting, services and outsourcing company for $93 million US, headquartered in Greenwood Village, Colorado.
In 2021, HTC Global Services unified its subsidiaries CareTech and Ciber under one company name, HTC Global Services.
The public source identifies “HTC Global Services” as american company. This brief keeps that definition visible, then builds a research path around Global, Services and American.
Why this record matters
A short description can identify a subject without explaining its stakes. For “HTC Global Services”, the useful work is to connect “american company” to the records capable of establishing context and consequence.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated May 28, 2026. The linked authority identifier is Q28406768. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1990, 2017, 2014 and 2018.
Official terminology may obscure informal participation, dissent or communities documented only indirectly. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “HTC Global Services”, its source revision and the description used here.
- Expand the search: follow HTC Global Services primary sources, HTC Global Services archive and Global research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “HTC Global Services”?
- Who created the surviving record, and for what administrative purpose?
- What chronology connects this entry to wider political or social change?
Search terms from this dossier
This entry incorporates text from “HTC Global Services” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.