Remote Security Engineer jobs – Senior Full‑Time Position in Medford, Oregon – Cloud‑Native (AWS, Azure) + SOC Ops – $130k‑$155k Salary – Pen‑Testing & Threat‑Hunting Expertise

TITLE:Remote Security Engineer jobs –Senior Full‑Time Position in Medford, Oregon – Cloud‑Native (AWS, Azure) + SOC Ops – $130k‑$155kSalary – Pen‑Testing & Threat‑Hunting Expertise --- Who we are We’re a fifteen‑person security‑first product studio that launched three years ago from a small co‑working space in Medford, Oregon. Our flagship offering is a compliance‑automation platform that lets regulated businesses (healthcare, fintech, education) prove they meet ISO 27001, HIPAA, and SOC 2 without hiring a full‑time audit team.In the last twelve months we grew ARR from $4 M to $9.3 M – a 133 % increase – and we just closed a $12 M Series B led by a firm that specializes in cloud‑security investments. Our “security‑by‑design” mantra isn’t a buzzword on a slide deck; it’s baked into every line of code, every feature request, and every support ticket. The security engineer role you’re reading about exists because we’re about to roll out a new “real‑time threat‑intelligence” module that will ingest millions of events per day and surface actionable alerts for our customers.To make that happen, we need someone who can own the end‑to‑end lifecycle of security engineering – from threat modeling to incident response – while keeping the rest of the team focused on delivering value to users. Why this role exists nowOur latest product roadmap shows a Q1 launch of “Adaptive Risk Scores”, an AI‑driven engine that calculates breach likelihood for each user session. That feature will require hardened pipelines, secure data‑in‑motion controls, and a hardened detection surface that can survive the noise of a global customer base.In the last quarter we logged 2,764 security‑related tickets, with an average resolution SLA of 3.2 hours for critical alerts. Our current security team (four engineers, two analysts) is stretched at 87 % utilization. The gap we’re feeling is the ability to drive proactive penetration testing, automate compliance checks, and mentor junior staff on secure coding practices. In short: we need a senior security engineer who can both roll up their sleeves on a pen‑test and step back to design a secure CI/CD pipeline that scales to $30 M ARR in the next 18 months.What you’ll do – day‑to‑day (not a laundry list) - Threat‑model the new Adaptive Risk Scores: work with product managers, data scientists, and our CloudOps crew to map attack surfaces, create data‑flow diagrams, and assign risk severity. Expect to run at least one threat‑modeling session per sprint (two‑week cadence). - Build and maintain secure CI/CD pipelines: integrate static application security testing (SAST), dynamic application security testing (DAST), and software composition analysis (SCA) into our GitHub Actions workflows.You’ll own the metrics: we currently see 12 % of PRs flagged for critical findings; our goal is to dip under 5 % in six months. - Lead hands‑on penetration testing: both black‑box and white‑box on our micro‑services (Node.js, Go, Python). You’ll draft findings, write remediation tickets, and verify fixes. The average time to remediate a critical vulnerability now is 14 days; we aim to cut that to 7 days. - Design and configure cloud‑security controls: In AWS (IAM, GuardDuty, Security Hub) and Azure (Azure Sentinel, Policy) you’ll implement least‑privilege roles, network segmentation, and encryption‑at‑rest.We already enforce encryption for 100 % of stored data; you’ll expand that to all transient data streams. - Mentor and grow the junior cyber analysts: you’ll run monthly “security office hours”, review their triage notes, and help them graduate from Level 1 to Level 2 analysts. Over the past year we promoted three analysts; we’d like to double that figure. - Respond to incidents: when a breach or suspicious activity spikes, you’ll be the first responder, coordinating with the SOC, forensic team, and legal.Our current mean time to detect (MTTD) is 45 minutes; we need to bring it down to sub‑30 minutes. - Document and evangelize: produce clear, concise runbooks, security policies, and internal blog posts. We run a weekly “Security Friday” where engineers share lessons learned – you’ll be a regular speaker. Who you are – not a checklist, a profile You are the kind of engineer who sees security not as a gate‑keeping add‑on but as a core product experience. You have at least five years of hands‑on experience building security into SaaS platforms, and you can recount a story where a single mis‑configured IAM policy led to a costly incident you helped resolve.You’ve held titles like security analyst, cyber analyst, or penetration tester, and you can comfortably flip between those hats. Your approach to problems is methodical: you start with data, write a hypothesis, test it in a sandbox, and iterate. You love the smell of fresh logs and can parse a massive JSON payload in under five minutes. You’re comfortable with cloud providers – you have an AWS Certified Security – Specialty or Azure Security Engineer Associate, but you can also pick up new services quickly.You speak the language of developers (Git, Docker, Kubernetes) and can walk into a code review and point out an insecure deserialization risk without derailing the conversation. Tools & technologies – the stack you’ll own 1. AWS (IAM, GuardDuty, Security Hub, KMS) 2. Azure Sentinel & Azure Policy 3. GitHub Actions (SAST – Checkmarx, DAST – OWASP ZAP, SCA – Snyk) 4. HashiCorp Vault for secret management 5. Kubernetes (OPA Gatekeeper, Falco) 6. Splunk & Elastic for log aggregation 7. Tenable.io / Qualys for vulnerability scanning 8.Burp SuiteProfessional for manual pentests 9. Jira Service Management for ticketing 10. Slack & PagerDuty for incident alerts 11. Terraform for IaC security checks 12. Python & Go for scripting custom detection rules We use about 100 GB of log data per day, and our current rule set in Splunk runs 850 alerts per week. You’ll have the chance to refine that to the top 5 % that matter. Team & impact – where you’ll fitOur security team sits beside product design, not in a separate “security silo”. You’ll partner daily with the lead UX designer (who lives in Medford, Oregon) to embed privacy notices, and with the data‑science lead (based remotely in Austin, TX) to ensure model outputs don’t leak PII.You’ll report to the VP of Engineering, who previously ran a SOC for a Fortune‑500 fintech firm, and you’ll sit on a cross‑functional “Security Steering Committee” that meets bi‑weekly with the CEO and CFO. The committee reviews a quarterly security scorecard that currently shows: - Critical findings: 9 % reduction YoY - Mean time to respond: 3.2 hours (target Your contributions will directly affect those numbers and will be visible to investors, customers, and regulators.> “I remember the first time I saw a junior analyst take a 0‑day alert, follow the steps you taught us, and close the loop in under an hour. It felt like watching a craftsman finish a piece of furniture – precise, satisfying, and a reminder why we do this work.” – Mia Patel, Security Analyst, 2 years at the companyCompensation & benefits – the real numbers - Base salary: $130,000 – $155,000 USD, based on experience and certifications. - Annual performance bonus: up to 12 % of base. - Equity: 0.05 % – 0.12 % RSU pool (fully‑vested over four years).- Remote‑first policy: work from anywhere in the United States, but we have a co‑working budget for when you’re in Medford, Oregon (we love meeting in person once a quarter). - Health & dental: 100 % covered for employee, 80 % for dependents. - Retirement: 5 % company match on 401(k). -Professional development: $4,000 annual stipend for certifications, conferences (RSA, Black Hat, DefCon), or online courses. - Paid time off: 25 days + 10 public holidays, plus unlimited sick days. - Wellness: quarterly mental‑health stipend, ergonomic home‑office allowance, and a “pet‑day” policy (you can bring your dog to video calls).Application process – what to expect 1. Resume & cover letter – we’re not looking for a generic template. Tell us about a specific security challenge you owned and the outcome (numbers if you have them). 2. Technical screen (45 min) – a senior engineer will ask you to walk through a recent incident you handled, focusing on reasoning, not just tools. 3. Take‑home exercise (2‑hour) – you’ll receive a small code repository with a known vulnerability. Your deliverable is a short write‑up (max 2 pages) describing the flaw, remediation steps, and how you’d prevent similar issues in CI/CD.4. On‑site (virtual) interview – three 30‑minute sessions with the security team, product manager, and the VP of Engineering. Expect a mix of scenario questions, culture fit discussion, and a brief “security whiteboard” where you’ll sketch a threat model for a hypothetical new feature. 5. Reference check – we’ll ask your last two managers about collaborative style, reliability, and growth mindset. If you get to the final stage, we’ll send an official offer within 48 hours, and you can start as soon as you give notice (we’ve seen new hires start in two weeks).Why we love Medford, Oregon and remote work Even though the role is remote, our roots in Medford, Oregon are strong. The city’s tech community is growing, with monthly OWASP meetups and a solid pipeline of security talent from the local university. We sponsor those events, and we encourage you to attend in person when you’re in town. Our remote‑first philosophy means you set your own schedule, as long as core hours (12 PM – 4 PM EST) overlap for live incident response. We’ve built a “virtual watercooler” channel where team members share a coffee break, memes, and occasionally a quick “show‑and‑tell” of a new security tool they discovered.Final note We know senior security engineers get bombarded with glossy job posts that promise “cutting‑edge tech” and “unlimited growth”. What we can promise is a concrete set of challenges, measurable impact, and a team that celebrates each win (even the small ones). If you’re ready to own security for a product that protects regulated data across the globe, and you enjoy mentoring a growing team while still writing code, we’d love to meet you. * Send your application to [email protected] with the subject line “Remote Security Engineer – Medford, Oregon”.* We’ll be reviewing applications on a rolling basis, and we plan to fill this role within the next three weeks.If you have any questions before applying, feel free to DM our hiring manager, Alex Rivera, on LinkedIn – he’s happy to chat about the role, the tech stack, or what the local lunch spots in Medford, Oregon are like. Apply tot his job