2

Backend Node Js Remote Jobs in Baltimore, MD (NOW HIRING)

next page

Showing results 1-20

Backend Node Js Remote information

See Baltimore, MD salary details

$11

$57

$83

How much do backend node js remote jobs pay per hour?

As of Jul 14, 2026, the average hourly pay for backend node js remote in Baltimore, MD is $57.37, according to ZipRecruiter salary data. Most workers in this role earn between $47.07 and $67.84 per hour, depending on experience, location, and employer.

How does a remote Backend Node.js developer typically collaborate with front-end teams and other stakeholders?

As a remote Backend Node.js developer, collaboration with front-end teams and other stakeholders is primarily facilitated through tools like Slack, Jira, and GitHub. Regular stand-ups, sprint planning meetings, and code reviews ensure alignment on project goals and deliverables. Clear documentation, API contracts, and frequent communication are essential to bridge the distance and prevent misunderstandings. Developers are also encouraged to participate in cross-functional team discussions to address technical challenges and provide backend insights that support overall product development.

What are the key skills and qualifications needed to thrive as a Backend Node.js Developer (Remote), and why are they important?

To thrive as a Backend Node.js Developer (Remote), you need strong proficiency in JavaScript (especially Node.js), understanding of backend frameworks, experience with RESTful APIs, and typically a degree in computer science or related field. Familiarity with databases (like MongoDB or PostgreSQL), cloud platforms (such as AWS or Azure), version control systems (Git), and knowledge of containerization tools (like Docker) are commonly required. Excellent problem-solving, communication, and time-management skills are crucial for remote collaboration and efficient project delivery. These skills and qualifications ensure robust backend development, seamless teamwork across distributed teams, and the ability to deliver scalable, reliable software solutions.

What is a Backend Node.js remote developer?

A Backend Node.js remote developer is a software engineer who specializes in building and maintaining the server-side logic of web applications using Node.js, and works remotely rather than in a traditional office setting. Their responsibilities include designing APIs, managing databases, ensuring application performance, and integrating with front-end technologies. Working remotely, they collaborate with team members using online tools and platforms to deliver high-quality backend solutions.

What is the difference between Backend Node Js Remote vs Backend Java Remote?

AspectBackend Node Js RemoteBackend Java Remote
Required CredentialsBachelor's in CS or related, Node.js certificationsBachelor's in CS or related, Java certifications
Work EnvironmentRemote, collaborative teams, Agile workflowsRemote, enterprise-focused, Agile or Scrum
Industry UsageTech startups, SaaS companies, startupsFinancial, healthcare, large enterprise sectors
Search & Comparison IntentCommonly compared for backend roles requiring JavaScriptOften compared for enterprise backend development

Backend Node Js Remote and Backend Java Remote are both backend development roles that can be performed remotely. Node.js roles typically focus on JavaScript-based development suitable for startups and tech companies, while Java roles are more common in large enterprises and industries like finance and healthcare. Both require relevant programming skills and certifications, but differ mainly in programming language and industry focus.

What are popular job titles related to Backend Node Js Remote jobs in Baltimore, MD? For Backend Node Js Remote jobs in Baltimore, MD, the most frequently searched job titles are:
Senior DevSecOps / AWS Cloud Engineer

Senior DevSecOps / AWS Cloud Engineer

GAMA-1 Technologies

Greenbelt, MD • Remote

$117K - $160K/yr

Full-time

Medical, Life, Retirement, PTO

Posted 21 days ago


Job description

Role summaryWe are seeking a remote Senior DevSecOps Engineer to own and evolve the platform — Terraform, EKS, GitLab CI/CD security gates, GitOps delivery, observability, and FISMA controls — and set the engineering standard for the team. You are the person who catches a backend block in the wrong module before it merges, and who makes the security gate something developers trust rather than route around.What you’ll do
  • Own the Terraform estate across the three repos and the 2-stack-perenv layout — directory-per-env roots, semver-pinned module consumption, a provider-pinning contract (version ranges in modules, locked in roots), S3 state with native locking, and OIDC (no static keys).
  • Lead state-safe refactors — split the monolith, fold sandbox stacks into the data stack using moved blocks / state mv, with backed-up state and zero-destroy plans on stateful resources (Aurora, Redis).
  • Build and operate EKS (toward Auto Mode), GitLab CI (runner-onEKS), and Argo CD GitOps — Helm, image signing, Kyverno admission, OPA policy decisions.
  • Harden the CI/CD security gate: container/filesystem scanning (Trivy), secret detection (Gitleaks), SBOM + signing, policy-as-code deny-gates, and ECR scan-on-push — wired so a failing gate blocks the merge.
  • Stand up the AWS-native observability stack (CloudWatch /
Container Insights, AMP, X-Ray/ADOT, Managed Grafana, Application Signals) with SLOs, alarms-as-code, and a dead-man’s-switch on the alerting path itself.
Drive the private-network migration (TGW egress, VPC endpoints, no NAT/IGW) and close FISMA gaps (CloudTrail/Config, Security Hub NIST 800-53, KMS where required, audit-account separation).
  • Review teammates’ IaC and set the standards.
Must-haves
  • Terraform at scale — root vs. child modules, state isolation, for_each/count/dynamic, drift, provider-pin conflicts, and state migration (moved/state mv) without destroying data. Writes modules others reuse. Can explain why workspaces ≠ directory-per-env.
  • Strong AWS cloud engineering — VPC/networking (private subnets, endpoints, TGW), IAM/OIDC, EKS, ECR, ALB/API-GW, and when SSE-S3 vs. KMS-CMK is actually required.
  • EKS you have operated, not just used — node/pod networking, IRSA, admission control, upgrades, troubleshooting a broken rollout.
  • CI/CD security (the “Sec” in DevSecOps)
SAST/dependency/container scanning, secret scanning, supply-chain (SBOM, signing), policy-as-code, secrets hygiene. You have made a pipeline block on a finding.
  • Federal compliance fluency — NIST 800-53 / FISMA-Moderate; can map a control family (AU, CM, SC) to an actual implementation.
  • Writes clear PRs and reviews others’ code constructively.
Strongly preferred
  • Observability depth (OpenTelemetry, Prometheus/Grafana, SLO/errorbudget design).
  • Prior regulated/federal environment (NOAA/DoD/civilian agency, ATO process), clearance or Public-Trust history.
  • GitLab CI specifically, Argo CD, and Kubernetes runners.

GAMA-1 also offers a variety of benefits, including health insurance coverage, life and disability insurance, 401(k) savings plan, training and career development opportunities, paid holidays and paid time off (PTO - to cover vacation, illness or disability, appointments, emergencies or other situations that require time off from work). For more information click here.

ABOUT GAMA-1

GAMA-1 is a rapidly growing technology business that is based in Greenbelt, Maryland. GAMA-1 Technologies provides strategic information assurance, information security, and business enterprise and networking solutions to the Federal Government. Our success is based on the utilization of industry and agency standards, establishment of standardized processes, and IT Services expertise. At GAMA-1, we believe employees should grow, achieve, and develop just as the company grows, achieves, and develops. GAMA-1 is committed to providing our employees with opportunities for career advancement throughout their employment. For more information, visit www.gama1tech.com

GAMA-1 is an Equal Opportunity Employer and all qualified applicants will receive consideration for employment without regard to: veteran status, uniformed servicemember status, race, color, religion, sex, sexual orientation, gender identity, age, pregnancy (including childbirth, lactation and related medical conditions), national origin or ancestry, citizenship or immigration status, physical or mental disability, genetic information (including testing and characteristics), domestic violence victims, political orientation, status as a smoker or tobacco user, hairstyle, use of a service animal, education status, familial status, HIV/AIDS status, height, weight, reproductive healthcare decisions or any other category protected by federal, state or local law.