Work at ECORTIQ
Build systems that carry real load.
We are a small team of senior engineers in Bratislava. You will own systems end to end, talk to clients directly, and carry the pager for what you ship. If that sounds like the job you want, read on.
Why join
Reasons senior engineers stay.
We keep the team small on purpose. That changes what the work feels like day to day, and it is the honest reason people come here and do not leave.
Senior team, real mentorship
Median eleven years of experience across the team. You review each other's designs, pair on the hard parts, and get feedback from people who have run these systems in production before.
Ownership from design to on-call
You own a system end to end: the architecture, the code, the runbook, and the pager. Nobody hands you a ticket with the interesting decisions already made.
No bureaucracy
Flat structure, direct client contact, and decisions made by the people doing the work. There are no status meetings whose only output is another meeting.
Learning budget that gets used
A yearly budget for conferences, courses, and books, plus dedicated time to dig into a tool before we put it near production. We would rather you learn on our time than guess on the client's.
Sane on-call
On-call is shared across the whole engagement team, compensated, and followed by time off. We invest in observability and runbooks so the pager is quiet, and we treat a 3am page as a bug to fix, not a fact of life.
Work on systems that matter
Ledgers that settle in milliseconds, pipelines moving millions of events per second, platforms that hundreds of services depend on. The stakes are high enough that doing it well is genuinely satisfying.
Open roles
Where we need people right now.
Four roles are open. If your background is close but not exact, apply anyway and tell us how it lines up. Every application goes to careers@ecortiq.com and is read by an engineer.
Senior Backend Engineer (Go)
You will build high-throughput services in Go: event-driven APIs, ledgers, and the kind of backend that has to hold its latency budget under load. We expect strong opinions about concurrency, data modelling, and where to draw service boundaries, backed by systems you have actually shipped and operated.
Site Reliability Engineer
You will run the platforms our clients depend on: Kubernetes, infrastructure as code, and the observability that makes an incident short. This is deep SRE work, defining SLOs, tuning error budgets, and improving the systems so the on-call rotation stays quiet. Comfort with Terraform, Prometheus, and a debugger under pressure is essential.
Data Engineer
You will design streaming pipelines that move data from source to decision in seconds, not overnight batches. Think Kafka, ClickHouse, and exactly-once semantics that actually hold. We want someone who cares about correctness under reordering and backpressure, and who can reason about a pipeline processing millions of events per second.
Applied AI Engineer
You will put language models into production behind guardrails you can measure: retrieval systems, model serving, and evaluation pipelines that catch regressions before a client does. This is engineering, not research. We care about latency, cost per request, and whether the eval numbers hold up on real traffic, not on a benchmark.
Do not see your role?
We hire senior engineers whenever we meet the right one. If you build the kind of systems on this site, tell us what you would want to work on.
How hiring works
Five steps, no busywork.
The whole process usually runs in two to three weeks. We tell you where you stand at every step, and we pay for the day you spend building with us.
Application
Send a short note and a link to work you are proud of: a repo, a system you built, a write-up. No cover letter theatre. An engineer reads it and replies within a few days.
Intro call
Thirty minutes to swap context. We tell you honestly what the work looks like and what on-call means here. You ask us anything. Both sides decide whether to keep going.
Technical conversation
Ninety minutes on systems you have built and one we are working on. We talk through trade-offs and failure modes together. No trick questions, no whiteboard algorithm trivia.
Paid pairing day
You spend a day working alongside the team on a real, scoped problem, and we pay you for it. It is the clearest signal for both of us: you see how we work, we see how you think.
Offer
If it is a fit, you get a written offer with a clear salary, the benefits below, and a start date that works for you. We answer any question before you sign.
I joined to stop being a ticket-taker. Here I own the ledger I built, I talk to the client's engineers every week, and when something pages me at night it is a bug we fix, not a ritual we accept.
Apply
Think you would fit here?
Send a short note and a link to work you are proud of. An engineer reads every application and replies within a few days.