Senior Software Engineer

About Us:

We looked at the enterprise data world and said: This is broken.

The biggest companies on Earth are drowning in data complexity. They're trapped between legacy systems that can't scale and cloud platforms that want to own their data. They're bleeding money on infrastructure while their teams struggle with tools that weren't built for their reality.

We built IOMETE to fix this. A sovereign-by-design lakehouse that gives enterprises back control of their data. Where AI optimization actually makes queries faster in the real world, not just in benchmarks. Where Data Mesh isn't just buzzword compliance, but a fundamental architecture. Fortune 500 companies run petabyte-scale data lakehouses on IOMETE.

Job Summary:

We need a Senior Software Engineer who gets it. Who understands that great engineering isn't about perfect code in isolation – it's about solving real problems for real customers at real scale.

You'll work across our entire platform. Backend services, APIs, infrastructure, user experience. You'll sit with customer teams, understand their pain, and build solutions that actually work in their world. Not theoretical solutions. Not "it works on my machine" solutions. Solutions that handle petabytes, thousands of users, and the messy reality of enterprise data.

Position overview:

We are seeking a highly skilled and motivated Senior Software Engineer to join our team. We tackle a variety of exciting challenges, from building microservices to developing database engines. This role requires expertise in our primary tech stack, which includes Kotlin, Java/Scala, Python and Go.

What You'll Do:

• Build the core infrastructure that powers IOMETE – Kotlin, Python, Golang services that have to work at massive scale, in hybrid environments, with zero room for "good enough"

• Get deep into Kubernetes – not just using it, but extending it. CRDs, webhooks, control-plane components that make on-site Spark workloads actually reliable

• Work directly with enterprise engineering teams. Not through tickets. Not through PMs. Directly. Understand their problems, debug their issues, guide their integrations

• Shape the architecture of distributed compute, query planning, data storage – but always with one question: Does this solve the customer's actual problem?

We are Looking For:

• Someone who's tired of building features that look good in demos but fail in production. Who wants to work on problems that matter.

• 5-7+ years building and operating systems end-to-end. (Got less experience but can show us you've built something real that scaled? We'll talk.)

• You've built production data workflows. Real ones. ETL pipelines that don't fall over when they hit messy data. Systems that handle failure gracefully

• You know modern data platforms – Snowflake, Databricks, whatever. But more importantly, you know where they fail enterprises

• Fluent in at least two languages (Kotlin, Java, Golang, Python, Rust). But you pick tools based on the problem, not your resume

• You can translate between "my Spark job is slow" and the actual architectural issue. You speak human and system

• You make architecture decisions thinking about next year, not next sprint. But you ship this sprint

• Your English is clear, your docs are readable, and you can explain complex problems without hiding behind jargon

• You take ownership. Not "that's not my component" ownership. Real ownership.

What We Offer:

• Work on technology that's actually changing how enterprises handle data. Not incrementally. Fundamentally.

• Shape a young engineering org's architecture, culture, and future. Your decisions will matter for years

• Solve problems alongside teams at the world's largest companies. Real scale. Real complexity. Real impact.

• Competitive compensation and meaningful equity. We're building something big.

• Full-time contract role. No bureaucracy. Just impact.

Compensation:

$60k - $100k annually, depending on what you bring to the table.

Ready to build something that matters? Show us what you've built. Tell us what broke. Explain how you fixed it. We care more about your battle scars than your certificates.