2

Remote Separator Operator Jobs in Silver Spring, MD

next page

Showing results 1-20

Remote Separator Operator information

What is the difference between Remote Separator Operator vs Remote Material Handler?

AspectRemote Separator OperatorRemote Material Handler
CredentialsTypically requires technical certifications or training in separation processesUsually requires general warehouse or logistics certifications
Work EnvironmentOperates specialized equipment in industrial or manufacturing settings, often remotely monitoring systemsWorks in warehouses or distribution centers, handling physical materials
Industry UsageCommon in manufacturing, recycling, or chemical industriesCommon in logistics, shipping, and warehousing sectors
Search/Comparison IntentOften compared for technical skills and remote operation capabilitiesCompared for physical handling and logistics roles

The Remote Separator Operator primarily focuses on remotely managing equipment to separate materials in industrial settings, requiring technical certifications. In contrast, the Remote Material Handler deals with physically moving and organizing materials in warehouses. Both roles may be remote but serve different industry needs and skill sets.

What are popular job titles related to Remote Separator Operator jobs in Silver Spring, MD? For Remote Separator Operator jobs in Silver Spring, MD, the most frequently searched job titles are:
What job categories do people searching Remote Separator Operator jobs in Silver Spring, MD look for? The top searched job categories for Remote Separator Operator jobs in Silver Spring, MD are:
Senior DevSecOps / AWS Cloud Engineer

Senior DevSecOps / AWS Cloud Engineer

GAMA-1 Technologies

Greenbelt, MD • On-site, Remote

$115K - $159K/yr

Full-time

Medical, Life, Retirement, PTO

Posted 11 days ago


Job description

Role summary
We 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.