Assess Secure Cross-Bank Fraud Computation for a Four-Bank Consortium
Overview
What this challenge is about.
Assess Secure Cross-Bank Fraud Computation for a Four-Bank Consortium. Expert-level challenge in code. Writing production code that solves real engineering p...
The Brief
What you'll do, and what you'll demonstrate.
Decide whether secure multi-party computation can compute joint cross-bank fraud signals correctly and fast enough to be production-viable at one million records per bank, and justify the verdict with a working demo and measured evidence.
This is not a coding exercise. It is the work a software engineer does between a Jira ticket and a merged PR. That distinction matters to every hiring manager who has seen candidates solve LeetCode problems and none who have shipped production code under real constraints.
When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."
Earning criteria — what you'll demonstrate
- Implement private set intersection and a private joint aggregate as multi-party protocols where no party reveals its own inputs.
- Verify cryptographic protocol output against a trusted plaintext baseline to prove correctness rather than assume it.
- Measure and interpret how secure-computation cost (time and bandwidth) scales with input size and identify the dominant bottleneck.
- Translate threat-model choices (honest-but-curious versus malicious) and operational risks into a clear adoption recommendation for non-technical risk committees.
- Package a distributed multi-party system for one-command, reproducible bring-up.
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Secure Computation
Apply secure computation to solve real industry problems and demonstrate production-level capability.
- Mpc
Apply mpc to solve real industry problems and demonstrate production-level capability.
- Cryptography
Apply cryptography to solve real industry problems and demonstrate production-level capability.
- Python Programming
Apply python programming to solve real industry problems and demonstrate production-level capability.
- Benchmarking
Apply benchmarking to solve real industry problems and demonstrate production-level capability.
- Privacy Engineering
Apply privacy engineering to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Privacy Engineer
Building a working private-computation demo and judging its real-world cost is exactly what privacy engineers do when evaluating data-sharing technologies; you practice turning a privacy requirement into a measured, defensible engineering recommendation.
This challenge sharpens
- privacy-engineering
- secure-computation
- benchmarking
Applied Cryptography Engineer
Implementing and verifying multi-party protocols against a plaintext oracle, then reasoning about honest-but-curious versus malicious threat models, mirrors the daily work of shipping cryptography that must be both correct and fast enough to deploy.
This challenge sharpens
- cryptography
- mpc
- secure-computation
Security Engineer, Financial Services
Banks increasingly need engineers who can prototype privacy-preserving systems and communicate their limits to risk committees; this challenge bridges hands-on protocol coding with the regulatory and operational judgment that financial security roles demand.
This challenge sharpens
- mpc
- python-programming
- privacy-engineering