CyberTec
They prefer local, that has its challenges, relo is an option, but they have to move quick............
Rate is 60.00 C2C max. No wiggle room.
Client- L-7 SWE
Ofallon, MO
1 year open ended
1 round interview-
*Must be on-site - 3 days/week- T, W, Th
*Interview process:
One interview
Organizational Overview
Reactive Systems Architecture allows Application Teams to focus on the functional business requirements, leaving the task of addressing various non-functional requirements to the underlying framework, platform components and infrastructure. The functional business logic layer deals in messages, the delivery of which is an event that invokes some processing on that message. Specific to Client / payment systems these are typically financial messages. The non-functional requirements include, but are not limited to, security, traffic management, infrastructure-independent deployment, scalability, resiliency, high availability, consistent message delivery, delivery auditing, message delivery for failed/absent consumers, application lifecycle management, live/silent mode testing, stateful stream processing, strong consistency, observability, root cause detection and recovery.
The Role: What's it all about and what we expect you to do day to day Own software delivery tasks (code development, test, deployment) at an application/software component level Able to troubleshoot and refactor existing code for exceptional code quality. Adopt new languages and architecture patterns needed for the work. Participate and contribute to team's agile process and decisions. Pull from backlog and deliver work after seeking guidance from experienced team members and in partnership with full scrum team. Understands the big picture and end-to-end logical architecture of systems in ownership areas Provide feedback and suggestions on areas to improve Understands the use of Client technology policies in everyday work Demonstrate active learning and sharing of software practices via Guild/Engineering community initiatives Influence the decisions made by the team. Assist peers and less experienced members. Influence the decisions made by the team. Assist in technical documentation of APIs and services being delivered. All About You and What you need to bring:
Working experience on messaging solutions and integration patterns such as Apache Kafka, NATS. Understands stateful stream processing concepts and knows basics of Apache Flink. Has ability to write secure code in three or more languages (e.g., Java, .NET, JavaScript, SQL) Familiar with secure coding standards (e.g., OWASP, CWE, SEI CERT) Infrastructure as code and cloud first software development knowledge experience preferred. Understands and implements standard branching (e.g., Gitflow) and peer review practices Apply tools (e.g., Sonar, Zally, Checkmarx ) and techniques to scan and measure code quality and anti-patterns as part of development activity Understands and builds test code at unit level, service level, and integration level to ensure code and functional coverage Understands the use of basic design patterns (e.g., factory, adaptor, singleton, composite, observer, strategy, inversion of control) Understands requirement analysis being essential part of delivering value to our customers and partners and participate in elaboration, prioritization, and effort estimation Understands agile and modern SDLC practices (Scrum/Kanban/Continuous Delivery/DevOps/Quality engineering) and the delivery situations they are used for Understands the basic engineering principles used in building and running mission critical software capabilities (security, customer experience, testing, operability, simplification, service-oriented architecture) Familiar with different application patterns to implement different types of business processes (e.g., APIs, event-driven-services, batch-services, web-applications, big data) Understands Continuous Integration (CI) and Delivery (CD) concepts, and capabilities to support automation, pipelines, virtualization, and containerization Has ability to write code (in languages such as Java, Python, Ruby, Bash, Perl, Groovy) to build automation tasks that are repeatable and efficient Understands functional and non-functional testing types to elaborate and estimate test efforts
Rate is 60.00 C2C max. No wiggle room.
Client- L-7 SWE
Ofallon, MO
1 year open ended
1 round interview-
*Must be on-site - 3 days/week- T, W, Th
*Interview process:
One interview
Organizational Overview
Reactive Systems Architecture allows Application Teams to focus on the functional business requirements, leaving the task of addressing various non-functional requirements to the underlying framework, platform components and infrastructure. The functional business logic layer deals in messages, the delivery of which is an event that invokes some processing on that message. Specific to Client / payment systems these are typically financial messages. The non-functional requirements include, but are not limited to, security, traffic management, infrastructure-independent deployment, scalability, resiliency, high availability, consistent message delivery, delivery auditing, message delivery for failed/absent consumers, application lifecycle management, live/silent mode testing, stateful stream processing, strong consistency, observability, root cause detection and recovery.
The Role: What's it all about and what we expect you to do day to day Own software delivery tasks (code development, test, deployment) at an application/software component level Able to troubleshoot and refactor existing code for exceptional code quality. Adopt new languages and architecture patterns needed for the work. Participate and contribute to team's agile process and decisions. Pull from backlog and deliver work after seeking guidance from experienced team members and in partnership with full scrum team. Understands the big picture and end-to-end logical architecture of systems in ownership areas Provide feedback and suggestions on areas to improve Understands the use of Client technology policies in everyday work Demonstrate active learning and sharing of software practices via Guild/Engineering community initiatives Influence the decisions made by the team. Assist peers and less experienced members. Influence the decisions made by the team. Assist in technical documentation of APIs and services being delivered. All About You and What you need to bring:
Working experience on messaging solutions and integration patterns such as Apache Kafka, NATS. Understands stateful stream processing concepts and knows basics of Apache Flink. Has ability to write secure code in three or more languages (e.g., Java, .NET, JavaScript, SQL) Familiar with secure coding standards (e.g., OWASP, CWE, SEI CERT) Infrastructure as code and cloud first software development knowledge experience preferred. Understands and implements standard branching (e.g., Gitflow) and peer review practices Apply tools (e.g., Sonar, Zally, Checkmarx ) and techniques to scan and measure code quality and anti-patterns as part of development activity Understands and builds test code at unit level, service level, and integration level to ensure code and functional coverage Understands the use of basic design patterns (e.g., factory, adaptor, singleton, composite, observer, strategy, inversion of control) Understands requirement analysis being essential part of delivering value to our customers and partners and participate in elaboration, prioritization, and effort estimation Understands agile and modern SDLC practices (Scrum/Kanban/Continuous Delivery/DevOps/Quality engineering) and the delivery situations they are used for Understands the basic engineering principles used in building and running mission critical software capabilities (security, customer experience, testing, operability, simplification, service-oriented architecture) Familiar with different application patterns to implement different types of business processes (e.g., APIs, event-driven-services, batch-services, web-applications, big data) Understands Continuous Integration (CI) and Delivery (CD) concepts, and capabilities to support automation, pipelines, virtualization, and containerization Has ability to write code (in languages such as Java, Python, Ruby, Bash, Perl, Groovy) to build automation tasks that are repeatable and efficient Understands functional and non-functional testing types to elaborate and estimate test efforts