Staff Infrastructure Engineer - Technical Staff
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map sections accordingly.
We must not repeat job title as heading. The job title is "first dedicated infrastructure engineer". Not needed.
We need to include sections only when posting has real specific content. So we can have:
- About the company? Could be "About Savvy Wealth" but not listed as standard heading; but we can use "About the role"? Actually "About the role" is a standard heading. The posting has "The Role" section describing role. So we can use About the role
and put that prose.
- Responsibilities: we have list.
- Requirements: we have "Must Have" and "Nice To Have". Could combine into Requirements? But we could have separate sections: Requirements (Must Have) and Qualifications (Nice To Have). The rules list possible headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Requirements for Must Have, Qualifications for Nice To Have.
- Benefits: we have list.
- Pay: we have compensation range.
- Schedule: not mentioned, so omit.
We also need to include maybe "Recognition" but not a standard heading; we could incorporate into About the role or maybe as a separate section like "About the company"? Not required. The instruction: "include a section ONLY when the posting has real, specific content for it". We could add a section like "About Savvy Wealth" but not in standard list; but we could still use About Savvy Wealth
if we think it's appropriate. However the list of allowed headings is given as examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to those. So we should not create arbitrary headings like "About Savvy Wealth". Instead we could fold that info into "About the role" or maybe a brief intro paragraph before headings. The instruction: "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings not in list, but the examples suggest we should use those. Safer to stick to those headings.
Thus we need to produce:
About the role
About the role
... description of role from "The Role" paragraph ... maybe also include some of the earlier description about Savvy? But that is about company; maybe we can include in About the role? The role description includes: "Savvy is hiring our first dedicated infrastructure engineer. Our platform runs on AWS, EKS, and OpenTofu, and we've built it with product engineers who picked up infrastructure work alongside shipping features. That got us here. Going forward we want someone who has run production infrastructure for years, can look hard at the decisions we've made, and set the direction from here. You'll own the cloud platform: cluster architecture, networking, IAM, cost, IaC standards, CI/CD, observability, and the operational side of Postgres, Redis, and our background job tiers. You'll set the deploy contract and the standards that 35+ engineers build within, and you'll be the person who decides what our infrastructure looks like in a year. The other half of the job is enablement. We're running coding agents across the engineering org and building the infrastructure to support them, which means compute, isolation, and observability problems that don't have settled answers yet. You'll work directly with product engineers on the problems in front of them rather than from behind a ticket queue." We'll put that in
. Then Responsibilities: list items. Then Requirements: list Must Have items. Then Qualifications: list Nice To Have items. Then Benefits: list benefits. Then Pay: compensation range. We need to ensure we preserve all substantive information, no boilerplate. We need to strip out cookie/navigation/legal/EEO etc. Not present. We need to remove duplicated lines. Let's extract content. About Savvy Wealth paragraph: It's descriptive of company; maybe we should include it somewhere. If we don't have a section for company, we could include it in About the role as a preamble? But the instruction says "About the role" heading for section headings; we could put a brief paragraph about the company inside that section before role specifics. That would preserve all info. Thus About the role section will contain: - Description of Savvy Wealth (the first paragraph up to "Come build the next stage with us!" maybe also recognition). Actually the "Recognition" section includes awards. We could include that as part of About the role or maybe separate? Since we don't have a heading for recognition, we could fold it into About the role. Thus About the role will include: Savvy Wealth description: "Wealth management is a $545 billion industry that still runs on manual work. 75% of advisors offer no digital communication beyond email, and most still build financial plans by hand in Excel. Savvy is reinventing what it looks like to be a financial advisor. Founder Ritik Malhotra saw the fragmentation firsthand after seeking out his own advisor, and started Savvy to give independent advisors a modern, AI-native home. Savvy is a registered investment advisor (RIA), and we partner with experienced financial advisors who want to grow without running the back office themselves. Advisors bring their book and join Savvy, running under their own brand (or ours), and Savvy earns a percentage of the assets they manage. In return, they get a true business-in-a-box: a proprietary tech platform and client portal, an in-house marketing team that helps them grow, a world-class investment management team, and a dedicated client services team that runs day-to-day operations and support. Advisors at Savvy service up to 50% more households and save 19 hours a week. AI runs through everything we do. On the product side, Savvy Intelligence (released April 2026) is the only AI built for wealth managers that can see a client's complete financial picture. Internally, everyone at Savvy uses Claude and is encouraged to experiment with it, backed by a dedicated AI enablement team and a RevOps org building agents in-house. The trajectory is steep and it's still early. We're a Series C company with 170+ people, $200M raised, and $100M ARR in sight this year. Inc. ranked us the No. 1 fastest-growing financial services company in America in 2026. Come build the next stage with us! Recognition We're a Certified Great Place to Work and have been honored for our culture and our growth: Newsweek's America's Greatest Startup Workplaces (2026)Fortune Best Workplaces in New York™ (2026)Great Place to Work Certified™" We need to ensure we don't duplicate lines. The "Recognition" line appears as a heading but we can just include the sentences. Now the role description after that: "The Role Savvy is hiring our first dedicated infrastructure engineer...." We'll include that. Thus About the role section will have possibly multiple paragraphs. Now Responsibilities list: bullet points from "Responsibilities" section. Let's extract: - Own the platform: Set architecture and technical direction for our AWS and EKS footprint, including cluster topology, networking, IAM boundaries, and cost. - Audit and course-correct: Review what we've built, identify what won't hold, and sequence the remediation against a team that has to keep shipping. - Set the standards: Define our OpenTofu module structure, state management, deploy contract, and the patterns every engineer works within. - Raise our operational bar: Build out SLOs, alerting that means something, incident response, and on-call practice. - Run our stateful systems: Own Postgres, Redis, and job processing in production, including upgrades, failover, and capacity. - Build the paved road: Ship the tooling and internal services that make the platform easy for product engineers to use correctly. - Support agent infrastructure: Help design and run the compute layer for our coding agents and LLM workloads. - Mentor: Grow the engineers on the team who've been doing infrastructure work part-time into stronger operators. Now Must Have list: - Production Kubernetes ownership: 3+ years as the escalation point for a cluster you owned, including upgrades, control plane, networking, and incidents. Deploying to a cluster someone else runs isn't the same job. - Experience inheriting infrastructure: You've taken over someone else's platform, formed a view on what to keep and what to replace, and executed it without stopping the business. - Small team, real consequences: You've worked on an infrastructure team of five or fewer where mistakes cost money, customers, or compliance standing. You couldn't specialize and you didn't have anyone to escalate to. - You build software: A controller, a CLI, a deploy system, an internal service, something other engineers depended on. Infrastructure work here is engineering, and IaC is one of the tools. - Terraform or OpenTofu depth: Module design, state management, and a real answer for drift. - Stateful systems in production: Postgres specifically, including connection management, upgrades, and failover. - CI/CD and observability as a practice: Not just standing up the tools, but making the signal useful. - Fluent with agentic coding tools: You use Claude Code, Codex, or similar in your own work, and you have opinions about what infrastructure for LLM and agent workloads should look like. Nice To Have list: - Experience operating Rails, Sidekiq, or another stateful monolithic application (Django, Java, and similar all count). - Fintech or regulated-industry background: financial services, wealth management, or compliance-constrained infrastructure. - Experience migrating off a managed PaaS onto self-managed infrastructure. Benefits list: - Competitive salary and equity package - Unlimited PTO + paid company holidays - Access to holistic medical, dental, and vision plans - Company 401(k), Commuter, and HSA/FSA plans - NYC office in the heart of Manhattan - Lunch and snacks provided in the office - Access to virtual mental health care (Spring Health) and health concierge (Rightway) to help you find the right care - Access to counseling for stress management, dependent care, nutrition, fitness, legal, and financial issues (Guardian WorkLifeMatters EAP) Compensation Range: $251K - $272.5K Now we need to output HTML fragment only. We'll wrap each section in
heading and then content.
For lists, use - .
For prose, use
.
We must not include any extra text like explanations.
Let's craft.
First, About the role: We'll have maybe two paragraphs: one about Savvy Wealth description and recognition, second about the role.
We need to ensure we don't include any boilerplate like "Come build the next stage with us!" is okay.
Let's write:
About the role
Wealth management is a $545 billion industry that still runs on manual work. 75% of advisors offer no digital communication beyond email, and most still build financial plans by hand in Excel. Savvy is reinventing what it looks like to be a financial advisor. Founder Ritik Malhotra saw the fragmentation firsthand after seeking out his own advisor, and started Savvy to give independent advisors a modern, AI-native home. Savvy is a registered investment advisor (RIA), and we partner with experienced financial advisors who want to grow without running the
. We must not include any extra text like explanations. Let's craft. First, About the role: We'll have maybe two paragraphs: one about Savvy Wealth description and recognition, second about the role. We need to ensure we don't include any boilerplate like "Come build the next stage with us!" is okay. Let's write:
About the role
Wealth management is a $545 billion industry that still runs on manual work. 75% of advisors offer no digital communication beyond email, and most still build financial plans by hand in Excel. Savvy is reinventing what it looks like to be a financial advisor. Founder Ritik Malhotra saw the fragmentation firsthand after seeking out his own advisor, and started Savvy to give independent advisors a modern, AI-native home. Savvy is a registered investment advisor (RIA), and we partner with experienced financial advisors who want to grow without running the