About the RoleOur infrastructure has been primarily built and maintained by product engineers alongside their regular workload. That's worked so far, but we need someone whose full-time job is thinking about what works at scale, with more data and more AI agents running in production.
We're not looking for someone to join an existing platform team and follow an established playbook. We're looking for the person who writes the playbook: someone who has already been the senior-most infrastructure voice at a company like ours, has made the architecture calls, and has lived with the consequences of those calls at scale. You'll own our AWS infrastructure, supabase/postgres databases, vercel deployments, trigger.dev job pipelines, and everything else we're built on and around, but this isn't a role for someone who only writes YAML and terraform. We need someone who can also read and write real application code, set the technical standards other engineers build against, and be the escalation point when something breaks in a way no one else on the team can diagnose.
You'll report directly to Nick (CTO) and effectively define what production ownership looks like at Hanover Park going forward. The mandate is broad because we're trusting you to set the bar, not because no one senior is watching: if it affects uptime, performance, or security, it's yours to own end to end, including the judgment calls about what to build, what to buy, and what to defer.
What You'll Work On- Set the technical direction for our infrastructure architecture as we scale, including build-vs-buy and vendor decisions
- Establish on-call practices, SLOs/SLIs, and an incident postmortem culture from scratch, then own uptime and incident response against them
- Build and maintain our CI/CD pipelines and deployment infrastructure across vercel and AWS
- Design, provision, and manage our AWS infrastructure and set the best practices other engineers follow
- Own our supabase/postgres infrastructure: performance tuning, backups, migrations, and scaling as data volume grows
- Build and maintain our background job and workflow infrastructure on trigger.dev
- Stand up real observability: logging, monitoring, alerting, and tracing, so we know about problems before customers do
- Harden security practices across the stack: secrets management, access control, and compliance readiness
- Write and ship application code when the right fix is a product fix, not just an infra one
- Mentor engineers on production best practices as the team grows, and lay the groundwork for a platform function that outlasts you being the only one who knows how it works
StackAWS, supabase (postgres), vercel, trigger.dev, typeScript
What We're Looking ForNeed- Minimum 5 years running production infrastructure at scale, whether the title was SRE, platform engineer, or DevOps
- A track record designing infrastructure architecture from the ground up, not just operating within one someone else already built
- Experience being the senior-most infra voice at a scaling startup: setting standards, being the escalation point, and living with the consequences of your own architecture decisions
- Experience owning postgres in production at scale
- Genuine software engineering ability. You can read, write, and debug application code, not just configs and scripts
- A history of establishing incident response practices and SLOs/SLIs where none existed before, not just following ones already in place
- A bias toward automating toil away rather than doing the same manual fix every week
Nice to have- Direct experience with vercel or supabase specifically
- Experience with trigger.dev or a similar workflow/queue orchestration tool
- Time as the founding or senior-most infrastructure hire at an early-stage startup, not a member of an established platform team
- Experience mentoring other engineers or building out an infra/platform function as a company scales
- Experience in financial services or another regulated, security-sensitive industry
- Exposure to compliance frameworks like SOC 2
This Isn't the Right Fit If- You've only ever operated within playbooks someone else wrote and haven't designed the playbook yourself
- You want to write infra code exclusively and never touch the product
- You're looking to join an established platform team with existing headcount and process to lean on
- You need a mature on-call rotation and a lot of process in place before you feel comfortable owning something
Why NowWe're past the point where infrastructure can be a side project. Every fund we onboard adds more data, more automation, and more surface area for something to break at the worst possible time. This role exists because we'd rather build that muscle now, with someone who's already done it before and owns it end to end, than find out the hard way what happens without it.
