Jobs · Information Technology · California

Senior Software Engineer, Agentic Commerce

ThredUp · California, United States · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Need to parse the posting. Let's extract content: First paragraph: About ThredUp (company description). That's not about the role; but we can put under "About the role"? Actually "About the role" heading is for description of role. The company description could be considered "About the role"? Usually "About the role" includes description of role and maybe company. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have sections: - "How You Will Make An Impact": description of impact. Could be under "About the role" or maybe "Responsibilities". It's more about what you'll do. Could be "Responsibilities". - "In This Role You'll Get To": bullet list of tasks. That's responsibilities. - "What We're Looking For": list of qualifications/requirements/skills. - "Many ThredUp employees also have the opportunity to own shares...": benefits. - "What We Offer": list of benefits (4-day work week, competitive salary, stock, ESPP, PTO, holidays, sabbatical, parental leave, medical etc). Also core values etc. We need to avoid boilerplate: EEO, disability accommodation request etc. Remove those lines. Also remove navigation/cookie etc (none present). Remove application instructions (the disability support email etc). Also remove "This role is not eligible for visa sponsorship." That's maybe a requirement? Could be considered a note but it's not a substantive requirement? Might be considered metadata; but we can keep as a short p maybe under Requirements? It's a condition. Might keep as a short p. We must not invent sections like Pay or Schedule unless posting actually states them. Pay: "Competitive salary (we leverage market data)" is mentioned under What We Offer. So we have pay info. So we can include a Pay section with that line. Schedule: "4-day work week, with most Fridays off" is schedule info. So we can include Schedule section. Benefits: many items. We need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't create empty sections. Let's structure:

About the role

maybe include company description? Could combine with impact? But we have "How You Will Make An Impact" and "In This Role You'll Get To". Those are responsibilities. So About the role could be brief summary: maybe the first paragraph about ThredUp? But that's about company, not role. However we could still put company description under About the role as context. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid using About the role for company overview. We'll include a short paragraph about ThredUp mission. Then Responsibilities: combine "How You Will Make An Impact" and "In This Role You'll Get To". Could be a
    list. Requirements/Qualifications/Skills: The "What We're Looking For" includes experience, fluency with LLMs, etc. Could split into Requirements (years experience, fluency) and Qualifications (experience building LLM systems, API design, backend depth, curiosity, comfort blank page, judgment, communication). Skills: familiarity with ACP/MCP, e-commerce/marketplace experience, built something from zero. Could also include "No prior experience with any particular piece required." That's a note. We need to avoid duplication. Let's extract bullet points from that section: - 5+ years of software engineering experience, owning systems end to end from ambiguous problem to production. - Fluent daily use of LLMs and agentic coding tools, with strong instincts for where AI output needs human judgment. - Experience building or deploying systems powered by LLMs, and an understanding of how model behavior shapes product experience. - Strong API and integration design skills, for interfaces consumed by other systems rather than by people. - Depth in backend engineering with the range to work across the stack. Design judgment matters more here than which languages you've used. - Genuine curiosity about a space that changes monthly — new protocols, new tooling, new model capabilities — and the habit of keeping up with it. - Comfort working from a blank page without a surrounding team to make progress. - The judgment to scope a problem, put a plan behind it, and drive it to shipped rather than exploring indefinitely. - Clear communication with engineers and non-technical executives alike. - Familiarity with the Agentic Commerce Protocol (ACP), MCP, or other emerging agentic-commerce standards is a plus. - E-commerce or marketplace experience is a plus. - Experience having built something from zero, whether at a startup or inside a larger company is a plus. - Many ThredUp employees also have the opportunity to own shares of ThredUp stock, ThredUp employees are eligible for discretionary restricted stock unit awards, as well as a discount when purchasing ThredUp stock if voluntarily participating in ThredUp's Employee Stock Purchase Plan. (This is benefits) - Subject to eligibility requirements, you'll also receive other benefits: Comprehensive medical & dental coverage, vision, 401k, life and disability insurance. (benefits) - This role is not eligible for visa sponsorship. (maybe a note) We need to separate benefits. Now "What We Offer" section: - 4-day work week, with most Fridays off - Competitive salary (we leverage market data) - Many ThredUp employees also have the opportunity to own shares of ThredUp stock and are eligible for discretionary restricted stock unit awards - Employee stock purchase plan - Flexible PTO (take the time you need) + 13 company holidays - Paid Sabbatical after 3 years of full time employment - Generous paid parental leave for new mothers and fathers - Medical, dental, vision, 401k, life and disability insurance offered - We live by our Core Values of Transparency, SpeakingUP, Thinking Big, Infinite Learning, Influencing Outcomes & Seeking the Truth - We believe diversity, inclusion and belonging is key for our team - At ThredUp, our mission has been built on extending the lives of millions of unique clothing items. Much like our inventory, we are proud to have fostered a workplace that is one-of-a-kind. As a company focused on diversity, inclusion and belonging, we are committed to ensuring our employees are comfortable bringing their authentic selves to work every day. A unique perspective is critical to solving complex problems and inspiring a new generation to think secondhand first. - Be you. - If you are a candidate with a disability and have a reasonable accommodation request for the job application process, please email disabilitysupport@ThredUp.com the specific details of your disability related accommodation request. This email address is reserved for candidates with disabilities only. General application inquiries will not receive a response. (remove as boilerplate/application instruction) We need to remove the disability accommodation request lines (application instructions). Also remove the core values and diversity statements? They are not boilerplate? They are company culture statements; could be considered part of Benefits? Might be considered fluff but still substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Core values and diversity statements are not exactly EEO boilerplate; they are cultural. Might keep? But they are somewhat generic; but they are part of "What We Offer". Might keep as a short paragraph under Benefits? However they are not benefits per se. Could be placed under a separate section like "Culture" but not in allowed headings. Since we only allowed headings list, we could incorporate them into Benefits or maybe under About the role. Safer to keep them as a paragraph under Benefits? But they'd be misfit. Perhaps we can omit them as they are not strictly required; but we must preserve ALL substantive information. Are they substantive? They describe culture, values. Might be considered substantive. However the instruction says prefer a few substantive sections over many thin ones. We could include them under Benefits as a paragraph about culture and values. Or we could create a separate section but not allowed headings. So we will include them in Benefits. Now we need to avoid duplication: The benefits about stock appear both in "What We're Looking For" and "What We Offer". We should not duplicate. We'll include stock info only once under Benefits. Now schedule: 4-day work week, most Fridays off. Pay: Competitive salary (we leverage market data). Now Benefits: list: stock ownership, RSU awards, employee stock purchase plan, flexible PTO + 13 holidays, paid sabbatical after 3 years, generous parental leave, medical/dental/vision/401k/life/disability insurance, core values and diversity statements (maybe as paragraph). Also note about visa sponsorship not eligible (maybe as a short p under Requirements? Could be a note). We'll include as a short p under Requirements maybe. Now we need to ensure we don't include any application instructions: the disability support email lines must be removed. Now produce HTML fragment. Structure:

    About the role

    ThredUp is transforming resale with technology and a mission to inspire the world to think secondhand first. By making it easy to buy and sell secondhand, ThredUp has become one of the world's largest online resale platforms for apparel, shoes and accessories. Sellers love ThredUp because we make it easy to clean out their closets and unlock value for themselves or for the charity of their choice while doing good for the planet. Buyers love shopping value, premium and luxury brands all in one place, at up to 90% off estimated retail price. Our proprietary operating platform is the foundation for our managed marketplace and consists of distributed processing infrastructure, proprietary software and systems and data science expertise. With ThredUp’s Resale-as-a-Service, some of the world's leading brands and retailers are leveraging our platform to deliver customizable, scalable resale experiences to their customers. ThredUp has processed over 172 million unique secondhand items from 55,000 brands across 100 categories. By extending the life cycle of clothing, ThredUp is changing the way consumers shop and ushering in a more sustainable future for the fashion industry. Recognized on TIME Most Influential Companies of 2023, Digiday's WorkLife 50 2023, TIME's Best Inventions of 2022, and Lattice's People Success Awards 2022.

    Responsibilities

    • As our first Senior Software Engineer for Agentic Commerce, you'll build the layer that makes 4 million unique secondhand items discoverable and transactable by AI shopping agents, and own how ThredUp shows up when someone asks an agent to find them a dress for a wedding.
    • Partner closely with engineering and product leadership to give the space shape — working out what's worth building, making the architectural decisions together, and getting real functionality in front of customers to learn from.
    • For the first stretch you'll be the primary engineer on this work, with broad ownership of how it comes together.
    • Design and build the agentic-commerce layer end to end — from exposing our catalog, pricing, and inventory to AI shopping agents through cart, checkout, and order handoff — defining the integration surface rather than inheriting one.
    • Own how ThredUp gets discovered and surfaced by LLM-driven shopping agents, including the structured data that makes 4M+ unique, single-SKU items legible to machines.
    • Prototype quickly against

Similar jobs