Java Developer in Richfield, MN at APEX Systems

Date Posted: 7/2/2018

Job Snapshot

Job Description

Job #:  863765

Title: IT - Developer (Specialty) IV

Duration: Projected through 1/16/19

Work Location: Richfield, MN

 

Business Overview:   

Position Overview:

 

What would a normal day for this position look like??

80% of the time actually doing the development and dev ops work

The remainder of the day is iteration planning, retrospectives, product demos and design sessions

 

Skills Overview:

What are the MUST have skills and technologies that you are looking for in a candidate?

Required Experience
Must have 10+ years of relevant systems software engineering experience
BS/MS in computer science or engineering (or equivalent professional experience)
Experience with large-scale distributed systems and web oriented architectures
Developing Spring/Java applications
Aggressive Refactoring
Service Oriented Architecture design

Experience with API’s

Preferred Experience
Experience in the use of Groovy and/or React/Javascript/Node

Experience in the use of containers for deployment (e.g. Docker, Rocket)

Experience as a Technical Lead or Lead Developer on a complex distributed systems project
Experience with cloud computing platforms (e.g. GCP, AWS, Azure, etc.)

Experience with JSON/RESTful services and best practices therein

Experience with Container Orchestration (Kubernetes, Mesosphere, etc.)

Pair Programming (Social skills)
Test Driven Development (TDD)
Experience with testing frameworks (JUnit and Spock in particular)

Experience and/or understanding of IoT

 

What are the soft skills that you feel candidates must-have in order to be successful in this role?

  • Social Skills
  • Communication
  • Sense of humor

 

Will there be testing required for this role? If so, what test would you like administered & who would you like to administer?

Interview will include a code sample and question/answer.

 

Prescreening Questions:

Must be submitted on resume, no exceptions!

  1. Based on your experience, what is your most- and least-favorite thing about pair programming?
  2. How much pairing would you do in a typical day of your ideal job?
  3. Is simplicity a feature of a system?
  4. How do you deal with ambiguous requirements?
  5. How often do you refactor?  
  6. How do you approach technical debt and what are some plans you’ve made to deal with it?
  7. What are the keys to successful Dev Ops environment?

 

Interview Process Overview:

 

45 minute phone interview with HackerRank followed by 90 minute in person panel interview