Gregor Bailar
American technology executive
Gregor Bailar (born May 3, 1963) is a US technology executive, professional director, and philanthropist who held executive roles at Citibank, NASDAQ and Capital One. He managed technology and operations for the NASDAQ Stock Market during the dot-com boom and 9/11 terrorist attacks. He led rescue operations during Katrina and the Beltway Sniper for Capital One. He has been cited as one of the most influential CIOs of the internet age and was inducted into the CIO Hall of Fame in 2007.
Early life
Bailar grew up in Miami, Florida, and was an honor student at South Miami High School, president of the Dade County Association of Student Government Presidents and active in debate, drama and the math club. Bailar is a graduate of Dartmouth College with a BA in Electrical Engineering and Computer Science.
Business and technology roles
Bailar worked at HP, NeXT Computer, Perot Systems, Citicorp, NASDAQ and Capital One. At NeXT, Bailar held several roles, including assisting Steve Jobs as his technical systems engineer during the previews and launch of the NeXT Cube. Bailar assisted at the October 12, 1988 launch and conducted launch-related Q&A and demonstrations as seen in the KPIX coverage of the event. He later became technical director of NeXT Europe and Country Head for NeXT UK. He has served on a variety of for-profit and non-profit boards including Digitas, Inc., Endurance Specialty Holdings and The Corporate Executive Board (now a part of Gartner Group), where he was Chairman of the Audit Committee.
Begin with the source’s own compact description: “Gregor Bailar” is american technology executive. The dossier treats that line as a proposition to test through Gregor, Bailar and American, not as a finished interpretation.
Why this record matters
The phrase “american technology executive” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Datasets, specimens, observations and peer-reviewed methods provide the appropriate test for the technical claims summarized here. The source revision retrieved here is dated May 27, 2026. The linked authority identifier is Q43177786. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1963, 2007 and 1988.
A general summary may omit uncertainty, sample limits or methodological disagreement that is explicit in the technical record. 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
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Gregor Bailar”, its source revision and the description used here.
- Expand the search: follow Gregor Bailar primary sources, Gregor Bailar archive and Gregor 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 “Gregor Bailar”?
- Is the terminology current, historical or disputed?
- Which observation, specimen, dataset or publication supports the account?
Search terms from this dossier
This entry incorporates text from “Gregor Bailar” 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.