OMS Developer - eCommerce Domain

You should have at least 8 years of experience, with a minimum of 5 years in the eCommerce and/or OMS domain. Your knowledge should cover various Commerce subsystems such as Storefront, Core Commerce back end, Post Purchase processing, OMS, Store/Warehouse Management processes, Supply Chain, and Logistic processes. It is mandatory to have proficiency in at least two areas apart from eCommerce. Your expertise should include extensive backend development knowledge using core Java/J2EE and Microservice based event-driven architecture within a cloud-based architecture, preferably AWS. Knowledge of integrations with downstream eCommerce systems like OMS, Store Systems, ERP, and additional knowledge in OMS and Store domains will be advantageous. You should have experience in Service-Oriented Architecture, developing and securely exposing/consuming Web Services RESTful, and integrating headless applications. Understanding system end-to-end, maintaining applications, troubleshooting issues, and knowledge of Data Structures and Entity models are essential. Experience in building, deploying, and maintaining server-based as well as serverless applications on the cloud, preferably AWS, is required. Expertise in integrating synchronously and asynchronously with third-party web services is crucial. Concrete knowledge of AWS services like Lambda functions, API Gateway, CloudWatch, SQS, SNS, EventBridge, Kinesis, Secret Manager, S3 storage, and server architectural models is beneficial. Knowledge of major eCommerce/OMS platforms and Production Application Support is advantageous. Familiarity with Agile methodology, CI/CD pipelines, code repo, and branching strategies, preferably with GitHub or Bitbucket, is necessary. Good observability tools knowledge like NewRelic, DataDog, Graphana, Splunk, and configuring new reports, proactive alert settings, monitoring KPIs are essential. You should have a good understanding of L3 support processes, roles, and responsibilities, and work closely with L1/L2 teams. Being flexible to overlap with some part of onsite (PST) hours for handoff/transition work for the day with onsite counterparts for L3 support is required.,