Nansen is hiring a Senior Data Engineer in Engineering — Remote Europe. The overview below is synthesized from the employer posting on job-boards.greenhouse.io: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
Talent Wanted. For hazardous journey. Small wages, bitter cold, long months of complete darkness, constant danger, safe return doubtful. Honour and recognition in case of success.
Fridtjof Nansen crossed the Arctic, going places no human had ever been. Together with our users, we're doing the same onchain: charting entirely new territory.
Nansen is the onchain analytics platform traders and funds use to see what's actually happening on-chain. We label and track 500M+ blockchain addresses, the largest such dataset in the industry.
Our mission: Surface the signal and create winners.
This seat also comes with a defined runway: you'll start as an IC, with a clear path to Engineering Manager within 12–18 months for the right person.
What you'll do at Nansen
Day-to-day scope for the Senior Data Engineer as described in the posting:
You'll work with data engineers and ML engineers to build the data infrastructure that powers Nansen's customer-facing analytics product.
- Design, build, and scale data pipelines and infrastructure in ClickHouse, Postgres, Python, and dbt
- Run the pipelines behind 500M+ labeled addresses, moving terabytes of streaming and batch data every day
- Partner with crypto researchers, software engineers, and product to shape how data gets modeled, surfaced, and productized
- Own data quality, reliability, and observability end-to-end. At most analytics companies a wrong number is a support ticket. Here, it's a position someone took.
- Mentor other data engineers and raise the technical bar across the team
- Use AI tools and agents to move faster and cut the busywork out of your day
What we're looking for
- You've shipped and scaled high-performance data systems in production
- Deep expertise in SQL and Python, with real hands-on experience in dbt, ClickHouse, and Postgres
- Strong grasp of streaming data architectures, comfortable operating at genuine scale
- You work the full data stack: ingestion, transformation, storage, modeling, serving
- You already build with tools like Cursor, Claude Code, and MCPs
- You write clearly. This team is remote and async, so most decisions get made in writing
- Bonus: experience leading or managing projects in a smaller team, fluency in onchain data structures, Web3 technologies, and crypto markets
What we offer our crew
What the posting highlights about the offer:
- Competitive salary. Meaningful equity. Real ownership in what you build
- Fully remote with support for in-person co-location
- Annual company retreat and team off-sites in Singapore, Bangkok, or Oslo, with flights and accommodation covered
- Unlimited AI tokens
- Your own OpenClaw for work
- Nansen Pro account: full access to the most detailed onchain data in the market
- Speed, ownership, curiosity, courage, transparency, simplicity
- A front-row seat (and a hand in building) the next chapter of finance
Work visa sponsorship is not provided for this role.
Safe return doubtful. Honour and recognition in case of success.
Build a standout application
For the Senior Data Engineer at Nansen, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.