🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
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 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 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.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.