Senior Java backend EngineerFull-timeLegal Entity: Bosch Global Software Technologies Private LimitedCompany DescriptionBosch Global Software Technologies Private Limitedis a 100% owned subsidiary of Robert Bosch GmbH, one of the world's leading global supplier of technology and services, offering end-to-end Engineering, IT and Business Solutions. With over 27,000+ associates, it’s the largest software development center of Bosch, outside Germany, indicating that it is the Technology Powerhouse of Bosch in India with a global footprint and presence in the US, Europe and the Asia Pacific region.Job DescriptionRoles & Responsibilities:Backend Developer ProfileCore Tech StackLanguages & FrameworksJava 11–25 (LTS focus: 11, 17, 21), modern language features (records, sealed classes, pattern matching, virtual threads)Spring Boot 3–4 (Spring Framework 6+, native compilation awareness a plus)Quarkus 1–2 (CDI, Panache, native image builds)Data & MessagingPostgreSQL (schema design, indexing, query optimization, migrations via Liquibase/Flyway)Kafka (producers/consumers, partitioning strategy, exactly-once semantics, schema registry/Avro or Protobuf)Elasticsearch (indexing strategy, query DSL, aggregations)Redis (caching patterns, TTL strategy, pub/sub, distributed locks)APIs & IntegrationREST (resource design, versioning, OpenAPI/contract-first)gRPC (protobuf contracts, streaming)GraphQL (schema design, resolver performance, N+1 avoidance)ArchitectureMicroservices (service boundaries, decoupling patterns, anti-corruption layers)Event-driven architecture (choreography vs. orchestration, eventual consistency, outbox pattern)12-factor app principles as a baseline design disciplinePlatform, Containers & DeliveryAzure DevOps (pipelines as code, release management, boards)Docker (writing/reading Dockerfiles, image optimization)Kubernetes (pods, services, ConfigMaps/Secrets, HPA, resource limits)Helm charts and GitOps-based deployment (ArgoCD)Testing & Quality GatesJUnit 5, Mockito, TestcontainersContract testing (Pact), static analysis (SonarQube/Checkstyle)Chaos/resilience testing awarenessObservability & ReliabilityStructured logging, distributed tracing (OpenTelemetry/Jaeger)Metrics, dashboards, SLO/SLI-based alertingResilience patterns: circuit breakers/bulkheads (Resilience4j), rate limitingSecurityOWASP Top 10, secure coding practicesSecrets management (Key Vault/External Secrets Operator)OAuth2/OIDC, service-to-service auth, dependency vulnerability scanning (Trivy/Snyk)Modern Engineering PracticesEffective, critical use of AI coding assistants (code generation, review, test/doc generation) without over-trusting outputExpectations:Designs service boundaries and evaluates microservice vs. modular monolith trade-offs for new capabilitiesLeads event-driven design decisions: schema evolution strategy, backward/forward compatibility, dead-letter handling, idempotencyMakes and documents architecture decisions (ADRs) with awareness of long-term maintenance costOwns performance: query optimization, caching strategy (Redis), connection pool tuning, JVM tuning basicsDesigns Helm charts and GitOps-based deployment pipelines (ArgoCD); understands HPA and resource planning at scaleDrives quality gates: static analysis (SonarQube/Checkstyle), contract testing (Pact), mutation testing where appropriate; owns test pyramid strategy for the teamDesigns for observability from day one: sets SLOs/SLIs, structured logging, distributed tracing, cost-aware alerting — not bolted on after an incidentApplies resilience patterns proactively (circuit breakers, bulkheads, rate limiting) rather than reactively after outagesUnderstands security deeply: threat modeling, dependency vulnerability management, least-privilege service accounts, zero-trust service-to-service authComfortable operating across Spring BootandQuarkus, and can make a reasoned recommendation for which fits a given serviceCan lead incident response: root cause analysis, blameless postmortems, follow-through on remediationMentors medior/junior developers through pairing and code review, not just gatekeepingEvaluates where AI-assisted tooling (code review, test generation, documentation) genuinely improves team velocity vs. where it introduces riskBalances pragmatism vs. purism — knows when "clean" should yield to "shipped," and can defend that callQuality mindset markersTreats clean architecture as a tool for change, not a religion — pushes back when it's used to over-engineerActively reduces coupling across the ~100-service scale, not just within their own serviceChampions quality gates and test strategy for the team, not just their own PRsQualificationsEducational qualification:Bachelor of Engineering in any of the below mentioned.Computer Science (CSE)Information Technology (IT)Electronics & Communications Engineering (ECE)Information Science / Software EngineeringExperience :8+ years, with demonstrable ownership of non-trivial systemsMandatory/requires Skills :Preferred Skills :high level of collaboration with the stake holdersbetter communication skillsBy clicking the link above or any third-party link within this posting, you are leaving this site and going to a third-party website where the third-party website's terms and privacy policy applyI'm interestedI'm interestedPrivacy NoticeImprint
About Bosch Group
