Skip to content

Systems where correctness matters more than novelty.

I'm Nikola Peković, a senior software engineer based in Montenegro, working with companies in Europe and the US. My work is the part of regulated software that has to be right: banking identity, healthcare claims, visa filings, and the AI agents that now sit inside those workflows.

I've been accountable for systems that had to pass an audit, where “it usually works” is a finding. That standard applies whether the system runs a bank or a restaurant floor.

Portrait of Nikola Peković
Based in Montenegro

Chronology

  1. Consulting: AI agents & product engineering

    Consulting on document-heavy AI agents, and taking products from idea to launch as the one accountable engineer for backend, mobile, web, infrastructure and deployment. The work includes an AI visa agent and a portal-autofill browser extension now in production for a visa services platform, and 3DIN, a geo-verified media platform built solo from architecture through a validated proof of concept.

  2. Healthcare claims & EDI

    Document intake and claims pipelines for US health plans: SFTP and S3 ingest, per-plan normalization rules, exports into downstream systems, and reconciliation of X12 837 claims against TA1, 999 and 277 acknowledgements. Built in Java and Spring, with queues and batch pipelines that have to balance.

  3. Banking identity

    Customer identity for the Serbian retail bank of a European banking group, as a backend engineer in the delivery team of a software consultancy, owning several services end to end: OAuth 2.0 and OIDC with Keycloak, authenticator device lifecycle, transaction signing and customer onboarding for the mobile and web banking app. The work was audited and security-reviewed.

  4. Hospitality & restaurant operations

    Operations platforms for hospitality: ordering, inventory, and the unglamorous reality of systems that have to keep working through a Friday-night rush on flaky restaurant Wi-Fi. That is where I learned to treat reliability as part of the product.

How I work

Stop mistakes at the door

Catching an error before it enters the system is cheaper than cleaning it up later. That goes for a form field and for an architecture decision.

Everything in writing

A written progress note every week, decisions recorded with their reasoning, and runbooks your team can run from after the handover.

Clear ownership

Whether I'm building alone or as part of your team, everyone knows who owns what. And you always talk to the person writing the code.

Have a system that has to be right?

Tell me what's at stake. You'll hear back within one business day, and the first call is 30 minutes, with no obligation.

Discuss your system

or email contact@nikolapekovic.com