Senior Software Engineer; Rustici US, Franklin, Remote

We are looking for a Senior Software Engineer to join our team. Rustici Software makes eLearning standards based software which is responsible for launching and tracking standards based online learning for millions of learners. You would join a team that develops software that integrates into other software products around the world. We are a remote/in-office hybrid company whose headquarters is located in Franklin, TN.

While we give consideration to local candidates, we are open to qualified remote candidates residing in the United States.

The ideal candidate will be able to balance the competing priorities of producing quality code and solving customer problems quickly. We are not hung up on a particular amount or type of experience, but we are adamant about a particular level of skill and aptitude. The areas of expertise we value are in software development, communication, and learning new technologies. Experience in specific languages is not crucial, but we look for developers that can code in more than one language and/or are familiar with more than one framework.

We primarily use Type Script for front end web development and Java or Python for back end web service development, but there is no guarantee we’ll use those languages for our next project.

US based only, direct hire only, no recruiters, no contracting agencies, please.

• Java or Python
• JavaScript/Type Script particularly Vue
• SQL (MySQL, Postgres, SQL Server)
• Git/Git Hub, Docker
• AWS

Our Senior Software Engineers work as full stack web developers on a team that maintains and improves one or more of Rustici’s software products. Senior Software Engineers are individual contributors reporting to an Engineering Manager

• Maintaining existing codebases
  :
  One or more software products and all of the ancillary tools needed to manage them. These are profitable products that have been around for 10+ years (and we expect to be around for 10+ more) and that our customers expect to work as well or better than they did last year or the year before or the year before that.
  
  There is technical debt to be paid, refinement to interfaces and implementations, bugs to squash, and processes to improve. QA is a forethought and a requirement, developing test code is just part of the work.
• Writing technical specifications for new work
  :
  Anytime we embark on larger features, we build out a technical specification, with the goal of expressing the work in English before we attempt to express it in code. We write technical specifications for the larger work we do.
• Taking new features from start to finish
  :
  We really value autonomy here ineers pick up work that needs to be done and run with it until it has passed code reviews and QA.
• Identifying new work
  :
  We rely a lot on customer feedback for improvements and new features, but we also don’t expect all the answers to come from the top down, and will look to our engineers for ideas on what to work on next.
• Weekly standups
  :
  We try to keep meetings at a minimum. Each team meets once a week to discuss the work that happened last week, and what they expect to accomplish in the coming week. Most teams also have a longer form meeting to dive deep into technical items impacting the team as a whole.
• Mentoring
  :
  We feel one of the best ways to enhance our teams overall and individually is for our more experienced developers to pass along their techniques, how they’ve honed their craft, and what successes and failures they’ve experienced in their career to more junior developers.
• Learn Everyday
  :
  We believe in continuous improvement whether that is at a product level or a personal one. Engineers should be improving their craft, whether that is via new technical skills or tools, diving deep into an existing ability, or learning more about how the business operates.

Successful candidates have a mix of skills in the technology space including programming in various languages, using various frameworks, and having a general familiarity with the components of a mature software development life cycle. We look for the following, but if you don’t have experience with all of the following…