Python Developer (Backend, Kubernetes, Concourse)

Company: Computer Enterprises, Inc.
Location: Not Specified, Not Specified, United States
Type: Full-time
Posted: 30.APR.2021

Summary

*Only W-2 candidates will be considered* This is a long-term contract position that is funded through 2021 and is planned to be extended in...

Description

*Only W-2 candidates will be considered*

This is a long-term contract position that is funded through 2021 and is planned to be extended into 2022 as well. Manager intends to convert to FTE if possible.

Majority of the team sits across Denver & Philadelphia but this position can be remote. Schedule would be based around Mountain Time.

Pay range for this position would be $55-60/hr on W2.

  • Project:
    • This is a backend development role
      • This is not an operations or testing role or integration
      • Strong Python background with at least 3-5 years of python development
      • Has experience querying data (not necessarily a database person)
    • Tools team is responsible for creating all sorts of tools used for validating video pipeline and much much more
    • 70% development and 30% data analysis and breakdown
      • Some of the systems they are building they need to figure out how disparate info and what info is desired and how to aggregate data and queries needed for proper metrics
      • Building out backend systems and making it more robust
      • Would be working alongside their team lead
    • Skills:
      • Must have/preferred
        • Python with minimum of 3-5 years but more is always welcome
          • Python is an absolute must have
        • Kubernetes & Docker
        • How to query- SQL
      • Nice to have
        • Airflow- scheduler system similar to Hadoop but this is an open source project
        • concourse- CI/CD
        • Understanding of concourse automation and airflow
        • Some testing knowledge
    • Day to day:
      • Check in with the team
      • Running in a modified agile format
        • Keeps the team focused but it isn't heavily process driven
      • Open schedule thereafter- they have goals for the sprint that they are chipping away on
      • Code most of the day, code reviews and pull requests for teammates, take initiative on issues you see and sharing with the team what you saw and how it was fixed/updated
      • Understand data sets better and ow to suck into system to make it more robust
      • Once story is completed, checking in after it
- provided by Dice

 
Apply Now

Share

Flash-bkgn
Loader2 Processing ...