REMOTEFULLTIME
Senior Software Engineer
Iomete
Remote · remote · Posted 70d ago
Sourced from
Undisclosed5–7 yrsfulltimeRemote
About a minute. You'll make an account on the way through.
agent · working
- Read this posting0.2s
- Found the form on Naukri · 12 questions to answer1.5s
- Decided the answers for all of them3.2s
- Tailor your résumé to this role
- Waiting for you
Section · 01
About this role
Job Summary
Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.
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.
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
- 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
- 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.
Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.
Sourced from naukri
Section · 02
Skills
Software EngineerKubernetesApache SparkScalaRustworkflowsPMSdata platformsdata storageintegrationsGolangKotlinDebugwebhookDatabricksPythonOperating SystemsJavaArchitectureMicroservicesETL PipelinesSnowflakeETL