Boris Nikolić
Software Developer · Backend-focused Full-Stack (Python, Go, PostgreSQL, React)
Based in Belgrade, Serbia · Remote friendly (CET) · Open to relocation within Europe · Looking for full-time or part-time backend, full-stack, or DevOps roles with flexible working hours · B2B contractor or employee
Odoo 16 modules in Python and PostgreSQL for Fairphone (2025 – present): carbon accounting and critical-material traceability
NestJS, Go, and Rust services, with the React and Next.js frontends that consume them
DevOps with security in mind: deploying and managing services, hardened Linux servers, Docker, CI/CD, monitoring
Building for the web since 2022, from frontend internships to contract engineering
Type a command and press Enter. Tab completes, arrow keys browse history, Ctrl+L clears.
Projects
4 projects, 2 with public code. Client work is under Experience.
rust-store/
Self-hosted on Forgejo
E-commerce store with crypto payments
An online store written in Rust that takes cryptocurrency payments, deployed and run on my own server.
- Deployed to my own server through a CI/CD pipeline on self-hosted Forgejo.
- Rust
- Forgejo
- CI/CD
snapsyncai/
SnapSyncAi: AI image-editing SaaS
An image-editing SaaS: sign in, buy credits, and edit photos with AI transformations.
- Photo restore, generative fill, object removal and recolor by text prompt, and background removal through Cloudinary's AI transformations; Clerk auth with webhooks syncing users to MongoDB; Stripe-paid credit packages.
- Next.js 14
- TypeScript
- MongoDB
- Cloudinary AI
- Clerk
- Stripe
ecommerce-platform/
repository ↗ (opens in a new tab)E-commerce platform (university project) (opens in a new tab)
A complete shop with real authentication, real payments, and an external product catalog that has to stay fast and keep working when the cache is down.
- Go (Gin) API gateway in front of an external product API: the browser never calls it directly; caching, error fallbacks, and dual-token JWT auth with revocable refresh tokens sit in one place.
- Two-step Stripe PaymentIntent checkout, order line-item snapshots, and an admin dashboard.
- Cache-aside Redis catalog that degrades gracefully; Nginx reverse proxy with rate limiting; Docker Compose.
- Go
- Gin
- Next.js
- PostgreSQL
- Redis
- Stripe
- Nginx
- Docker Compose
insightify/
repository ↗ (opens in a new tab)Insightify: website analysis tool (opens in a new tab)
Submit a website URL and get an analysis of its design, content, and user experience.
- Go (chi) service scrapes a submitted site with chromedp and passes the content to OpenAI's GPT-4o (first direct API calls, later the Assistants API) for an analysis of design, content, and UX; Next.js frontend.
- Go
- chi
- chromedp
- OpenAI API
- OpenAI GPT-4o
- Redis
- WebSockets
- Next.js
Working with people
- Requirements gathered directly from the people who use the software, then turned into a scope both sides understand.
- Technical terms and trade-offs explained in plain language, so non-technical stakeholders can decide on priorities and timelines with the full picture.
- Modules and features shipped end to end: built, tested, reviewed in GitLab merge requests, and deployed to production.
- Alongside the stakeholders from the first requirement to delivery, so what ships matches how they actually work.
Experience
Newest first. Client work is described at the level the engagement allows.
Software Developer (B2B contract) · Fairphone
Contracted via KIBNET, Belgrade · Python · Odoo 16 · PostgreSQL · OWL · GitLab. Responsible for the EU-side sustainability modules, both in production.
- FairMaterials, designed and built from scratch (live since August 2026): turns received purchase lines into grams of gold, cobalt, tin and tungsten through time-versioned product recipes, splits them across fair-sourcing programs with largest-remainder rounding at 1 µg, and posts them to a signed material ledger.
- GHG carbon accounting: backported Odoo's ESG module from v19 to v16 and built finance and supply collectors that turn journal items and received purchase lines into kgCO₂e across GHG Protocol scopes 1–3, using rule-matched emission factors and per-period currency rates.
- Resumable background jobs: chunked rebuilds under PostgreSQL advisory locks, an atomic UPDATE … RETURNING job claim and idempotent replays; new rows are swapped in one step, so a failed run never leaves a period empty.
- Reporting: OWL dashboards on JSON routes backed by materialized SQL views refreshed in dependency order; FairMaterials dashboard load cut from 2.8 s to 0.55 s.
- CDC API (prototype): external systems such as data warehouses read Odoo changes in cursor-based batches, acknowledged in order so no change is skipped.
- Full cycle with stakeholders: requirements, plain-language trade-offs, GitLab merge-request review, deployment to production.
Client-owned, licensed software; details limited by agreement.
Independent Full-Stack Developer · Self-directed
Belgrade
- Moved from frontend into backend: built NestJS servers and REST APIs with auth and PostgreSQL, plus the React frontends consuming them.
Frontend Developer (part-time) · High school partner company
Zaječar
- Contributed to a production React codebase: built UI components and styling to spec.
- Prepared request data for backend APIs and handled responses and state on the frontend.
Web Development Intern (school programme) · Local team, Zaječar
Alongside school
- Built and styled websites in HTML, CSS, and JavaScript.
education: BSc Software Engineering, Singidunum University, Belgrade, expected 2027
Skills
Entries marked (working knowledge) are used less often.
Languages/
- Python
- Go
- TypeScript/JavaScript
- SQL
- C/C++
- Rust
- Java (Spring Boot) (working knowledge)
- PHP (Laravel) (working knowledge)
Backend/
- Odoo module development
- Go (Gin, chi)
- NestJS (Node.js, Express)
- REST API design
- JWT auth & RBAC
- Stripe
Data/
- PostgreSQL (materialized views, partial indexes, advisory locks, PL/pgSQL)
- Redis
- MongoDB
- Change data capture
- Query optimization
- RabbitMQ
- Scheduled jobs
Frontend/
- React
- Next.js
- Angular
- Tailwind CSS
- Redux Toolkit
- Odoo OWL
Ops/
- Linux
- Docker/Compose
- Nginx
- GitHub Actions
- GitLab CI
- Forgejo Actions
- Prometheus
- Grafana
Generative AI/
daily agentic coding with Claude Code and Codex
- OpenAI API (GPT-4o, Assistants)
- Cloudinary AI
- prompt engineering
How I work with AI
An agent in the terminal, briefed like a teammate. The loop stays the same whether the codebase is years old or an empty directory: brief, plan, build with tests, review, verify, document. The agent gets the same context a new colleague would, written down in the repository.
loop
Every task, every repository, the same six steps.
- briefA written brief with goals, constraints, and integrity rules: what the agent may and may not invent.
- planBrainstorm, then a written plan before code. Specs and plans are committed next to the code.
- buildSmall tasks, tests first where the stack allows. The agent works from CLAUDE.md and the docs hierarchy, not from chat memory.
- reviewAI review passes (code review, security review) followed by my own read of every change.
- verifyLint, build, run, and drive the actual app before anything is called done.
- documentSTATUS, CHANGELOG, and open-question files so the next session, human or agent, starts with context.
prompting
Prompts are repository files with a job, a reading order, rules, and a done checklist. They are versioned like code and reviewed like code.
- Role prompts per job: a Builder prompt for features and fixes, a Testing prompt for coverage, each with its own goal, workflow, and checklist.
- A docs hierarchy the agent reads first: CONTEXT.md, STATUS.md, coding standards, and the security remediation plan.
- Hard rules as NEVER / ALWAYS lists (no secret logging, parameterized SQL, crypto/rand only) that come before style preferences.
- A reporting format for finished work: what changed, files, tests added, breaking changes, next steps.
- An example session in the prompt so the agent sees a full loop, not just rules.
- Tool inventory in CLAUDE.md: which commands and MCP servers exist, so the agent uses real tools instead of guessing.
day to day
Every repository carries its own setup, so a session starts knowing the project instead of asking about it.
- a codebase I'm new to
- The first session is orientation: the agent reads the repository and writes down what it learned (stack, commands, architecture, rules), so every session after starts productive.
- from the ground up
- Brainstorm before code: goals, constraints, and trade-offs argued out with the agent, a plan written and committed next to the code, then small tasks with tests first.
- the everyday
- Features, fixes, debugging, and reviews run the same loop, with planning, review, and verification checklists so quality does not depend on the day.
- memory and specs
- Persistent memory files plus written specs and plans committed next to the code, so the next session, human or agent, picks up where the last one stopped.
real systems
The agent does not just write code, it acts. MCP servers give it real tools instead of pasted output, declared per project so it knows exactly what it can call.
- GitLab
- Pipeline automation from the agent: merge requests, pipeline status, and job logs without leaving the session.
- cloud infrastructure
- Managing infrastructure resources through MCP tools, with the same review loop as code changes.
- issue and ops trackers
- GitHub, Jira and Confluence, Linear, Datadog, and PagerDuty connectors, enabled per project.
- browser
- The agent drives a browser against the running app: screenshots, console, DOM checks, keyboard navigation.
Home lab
Self-hosted infrastructure and free-time projects, run like production.
- forge:
- Forgejo git forge on a self-hosted server.
- servers:
- Hardened Linux servers.
- monitoring:
- Prometheus and Grafana over the stack.
- irc:
- IRC chats hosted over onion services (Tor) and garlic routing (I2P).
- rust:
- Rust implementations for systems work, built in free time.
About
Python/Odoo developer at Fairphone since 2025, building Odoo 16 modules in Python and PostgreSQL for carbon accounting and critical-material traceability; building for the web since 2022.
I own features end to end, from stakeholder requirements to deployment, and also write Go and Rust services and take care of the DevOps side with security in mind: deploying and managing services, hardened Linux servers, Docker, CI/CD pipelines, and monitoring.
university
BSc Software Engineering, Singidunum University, Belgrade. Expected 2027, alongside the work.
off the keyboard
- Sim racing, Counter-Strike, and cars.
- The gym, trying to stay in shape.
- A good meal: pasta, or anything protein-rich.
How I work
- Model the domain before the endpoints
- Schemas, states, and invariants come first. APIs and screens follow from them.
- Design for failure
- Acknowledgments, retries, and idempotent steps, so a crash midway becomes a retry instead of a data gap.
- Measure the database
- Query plans and real data volumes before optimizing. PostgreSQL usually has the answer.
- Keep boundaries clear
- Layers and services that can be understood, tested, and changed on their own.
- AI writes, I answer for it
- Agents work from written briefs and rules; every change is read, understood, and verified by me.
- Automate what would otherwise repeat
- If something has to be done twice, it gets a script: server hardening, pipelines, reports.
Open to new roles and projects
Looking for full-time or part-time backend, full-stack, or DevOps roles with flexible working hours, remote friendly (CET), as a B2B contractor or an employee. Open to relocation within Europe for hybrid roles with a couple of office days a week. Email is the fastest way to reach me.