Software Engineer, Frontend
Posted May 12, 2026·Open for 103 days (and counting)
Hiring for this role?
Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Function
Engineering
Seniority
Junior
Workplace
Hybrid
Location
US
Specialty
Frontend
Job Description
*This role supports US-based remote work, or Palo Alto, CA based hybrid in-office.
We’re looking for Software Engineers to join our team. As part of a cross-functional scrum team you will design and develop new products and features to help clients grow their wealth. In addition to building client facing features leveraging our in-house Design System components, you also work on improving our infrastructure and developer productivity and can have significant impact afforded by our cross-platform collaboration methods.
Audit details(provenance, verification trail, raw fields)
Core fields
Posting ID
wealthfront:a4a9fd4e-d33a-4767-995f-7a2286bc9762Title
Software Engineer, Frontend
Function
Engineering
Location
Palo Alto, CA
Workplace mode
hybrid
Posted at
2026-05-12 20:36:50Z
Compensation
undisclosed
Provenance
First seen (our tracker)
2026-08-11 12:15:05Z
Last seen
2026-08-23 12:30:15Z
Last updated
2026-08-23 12:30:15Z
Removed at
still open
Days open
Open for 103 days (and counting)
ATS adapter
lever
ATS slug
wealthfrontVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
LLM enrichment
Enriched at 2026-08-18 01:47:06Z. Enrichment runs once per posting, never re-runs.
Seniority
ic_l2
Role archetype
engineering
Specialty
frontend
Workplace mode
hybrid
City (normalized)
Palo Alto
Country (normalized)
United States
Comp range
—
Tech stack
—
Novel role archetype?
no
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.