
1
1
Germany
1 year of experience
M.Sc. candidate in Electrical Engineering and Information Technology at Otto-von-Guericke University Magdeburg, Germany, specializing in heterogeneous computing, digital communication systems, and power electronics. Holds a B.Sc. in Aeronautical Engineering (Avionics) with Honors (94.05/100) from the National Aviation Academy, Baku. Technically grounded in embedded systems, PCB design (KiCad), FPGA-GPU communication, and high-performance computing. Currently conducting active research on RDMA technologies — covering InfiniBand, RoCEv2, and GPUDirect RDMA — with a focus on latency, bandwidth, and CPU-offload trade-offs across GPU-to-GPU and FPGA-GPU interconnects, drawing from analysis of 33 academic papers. Beyond hardware, builds AI-driven software systems — including a live prediction markets trading bot using Binance-leads-Chainlink oracle edge detection, achieving 83%+ win rates in paper trading. Experienced with MATLAB, Simulink, avionics test equipment, and GPU-accelerated computing pipelines. Certified by TU München, University of Colorado, and MathWorks. Interests: AI-assisted development tooling, autonomous systems, HPC, and real-world deployment of ML-driven solutions.

Legacy modernization is one of the most expensive problems in enterprise software. Banks run dual systems for years during migration — old COBOL-style services alongside modern microservices — but no tool tells them precisely WHEN it's safe to flip the switch at code-function granularity. Bob the Judge solves this. It's a Bob-native, real-time cutover decision advisor that: - Compares legacy and modern banking services function-by-function - Scores parity across transaction types: domestic, international, instant, scheduled - Identifies where systems have diverged and exactly why - Recommends which functions are safe to cut over today vs. which need more validation - Generates a regulator-grade PDF audit trail in one click Built as a banking payment processing demo, divergence is intentional andbrealistic: rounding rules (ROUND_HALF_DOWN vs ROUND_HALF_UP), FX spread methodology (fixed 2% vs real-time 5bps), latency profiles (50–120ms vs 5–20ms), and audit log formats (fixed-width vs JSON). Bob's verdict: cut over instant and scheduled payments now. Hold international until the FX team reconciles. That's not a gut feeling —it's function-level evidence. The gap in the market: tools like Cutover.com, ServiceNow, and PDI handle project and change management around cutovers. None operate at code-function granularity. Bob the Judge fills that gap natively — using Bob's repository context to answer the question every migration team dreads: "Is it safe to cut over yet?"
17 May 2026