Vacancy expired!
Calling all Java and Python engineers for York's new hiring intiative! Our Fortune 10 client is building out a new team for a re-platforming project! This project will involve both Java & Python software engineers. Look no further if you are looking for something new and would love to work with an enterprise company on an exciting new team! This is an opportunity to solidify experience in a true full stack environment and is also a GREAT opportunity for growth.
Logistics:- Yes Remote!- IV blocks EVERYDAY (Will have a 30 minute screen solely around communication collaboration. No coding).- Working under a fabulous leader who was recently promoted- Opportunity to participate in an 'Innovation Week'CULTURE:- Collaboration- Process oriented - If unsure or unclear speak up!- Share your innovative ideas; dont hold them close.TECHNOLOGY ENVIRONMENT/ WHAT YOU WILL LEARN:At the core adding new contract sources to the existing Python app. Re-platform, modernizing of data, adding (2) new contracts systems, Openshift to Kubernetes Anthos (Anthos: state-of-the-art container management platform based on Kubernetes), upgrading Python.- Python - Most Important- Mostly backend- If Java - ideally would like some Angular on Front-end- Python vs. 3.0 +Why Python?- All ingestion runs on a Linux box written in Python- All interaction with contract systems and storage of documents is in Python- Runs on a schedule, once a week, to pull contracts from these sources- Not a large amount of Java that will be re-written; the structure is already there in ElasticSearch.- OOP in Python (NOT scripting)- Python does run Pandas library, but it is nothing groundbreaking in Panda.- ElasticSearch for Metadata- Java (queries are not going anywhere)- Python specific search packages- ETL structured- Unit Testing- Simply know how to set up unit tests (NO regression or integration testing)- Junit for Java- Pytest for Python - Devops- As part of the move from Openshift to Kubernetes, will need to update those piplelines. Several existing templates due to having done this with other services previously. Will NOT have to write from scratch but need understanding of Jenkins and devops pipelines.- S3 for storage- API- Microservice less heavy, NOT 12 services doing different things, but rather more paired down- 1 service doing ingestion on Linux box- 1 API in a large dashboard running for logging and retrieving ElasticSearch- NO ActiveMQ or ServiceBus needed- NoSQL Database- NoSQL is what ElasticSearch runs on (if no experience with NoSQL, need Kubenetes)- User InterfaceMUST HAVE:For Python:- Python vs. 3.0 + (theyll upgrade from 2.7 to 3.7)- OOP in Python (NOT Scripting) Python runs on a Pandas library- Mostly backend- ElasticSearch- Kubernetes Understanding!- Common commands- What is and Why Kubernetes containers- Kubernetes understanding would lead to Cloud understanding (can be on-prem or public their platform is hosted on their own Healthcare Cloud, on-prem)- API- Microservice (only 1 microservice in their API layer, not multiple services)- ETL- Unit Testing- Devops Understanding what are Jenkins/ devops pipelines?- NoSQL DB (ElasticSearch runs on NoSQL)Note: If do not have NoSQL/ ElasticSearch, need Kubernetes- Linux their Python runs on Linux NICE TO HAVE: Anthos, GKEFor Java:-Java/ Springboot- Python somewhere in background would eventually move to more Python- 80% backend / 20% front-end- Angular on front-end (10-20%)- OOP- Kubernetes Understanding!- Common commands- What is and Why Kubernetes containers- Kubernetes understanding would lead to Cloud understanding (can be on-prem or public their platform is hosted on their own Healthcare Cloud, on-prem)- API- Microservice (only 1 microservice in their API layer, not multiple services)- Unit Testing- Devops Understanding what are Jenkins/ devops pipelines- NoSQL DBIf interested, simply apply on this site or send your resume directly to myself!Vacancy expired!