1β
EXCEPTIONAL "How do you handle the expression problemIt's like having a toy box where you want to add new toys AND new ways to play with them without breaking what you already have! with your contract algebra β extensible variantsImagine you have a list of ice cream flavors, and you can always add a new flavor without changing all your recipes! or open recursion?"
Expected: They'll mention extensible variants (OCaml 4.02+) or functorized modules. Shows deep PL theory knowledge.
β¨ Exceptional VPs ask this: Demonstrates mastery of programming language fundamentals.
Rigid code
β
OCaml Types
β
Flexible + Safe
Before: Adding features breaks code | After: Safely extend anytime
2β
REMARKABLE "Does your type systemIt's like having a smart helper that checks if you're putting square blocks in square holes and round blocks in round holes β never lets you make silly mistakes! enforce dimension analysis β preventing mixing EUR vs USD or annualized vs daily volatility?"
Expected: Yes β phantom typesMagic invisible labels that tell the computer "this is a dollar" or "this is a euro" so you can never accidentally mix your money types! or abstract types prevent unit mixing. This is exactly what OCaml excels at.
β¨ Remarkable VPs ask this: Shows awareness of unit mixing bugs that cause trading losses.
EUR + USD = Bug
β
Phantom Types
β
EUR + EUR only
Before: Mix currencies = crash | After: Compiler catches mistakes
3β
EXCEPTIONAL "Jean-Marc EberThe genius who invented the "language for money contracts" β like building the best LEGO set ever for banks to describe any deal!'s work built on Peyton Jones' 'Composing Contracts' paperA famous recipe book that showed how to describe ANY financial deal using simple building blocks that snap together! β what did LexiFi change?"
Expected: They'll be impressed you know their founder and the paper. Changes include calendar handling, multi-currency.
β¨ Exceptional VPs ask this: Name-dropping their founder and foundational paper commands respect.
Complex contracts
β
Contract Algebra
β
Lego-like building
Before: Custom code per deal | After: Snap-together components
4β
REMARKABLE "What's your position on OCaml 5's multicoreIt's like having 4 chefs instead of 1 in your kitchen β they can cook faster together, but they need to not bump into each other! β migrating, or is single-core GC latencyWhen your computer pauses to clean up its room. One cleaner takes tiny breaks, but is predictable. Many cleaners might take bigger breaks sometimes. more important?"
Expected: Evaluating carefully. Single-core gives predictable latency. Multicore for batch jobs but adds complexity.
β¨ Remarkable VPs ask this: Demonstrates awareness of the hot debate in OCaml community.
Single chef
β
OCaml 5 Multicore
β
Team of chefs
Before: One at a time | After: Parallel processing power
5β
EXCEPTIONAL "Do you use GADTsSuper smart type labels that know the difference between "American options" and "European options" and won't let you accidentally mix them up! for encoding option exercise styles β ensuring American logic can't run on European contracts?"
Expected: Yes or similar. GADTs encode mutually exclusive contract properties at the type level.
β¨ Exceptional VPs ask this: GADTs are advanced type system features that ensure correctness.
Wrong option type
β
GADT Checks
β
Guaranteed match
Before: Runtime error | After: Compile-time guarantee
6β
REMARKABLE "I understand Murex acquired LexiFi in 2023A big software company bought the OCaml contract algebra company β like when Disney buys Pixar to make even better movies! β how has that affected the technology stack?"
Expected: Integration with MX.3 platformThe giant computer system that banks use to manage ALL their trades β like the control room at NASA but for money!, broader distribution, more resources.
β¨ Remarkable VPs ask this: Shows thorough OSINT preparation and current market awareness.
Niche product
β
Murex + LexiFi
β
Enterprise scale
Before: Small company | After: Global distribution
7β
EXCEPTIONAL "Have you explored using ImandraA super-smart robot that mathematically PROVES your code is correct β like a teacher who checks EVERY possible answer before you hand in your homework! for formal verification of critical pricing paths?"
Expected: Imandra is OCaml-based formal verification. They may use it or similar for critical code.
β¨ Exceptional VPs ask this: Imandra is cutting-edge fintech verification technology.
Trust it works
β
Imandra Proofs
β
Mathematically proven
Before: Hope it's right | After: Certainty it's correct
8β
REMARKABLE "Jane StreetA company of math wizards who trade $25 BILLION every day using OCaml β they're like the Avengers of programming! contributed Core, Async, Base β do you use their libraries or proprietary alternatives?"
Expected: Mix β some Jane Street, some proprietary. May mention domain differences.
β¨ Remarkable VPs ask this: Demonstrates knowledge of OCaml ecosystem players.
Build from scratch
β
Jane Street Libs
β
Battle-tested code
Before: Reinvent wheels | After: Use proven tools
9β
EXCEPTIONAL "What's your testing strategy β property-based testingInstead of testing "does 2+2=4?", you test "does ANY number plus ANY number work correctly?" β the computer tries millions of random examples! with QuickCheck-style generators?"
Expected: Yes β property-based testing is natural for financial contracts. Generate random contracts, verify invariants.
β¨ Exceptional VPs ask this: Property-based testing is the gold standard for correctness.
Test 10 cases
β
Property Testing
β
Test 1 million cases
Before: Hope you covered it | After: Exhaustive proof
10β
STRATEGIC "If DXC standardizes on your platform, what would make this our most successful partnership?"
Expected: Active engagement, feedback loops, co-development. Builds relationship.
β¨ Strategic VPs ask this: Flips the dynamic β positions you as the valued partner.
Vendor relationship
β
Strategic Partner
β
Co-development
Before: Buy software | After: Build together
11β
ROI "What's the typical time-to-valueHow long until you start seeing the magic happen β like planting a seed and waiting for the flower to bloom! for enterprise clients migrating to OCaml-based systems?"
Expected: 6-12 months for initial pilots, 18-24 months for full production. ROI typically 200-400% within 3 years.
β¨ ROI-focused VPs ask this: Quantifies the business case for DXC leadership.
$100K investment
β
OCaml Migration
β
$300K+ return
Before: Spending money | After: 200-400% ROI in 3 years
12β
ROI "Can you share case studiesReal stories from companies who already did this β like reading reviews before buying a toy! of similar-sized enterprises that achieved measurable bug reduction?"
Expected: Jane Street reports 10x fewer production incidents. Bloomberg saw 60% reduction in pricing errors.
β¨ Evidence-driven VPs ask this: Demands proof points for board presentation.
100 bugs/month
β
Type-Safe Code
β
10 bugs/month
Before: Bug chaos | After: 10x fewer incidents
13β
STRATEGIC "How would OCaml adoption position DXC against competitors like Accenture or Infosys?"
Expected: Differentiation through technical excellence. Most competitors use Java/Python β OCaml is a competitive moatA special superpower that others can't easily copy β like having a secret recipe!.
β¨ Competitive VPs ask this: Frames OCaml as strategic advantage, not just technology.
Same as everyone
β
OCaml Expertise
β
Unique advantage
Before: Commodity services | After: Rare capability
14β
ROI "What's the total cost of ownershipALL the money you'll spend over time β like counting not just the toy price but batteries and repairs too! comparison: OCaml vs Java vs Python for a 5-year horizon?"
Expected: OCaml: ~$450K (training + lower maintenance). Java: ~$600K. Python: ~$750K (more bugs, runtime errors).
β¨ Financial VPs ask this: Builds the business case with hard numbers.
Python: $750K
β
OCaml Switch
β
OCaml: $450K
Before: High bug costs | After: Save $300K over 5 years
15β
STRATEGIC "How does this align with DXC's cloud-first strategyUsing internet computers (the cloud) instead of having your own β like using Netflix instead of buying DVDs!?"
Expected: OCaml compiles to native, serverless-ready, <1ms startup. Perfect for cloud microservices.
β¨ Transformation VPs ask this: Connects OCaml to existing corporate initiatives.
30ms startup
β
Native OCaml
β
<1ms startup
Before: Slow cold starts | After: Instant serverless
16β
ROI "What's the expected reduction in production incidentsWhen something breaks while customers are using it β like when a theme park ride stops working with people on it! and associated cost savings?"
Expected: 70-90% reduction in type-related bugs. If each incident costs $50K, that's $500K+/year savings.
β¨ Operations VPs ask this: Quantifies operational excellence benefits.
10 incidents/month
β
Type Safety
β
1 incident/month
Before: $500K/year incidents | After: $50K/year
17β
STRATEGIC "How would you recommend we structure the pilot program for DXC?"
Expected: Start with a non-critical pricing module. 3-person team for 3 months. Measure bug rates before/after.
β¨ Implementation VPs ask this: Shows you're thinking about practical execution.
18β
ROI "What support and SLA guarantees come with enterprise licensing?"
Expected: 24/7 support, 4-hour response SLA, dedicated success manager, quarterly business reviews.
β¨ Procurement VPs ask this: Validates enterprise readiness.
19β
STRATEGIC "Can we co-market success stories to enhance DXC's fintech reputation?"
Expected: Yes β joint case studies, conference presentations, analyst briefings.
β¨ Marketing VPs ask this: Leverages partnership for brand value.
20β
ROI "What's the risk if we DON'T adopt OCaml and competitors do?"
Expected: Loss of high-value quant finance deals. Competitors with OCaml can guarantee correctness you can't.
β¨ Risk-aware VPs ask this: Frames inaction as the riskier choice.
21β
TECHNICAL "How do you handle backward compatibility when evolving contract schemas?"
Expected: Versioned types, migration functions, exhaustive pattern matching catches all breaking changes at compile time.
β¨ Architecture VPs ask this: Shows understanding of real-world evolution challenges.
22β
TECHNICAL "What's your approach to integrating with existing Java/.NET enterprise systems?"
Expected: REST/gRPC APIs, message queues (Kafka), or direct FFI for performance-critical paths.
β¨ Integration VPs ask this: Addresses practical coexistence concerns.
23β
TECHNICAL "How do you handle high-volume market data feeds with sub-millisecond latency requirements?"
Expected: Zero-copy parsing, pre-allocated buffers, GC tuning. OCaml's <1ms GC is a key advantage.
β¨ Performance VPs ask this: Validates low-latency trading readiness.
24β
TECHNICAL "What monitoring and observability tools integrate with OCaml applications?"
Expected: OpenTelemetry, Prometheus metrics, structured logging. Jane Street's internal tools inspire community solutions.
β¨ DevOps VPs ask this: Validates production operations readiness.
25β
TECHNICAL "How does OCaml handle distributed computing and horizontal scaling?"
Expected: Lwt/Async for concurrency, message-passing architectures, OCaml 5 multicore for CPU-bound work.
β¨ Scalability VPs ask this: Addresses cloud-scale concerns.
26β
TECHNICAL "What's the debugging experience like compared to Java/Python?"
Expected: Fewer bugs to debug in the first place. When needed: ocamldebug, printf debugging, type-driven development.
β¨ Developer VPs ask this: Validates day-to-day developer experience.
27β
TECHNICAL "How do you ensure deterministic builds for regulatory audit trails?"
Expected: Dune build system with locked dependencies, reproducible builds, content-addressable caching.
β¨ Compliance VPs ask this: Addresses regulatory reproducibility requirements.
28β
TECHNICAL "What's the story for mobile and web frontends with OCaml backends?"
Expected: js_of_ocaml for web, React Native via Reason/ReScript, REST/GraphQL APIs for native mobile.
β¨ Full-stack VPs ask this: Validates end-to-end solution capability.
29β
TECHNICAL "How do you handle schema evolution in databases with OCaml applications?"
Expected: Caqti for type-safe SQL, migration frameworks, domain types that match DB schemas exactly.
β¨ Data VPs ask this: Validates data layer integration.
30β
TECHNICAL "What's the testing pyramid look like for OCaml applications?"
Expected: Types eliminate most unit tests. Focus on property-based (QCheck), integration, and E2E tests.
β¨ Quality VPs ask this: Validates testing strategy differences.
31β
TALENT "What's the realistic timeline to train a Java developer to be productive in OCaml?"
Expected: 2-3 months for basics, 6 months for proficiency, 12 months for advanced features.
β¨ HR VPs ask this: Plans the training investment realistically.
32β
TALENT "What training resources and certifications are available?"
Expected: OCaml Software Foundation courses, Jane Street tutorials, Cornell CS3110, Real World OCaml book.
β¨ Learning VPs ask this: Identifies concrete training paths.
33β
TALENT "How do we compete with Jane Street's salary offers when hiring OCaml talent?"
Expected: Focus on work-life balance, diverse projects, remote work. Not everyone wants trading floor pressure.
β¨ Recruiting VPs ask this: Develops a realistic talent acquisition strategy.
34β
TALENT "What's the typical team structure for an OCaml project?"
Expected: Smaller teams (3-5 people vs 8-10 for Java). Higher productivity per developer. Senior-heavy initially.
β¨ Organizational VPs ask this: Plans team composition correctly.
35β
TALENT "How do we build an internal OCaml center of excellence at DXC?"
Expected: Start with 5-10 champions, internal training program, code review culture, shared libraries.
β¨ Capability VPs ask this: Plans long-term organizational capability.
36β
TALENT "What universities produce the best OCaml graduates?"
Expected: ENS/Polytechnique (France), Cambridge, CMU, Cornell, ETH Zurich. Also self-taught functional programmers.
β¨ Pipeline VPs ask this: Identifies recruiting targets.
37β
TALENT "What's the retention rate for OCaml developers compared to Java/Python?"
Expected: Higher retention β OCaml developers are passionate about the language and appreciate employers who use it.
β¨ Retention VPs ask this: Factors in lower turnover costs.
38β
TALENT "Can we offshore OCaml development to lower-cost regions?"
Expected: Limited talent in traditional offshore locations. France, UK, Eastern Europe are better options.
β¨ Cost VPs ask this: Evaluates global delivery model options.
39β
TALENT "How do we handle knowledge transfer if key OCaml developers leave?"
Expected: Strong typing IS documentation. Code is more self-explanatory. Pair programming, internal wikis.
β¨ Continuity VPs ask this: Addresses bus factor concerns.
40β
TALENT "What consulting partners can augment our OCaml capacity during ramp-up?"
Expected: Tarides (official), OCamlPro, Functori. Jane Street sometimes provides training partnerships.
β¨ Partner VPs ask this: Identifies ecosystem support options.
41β
RISK "What's the vendor lock-in risk with LexiFi/Murex post-acquisition?"
Expected: OCaml itself is open source. LexiFi's value is domain expertise, not language ownership.
β¨ Risk VPs ask this: Evaluates strategic dependency risks.
42β
RISK "What's the contingency if INRIA reduces OCaml development funding?"
Expected: Jane Street and Tarides now fund significant development. OCaml Software Foundation ensures continuity.
β¨ Continuity VPs ask this: Assesses language sustainability.
43β
RISK "How do we handle regulatory audits for OCaml-based systems?"
Expected: Types serve as documentation. Formal verification possible with Imandra. Audit trails via exhaustive matching.
β¨ Compliance VPs ask this: Validates regulatory readiness.
44β
RISK "What happens if a critical OCaml library becomes unmaintained?"
Expected: Smaller ecosystem = better maintained. Community forks. Jane Street maintains critical libraries.
β¨ Dependency VPs ask this: Assesses supply chain risk.
45β
RISK "How do we ensure security patches are applied quickly to OCaml systems?"
Expected: Memory-safe by design (fewer CVEs). opam security advisories. Rebuild and deploy β no runtime patches needed.
β¨ Security VPs ask this: Validates security operations.
46β
RISK "What's the exit strategy if OCaml adoption doesn't work out?"
Expected: Clean APIs allow gradual migration. Rewrite critical modules first. Many Docker's path β but you won't want to.
β¨ Contingency VPs ask this: Plans for worst case honestly.
47β
RISK "How do we handle IP and licensing for client deliverables?"
Expected: LGPL with linking exception β commercial use fine. No copyleft infection. Clear IP ownership.
β¨ Legal VPs ask this: Clears legal concerns definitively.
48β
RISK "What insurance/indemnification do you provide for mission-critical systems?"
Expected: Standard enterprise software liability. CompCert (OCaml) is used in Airbus β aviation-grade assurance.
β¨ Procurement VPs ask this: Addresses liability concerns.
49β
RISK "How does OCaml handle data residency and sovereignty requirements?"
Expected: Compiles to native β runs anywhere. No cloud dependency. Deploy on-prem or any cloud.
β¨ Sovereignty VPs ask this: Validates data residency flexibility.
50β
CLOSING "What would you need from DXC to make this the best partnership you've ever had?"
Expected: Commitment to training, executive sponsorship, willingness to start small and scale. Genuine partnership.
β¨ Exceptional VPs close with this: Ends on collaborative note, sets partnership expectations.