Jobs · Engineering

Senior Full-Stack Software Engineer, Discover

Circle · Wilmington, DE · 1 mo ago
RemoteRemoteEngineering$130k–$140k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Be Doing"), Requirements (maybe "What you'll need to be successful"), Benefits (Compensation & Benefits). Also maybe "About Us" is not needed as it's not a section heading per rules? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real content. The posting includes "About Us" but that's not a required heading; we could include "About Us" as a section? The list of example headings does not include About Us, but we could still use

for any section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but not exclusive? Safer to follow the examples: include sections for About the role, Responsibilities, Requirements, Benefits (Compensation & Benefits). Possibly also Skills? The posting includes qualifications etc. We can combine Requirements and Skills into one Requirements section. We must not repeat job title as heading. No Job ID. Remove boilerplate: About Us maybe we can keep as a brief paragraph? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not boilerplate; it's descriptive about company. Could keep as a

maybe under a heading? But we don't have a heading for About Us; we could just include it as a

before sections. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow that pattern. Probably better to include an

for About Us? Not in list but could be okay. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. I'd include About the role, Responsibilities, Requirements, Benefits. Also maybe "About Us" as a

without heading. We must preserve all substantive information. So we need to include details from About Us paragraph, role description, responsibilities list, requirements list, compensation and benefits. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we don't repeat. We must not include application instructions, EEO, etc. Remove lines like "Learn more in our Candidate Hub." etc. Also remove "Learn more Candidate Safety & Interview Process Notice..." etc. We need to output only HTML fragment. Let's extract content: About Us paragraph: "Circle is building the world’s leading AI-powered, all-in-one platform for digital businesses. We make it possible for creators, coaches, educators, and businesses to bring together their audience with engaging discussions, live streams, events, chat, courses, and payments — all in one place, all under their own brand. We’re proud to be a fully remote company of around 270 (and growing!) team members from 30+ countries around the world. We seek exceptional individuals around the world, set them up to do the best work of their lives, and in turn, create a meaningful impact in their own lives. We don't track hours, but we do manage for high expectations very closely. We collaborate across time zones, are highly async, and like to document a lot. Twice a year, we bring the whole company together in beautiful places around the world for our company offsites. So far, we’ve hosted offsites in Turkey, Portugal, Mexico, Thailand, Colombia, Italy, Ireland, and more, with still more to come! Check out our Careers page for more about working at Circle." We can keep that as a

maybe preceded by an

About Circle? Not required. We'll just put as a

before sections. About The Role heading: "About The Role". We'll use

About the Role

(lowercase? Keep as given). Then paragraph: "We’re looking for a seasoned full-stack engineer to help evolve and expand Circle Discover - Circle’s curated marketplace for finding and buying digital experiences (communities, courses, memberships, and eventually more). As a part of the Discover team, you’ll build the product surface area that helps members explore, discover, and join digital experiences - including algorithmic recommendations, rich listings, engaging content feeds and seamless purchasing flows. We’re looking for someone who’s excited to shape how people find value in community and cares deeply about creating intuitive, performant, and elegant user experiences at scale." That's prose. What You'll Be Doing: list of bullet points. We'll make

Responsibilities

then
  • each. List: - Build polished, high-converting purchasing experiences that help members discover digital experiences and businesses sell digital memberships, courses, and content at scale. - Run A/B tests and experiments to validate changes that boost user acquisition, retention, and conversion behavior. - Implement and improve features in the Discover Next.js frontend application together with API endpoints in our Rails backend. - Work on data pipelines and services driving search and recommendations. - Proactively improve the quality of our codebase, processes and architecture. - Work closely with Circle's leaders throughout the feature design process. - Work closely with our designers to create a world-class user experience. - Foster a bias for action, prioritizing speed of iteration without compromising on the quality of code or user experience. What you'll need to be successful: list. We'll make

    Requirements

    then
    • . List: - 5+ years experience working as a full-stack engineer on complex web applications with significant scale (100k+ rpm, 100GB+ databases). - Strong proficiency in Next.js, ReactJS, TypeScript, Tailwind, Ruby on Rails and MySQL/Postgresql. - Familiarity with both frontend and backend is necessary, but a high degree of proficiency in frontend is required. - A desire to work in an environment which values speed of iteration and individual autonomy, while also embracing personal accountability and the ability to collaborate effectively as part of a dynamic team. - Comfortable in a fast-paced environment with a certain level of ambiguity, especially when learning and picking up new technologies when projects require it. - Great communication skills both in writing and verbal/oral (English). - Experience working on a fully distributed remote team. - Strong alignment with our values, find our values on our career page if you haven’t read up on them yet. - You are proficient in English (spoken, written, and reading) at a CEFR Level C2 / ILR Level 5. Bonus points: we could include as a subsection under Requirements or separate

      Preferred Qualifications

      . The instruction includes Qualifications as possible heading. We could make a

      Preferred Qualifications

      list. Bonus points list: - Previous experience working with creator-platforms, social content and video feeds, or marketplaces. - Experience with A/B testing and experimentation to optimize user experience, performance and conversion within consumer-facing applications. - Previous exposure to search, recommendation and personalization at scale. - Production experience with Next.js and hybrid React/Next.js systems for high-traffic applications. Compensation & Benefits: we have "$130,000 - $140,000 USD per year Circle offers U.S.-benchmarked compensation globally, equity in the company with ongoing refresh grants, and 35 days of paid time off each year. We’re a remote-only team that comes together twice a year for company retreats in incredible destinations around the world. Alongside incredible flexibility and autonomy, we offer a benefits package that supports health, wellbeing, and professional growth." We'll make

      Benefits

      then

      with that content. Also maybe Pay section? But we have compensation in benefits. We'll not create separate Pay. We must not include duplicated lines like "Compensation Range: $130K - $140K" appears later; we should not repeat. We'll just include once. We must remove boilerplate like "Learn more in our Candidate Hub." etc. Also remove "Learn more Candidate Safety & Interview Process Notice..." etc. Now produce HTML. We need to output only HTML fragment, no or . We'll start with maybe a

      for About Us, then sections. Let's craft:

      Circle is building the world’s leading AI-powered, all-in-one platform for digital businesses. We make it possible for creators, coaches, educators, and businesses to bring together their audience with engaging discussions, live streams, events, chat, courses, and payments — all in one place, all under their own brand. We’re proud to be a fully remote company of around 270 (and growing!) team members from 30+ countries around the world. We seek exceptional individuals around the world, set them up to do the best work of their lives, and in turn, create a meaningful impact in their own lives. We don't track hours, but we do manage for high expectations very closely. We collaborate across time zones, are highly async, and like to document a lot. Twice a year, we bring the whole company together in beautiful places around the world for our company offsites. So far, we’ve hosted offsites in Turkey, Portugal, Mexico, Thailand, Colombia, Italy, Ireland, and more, with still more to come! Check out our Careers page for more about working at Circle.

      About the Role

      We’re looking for a seasoned full-stack engineer to help evolve and expand Circle Discover - Circle’s curated marketplace for finding and buying digital experiences (communities, courses, memberships, and eventually more). As a part of the Discover team, you’ll build the product surface area that helps members explore, discover, and join digital experiences - including algorithmic recommendations, rich listings, engaging content feeds and seamless purchasing flows. We’re looking for someone who’s excited to shape how people find value in community and cares deeply about creating intuitive, performant, and elegant user experiences at scale.

      Responsibilities

      • Build polished, high-converting purchasing experiences that help members discover digital experiences and businesses sell digital memberships, courses, and content at scale.
      • Run A/B tests and experiments to validate changes that boost user acquisition, retention, and conversion behavior.
      • Implement and improve features in the Discover Next.js frontend application together with API endpoints in our Rails backend.
      • Work on data pipelines and services driving search and recommendations.
      • Proactively improve the quality of our codebase, processes and architecture.
      • Work closely with Circle's leaders throughout the feature design process.
      • Work closely with our designers to create a world-class user experience.
      • Foster a bias for action, prioritizing speed of iteration without compromising on the quality of code or user experience.

      Requirements

      • 5+ years experience working as a full-stack engineer on complex web applications with significant scale (100k+ rpm, 100GB+ databases).
      • Strong proficiency in Next.js, ReactJS, TypeScript, Tailwind, Ruby on Rails and MySQL/Postgresql.
      • Familiarity with both frontend and backend is necessary, but a high degree of proficiency in frontend is required.
      • A desire to work in an environment which values speed of iteration and individual autonomy, while also embracing personal accountability and the ability to collaborate effectively as part of a dynamic team.
      • Comfortable in a fast-paced environment with a certain level of ambiguity, especially when learning and picking up new technologies when projects require it.

Similar jobs