Senior Java Backend Developer
Hybrid @ Dayton, OH
Long Term
Contract
(Java 17 + ADX/KQL + Event Hub + Search/Retrieval APIs)
Java backend / event-driven processing
• Implement Event Hub consumption patterns: consumer groups, partition awareness, batching, checkpointing strategy, retries/DLQ, idempotency.
• Design and tune thread pools and scheduled work (e.g., backfills/replays/retries) with safe operational controls.
• Build robust JSON parsing/validation, schema evolution handling, and error routing
ADX (Azure Data Explorer) + query performance
• Write KQL queries for search/filter use cases and operational diagnostics.
• Profile and tune ADX queries (query plan/diagnostics), reducing p95 latency and cost for hot queries.
• Create clear query patterns and guardrails (parameterization, paging strategy, consistent query shapes).
API design: Search vs Retrieval
• Define clean API contracts for search results: returned fields, filters, pagination semantics, error handling.
• Implement retrieval “views” carefully (versioned, testable, limited scope) to avoid a server-side dumping ground.
• Apply JWT authentication patterns and integrate with internal auth requirements.
Deployment literacy (not SRE, but must be self-sufficient)
• Make safe updates to Helm chart values.
• Use ArgoCD workflows to deploy and understand diffs/sync/rollback.
• Troubleshoot common AKS runtime issues: CrashLoopBackOff, OOMKilled, probe failures, CPU throttling, config/secrets/Managed Identity failures.
Testing + performance testing
• Write strong unit tests (JUnit; mock only boundaries) and integration tests against key dependencies (ADX/ADLS/Event Hub) or realistic test doubles.
• Create repeatable performance tests and publish results/thresholds.
________________________________________
Required qualifications (must-have)
• Senior-level experience shipping and operating production backend services.
• Java 17: concurrency/thread pools, scheduled work, resilience patterns, profiling (CPU/GC/threading).
• Event-driven systems (Event Hub/Kafka equivalents): idempotency, retries/DLQ, replay/backfill safety.
• ADX / KQL: proven ability to write and tune/profile queries (not just run them).
• API design: production experience building search/filter endpoints and retrieval endpoints with stable contracts.
• AKS/Kubernetes literacy: can deploy and debug your service (pods, logs, resources, probes, HPA basics).
• Security basics: JWT validation/claims awareness; practical Managed Identity understanding for accessing Azure services.
• Demonstrated history of becoming the “go-to” engineer/SME for a service or subsystem.
• Proven ability to drive initiatives: propose roadmap items, shape scope, and deliver with minimal oversight.
• Strong written communication: can produce clear design notes/runbooks and explain complex issues to other teams.
________________________________________
Preferred qualifications (nice-to-have)
• Direct hands-on experience with Azure Event Hubs, ADLS Gen2, AKS, and ADX in the same system.
• HashiCorp Vault and/or Akeyless integrations and secret management patterns.
• Helm chart authoring (not just values editing) and ArgoCD operational experience.
• API “views” / projection patterns, versioning strategies, and backward compatibility discipline.
• Broader “search architecture” experience (facets/filter UX, result shaping, pagination edge cases, indexing strategy).
• Observability maturity
________________________________________
“Platform literate” definition (what we mean)
You are not expected to be SRE, but you are expected to:
• Diagnose: restart loops, OOMs, CPU throttling, misconfigured probes, bad config rollouts.
• Adjust: Helm values for resources/config safely and validate via ArgoCD.
• Identify: when it’s a service issue vs a cluster/network/identity policy issue and escalate with crisp evidence.
Munesh
770-838-3829,
CYBER SPHERE LLC
