<h2><strong>Who We Are<br></strong></h2> <p>The Motley Fool is a purpose-driven financial services company on a mission to make the world smarter, happier, and richer. For 30 years, we’ve been helping people make better investment decisions through transparency, education, and a healthy dose of Foolish fun. We’re a fast-moving, collaborative team that values high-quality work, curiosity, and initiative. We care deeply about what we do, and we’re driven by the impact our work has on real people’s financial futures.<br><br>With a growing portfolio of 50+ subscription products, we're investing heavily in the technology that powers Fool.com — one of the most widely read financial sites on the web — and the systems that turn readers into long-term members. </p> <h2><strong>What Does This Team Do? </strong></h2> <p>The Fool.com team owns the public-facing experience that millions of readers, search engine crawlers, and prospective subscribers hit every day. Today, the team is strong on the client side: we have two excellent front-end engineers shipping interface work. We're looking for an engineer who can own the <strong>server-side and infrastructure layer</strong> of the site alongside them.</p> <h2><strong>About the Role</strong></h2> <p>This is a full-stack role with a clear weighting toward the parts of the system that run before pixels reach the browser — API integrations, server-rendered routes, caching, observability, deployment, and the SEO-critical surface that determines how millions of crawler requests resolve. Much of <a href="http://fool.com">fool.com</a> is server side rendered. </p> <h2><strong>What You'll Do</strong></h2> <ul> <li>Build and maintain server-side features in our <strong>Next.js App Router</strong> codebase using <strong>TypeScript</strong> — route handlers, server components, server actions, streaming, ISR, and revalidation strategy. </li> <li>Design and harden integrations with the <strong>third-party APIs</strong> that power our content, market data, and subscription experiences. We care a lot about doing this well: timeouts, retries, circuit breakers, fallbacks, and graceful degradation when upstream services misbehave are first-class concerns, not afterthoughts.</li> <li>Own caching strategy across <strong>Redis</strong> and <strong>Cloudflare</strong>, balancing freshness against performance, cost, and crawler behavior.</li> <li>Deploy and operate services on <strong>AWS</strong> using <strong>Docker</strong>, with first-class instrumentation in <strong>DataDog</strong> so we catch issues before our readers and crawlers do.</li> <li>Write meaningful end-to-end coverage with <strong>Microsoft Playwright</strong> for the flows that matter most.</li> <li>Optimize the site for the way it's actually consumed by <strong>SEO crawlers</strong>: rendering strategy, structured data, sitemap generation, canonicalization, hreflang, robots directives, performance budgets, and crawl budget management.</li> <li>Partner with our front-end engineers on the seam between server and client, and collaborate with content, marketing, SEO, and platform teams across the company.</li> <li>Use AI-assisted development tools (Claude Code, Cursor) as a core part of your daily workflow — we have a company-wide commitment to use the latest tooling and workflows to make every person as impactful as possible.</li> <li>Integrate with our CMS for content management</li> </ul> <h2><strong>What We're Looking For</strong></h2> <ul> <li>5+ years of professional software engineering experience, with meaningful time spent on the server side of a production web application.</li> <li>Strong <strong>TypeScript</strong> and <strong>Next.js</strong> experience, including the App Router, server components, route handlers, ISR, and streaming.</li> <li>Demonstrated track record integrating third-party APIs in production, with clear opinions about how to do it safely. You've debugged a flaky upstream at 11pm and you have views about it.</li> <li>Solid grounding in <strong>caching</strong> (Redis or equivalent) and <strong>CDN behavior</strong> (Cloudflare or equivalent), including cache invalidation, stale-while-revalidate patterns, and edge vs. origin tradeoffs.</li> <li>Comfort with <strong>AWS</strong>, <strong>Docker</strong>, and modern CI/CD workflows.</li> <li>Working knowledge of <strong>how SEO crawlers actually see a site</strong>: how Googlebot renders JavaScript, what causes soft 404s, how canonical and hreflang tags affect indexing, what Core Web Vitals look like in CrUX vs. lab data, and how to think about crawl budget on a large site.</li> <li>Production observability instincts — you reach for <strong>DataDog</strong> dashboards, logs, and traces before guessing.</li> <li>Experience writing maintainable end-to-end tests with <strong>Playwright</strong>, Cypress, or similar.</li> </ul> <h2><strong>Bonus Points</strong></h2> <ul> <li>Background on a high-traffic content, media, or publishing site where SEO is a primary acquisition channel.</li> <li>Hands-on work with structured data (JSON-LD, schema.org), automated sitemaps, Search Console, or auditing tools like Screaming Frog.</li> <li>Familiarity with analytics and event pipelines (Segment, PostHog, GTM, or similar).</li> <li>Prior work on subscription, paywall, or e-commerce flows.</li> <li>Genuine interest in financial markets, investing, or fintech — we're a company of people who care about this stuff.</li> </ul> <h2><strong>Why This Role</strong></h2> <p>You'll be the person who makes Fool.com faster, safer, and more observable on the side of the wire that most users never see. You'll work alongside two strong front-end engineers who are eager to have a real partner across the seam, and you'll do it on a team that takes engineering quality seriously — we've recently invested in standardizing error-handling practices around external services, AI-assisted development tooling, and cross-repository coding guidelines.</p>