Nikola Čorlija

Lead iOS Engineer · London, UK

Nikola Čorlija

iOS engineer with twelve years in software. I have built iPhone apps since 2014, first in Sarajevo and, since 2018, for fintech companies in London. Currently Senior iOS Developer at NewDay.

nikola.corlija.ch · linkedin.com/in/nikolacorlija · London, United Kingdom

Download CV (PDF) LinkedIn ↗

About

I'm a Lead iOS Engineer based in London. Most of my iOS work has been in finance: a social trading app at SwipeStox, open banking at Bud, and consumer credit at NewDay, where I have worked since 2021.

Before London I wrote iOS apps at Atlantbh and Ministry of Programming in Sarajevo and led iOS development on contract at Tech 387. I started my career as a software engineer at m:tel in Banja Luka.

Experience
12+ years
iOS since
2014
Domain
Fintech
Based in
London, UK

Experience

  1. 2021 — Now

    Senior iOS Developer · NewDay

    London, UK · Full-time · UK consumer credit and credit cards

  2. 2018 — 2021

    Senior iOS Developer · Bud

    London, UK · Full-time · Open banking and financial data

  3. 2017 — 2018

    Lead iOS Developer · Tech 387

    Sarajevo, BA · Contract

  4. 2016 — 2018

    iOS Developer · SwipeStox GmbH

    Social trading app

  5. 2016 — 2017

    iOS Developer · Ministry of Programming

    Sarajevo, BA · Software product studio

  6. 2014 — 2016

    iOS Developer · Atlantbh

    Sarajevo, BA · Software engineering company

  7. 2013 — 2014

    Software Engineer · m:tel

    Banja Luka, BA · Telecom operator

Skills

Languages
Swift, Objective-C
UI
UIKit, SwiftUI, Auto Layout
Concurrency & data
Swift Concurrency, Combine, GCD, Core Data, Keychain
Quality & delivery
XCTest, Instruments, Xcode, Git, TestFlight, App Store Connect

Education

  1. 2008 — 2013

    BSc Computer Science 9.2 / 10

    Faculty of Electrical Engineering, University of East Sarajevo

Notes

  1. What @MainActor actually promises

    It guarantees where your code runs, not that nothing changes while it waits. Three places where that difference turns into bugs.

  2. Storing tokens in the Keychain: the settings that matter

    SecItemAdd is the easy part. Accessibility classes, device-only items and the item that outlives your app decide whether your login really is secure.

  3. Deep links come through two doors

    A link that works while the app is running can do nothing on a cold start. Why, and how to route both paths through one place.

All notes →

Contact

The quickest way to reach me is on LinkedIn ↗