1

Telecommute Python Django Backend Developer Jobs in Maryland

What You'll Be Doing (We don't love the bullet points, but we love the work!) As the Back End ... Recent Python (3.x) software development experience * Experience with Rust programming concepts, or ...

Showing results 41-60

Telecommute Python Django Backend Developer information

What are the most commonly searched types of Python Django Backend Developer jobs in Maryland?

The most popular types of Python Django Backend Developer jobs in Maryland are:

What job categories do people searching Telecommute Python Django Backend Developer jobs in Maryland look for?

The top searched job categories for Telecommute Python Django Backend Developer jobs in Maryland are:

What cities in Maryland are hiring for Telecommute Python Django Backend Developer jobs?

Cities in Maryland with the most Telecommute Python Django Backend Developer job openings:

Back End Developer

Rockville, MD • On-site

KMM Technologies, Inc.
11 - 50 employees

Other

This job post has expired today. Applications are no longer accepted.


Job description

RQ00203 - Senior Backend Engineer at Rockville, MD-3 days onsite and F2F is a Must


Required Qualifications:

· Bachelor’s degree in computer science, Information Technology, Engineering, or related technical field

· 8+ years of professional software engineering experience with demonstrated leadership capabilities

· 3+ years of hands-on development experience in Java, JavaScript/TypeScript, or SQL

· 2+ years developing REST/web services and writing complex SQL queries for relational databases

· 3+ years working with big data technologies such as Hadoop, Spark, or Presto

· Proven experience with AWS services including EMR (Hive/Presto), ECS, Lambda, and S3

· Proficiency with DevOps practices and CI/CD pipelines using tools like Jenkins and CloudFormation

· Working knowledge of scripting languages including Unix Shell or Python

· Experience using LLM-based coding tools with a disciplined approach to validating output — you don't merge what you can't explain