Engineer - Future Founder

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Savvy Wealth" description, then "Recognition", then "The Role", then "Responsibilities", then "Must Have", "Nice To Have", "Benefits", "Benefits", "Compensation Range". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The posting includes "About Savvy Wealth" (company description) but not exactly "About the role". The "The Role" section describes role. Could map that to "About the role". Also "Responsibilities" present. "Must Have" could be Requirements or Qualifications. "Nice To Have" could be Skills. "Benefits" present. "Compensation Range" is Pay. No schedule info. So we will include sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. Use

headings. Use

• for lists. Use

  for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like navigation, EEO, etc. There's none. Also remove duplicated lines. Ensure we don't repeat job title as heading (none given). No Job ID. We need to include content from "About Savvy Wealth" (first paragraph(s)) under About the role? Actually "About Savvy Wealth" is company overview. Could be part of About the role? Probably we put that under About the role heading. Then "Recognition" maybe could be part of About the role as well? Might be separate but we don't have a heading for Recognition; we could incorporate into About the role as prose. But we must not create sections without content. We could include Recognition as part of About the role paragraph. "The Role" description: we can put under About the role as well? Actually The Role is separate but we already using About the role heading for role description. Might be okay. Better: Use About the role heading for the role description (The Role). Then maybe include company overview as a preceding paragraph before heading? But we need to output only HTML fragment; we can include a

  before first heading describing company overview. That's allowed. Thus structure:

  About Savvy Wealth ... (company overview and recognition)

  About the role

  The Role Savvy is hiring engineers who want to start a company someday....

  Responsibilities

  • Take problems from discovery to production....
  ... etc

  Requirements

  • Must Have Evidence that you build things....
  ... etc

  Skills

  • Nice To Have Experience finding users for something you built....
  ... etc

  Benefits

  • Competitive salary and equity package
  ... etc

  Pay

  Compensation Range: $175K - $230K

  We must not include Schedule section. Check that we preserve all substantive info: need to include all bullet points from Responsibilities, Must Have, Nice To Have, Benefits. Also include company overview and recognition details. Also include the line about "You're encouraged to read through our other engineering job postings..." maybe part of About the role? It's in The Role paragraph after "Your scope and support will reflect your experience." Actually that line appears after "You're encouraged to read through our other engineering job postings to get more information about our stack, systems, architecture, etc -- they are not present in this role." We should keep that. Also include "Founder Ritik Malhotra saw the fragmentation firsthand..." etc. Also include "Recognition We're a Certified Great Place to Work..." etc. Also include "The trajectory is steep and it's still early. We're a Series C company..." etc. Also include "Come build the next stage with us!" maybe. We must not invent or summarize away detail. So we need to keep all those sentences. Let's extract the company overview paragraph(s): "About Savvy Wealth 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 keep that as prose. Could split into paragraphs but fine. Now The Role section: "The Role Savvy is hiring engineers who want to start a company someday. This is an engineering role for people who want to understand customers (you can DM our customers on Slack!), help decide what’s worth building (road mapping, prototyping, building, shipping), and take responsibility for the results (own company-level OKRs yourself). You’ll join a high energy team that uses AI aggressively to build, experiment & ship. You’ll work directly with financial advisors and operations teams across Savvy. You’ll work alongside serial founders, including Ritik Malhotra (Savvy is his third company -- the first two got acquired by Box and Brex), and experienced engineering, product, and business leaders. This role is open to engineers at any career level, and we especially encourage people early in their careers to apply. Your scope and support will reflect your experience. We care more about what you’ve built, how quickly you learn, and the ownership you demonstrate than the number of years on your CV. You're encouraged to read through our other engineering job postings to get more information about our stack, systems, architecture, etc -- they are not present in this role." Now Responsibilities bullet list: "Take problems from discovery to production. Partner with Product, Design, and fellow engineers (EPD) to understand problems and build out end to end product solutions.Get close to the customer and the business. Work directly with financial advisors and internal teams to uncover friction, challenge assumptions, and identify opportunities to improve client experiences, reduce manual work, or support growth.Use AI, like coding agents, to expand what you can accomplish. Use the latest and greatest tools you discovered at 1am on X to deliver even faster the following day. Stay accountable to your product execution (but don't feel like you need to review every line of code written).Make thoughtful decisions about what to build. Just because you can build anything doesn't mean you should.Own the outcome (one of our core values)." We need to split into separate
• items. The original seems to be a run-on sentences separated by periods. We'll split each sentence as a bullet. Sentences: 1. Take problems from discovery to production. 2. Partner with Product, Design, and fellow engineers (EPD) to understand problems and build out end to end product solutions. 3. Get close to the customer and the business. 4. Work directly with financial advisors and internal teams to uncover friction, challenge assumptions, and identify opportunities to improve client experiences, reduce manual work, or support growth. 5. Use AI, like coding agents, to expand what you can accomplish. 6. Use the latest and greatest tools you discovered at 1am on X to deliver even faster the following day. 7. Stay accountable to your product execution (but don't feel like you need to review every line of code written). 8. Make thoughtful decisions about what to build. 9. Just because you can build anything doesn't mean you should. 10. Own the outcome (one of our core values). Now Must Have bullet list: "Must Have Evidence that you build things. We'll be looking for side projects, attempts at launching businesses, startup accelerator applications, etc.Solid AI-enabled engineering fundamentals. You can wield AI to write and debug code. You don’t need to know our entire stack -- Codex and Claude can teach you.An AI-first approach to building. You already use AI tools in your development workflow and actively experiment with better ways to build, and you rarely write a line of code yourself. You can evaluate their output, investigate mistakes, and recognize when you need to shift how you're using the agents.High agency and follow-through. When you encounter something unclear or broken, you investigate, ask useful questions, propose a path forward, and see it through. You know when to work independently and when to bring others in.Desire to build a business. You want to understand who the customer is, why a problem matters, and how solving it creates enterprise value.A collaborative & coachable approach. You communicate clearly, seek feedback early, change your mind when the evidence warrants it. You care more about the business impact than the path to get there.A willingness to quit after 18 months to be a founder. We expect this to be a short-term stint with Savvy. We want you to learn as much as possible in 18 months and then delight us with a resignation note titled "I got a pre-seed check, goodbye." (Just leave us a little allocation, please!) (And you might even find your co-founder here.)" Split sentences: 1. Must Have Evidence that you build things. 2. We'll be looking for side projects, attempts at launching businesses, startup accelerator applications, etc. 3. Solid AI-enabled engineering fundamentals. 4. You can wield AI to write and debug code. 5. You don’t need to know our entire stack -- Codex and Claude can teach you. 6. An AI-first approach to building. 7. You already use AI tools in your development workflow and actively experiment with better ways to build, and you rarely write a line of code yourself. 8. You can evaluate their output, investigate mistakes, and recognize when you need to shift how you're using the agents. 9. High agency and follow-through. 10. When you encounter something unclear or broken, you investigate, ask useful questions, propose a path forward, and see it through. 11. You know when to work independently and when to bring others in. 12. Desire to build a business. 13. You want to understand who the customer is, why a problem matters, and how solving it creates enterprise value. 14. A collaborative & coachable approach. 15. You communicate clearly, seek feedback early, change your mind when the evidence warrants it. 16. You care more about the business impact