PayNearMe develops technology to facilitate the end-to-end customer payment experience, making it easy for businesses to accept, disburse and manage payments. Our modern and reliable platform lowers the total cost of payments by increasing acceptance rates, driving self-service and simplifying exceptions. We future-proof our clients’ payments roadmap by including all payment types and channels through a single contract and integration. With PayNearMe, businesses can focus on acquiring new customers while we make accepting payments a modern and seamless experience.

PayNearMe has over 240 employees and is processing over $40B in payments annually. We are a fully-funded private company headquartered in Silicon Valley with our employees distributed across the U.S. 

This is an opportunity to join a high-growth, private, venture-backed company during its critical growth phase. Come help us solve our clients’ biggest payment problems.

We’re investing heavily to harden reliability, modernize our stack, and accelerate product velocity. Today, we operate two worlds:

1. A mission‑critical Rails monolith on AWS EC2 that runs 24×7×365.
2. A modern services stack (Go on Kubernetes) we’re rapidly scaling.

We need a hands‑on VP of Cloud to own both worlds: driving proactive reliability, transforming infrastructure as code, and making it fast and safe for product teams to ship. You’ll lead the program that turns reliability into a competitive advantage and lays the runway for the next stage of growth.

What you’ll do & own

• Reliability & SLOs: Define and enforce SLOs (target ≥99.95% for core services). Lead incident management and the shift from reactive to proactive reliability (redundancy, failure testing, chaos/DR exercises, error budgets).
• AWS at Scale: Own our AWS environment (EC2/EKS, VPC, ALB/NLB, Route 53, S3, RDS/Aurora, IAM/KMS). Drive cost/performance tradeoffs and manage a seven‑figure AWS budget with clear FinOps guardrails.
• Two Stacks, One Standard: Operate and evolve the Rails monolith (EC2 today; containerized & Terraform‑managed going forward). Standardize the Go/Kubernetes services stack (EKS, Helm) with paved‑road templates, service bootstrapping, and zero‑toil deploys.
• Infrastructure as Code & CI/CD: Make infrastructure repeatable and reviewable using Terraform (authoring and review), Helm, and GitLab CI/CD. Reduce manual work to near zero.
• Networking & Service Mesh: Own ingress/egress (NGINX) and service mesh (Linkerd). Establish golden patterns for traffic management, authn/z, and resiliency.
• Observability: Ensure end‑to‑end visibility (DataDog, CloudWatch, logs/traces). Set high‑signal alerting and dashboards tied to user outcomes.
• Security & Compliance Partnering: Work hand‑in‑hand with Security to meet/beat PCI, SOC 2 and related audits; build controls into the platform by default.
• Data Layer Alignment: Partner with Data/DBA teams (Aurora MySQL & Postgres). Advise on reliability, strategies to support horizontal scaling of relational databases (examples under evaluation include TiDB and Vitess), backups/restore and multi‑AZ/region patterns. Scope may expand to include DB Engineering over time.
• People & Org: Lead ~10–12 engineers/contractors initially (growing to ~15). Uplevel talent, hire bar‑raisers, and coach legacy sysops profiles toward DevOps/SRE. Clarify roles, on‑call, and ownership to reduce bottlenecks.

Must-Have Experience:

• 10-12+ years in engineering with 5+ leading Infra/Platform/DevOps/SRE teams.
• Deep AWS experience operating 24×7, high‑volume systems.
• Rails at scale: You’ve operated a Ruby on Rails application in production on AWS (EC2/containers) and understand its deployment/runtime characteristics.
• Kubernetes expert: Designed/operated EKS (or equivalent) for mission‑critical services; multi‑AZ patterns, autoscaling, rollout strategies.
• Terraform author: You’ve written and reviewed Terraform in anger; you enforce code review, testing, and module standards.
• CI/CD & automation: GitLab pipelines, Helm, container build/publish, progressive delivery.
• Observability & incident leadership: You set SLOs, build usable dashboards, and run world‑class on‑call.
• Security & audits: Comfortable building for PCI/SOC 2 controls in regulated environments.
• Pragmatic technologist: Preference for boring, battle‑tested tech over novelty; bias to shipping.

Nice-to-Haves 

• Payments/fintech or other highly regulated domains (banking, healthcare, insurance).
• Sharding/partitioning at scale (Aurora MySQL/Postgres; Vitess/TiDB exposure).
• Go and Ruby proficiency (enough to review and challenge design/operational choices).
• Experience leading/absorbing DBA teams into a cloud/reliability org.

What Success Looks Like in 12 Months

• Boringly reliable core: We can’t remember the last time a core service failed for infrastructure reasons; SLOs are met or exceeded quarter after quarter.
• Monolith modernized: The Rails monolith is on its way to be described in Terraform with containerized runtime and automated change management; manual one‑offs are eliminated.
• Services at the push of a button: Two additional production services launched using a paved‑road template; new service infra bootstraps in hours, not weeks.
• Faster incident loop: MTTR materially reduced; blameless postmortems produce guardrails and automation, not tickets.
• Efficient at scale: Cost per payment trending down; AWS spend within plan with real‑time visibility and enforceable budgets.
• Audit‑ready by default: PCI/SOC 2 controls automated in pipelines and infrastructure; zero critical findings.

What you’ll do in your first 90–180 days

• 90 days: Reliability & risk assessment across EC2/EKS; publish SLOs and error budgets; map single points of failure; perform a review and update of the roadmap to reach infrastructure-as-code for the monolith.
• 120 days: Ship paved‑road v1 (service template + CI/CD + IaC). Begin Terraform coverage of monolith infrastructure. Establish on‑call rotations with clear runbooks.
• 180 days: Complete containerization/Terraform plan for monolith; launch second production service on the paved road; land initial cost optimizations and game‑day DR.

Current Data Stack:

• Key AWS services: EC2, ELB, EKS, Elasticache, Aurora/RDS
• Puppet (project underway to replace it with Ansible)
• nginx, Passenger
• Hashicorp Vault
• NATS
• Terraform, FluxCD, Helm

Why Join Us?:

• Competitive salary and benefits with growth-company options grant
• Fast- paced and professional work culture
• Stock options with standard startup vesting - 1 year cliff; 4 years total
• $50 monthly communication expense stipend to go towards your phone/internet bill
• $250 stipend to enhance your WFH setup
• Reimbursement for peripheral equipment: monitor (up to $400), keyboard and mouse (up to $200)
• Premium medical benefits including vision and dental (100% coverage for employees)
• Company-sponsored life and disability insurance
• Paid parental bonding leave
• Paid sick leave, jury duty, bereavement
• 401k plan
• Flexible Time Off (our team members typically take off ~3-4 weeks per year)
• Volunteer Time Off
• 13 scheduled holidays

Salary Range: $260,000 - $300,000

PayNearMe strives to create a workplace where all employees thrive. Our core values represent who we are today and we take pride in the way we work with each other as well as with our stakeholders.

We’re in this together to do the right thing. We deliver real results we are proud of while remaining respectful, transparent, and flexible.

PayNearMe is an equal opportunity employer. We are diligently and thoughtfully working towards cultivating a diverse workforce which in turn, enhances our products and services for the communities we serve. Applicants who represent all backgrounds are strongly encouraged to apply.

—

CALIFORNIA CONSUMER PRIVACY ACT: APPLICANT NOTICE

Effective Date: January 1, 2020

Last Reviewed on: December 23, 2019

PayNearMe, Inc. (the “Company”) is providing you with this Notice (“Notice”) to inform you about:

1. the categories of Personal Information that the Company collects and maintains about applicants; and
2. the purposes for which the Company uses that Personal Information.

For purposes of this Notice, “Personal Information” means information that identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly with, a natural person that the Company may collect in connection with screening applicants for job openings at the Company.

1. Identifiers and Professional or Employment-Related Information. The Company collects identifiers and professional or employment-related information, which may include some or all the following: real name, nickname or alias, postal address, telephone number, e-mail address, membership in professional organizations, professional certifications, language skills, and current and past employment history. The Company collects this Personal Information to evaluate previous job performance and consider applicants for positions, to develop a talent pool and plan for succession, to conduct applicant surveys, to maintain an internal applicant directory and for purposes of identification, to promote the Company as a place to work, and for workforce reporting and data analytics/trend analysis.
2. Personal Information Categories from Cal. Civ. Code § 1798.80(e). The Company may collect categories of Personal Information listed in Cal. Civ. Code §1798.80(e), other than those already listed above, (a) to the extent necessary to comply with the Company’s legal obligations, such as to accommodate disabilities; (b) to conduct a direct threat analysis in accordance with the Americans with Disabilities Act and state law; (c) for occupational health and safety compliance and record-keeping; and (d) to respond to an applicant’s medical emergency.
3. Characteristics of Protected Classifications Under California or Federal Law. The Company may collect information about race, age, national origin, disability, sex, and veteran status as necessary to comply with legal obligations, including the reporting requirements of the federal Equal Employment Opportunity Act, the federal Office of Contracting Compliance Programs (applicable to government contractors), and California’s Fair Employment and Housing Act. The Company collects this Personal Information for purposes including: to comply with Federal and California law related to accommodation. The Company also collects this category of Personal Information on a purely voluntary basis, except where required by law, and uses the information only in compliance with applicable laws and regulations.
4. Education Information. The Company collects education information such as resumes and graduation records. The Company collects this Personal Information to determine suitability for roles, to determine eligibility for training courses, and to assist with professional licensing.
5. Profile Data. The Company may collect profile data, including the following: psychological assessments, behavior analyses, or other profiling of its applicants. The Company collects this Personal Information to determine aptitude for certain positions and job assignments as well.
6. Background Screening Information. In the event that an applicant is given a formal job offer, the Company collects background screening information prior to hiring, including results of the following types of background screening: criminal history; sex offender registration; motor vehicle records; credit history; employment history; drug testing; and educational history. The Company collects this Personal Information to screen for risks to the Company and its clients, and continued suitability for their jobs and to evaluate applicants for promotions.

Assistance for Disabled Applicants

Alternative formats of this Notice are available to individuals with a disability. Please let us know if you need assistance.

All your information will be kept confidential according to EEO guidelines.