p. 01
of 32
Sumeru Chatterjee.

Index of Work, 2009 — present.

A working monograph by Sumeru Chatterjee — staff software engineer, mobile & platform.

15+ yrsshipping production systems
4 yrsindependent founder track
10⁹ eventshandled per day at Iterable
100+enterprise SDK integrations

I.Foreword

A note from the author.

I’m Sumeru. I’ve spent the last fifteen years on the harder problems near the edges of mobile — AR SDKs at Layar, regulated banking at ABN AMRO, classifieds at eBay, real‑time wearables at Athos, then founding engineer for a regulated crypto fintech in Amsterdam.1

Since 2022 I’ve been on an independent track in parallel with the day job: building consumer apps, automated trading systems with real money on the line, and AI‑augmented backend infrastructure. Right now I’m Staff at Iterable, owning the cross‑platform SDK that a hundred‑odd enterprises integrate against; and I’m shipping Naksh on the side.

The pages that follow are a working monograph: the five things I’d point a hiring manager at first, then a thinner bibliography of older positions, then enough about the rest of life to read like a person. If any of it is interesting — or if you’re hiring at the staff or principal level — write to me.2

II.Plates — selected works

Five things, in some depth.

FIG. I.A Wallet onboarding
+ KYC/AML flow
· 4 screens, iOS ·

Fig. I.A Onboarding and identity verification flow, integrated with PrimeTrust. Renders pending designer drop-in.

PLATE I · 0012021 — 2022 · Amsterdam

Burst (now Glide).

Founding engineer · regulated crypto fintech.

End‑to‑end technical delivery of a regulated wallet platform: cross‑platform SDKs for secure transaction signing and private‑key management; a fiat‑to‑crypto onramp with full KYC/AML integrated against PrimeTrust; and the Node.js + AWS backend doing real‑time transaction processing, compliance auditing and regulatory reporting.

I joined as employee one on the engineering side and owned the technical case that got the product through regulatory approval and into the market.

RoleFounding engineer · Lead StackSwift · Kotlin · Node.js · AWS · PrimeTrust SurfaceMobile SDKs · Backend · Compliance OutcomeRegulatory approval & platform launch3
Read Plate I
FIG. II.A Cross‑platform
SDK surface
· iOS · Android · RN · Flutter ·

Fig. II.A Public API surface across four runtimes. Schematic.

PLATE II · 0022024 — present · Lisbon (remote)

Iterable Mobile SDK Platform.

Staff engineer · technical owner.

Cross‑platform SDK architecture (iOS, Android, React Native, Flutter) powering push, in‑app messaging and real‑time analytics for over a hundred enterprise customers — among them NBC and DoorDash — at billion‑event scale.

Versioned interfaces, backward‑compatibility contracts, comprehensive test infrastructure. The dev‑rel and escalation work that turns a hard integration into a fast one — Priceline, threading deadlocks, the ANR that took three days.

RoleStaff · Technical owner StackSwift · Kotlin · React Native · Flutter · CI SurfacePublic SDK · Internal platform · DevRel OutcomeMaterially fewer regressions; faster enterprise integrations
Read Plate II
FIG. III.A Live position graph
+ event stream
· Polymarket · Tradofire ·

Fig. III.A Position curve over a 30‑day window. Real money.

PLATE III · 0032023 — present · Independent

Polymarket bot + Tradofire.

Sole engineer · live algorithmic trading.

Two real‑money trading systems running in production. The first is a live, profitable Polymarket bot trading a combination of strategies across prediction markets, with automated execution, market‑data handling and position management.

The second is Tradofire — a multi‑exchange crypto system ingesting WebSocket market data from Binance and Coinbase, with an event‑driven execution engine, secure API integrations and risk controls. Both designed for low‑latency and the kind of failure modes you only learn about by being on the wrong side of one.

RoleSole engineer · founder StackPython · WebSocket · Postgres · Docker SurfaceExchange APIs · Strategy engine · Risk OutcomeLive; profitable to date4
Read Plate III
FIG. IV.A BLE signal trace
+ on‑device DSP
· hardware → app ·

Fig. IV.A EMG waveform from garment sensor through BLE to iOS. Sub‑second.

PLATE IV · 0042020 — 2021 · Amsterdam

Athos.

Senior iOS engineer · real‑time systems.

The full hardware‑to‑app pipeline for a biometric wearable: embedded firmware in C, the BLE communication protocol, on‑device signal processing, and the native iOS client. Sub‑second latency from sensor to insight.

Modernised the iOS platform from legacy Objective‑C to Swift/SwiftUI in parallel — redesigning architecture for real‑time visualisation and long‑running sensor sessions.

RoleSenior · cross‑functional StackC · Swift · SwiftUI · BLE · DSP SurfaceFirmware · Protocol · iOS client OutcomeLive streaming at sub‑second latency
Read Plate IV
FIG. V.A Daily introductions
+ compatibility card
· iOS app ·

Fig. V.A A daily set, with the 36‑point compatibility breakdown.

PLATE V · 0052024 — present · Independent

Naksh.

Founder · iOS & backend.

A matrimonials iOS app for people with serious intentions. Three to seven curated introductions per day — scored against a thirty‑six‑point compatibility framework with profile, family context and verification — in place of an infinite feed of swipes.

I do everything here: the Swift/SwiftUI app, the Node.js backend, the scoring framework, the verification flow, the website. iOS app is currently in App Store review.

RoleFounder · sole engineer StackSwift · SwiftUI · Node.js · Postgres SurfaceiOS · Backend · Web · Brand OutcomeWebsite live; iOS in review
Visit trynaksh.com

III.Bibliography

Earlier & supporting work.

2019Holberton School — Software Engineering Instructor (C, Python, DevOps). Cali & Barranquilla, Colombia.Cali cohort highest‑performing across the program at the time.
2018 — 19Moneyou / ABN AMRO — Senior Engineer (iOS, Node.js, AWS Lambda). Amsterdam.Serverless backends powering regulated banking; rebuilt the Moneyou Go iOS app.
2017VEON — Senior Software Engineer (Contract). Amsterdam.Consumer iOS application in Swift / VIPER for the multinational telecom.
2016 — 17eBay Classifieds (Marktplaats) — Senior iOS Engineer. Amsterdam.Shared modular codebase across 11 countries. Tweedehands app, Belgium. Hackathon winner.
2014 — 16Layar — Senior SDK Engineer (iOS, Android, C++). Amsterdam.Cross‑platform AR SDK with shared C++ core for computer vision and real‑time rendering.
2014IceMobile (Jumbo) — Senior iOS Developer. Amsterdam.Loyalty app over a full product cycle; shared component framework.
2013 — 14Booking.com (acq. eBuddy) — Senior iOS Developer. Amsterdam.XMS Chat; migrated the entire Booking.com iOS codebase from MRC to ARC.
2010 — 12MicroStrategy · Bloomberg LP — Software Engineer.Earlier US‑based work, before Amsterdam.

IV.Biographical note

A longer self‑portrait.

I wrote my first iOS app in 2009, back when memory was still managed by hand. The career arc since has bent toward platform engineering: SDKs, mobile architecture, the systems that sit underneath consumer products and have to keep working when a hundred teams pull on them at once.

The work I’m proudest of usually sits at the intersection of mobile and a regulated environment — wallets at Burst, banking at ABN AMRO. The constraints sharpen everything. You can’t move fast and break things when "breaking things" means a regulator opens a file on you, and that’s the kind of forcing function I’ve come to like.

The independent track since 2022 is partly an experiment in being the only engineer on systems that have real consequences if they fail — trading bots running real capital, an iOS app for something as serious as choosing a partner. That experience is shaping how I think about the next staff role.

Outside the screen: living in Lisbon, occasionally back in Cali, occasionally on a stage at a medical conference talking about something tangentially related to all of the above.

V.Correspondence

How to reach me.

Write to me if you’re hiring at staff or principal, or you’re building at the edge of mobile, payments or real‑time.

I read everything that lands in the inbox at hello@sumchattering.com — usually within twenty‑four hours.

For recruiters: LinkedIn is the most efficient channel. For talks or speaking engagements, email is best.