ZipRecruiter

Log In

1

Batch Record Review Jobs in Remote, OR (NOW HIRING)

Logging-in

Principal Cloud Engineer

OR · Remote

$55 - $60/hr

Architecture decision records (ADRs). * Reference architectures and "golden paths". * Patterns ... Provide technical leadership during delivery: unblock teams, review PRs, guide implementation ...

New

All JobsBatch Record Review JobsBatch Record Review Jobs in Remote, OR

Batch Record Review information

See Remote, OR salary details

$12

$20

$33

How much do batch record review jobs pay per hour?

As of Aug 29, 2026, the average hourly pay for batch record review in Remote, OR is $20.32, according to ZipRecruiter salary data. Most workers in this role earn between $17.31 and $21.15 per hour, depending on experience, location, and employer.

What is a batch record reviewer?

A Batch Record Reviewer is a quality assurance professional responsible for reviewing and verifying production batch records in pharmaceutical or manufacturing environments. Their main role is to ensure that all documentation related to the production of each batch complies with regulatory standards and company procedures. This includes checking for accuracy, completeness, and compliance with Good Manufacturing Practices (GMP). By doing so, they help maintain product quality and safety before products are released to the market.

What skills and qualifications are needed to be a batch record reviewer?

To thrive as a Batch Record Reviewer, you need strong attention to detail, knowledge of Good Manufacturing Practices (GMP), and experience in pharmaceutical or biotechnology documentation, often supported by a degree in life sciences or related fields. Familiarity with electronic document management systems (EDMS), quality management software, and regulatory compliance tools is typically required. Excellent analytical skills, organization, and effective communication are standout soft skills for this role. These abilities ensure the accuracy, compliance, and completeness of batch records, which are critical for product quality and regulatory approval.

What are common challenges faced in a batch record review role, and how can they be addressed?

One common challenge in a Batch Record Review role is ensuring the completeness and accuracy of documentation while working under tight deadlines, as production schedules often depend on timely batch release. Attention to detail is critical, since even minor discrepancies can lead to delays or compliance issues. Effective communication and collaboration with production, quality assurance, and laboratory teams are key to resolving discrepancies quickly. Proactively staying updated on current Good Manufacturing Practices (cGMP) and internal protocols can also help minimize errors and streamline the review process.

What is the difference between Batch Record Review vs Quality Control Analyst?

AspectBatch Record ReviewQuality Control Analyst
Primary RoleReview and approve manufacturing batch records for compliance and accuracyPerform testing and analysis of raw materials, in-process, and finished products
CertificationsOften requires GMP, cGMP, or industry-specific certificationsRequires laboratory certifications, such as ASQ or equivalent
Work EnvironmentManufacturing or production facilities, quality assurance departmentsLaboratories, quality control labs, manufacturing sites
Industry UsagePharmaceutical, biotech, and manufacturing sectorsPharmaceutical, biotech, and food industries

While both roles focus on quality, Batch Record Review primarily involves reviewing manufacturing documentation for compliance, whereas Quality Control Analysts conduct testing and analysis to ensure product quality. Both are essential in regulated industries and often collaborate to maintain product standards.

What job categories do people searching Batch Record Review jobs in Remote, OR look for?

The top searched job categories for Batch Record Review jobs in Remote, OR are:

Batch Record Review jobs near you
Infographic showing various Batch Record Review job openings in Remote, OR as of August 2026, with employment types broken down into 2% As Needed, 82% Full Time, 12% Part Time, and 4% Contract. Highlights an 79% Physical, 1% Hybrid, and 20% Remote job distribution, with an average salary of $42,262 per year, or $20.3 per hour.

Principal Cloud Engineer

OR • Remote

Logging-in
51 - 200 employees
Learn more about Logging-inexternal

$55 - $60/hr

Contractor

Posted 2 days ago

New

Job description

Role: Principal Cloud Engineer
Location: Remote
Duration: Long Term

We are seeking a Principal Cloud Engineer who thrives at the intersection of cloud architecture, platform engineering, and delivery excellence.
This is a high-impact, design-centric role responsible for shaping cloud strategy and producing implementation-ready designs that teams can execute confidently.

You will lead the design of scalable, secure, reliable systems—and you will remain close to the code and the infrastructure to ensure designs are practical, automatable, and operable.

You’ll partner with Architecture, Security, DevOps, SRE, Data, and Application teams to deliver well-architected solutions across compute, networking, identity, data, integration, observability, resiliency, and cost optimization.

Design is not just diagrams here. We expect you to establish patterns, document decisions (ADRs), validate designs through prototypes, and drive adoption through reference implementations and guardrails.
 
What You’ll Do (Core Responsibilities):
Lead cloud solution design (primary focus):
  • Own architecture and detailed design for complex cloud initiatives (greenfield + modernization). 
  • Create implementation-ready designs: 
    • Logical + physical architectures.
    • Network and identity models.
    • Security controls and threat analysis.
    • Availability, DR, and scaling strategies.
    • Data flow and integration patterns.
    • Observability and operational runbooks.
  • Produce clear and actionable artifacts, such as: 
    • Architecture decision records (ADRs).
    • Reference architectures and “golden paths”.
    • Patterns catalog (e.g., event-driven, API-first, data share, batch/stream).
    • Standards and guardrails for teams.
 
Validate designs with practical engineering:
  • Build prototypes / spike solutions to de-risk complex designs (e.g., networking, IAM, performance, data movement). 
  • Create reference implementations (IaC, CI/CD templates, policy as code, sample services). 
  • Provide technical leadership during delivery: unblock teams, review PRs, guide implementation choices, and ensure design fidelity. 
 
Establish secure, compliant, well-governed cloud platforms:
  • Define a secure-by-default posture: identity, encryption, secrets, network isolation, logging, vulnerability management. 
  • Implement governance using native cloud capabilities and automation (policies, blueprints, landing zones, guardrails). 
  • Partner with security and risk teams to ensure controls are built-in, not bolted-on. 
 
Engineer for reliability and operability (SRE mindset):
  • Design for resilience: HA patterns, DR strategies, chaos/testing approaches, graceful degradation. 
  • Create observability standards: logs/metrics/traces, SLOs/SLIs, alerting, incident response workflows. 
  • Drive operational readiness: runbooks, on-call enablement, error budgets, postmortems. 
 
Optimize cost and performance (FinOps + pragmatism):
  • Design cost-aware architectures and continuous optimization practices: right-sizing, storage tiers, reserved capacity, autoscaling. 
  • Provide guidance for performance testing, capacity planning, and scaling strategies. 
 
Mentor and elevate engineering practices:
  • Raise the bar for design quality and engineering rigor across teams. 
  • Lead architecture reviews and design sessions; coach engineers on tradeoffs and patterns. 
  • Influence without authority—build alignment across stakeholders. 
 
Lead vendor partner selection and engagement:
  • Identify, evaluate, and select cloud technology vendors and partners to support strategic initiatives.
  • Assess vendor solutions for technical fit, security, compliance, cost, and operational impact.
  • Drive RFP/RFI processes, coordinate technical due diligence, and negotiate terms with vendors.
  • Establish ongoing relationships with key partners, ensuring alignment with architecture standards and delivery goals.
 
Required Qualifications (Must Have):
  • 10+ years in software/platform engineering with significant cloud architecture ownership at scale.
  • Proven experience leading design for complex cloud systems (not just participating).
  • Demonstrated hands-on experience building and operating cloud workloads: 
    • Infrastructure as Code (Terraform strongly preferred; CloudFormation/Bicep acceptable).
    • CI/CD and release automation (GitHub Actions/Azure DevOps/Jenkins/etc.)
    • Containers and orchestration (Kubernetes/EKS/AKS/GKE; or equivalent)
  • Strong cloud fundamentals across: 
    • Identity and access management (IAM, RBAC, OAuth/OIDC, least privilege)
    • Networking (VPC/VNet, routing, peering, private endpoints, DNS, zero trust patterns)
    • Security (encryption, key management, secrets, threat modeling, posture management)
    • Reliability (HA, DR, multi-zone, multi-region strategies)
    • Observability (structured logging, distributed tracing, metrics, SLOs)
  • Experience with architecture artifacts and methodologies: 
    • ADRs, reference architectures, patterns, and well-architected reviews.
    • Ability to communicate design tradeoffs clearly to technical + executive audiences.
 
Preferred Qualifications (Nice to Have):
  • Multi-cloud design experience (Azure/AWS/GCP) or hybrid cloud design (on-prem + cloud). 
  • Strong integration architecture background: 
    • API management, event streaming, messaging, service mesh, integration platforms.
  • Data platform knowledge: 
    • Data lakes/lake houses, data sharing patterns, streaming vs batch, governance.
  • Policy-as-code tooling (OPA/Gatekeeper, Azure Policy, AWS SCPs; etc.). 
  • FinOps practices and cloud cost optimization leadership. 
  • Certifications (helpful but not required): 
    • AWS Solutions Architect Professional / Azure Solutions Architect Expert / GCP PCA.
  • Kubernetes (CKA/CKAD), Security (CCSP), etc.