Emir Ribic · Selected work

Problems I've helped
companies solve.

I help teams with Go backends, cloud infrastructure, API integrations and technical direction. These examples show the problems I worked on, my contribution, and what changed.

Selected case studies

PolymerSearch · 2020–2024

From spreadsheets to a product people can use

The problem
Build and scale a platform that turns spreadsheets into interactive web apps.
My contribution
I architected the platform, owned the Go backend and AWS infrastructure, and led a team of 7+ engineers. I moved manually managed infrastructure into Terraform and added deployment notifications in Slack.
The result
The team shipped more frequently and operated a more reliable system, with infrastructure changes managed in code.
Read the deployment write-up →

Work&Co · 2019

Reducing API load by 70%

The problem
Reduce the API load created by an integration between systems.
My contribution
I built the integration in Go and used webhooks to change how updates moved between the systems.
The result
The integration reduced API load by 70%.

Shamaazi · 2019–2020

Moving legacy services to serverless

The problem
Modernise legacy systems and build a donation chatbot for charities.
My contribution
I migrated services to AWS Lambda and DynamoDB and built Zak, the donation chatbot, using Go.
The result
The legacy services moved to serverless infrastructure, and the donation workflow became available through Zak.

Current work at Kayse

Engineering leadership · December 2024–Present

Leading engineering for an AI legal tech platform

I lead a team of 15 engineers and own architecture, technical direction and engineering standards. I introduced coding agents and agent loops into the team's development workflow.

That work shapes how I approach AI products: the services, data flows and development practices around a model need as much attention as the model itself.

Other engagements

GiveCard
Refactored a Go backend for scalability, using AWS and Terraform.

Qopla
Improved microservices architecture and the CI/CD setup.

Damudo
Worked on a migration from a monolith to microservices and Austrian tax requirements.

T-Mobile
Built backend functionality for a B2B VoIP self-service portal.

Vibe
Connected external services through webhooks and CLI tools.

Claire Automotive Support
Built automotive aftersales SaaS used across European dealerships.

How I approach the work

01 · Understand

Start with the real workflow

We look at what should happen, what happens today, and where the gap is. For an existing system, I review the code, data and infrastructure before proposing changes.

02 · Agree

Define a first milestone

We agree on scope, my involvement and a schedule. You know what you will be able to review before the implementation starts.

03 · Deliver

Show working progress

I explain tradeoffs and flag scope changes early. Testing, deployment and documentation are part of the work.

What are you working on?

Send me a short description of the problem, your current stack, and the timeline you have in mind. We can work out the scope and a first milestone together.

Sarajevo, Bosnia & Herzegovina · CET/CEST · Working remotely