Backend engineer · Python

Chaitanya Arora

I build transactional backend systems where being wrong is expensive: ledgers, payouts, credit decisions and approval workflows. When they fail or slow down, I find the real cause and bring numbers to the argument.

Since 2022 I've built a bank's balance ledger, the credit-decision and document-AI services behind a lending platform, search over 18–20 million court documents, and the vendor portal PVR INOX runs its accounts payable on.

Delhi NCR, India

Experience

Where I've worked

GoTymeX

Jan 2026 – present

Software Development Engineer III, Enterprise Payments · contract · Remote / Delhi NCR

Backend services for the enterprise payments platform behind GoTyme Bank in the Philippines and TymeBank in South Africa: accounts, pay-ins and payouts for business clients. Unlike consumer banking, where activity spreads across millions of accounts, a few business accounts take heavy concurrent writes, so the system is OLTP and has to stay consistent under contention.

  • Built the balance-ledger service from an empty repository to production.
  • Designed the payout service's state machine, written up in a decision record the team adopted, and made message redelivery safe to retry.
  • Traced a latency collapse in the Java payout service to a synchronized logger rather than the database, and fixed it with asynchronous logging.
  • Ran the benchmarks behind the team's datastore decisions, for the ledger and for transaction search.
  • Now building the backend for the client portal.
  • Rewrote the team's logging standard and gave technical sessions to the engineers.
  • Python
  • FastAPI
  • Java (Spring Boot)
  • PostgreSQL
  • DynamoDB
  • SQS
  • EventBridge
  • ECS Fargate
  • event-driven services

Savii (acquired by GoTyme Bank)

Mar 2022 – Dec 2025

Software Engineer II, lending platform · contract · Remote

A Philippine fintech that offers salary loans to employees through their employers.

  • Owned the document-processing service end to end, from proof of concept to production. It reads payslips, government IDs and employment certificates and pre-fills the data for loan officers, cutting manual processing per application from about 15 minutes to about 2.
  • Moved its extraction from OCR templates to LLMs, and made the provider and model per document type a configuration change rather than a release.
  • Co-designed and co-built the credit-risk service from scratch with one other engineer. Credit decisions went from 8–9 seconds to under 500 ms, and lending-policy changes went from months of engineering to runtime configuration.
  • Created its eligibility-validator framework, still in use today, and the employer-policy admin APIs, which are unchanged since I left.
  • Wrote the effective-interest-rate (XIRR) compliance logic that keeps every loan offer under a monthly cap. Its core calculation became part of the company's shared SDK.
  • Productionised the data-science team's loan-scoring models as a service on AWS.
  • Built Tracker Service, unprompted and with one other engineer: a FastAPI and MongoDB app with Google sign-in and two-way BigQuery sync, replacing the spreadsheets collections and finance were working in. It has run for four years with no code changes.
  • Wrote the scheduled job that purged the risk service's never-cleaned simulation-log table, cutting it by about 90% and keeping a rolling three-month window.
  • Mentored the engineer who took over the risk service through a year-long handover, and ran a Datadog session for the engineering team.
  • Python
  • Django
  • FastAPI
  • PostgreSQL
  • AWS (Textract, Bedrock)
  • Redis Streams
  • BigQuery
  • MongoDB
  • LLMs

Dr Lal PathLabs

Oct 2020 – Feb 2022

Deputy Manager, Information Security (joined as IT trainee) · Delhi NCR

In my final year of college I found a security flaw in their systems and disclosed it responsibly. Two weeks later they hired me, and I was promoted twice in 14 months.

  • Built a computer-vision pipeline that automated onboarding for phlebotomists: OpenCV to correct skew and lighting, Google Vision to pull text and faces from ID documents and certificates, and a parser that filled in the onboarding forms.
  • Ran the vulnerability assessment and penetration testing programme across applications, infrastructure and medical instruments, and designed the vulnerability-management process.
  • Wrote the secure-coding guidelines, and assessed software releases, vendors and the data-lake architecture.
  • Built application-security dashboards for senior management, presented weekly to the CEO and CTO and monthly to the managing director, and worked directly with the CISO.
  • Python
  • OpenCV
  • Google Vision
  • application security
  • VAPT

Independent work

As a sole proprietor

I also run a small practice of my own: a product I build and license, consulting work, and two browser extensions.

PVR INOX Vendor Portal

2022 – present

Independent product, licensed to PVR INOX · sole developer

  • Built, and still run, the vendor-invoice portal PVR INOX's accounts payable works through. Vendors submit invoices against purchase orders and track them through approval and goods receipt to payment.
  • Built an eight-stage invoice lifecycle and a separate vendor-advance state machine, approval chains that route each invoice by amount, and purchase-order balance, duplicate and GSTIN checks at submission, with a full audit trail.
  • Added role-based access for vendors and five kinds of employee, scoped by location and department. Master data, approval workflows and ERP payment files load in bulk by CSV, and one payment can cover several invoices or part of one.
  • Moved its ERP integration from Navision to SAP.
  • Python
  • Django
  • PostgreSQL
  • S3
  • Gunicorn
  • Nginx

Freelance consulting

Oct 2024 – Jul 2026

Technical lead, data and research · an AI legal-tech platform · Remote

  • Led the data and research team, three engineers over the engagement plus 4–5 legal interns, that collected India's case law: the Supreme Court, about 25 High Courts, tribunals, GST rulings, central Acts and the e-Gazette. About 18–20 million documents, OCR'd to full text.
  • Created the research service and wrote most of its code: full-text search on PostgreSQL and then Elasticsearch, semantic search on Pinecone, and a Neo4j graph of which judgments cite which.
  • Re-architected a founder's legal-notice prototype into a multi-tenant product for lenders. It scores defaulted loans and routes each one to soft recovery, a cheque-bounce notice or litigation; uses an LLM to map each lender's templates and borrower files; and sends and tracks notices over WhatsApp, SMS, email and post. It was deployed and in pilot when I handed over.
  • Mentored the engineer who now runs the research service, and onboarded my successor.
  • Python
  • Django
  • PostgreSQL
  • Elasticsearch
  • Pinecone
  • Neo4j
  • Redis Streams

Chrome extensions

Side projects

Built and published on my own

  • Hashtag ToolTips shows how many followers a hashtag has, right where you read and write LinkedIn posts. About 1,800 people use it every week, with no marketing. I rebuilt it in 2026 for LinkedIn's current pages.
  • My first extension peaked at more than 13,000 weekly users, until changes to LinkedIn's API broke it.
  • JavaScript
  • Chrome Manifest V3
  • 8 languages

How I work

Correctness is the job

Before I build, I pin the requirement down one question at a time until the edge cases are explicit, and I write the expected behaviour down first. I measure before I argue. When a service falls over under load, I profile it until I know where the time goes; when a design is contested, I build a test rig and bring numbers.

I keep designs small and don't repeat checks the system already guarantees. I'm sceptical of any claim, from a teammate's report, a library's default or an AI agent, until I've seen the evidence. I use AI coding agents a lot, as a supervised team rather than an autopilot: every change is checked against the requirement before it merges.

And I write decisions down, in design records, contracts and load-test reports, so the next engineer doesn't have to rediscover them.

Writing

On the blog

Notes on things I've built, what broke along the way, and what I changed.

All posts →

About

How I got here

I got into computer science at school, where my final-year project was a 2,000-line quiz game in C++. At Netaji Subhas Institute of Technology I was technical head of the Entrepreneurship Cell and built websites for college startups. I also got into deep learning through online competitions, and finished 11th in one that classified roof types from aerial images.

In my final year I found a security flaw at Dr Lal PathLabs and reported it to them. They hired me two weeks later, and I spent the next 16 months in information security. Since 2022 I've been a backend engineer in fintech: first on Savii's lending platform, and now on GoTymeX's enterprise payments platform. Alongside that I build and license software of my own.

  • BE, Netaji Subhas Institute of Technology · 2017–2021
  • Class XII (CBSE), St. Columba's School · 2016 · 99/100 in Computer Science

Contact

Get in touch

Email is the fastest way to reach me. If you'd like my resume, ask and I'll send it.