Data Infrastructure / Product Engineer
Grow into the engineer our internal tooling and client data infrastructure get built around. We're betting on raw talent and fundamentals — not on years of industry experience.
Most of Datacop is consultants running technical marketing for US and UK eCommerce brands ($25M–$2B revenue range). This role is different: you're the engineer. The work has two sides that feed each other — technical client work, mostly in Google Cloud: data engineering in BigQuery, pipelines, tracking implementations, warehouse builds for real brands with real data volumes. And building the tools that make that work repeatable — internal tooling that's increasingly becoming products in its own right. The concrete work is listed below.
Both our founders spent years at Exponea — the Slovak startup whose platform became Bloomreach Engagement. What we remember from there: some of the most important systems were built by people in their first job. Matfyz and FIIT people with no industry experience, terrifying fundamentals, and the nerve to own hard problems. That's the profile this role exists for.
If you've never had a job, that's fine. If your degree isn't finished, that's fine. What matters is whether the underlying material is there — the fundamentals, the builder instinct, the learning rate. The domain can be taught; the material can't.
Before applying, please read our full Join Datacop page — it explains who we hire, how we work, what we offer, and what we expect. The rest of this page assumes you've read it.
The shape of your work will evolve as you grow. In the first 6–12 months, expect a mix of:
You studied (or study) at matfyz, FIIT, or somewhere with the same relationship to first principles. Not because we care about the diploma — because we care what years of real math and computer science do to how a person thinks. You know why a hash map is fast — and when it isn't. You've implemented things most people only import.
You build things nobody asked you to build. There's a repo, a game, a scraper, a bot, a compiler for a language with one user. Possibly abandoned. That's fine — the instinct is the point.
A vague brief doesn't freeze you — you sharpen it. You decompose problems you've never seen before, because that's what problem sets trained you to do.
This profile has no industry experience by definition. What it has instead is a learning rate that makes inexperience a temporary condition.
Tasks live in a project management tool and you're expected to keep them updated — deadlines exist, and delivery gets checked. What we don't do is micromanage the path: nobody prescribes how you solve a problem or watches over your shoulder while you do. You get context, ownership, and mentorship when you want it. That's freeing for the right person and uncomfortable for the wrong one.
Our clients are in the US and UK, our tools and docs are in English. You don't need to be a polished presenter — this is an engineering role — but you need to read, write, and hold a technical conversation comfortably.
Or hunger to get there fast. AI is how the work is done at Datacop, not a side experiment.
What we don't require: work experience, a finished degree, a polished CV, or prior knowledge of eCommerce and marketing tech. We've hired people whose only track record was what they built for themselves.
Send a short note to hiring@datacop.services — subject line “Data Infrastructure / Product Engineer — Future Builder.”
Skip the cover letter. Send us something you built instead. Tell us:
If you're reading this in your last year at FIIT or matfyz and thinking “I could do this but I've never had a job” — that's not a gap in your application. That's the profile.