SRE (Platform) Engineer

About Hanover ParkWe're building the AI-native ERP that will define private markets infrastructure. This isn't an AI wrapper slapped onto legacy software - we built a proprietary general ledger accounting system from the ground up, designed specifically for complex investment firms. As the system of record, we've earned the trust to bundle fund administration with tools that were previously fragmented: investor portals, AI-powered portfolio management, KPI collection, and more.With AI, context is king. And Hanover Park has all the context on our <customers.In> under a year, we've scaled to over $40 billion in assets under administration, serving investment firms and LPs that include top-5 banks and major endowments. We're backed by Emergence Capital (first investor in Salesforce and Zoom), Susa Ventures (first investor in Robinhood and Flexport), and Lux Capital.Stripe for payments. Ramp for expenses. Hanover Park for investments.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 OnSet the technical direction for our infrastructure architecture as we scale, including build-vs-buy and vendor decisionsEstablish on-call practices, SLOs/SLIs, and an incident postmortem culture from scratch, then own uptime and incident response against themBuild and maintain our CI/CD pipelines and deployment infrastructure across vercel and AWSDesign, provision, and manage our AWS infrastructure and set the best practices other engineers followOwn our supabase/postgres infrastructure: performance tuning, backups, migrations, and scaling as data volume growsBuild and maintain our background job and workflow infrastructure on trigger.devStand up real observability: logging, monitoring, alerting, and tracing, so we know about problems before customers doHarden security practices across the stack: secrets management, access control, and compliance readinessWrite and ship application code when the right fix is a product fix, not just an infra oneMentor 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 worksStackAWS, supabase (postgres), vercel, <trigger.dev>, typeScriptWhat We're Looking ForNeedMinimum 5 years running production infrastructure at scale, whether the title was SRE, platform engineer, or DevOpsA track record designing infrastructure architecture from the ground up, not just operating within one someone else already builtExperience 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 decisionsExperience owning postgres in production at scaleGenuine software engineering ability. You can read, write, and debug application code, not just configs and scriptsA history of establishing incident response practices and SLOs/SLIs where none existed before, not just following ones already in placeA bias toward automating toil away rather than doing the same manual fix every weekNice to haveDirect experience with vercel or supabase specificallyExperience with <trigger.dev> or a similar workflow/queue orchestration toolTime as the founding or senior-most infrastructure hire at an early-stage startup, not a member of an established platform teamExperience mentoring other engineers or building out an infra/platform function as a company scalesExperience in financial services or another regulated, security-sensitive industryExposure to compliance frameworks like SOC 2This Isn't the Right Fit IfYou've only ever operated within playbooks someone else wrote and haven't designed the playbook yourselfYou want to write infra code exclusively and never touch the productYou're looking to join an established platform team with existing headcount and process to lean onYou need a mature on-call rotation and a lot of process in place before you feel comfortable owning somethingWhy 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.Equal OpportunityHanover Park is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees.