Job Description
Year of Experience: 10 years in the OMS domain.
A thoroughly experienced OMS resource with preference to Blue Yonder OMS and good exposure in building custom microservices as extension points to OMS, possessing good cloud knowledge.
Extensive backend development knowledge with core Java/J2EE and Microservice based event driven architecture with a cloud based architecture (preferably AWS).
Should be cognizant of key integrations undertaken in eCommerce and associated downstream subsystems which should include but not limited to different Search frameworks, Payment gateways, Product Lifecycle Management Systems, Loyalty platforms, Recommendation engines, Promotion frameworks etc.
Recommend someone having a good knowledge of integrations with downstream eCommerce systems like OMS, Store Systems, ERP etc. Any additional knowledge on OMS and Store domains will be additional advantage.
Experience in Service Oriented Architecture - Developing/securely exposing/consuming Web Services RESTful and integrating headless applications.
Should be able to understand system end-end, maintain application and troubleshoot issues.
Good understanding of Data Structures and Entity models.
Should have understanding of building, deploying and maintaining server based as well as serverless applications on cloud, preferably AWS.
Expertise in integrating synchronously and asynchronously with third party web services.
Good to have concrete knowledge of AWS Lambda functions, API Gateway, AWS.
CloudWatch, SQS, SNS, Event bridge, Kinesis, Secret Manager, S3 storage, server architectural models etc.
Knowledge of any major eCommerce / OMS platforms will be of added advantage.
Must have a working knowledge of Production Application Support.
Good knowledge of Agile methodology, CI/CD pipelines, code repo and branching strategies preferably with GitHub or Bitbucket.
Good knowledge of observability tools like NewRelic, DataDog, Graphana, Splunk etc., with knowledge in configuring new reports, proactive alert settings, monitoring KPIs etc.
Should have a fairly good understanding of L3 support processes, roles and responsibilities.
Should work closely with counterparts in L1/L2 teams to monitor, analyze and expedite issue resolutions, reduce stereoptypes, automate SoPs or find avenues for the same by being proactive.
Should be flexible to work with overlap with some part of onsite (PST) hours as part of various client meetings with client leadership team.
