Sr. Software Engineer

<< Back to all jobs

•   PRINT

Sr. Software Engineer (Rest API)

Remote Job |   2023-01-06 14:22:58

Apply Now

Share Job 

Job Code : 2023-MY3TECH0002

Sr. Software Engineer (Rest API)

Fully Remote (Must work for PST Zone)

12-month Contract with possibility to extension

Description:

We Transform Ideas into Software.

As a recognized leader for fast-paced software delivery, we have established a highly disciplined agile software development practice for API, and services development. Our approach is like what you might find in a modern start-up company, but with the resources of a Fortune 20 company.

We Can Go Fast Forever

We prefer pair program, all day, every day because we know it delivers remarkable results. We practice Extreme Programming in a KANBAN style agile team, an approach to software engineering that applies across industries and organizations, using the latest technologies. And we believe in working at a sustainable pace ? you’ll typically code hard for 8 hours each day, but then you’re off work to relax, recharge and refocus.

We Court Perfection

Working as part of the Digital Services team means you get better at what you already do well. We set up regular retrospectives to figure out what we’re doing wrong so we can fix it, and what we’re doing right so we can improve on it. We practice Test Driven Development, which results in high-quality, reliable, and more maintainable code. We believe that methodical, steady, relentless forward momentum drives consistent results.

What Project/Projects will the candidate be working on while on assignment?

New work will include creation of new RESTful APIs that are extensible and consumable across our enterprise. We are also in the process of moving our applications into the cloud. It will include best practices from the industry as well as internal API certification requirements for the best breed of sustainable service portfolios including decoupling techniques, versioning, performance testing as well as security implementations.

Insurance Solutions ACES Team. Enterprise highly available services is at the heart of this team. The team is small, 8-10 members.

Top 5-10 Responsibilities:

• Java development on a daily basis
• Influence high-level solution design and detailed design
• Identify ways to improve and evolve our Agile delivery practice
• Collaborate with Architect, Product Owner, QA members and peers.
• Participate in daily team stand ups
• Level 2 support for production services

What software tools/skills are needed to perform these daily responsibilities?

• IntelliJ IDEA
• HCC Kubernetes utilizing Google Anthos
• git
• Maven
• Jenkins
• Spring
• WebSphere Application Server, JBoss, Tomcat
• RESTful API principles and design
• DevOps
• Bash scripting
• Database modeling and scripting

What skills/attributes are a must have?

• 8+ years of Java development experience developing complicated business functionality
• Strong knowledge of programming and software engineering; Object Oriented Design Principles.
• Strong knowledge of API Design and Implementation for REST Services
• Strong Java development. Java 1.8+
• Experience with common Java frameworks; Spring, Hibernate, Spring Boot, etc.
• Experience with cloud platforms like Kubernetes.

What skills/attributes are nice to have?

• Experience in Test Driven Development and Pair Programming practices
• Experience with Service Oriented Design Patterns
• Experience with Enterprise Application container (e.g., WebSphere, JBoss)
• Experience with Security frameworks (e.g., JWT, OATH2)
• Experience with Integration frameworks (e.g., Mule, Camel)
• Experience with Enterprise Integration Patterns

What does the interview process look like?

a. How many rounds? 1 interview time slot for approximately 2 hours broken into 2 technical discussions of 45 minutes in length each and one 30 minutes.

b. Video vs. phone? Camera must be on. Using Zoom or TEAMS is acceptable

c. How technical will the interviews be? In depth knowledge of the various required technologies will be assessed. Applicants should be prepared to answer how they approach a solution and then code and test for it. They will also be asked to define why to detail why they chose a particular path for solutioning.