The company runs a merchant risk intelligence platform that helps financial institutions judge whether the businesses they serve are legitimate. It is backed by Y Combinator.
It already works with some of the largest payments and financial services firms, but the team is still small, so one strong hire can shape the product and how the company grows.
The company has stayed lean and fast-moving and gives people far more ownership than is typical at its level of enterprise traction. Few layers separate spotting a problem from fixing it.
The platform keeps fraudulent and abusive businesses out of the financial system and helps legitimate ones get approved sooner with less friction.
Stack: AWS with ECS on Fargate, Aurora PostgreSQL, ElastiCache for Redis, Lambda, EventBridge, SNS, Secrets Manager and KMS. Infrastructure in AWS CDK with Python. Application in Python, Django, Celery and a Scrapy crawling fleet. Deployments through GitHub Actions using short-lived OIDC roles, with separate AWS accounts for staging and production. Observability through CloudWatch, Better Stack and Sentry.
Within 30 days you should be deploying to production alone, be on the on-call rotation, and know which alarms you trust. Within 90 days, SLOs should exist and be reported, every production alert should have an owner and a runbook, a database restore should be tested and timed, and vulnerability fixes should follow a written schedule. Within 6 months, the next SOC 2 evidence cycle should run mostly on automation, traffic bursts and vendor slowdowns should be handled by the system, and a second person should be able to cover on-call from your documentation.
Responsibilities
Reliability takes most of your time. You own uptime for the production platform: the AWS infrastructure, the release path, alerting, and incident response. This is the company's first dedicated infrastructure role. The Director of Engineering currently covers much of this alongside other duties, and it will pass to you.
Carry the production pager, lead incident response, and write postmortems that prevent repeat incidents.
Own alarms, dashboards, log pipelines, and regular checks that alerts reach a person.
Size capacity against measured traffic. Load arrives as bursts of thousands of reviews within a few minutes, so you own the autoscaling floors, queue depths, and load tests that keep those bursts smooth.
Define service level objectives with engineering and report against them.
Run backups and disaster recovery: tested database restores, documented recovery targets, and periodic recovery drills.
Manage all infrastructure as code in AWS CDK with Python. Nothing in production is changed by hand.
Own the release path from merge to production: the CI/CD pipeline, deployment PRs, post-deploy checks, and rollback.
Plan and carry out migrations and decommissions, including schema changes on large tables, engine upgrades, and full retirement of old systems.
Operate the data layer: Aurora PostgreSQL, read replicas, and Redis.
Keep staging a reliable rehearsal for production.
Manage AWS and vendor spend, including reserved capacity and cost per review.
Monitor error rates, latency, and quota use for the third-party APIs that reviews depend on. Tell apart a vendor outage, a rate limit, and an exhausted plan.
Work with application engineers on client behavior that protects the platform when a vendor degrades: timeouts, backoff, circuit breakers, and budgets.
Advise on plan sizing and renewals using real usage data.
Security operations takes a smaller share of your time. Triage findings from GuardDuty, Inspector, and dependency scanners, and fix vulnerabilities on a severity-based schedule.
Run identity and access: single sign-on, least-privilege roles, access reviews, onboarding and offboarding, and credential hygiene.
Own secrets and encryption keys, including inventory, rotation, and audit logging.
Maintain the network edge, including rate limiting and web application firewall rules.
Work with the outside security advisor on architecture reviews and the annual penetration test, and close the findings.
Compliance also takes a smaller share. Run the technical SOC 2 controls day to day and produce their evidence, most of it from systems you already operate. A compliance platform and outside advisors handle policy, audits, and architecture review.
Provide the technical facts for customer security questionnaires and audit findings, and carry out the remediation.
Keep runbooks, architecture documentation, and change records current enough that a colleague could cover for you.
Requirements
5+ years running production systems, including on-call time for a customer-facing service where you were the person paged.
Deep hands-on AWS experience: ECS on Fargate or a similar container platform, load balancing, VPC networking and security groups, IAM, RDS or Aurora, and CloudWatch.
Infrastructure as code as your default way of working. CDK is ideal. Strong Terraform or CloudFormation experience is fine if you are willing to switch.
Comfortable reading and writing Python, which covers the infrastructure code, tooling, and application.
A record of leading incidents and writing candid postmortems.
Experience owning a CI/CD pipeline and a release process with safe rollback.
Working security knowledge of IAM policy, KMS, CloudTrail, and vulnerability triage. You do not need to be a security specialist.
Clear written communication for engineers, leadership, and occasionally a customer's security team.
Sound risk judgment: you verify before you delete and can explain why a change is safe.
You have been through a SOC 2 audit as the person supplying evidence.
PostgreSQL operations at scale: upgrades, replication, query tuning, and online schema changes.
Django and Celery, or another task-queue-heavy application.
Web scraping or headless-browser workloads.
Managing dependence on rate-limited third-party APIs.
GitHub Actions with OIDC-based deployment to AWS.
You have been the first infrastructure hire somewhere before.
Experience: 6+ years.
Conditions
Open only to US citizens or holders of a visa.
Where you’d work
Fully remote
You can work from
United States
Canada
No visa sponsorship
You must already be able to work in the United States