Dropbox
Remote work with intentional meetups
Virtual First makes remote work the default, with planned in-person collaboration. Ask about core hours, travel, and your approved work location.
Read employer policy ↗THE NEXT CHAPTER / EMPLOYER RESEARCH
Compare NYC & SF employers by work-life balance, pay, and office days.
Checked Oct 26–28, 2026 · Research snapshot
THE DIRECTORY
55 of 55 employers · Ratings / 5 · USD/year
Pay in USD/year. ~ means a posting estimate: mean of each distinct engineering role/pay band’s midpoint, across US locations and levels. These estimates exclude equity, are not employee medians or senior-only pay, and do not change with the city filter. Expand a company for every source and the calculation. Verified senior medians are preserved.
| WLB rank | Company / sources | Founded | Work mode / office days | Work-life balance | Senior eng median TC | Salary median / posting avg | Pay & benefits rating | Career growth | Senior management | Total company reviews |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | PlaidSmall review poolFounded: 2013. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: Standardized senior engineer band. Salary samples: Not verified. Source updated: October 19, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: How does your team protect focus time during bank integrations and launches? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2013 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.4 | $500K ↗US · Levels.fyiUpdated October 19, 2026 | —Base not verified | 4.0 | 4.1 | 4.0 | 202 |
| 2 | DropboxFounded: 2007. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Remote-first. Regular offsites; no weekly count. Remote work with core collaboration hours, on-demand workspaces, community events, and regular offsites. Confirm team travel and location requirements. Work-mode scope: Virtual First policy. Checked 2026-10-26. Work-mode source ↗ Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 106. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What are the core collaboration hours and required travel costs for this remote role? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2007 ↗ | Remote-first ↗Regular offsites; no weekly countEmployer policy · see details | 4.2 | $390K ↗US · GlassdoorUpdated Apr 10, 2025 | $230KSenior median base | 4.6 | 3.5 | 3.1 | 1,636 |
| 2 | Founded: 1998. Founding-year source ↗ Front-end interview typesCandidate report · Frontend Developer; United States; one anonymous account
Take-home: Not reported; the account describes a timed screening assessment. Self-reported 30-minute task, not an employer-wide standard. React and the final-loop format are not verified. Read candidate account ↗ · Source dated 2024-12-19 · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: L5 / Senior SWE. Salary samples: Not verified. Source updated: October 26, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Which product will I join, and how often do launch deadlines or on-call interrupt evenings? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 1998 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.2 | $437K ↗US · Levels.fyiUpdated October 26, 2026 | —Base not verified | 4.5 | 4.1 | 3.8 | 51,103 |
| 2 | SpotifyFounded: 2006. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Remote / hybrid. Days vary by role. Most roles offer home or office options within eligible regions and time zones. The employer confirms the work mode for the specific role before joining. Work-mode scope: Work From Anywhere policy. Checked 2026-10-26. Work-mode source ↗ Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 114. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): Application, interviews, and decision. The general employer guide does not establish a fixed senior-engineer round count. Request your role-specific itinerary before scheduling. Interview role / scope: General hiring; role-dependent. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: Which Work From Anywhere options apply to this role, and how are promotions evaluated? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2006 ↗ | Remote / hybrid ↗Days vary by roleEmployer policy · see details | 4.2 | $325K ↗US · GlassdoorUpdate date not reported | $220KSenior median base | 3.7 | 3.3 | 3.3 | 1,799 |
| 2 | TwilioFounded: 2008. Investor FAQ: founded 2008; headquarters San Francisco, CA. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Which product will I join, and how often do incidents interrupt evenings? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2008 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.2 | —US median unverified | —Base not verified | 4.2 | 3.5 | 3.3 | 2,110 |
| 6 | AdobeFounded: 1982. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 392. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Do company breaks fully cover this team, or is support coverage still required? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 1982 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.1 | $275K ↗US · GlassdoorUpdated Apr 10, 2025 | $192KSenior median base | 4.1 | 3.8 | 3.4 | 10,267 |
| 6 | AsanaFounded: 2008. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Hybrid. Mon, Tue, Thu · Fri varies. Three standard office days. Wednesday is generally optional WFH; Friday WFH depends on work and partner teams, so this is not a guarantee of only three office days. Work-mode scope: NYC · Staff Software Engineer, AI Developer Experience. Checked 2026-10-26. Work-mode source ↗ Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 51. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What does the first 90 days look like, and how have team priorities changed recently? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2008 ↗ | Hybrid ↗Mon, Tue, Thu · Fri variesCited role · see details | 4.1 | $323K ↗US · GlassdoorUpdated Apr 10, 2025 | $222KSenior median base | 4.1 | 3.6 | 3.3 | 976 |
| 6 | BloombergFounded: 1981. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 3,421. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: How do promotions work in this team, and what are its support or market-hours obligations? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 1981 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.1 | $250K ↗US · GlassdoorUpdated Apr 10, 2025 | $214KSenior median base | 4.0 | 3.7 | 3.4 | 8,487 |
| 6 | EtsyFounded: 2005. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 96. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What flex-work mode applies, and how many people actually take extended time off? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2005 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.1 | $203K ↗US · GlassdoorUpdate date not reported | $166KSenior median base | 3.8 | 3.4 | 3.1 | 574 |
| 6 | LyftMixed workforceFounded: 2012. Lyft's operating business dates to 2012; its predecessor Zimride dates earlier. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Mixed workforce: company reviews may include retail, warehouse, driver, delivery, or support roles; not a corporate-only score. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 167. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Can you share corporate-team feedback separately from driver reviews? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.1 | $380K ↗US · GlassdoorUpdated Apr 10, 2025 | $228KSenior median base | 3.6 | 3.4 | 3.0 | 2,183 |
| 6 | SquarespaceFounded: 2003. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 148. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What is the promotion path, and which roles are actually open in NYC? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2003 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.1 | $240K ↗US · GlassdoorUpdate date not reported | $191KSenior median base | 3.4 | 3.3 | 3.0 | 562 |
| 12 | AirbnbFounded: 2007. Uses Airbnb's stated 2007 origin; legal incorporation and public launch followed in 2008. Founding-year source ↗ Front-end interview typesCandidate report · Front End Engineer; United States; one anonymous account
Take-home: Not reported. Candidate expected front-end concepts but encountered algorithms. One historical screen does not establish the complete or current loop. Read candidate account ↗ · Source dated 2025-05-05 · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Remote / office option. Flexible · in-person gatherings. Flexibility depends on regulatory and role eligibility. Team gatherings still apply; a fixed weekly office-day requirement is not established by the cited page. Work-mode scope: Live and Work Anywhere policy. Checked 2026-10-26. Work-mode source ↗ Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 344. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What gatherings are mandatory, and does Live and Work Anywhere apply to this specific role? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2007 ↗ | Remote / office option ↗Flexible · in-person gatheringsEmployer policy · see details | 4.0 | $506K ↗US · GlassdoorUpdated Apr 10, 2025 | $246KSenior median base | 4.2 | 3.5 | 3.5 | 2,417 |
| 12 | DuolingoSmall review poolFounded: 2011. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 38. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): Recruiter conversation, pre-onsite sessions, and a virtual onsite with multiple interviews that may span several days. No universal count: technical video interview 60 min, pair programming 75 min, code review 60 min, and design 60 min are possible session types. Online tasks and whiteboard sessions described for university roles do not establish senior requirements. Interview role / scope: Engineering; plan differs by role. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: Is this a NYC role, and how are experimentation deadlines balanced with normal working hours? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2011 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.0 | $329K ↗US · GlassdoorUpdated Apr 10, 2025 | $209KSenior median base | 4.0 | 3.8 | 3.4 | 172 |
| 12 | NotionSmall review poolFounded: 2013. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: Standardized senior engineer band. Salary samples: Not verified. Source updated: October 19, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Which days are expected in office, and how does the team handle release-week workload? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2013 ↗ | UnverifiedDays not verifiedAsk recruiter | 4.0 | $600K ↗US · Levels.fyiUpdated October 19, 2026 | —Base not verified | 4.5 | 3.9 | 3.7 | 340 |
| 15 | AirtableSmall review poolFounded: 2012. Employer about page: started in 2012. San Francisco HQ listed at 1 Front Street, Floor 28. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Which office is this role tied to, and what are the core hours? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.9 | —US median unverified | —Base not verified | 4.2 | 3.6 | 3.1 | 257 |
| 15 | ChimeSmall review poolFounded: 2012. Employer about page: co-founders started in 2012. Listed address 101 California Street, Floor 5, San Francisco. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Which days are spent at 101 California, and how is on-call staffed? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.9 | —US median unverified | —Base not verified | 3.8 | 3.2 | 2.6 | 320 |
| 15 | DatadogFounded: 2010. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: A US senior-engineer median was not verified; the accessible source did not confirm the geography. No estimate substituted. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-26. Posted engineering salary: $236K average of 3 distinct role/pay bands. Unweighted mean of advertised range midpoints for distinct US engineering role/pay bands. Levels vary; this is not an employee median, senior-only salary, actual offer average, or total compensation. Equity and OTE ranges are excluded. Duplicate role/pay bands are counted once. NYC/Boston posting sample · senior + staff. Posted annual salary; excludes equity. Checked 2026-10-26. Levels: Senior, Staff / principal. Mean of (published minimum + published maximum) / 2, one equally weighted observation per distinct role/pay band. Board / research source ↗ Salary postings & calculation (3)
General hiring process (not front-end-specific): Initial recruiter or hiring-manager screen; face-to-face interviews may include multiple rounds or panels. Some roles add take-home work or an executive interview. No fixed round count is published on this page. The six listed process stages include selection and a survey, which are not interviews. At least one step is expected in person. Interview role / scope: Role-dependent hiring. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: How many pages did this team receive outside office hours last month? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2010 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.9 | —US median unverified | ~$236K ↗Posted salary avg · US3 role/pay bands · mixed levelsEstimate · not a median | 3.8 | 3.8 | 3.7 | 1,698 |
| 15 | MicrosoftFounded: 1975. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: 63 / Senior SDE. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): Technical sessions assess problem solving, coding, design, testing, and role-related experience. The guide references 45-minute rounds. Session duration is not a round count. Confirm the team-specific number, system-design expectations, and interview format. Interview role / scope: Technical roles. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: What are the actual office days and on-call load for this org? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 1975 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.9 | $232K ↗US · Levels.fyiUpdate date not reported | —Base not verified | 3.8 | 3.7 | 3.3 | 55,001 |
| 15 | SamsaraFounded: 2015. Employer post: founded in San Francisco in 2015. About page lists headquarters at 1 De Haro St, San Francisco. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: What hours did the team work last week, and how many days are required at 1 De Haro? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2015 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.9 | —US median unverified | —Base not verified | 3.8 | 3.8 | 3.6 | 1,465 |
| 15 | WebflowSmall review poolFounded: 2013. Employer about page: started in 2013. San Francisco office at 398 11th Street is from Built In SF, a directory listing rather than an employer filing. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Is this role remote, and how many in-person days does the team actually keep? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2013 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.9 | —US median unverified | —Base not verified | 3.8 | 3.1 | 2.9 | 169 |
| 21 | DiscordSmall review poolFounded: 2012. Employer timeline starts the studio in April 2012. Discord the product shipped in May 2015. Year stored is the operating-business origin. Legal address: 444 De Haro Street, Suite 200, San Francisco. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: What hours did this team work last week, and which days are spent at 444 De Haro? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.8 | —US median unverified | —Base not verified | 3.8 | 3.5 | 3.2 | 252 |
| 21 | DocuSignFounded: 2003. Employer corporate profile: established 2003; headquarters 221 Main Street, Suite 1000, San Francisco. The company began in the Seattle area and later moved its headquarters. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: How many days does this team spend in the San Francisco office? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2003 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.8 | —US median unverified | —Base not verified | 3.9 | 3.4 | 3.1 | 3,693 |
| 21 | GitHubSmall review poolFounded: 2008. Operating origin February 2008. A 2015 SEC Form D lists a later Delaware incorporation year of 2012 and a principal office at 88 Colin P. Kelly Street, San Francisco; that incorporation year is not used. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Is this a GitHub role, and what are the San Francisco office expectations? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2008 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.8 | —US median unverified | —Base not verified | 4.1 | 3.3 | 2.8 | 488 |
| 21 | OktaFounded: 2009. S-1: founded in 2009, incorporated as Saasure Inc. and later renamed Okta, Inc. Principal office cited at 301 Brannan Street, San Francisco. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: How many office days does this team keep, and who covers after-hours security incidents? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2009 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.8 | —US median unverified | —Base not verified | 4.1 | 3.4 | 3.1 | 1,712 |
| 21 | Founded: 2008. Investor FAQ gives October 2008; the product launched later. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 86. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): Initial recruiter and hiring-manager conversations, followed by competency-based interviews with the team and cross-functional partners. The general guide does not give a fixed session count. Published intern/new-grad counts are not used as senior-engineer estimates. Interview role / scope: General hiring; not a senior-specific plan. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: What are the team-specific attendance and promotion expectations? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2008 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.8 | $347K ↗US · GlassdoorUpdated Apr 10, 2025 | $220KSenior median base | 4.2 | 3.3 | 2.7 | 1,046 |
| 21 | RedditSmall review poolFounded: 2005. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 129. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Does this role cover live incidents or moderation escalations after hours? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2005 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.8 | $261K ↗US · GlassdoorUpdate date not reported | $201KSenior median base | 4.3 | 3.6 | 2.9 | 357 |
| 21 | SalesforceFounded: 1999. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 819. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: How stable is the team charter, and what does internal mobility require? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 1999 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.8 | $265K ↗US · GlassdoorUpdate date not reported | $189KSenior median base | 4.3 | 3.8 | 3.5 | 23,199 |
| 28 | AffirmFounded: 2012. Employer history: started March 14, 2012 in San Francisco. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: What does a normal week look like around product launches and credit deadlines? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.7 | —US median unverified | —Base not verified | 4.4 | 3.5 | 3.2 | 641 |
| 28 | BrexFounded: 2017. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 71. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Which office cadence and first-year success targets apply to this role? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2017 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.7 | $242K ↗US · GlassdoorUpdated Apr 10, 2025 | $199KSenior median base | 4.0 | 3.7 | 3.5 | 619 |
| 28 | Founded: 2002. Company began in 2002; LinkedIn launched publicly in May 2003. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 2,393. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What is the team roadmap and what happened to people seeking promotion last cycle? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2002 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.7 | $329K ↗US · GlassdoorUpdate date not reported | $208KSenior median base | 3.9 | 3.2 | 3.0 | 7,879 |
| 28 | MongoDBFounded: 2007. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 119. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What is the escalation rotation, and are sales targets or engineering goals realistic for new hires? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2007 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.7 | $264K ↗US · GlassdoorUpdated Apr 10, 2025 | $194KSenior median base | 4.0 | 3.9 | 3.6 | 2,603 |
| 32 | AppleMixed workforceFounded: 1976. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Mixed workforce: company reviews may include retail, warehouse, driver, delivery, or support roles; not a corporate-only score. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 1,015. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Is this corporate or retail work, and what are the launch-period or shift expectations? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 1976 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.6 | $375K ↗US · GlassdoorUpdated Apr 10, 2025 | $221KSenior median base | 4.2 | 3.7 | 3.5 | 43,645 |
| 32 | CheckrSmall review poolFounded: 2014. Y Combinator company profile: founded 2014, location San Francisco. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: What hours did this team work last month, and is the role based at the San Francisco office? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2014 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.6 | —US median unverified | —Base not verified | 3.6 | 3.3 | 3.0 | 449 |
| 32 | SnowflakeFounded: 2012. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: Standardized senior engineer band. Salary samples: Not verified. Source updated: October 19, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Where is the actual worksite? Bay Area locations may be outside San Francisco city. What is on-call like? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.6 | $550K ↗US · Levels.fyiUpdated October 19, 2026 | —Base not verified | 4.1 | 3.6 | 3.3 | 1,130 |
| 35 | FlexportFounded: 2013. Y Combinator profile: founded 2013, location San Francisco. Employer office list includes 100 California Street, Floor 5, San Francisco. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Is this role at the San Francisco office, and how often do shipment issues create after-hours work? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2013 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.5 | —US median unverified | —Base not verified | 3.8 | 3.5 | 3.1 | 1,210 |
| 35 | InstacartMixed workforceFounded: 2012. Employer press release: founded in San Francisco in 2012. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Mixed workforce: company reviews may include retail, warehouse, driver, delivery, or support roles; not a corporate-only score. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Which team is this, and do shopper operations change the hours or on-call for the role? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.5 | —US median unverified | —Base not verified | 3.7 | 3.3 | 3.0 | 1,913 |
| 35 | Oscar HealthFounded: 2012. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 42. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What are the workload peaks around enrollment, and which promotion opportunities exist? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.5 | $258K ↗US · GlassdoorUpdate date not reported | $192KSenior median base | 3.3 | 2.8 | 2.6 | 936 |
| 35 | YelpFounded: 2004. Employer fast facts: founded in San Francisco in 2004. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; sales roles are a large share of the pool, and your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: Is this a sales-quota role or a product role, and what hours did that team work last month? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2004 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.5 | —US median unverified | —Base not verified | 3.1 | 3.2 | 3.0 | 6,020 |
| 39 | DatabricksFounded: 2013. Founding-year source ↗ Front-end interview typesEmployer guide · Front-End / Full-Stack Software Engineer; not the back-end track
Take-home: Not stated in the front-end track. Use the Front-End/Full-Stack section, pages 3–4. Algorithm rounds listed for back-end candidates are not imported here. Employer front-end guide ↗ · Source dated 2025-04 · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: Standardized senior engineer band. Salary samples: Not verified. Source updated: October 19, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): Recruiter screen (30 min), technical screen (60 min), team matching, then 4–6 panel interviews (60 min each). Final-loop count excludes screens, internal committee, references, and offer. Backend topics include coding, algorithms, systems, architecture, domain depth, and cross-functional work. Interview role / scope: Engineering; backend panel illustrated. Guide dated 2025-04. Checked 2026-10-26. Employer guide ↗ Ask the team: What deadlines define success in the first 90 days, and how are incidents staffed? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2013 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.4 | $588K ↗US · Levels.fyiUpdated October 19, 2026 | —Base not verified | 4.3 | 4.0 | 3.7 | 1,697 |
| 39 | GustoFounded: 2011. Founded as ZenPayroll; later renamed Gusto. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 38. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: How does the team manage payroll deadlines and year-end workload peaks? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2011 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.4 | $271K ↗US · GlassdoorUpdate date not reported | $202KSenior median base | 3.3 | 2.8 | 2.6 | 1,160 |
| 39 | HubSpotFounded: 2006. Uses HubSpot's own founding year; its legal predecessor was formed in 2005. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 364. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Is this role eligible for remote work in my state, and what are the team core hours? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2006 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.4 | $287K ↗US · GlassdoorUpdated Apr 10, 2025 | $206KSenior median base | 3.6 | 3.3 | 3.0 | 4,361 |
| 42 | CloudflareFounded: 2009. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: A US senior-engineer median was not verified; the accessible source did not confirm the geography. No estimate substituted. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-26. Posted engineering salary: $241K average of 2 distinct role/pay bands. Unweighted mean of advertised range midpoints for distinct US engineering role/pay bands. Levels vary; this is not an employee median, senior-only salary, actual offer average, or total compensation. Equity and OTE ranges are excluded. Duplicate role/pay bands are counted once. New York salary tiers · senior + staff sample. Posted annual salary; excludes equity. Checked 2026-10-26. Levels: Senior, Staff / principal. Mean of (published minimum + published maximum) / 2, one equally weighted observation per distinct role/pay band. Board / research source ↗ Salary postings & calculation (2)
General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What are the overnight incident rate, follow-the-sun handoffs, and recovery-time policy? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2009 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.3 | —US median unverified | ~$241K ↗Posted salary avg · US2 role/pay bands · mixed levelsEstimate · not a median | 3.5 | 3.1 | 2.6 | 1,074 |
| 42 | DoorDashMixed workforceFounded: 2013. Founding-year source ↗ Front-end interview typesEmployer guide · Web technical phone screen only; not a verified full loop
Take-home: Not stated; this source describes a live screen. Undated web-screen PDF describes roughly 45 minutes of coding in CodeSandbox. DoorDash announced engineering interview changes in 2026; confirm whether this web format still applies. Employer front-end guide ↗ · Source undated · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Mixed workforce: company reviews may include retail, warehouse, driver, delivery, or support roles; not a corporate-only score. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 81. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): Recruiter call (30 min), coding technical screen (60 min for most roles), then a virtual onsite covering coding, systems design, and behavioral topics. The page labels the technical screen Round 1 and the onsite Round 2, but does not give the number of separate onsite sessions. Ask for the level-specific itinerary. Interview role / scope: Software engineering. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: What are the corporate team incident expectations and mandatory field activities? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2013 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.3 | $392K ↗US · GlassdoorUpdated Apr 10, 2025 | $239KSenior median base | 3.5 | 3.3 | 2.9 | 4,948 |
| 42 | FigmaSmall review poolFounded: 2012. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 14. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: How do launch deadlines affect the team, and how much time is protected for craft and development? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.3 | $216K ↗US · GlassdoorUpdate date not reportedOnly 14 salary reports | $180KSenior median base | 3.9 | 3.4 | 3.2 | 229 |
| 42 | StripeFounded: 2010. Uses co-founder Patrick Collison's stated 2010 start; some directories list 2009. Founding-year source ↗ Front-end interview typesCandidate report · Frontend Engineer; United States; one anonymous account
Take-home: Not reported. Older 2022 account; confirm current relevance. Candidate describes a screen and onsite exercises, not an employer-approved question bank. Read candidate account ↗ · Source dated 2022-03-01 · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 117. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): Most processes include a recruiter screen, technical or skills-based assessment, then team interviews. The employer FAQ says timing and process vary by role, level, and location; no fixed number of interview sessions is published. Interview role / scope: General hiring; role-dependent. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: Is the role in San Francisco, South San Francisco, or NYC? What is its incident rotation? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2010 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.3 | $392K ↗US · GlassdoorUpdated Apr 10, 2025 | $217KSenior median base | 4.3 | 3.6 | 3.3 | 1,403 |
| 42 | UberMixed workforceFounded: 2009. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Mixed workforce: company reviews may include retail, warehouse, driver, delivery, or support roles; not a corporate-only score. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 5,066. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: Can I speak with corporate teammates about their hours, separate from driver experiences? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2009 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.3 | $340K ↗US · GlassdoorUpdated Apr 10, 2025 | $200KSenior median base | 3.6 | 3.2 | 3.0 | 16,526 |
| 47 | AtlassianFounded: 2002. Company origin, not the 2022 US parent incorporation. Founding-year source ↗ Front-end interview typesEmployer guide · Frontend engineering; P30–P50 guide
Take-home: Not stated; guide describes live coding. Older employer guide: confirm the current loop. Local IDE or arranged CodePair; testing and debugging are encouraged. Employer front-end guide ↗ · Source dated 2023-12 · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Remote / office option. Office optional · team gatherings. Work location depends on legal-entity, work-rights, time-zone, and role eligibility. Confirm intentional team gatherings and any role-specific office requirement. Work-mode scope: Team Anywhere policy. Checked 2026-10-26. Work-mode source ↗ Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 220. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): Two coding sessions (60 min each), system design (60 min), management (60 min), and values (45 min). Five interview sessions counted from the frontend guide across three stages; recruiter conversations excluded. Other engineering specialisms and levels can differ. Interview role / scope: Frontend engineering P30–P50. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: Which location is approved, and what are the performance review and time-zone expectations? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2002 ↗ | Remote / office option ↗Office optional · team gatheringsEmployer policy · see details | 3.2 | $311K ↗US · GlassdoorUpdated Apr 10, 2025 | $208KSenior median base | 4.2 | 3.1 | 2.4 | 3,781 |
| 47 | Scale AISmall review poolFounded: 2016. Employer about page: founded 2016; headquarters San Francisco, CA. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-28. Senior pay evidence: No verified senior-engineer median. Advertised job ranges are not substituted for a median. Role / level: Senior Software Engineer. Salary samples: Not verified. Source updated: Not reported. Checked 2026-10-28. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-28. Ask the team: What hours did this team work last week, and how are launch weeks staffed? Glassdoor rating source ↗ Checked 2026-10-28. Confirm exact worksite and role requirements before applying. | 2016 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.2 | —US median unverified | —Base not verified | 3.9 | 4.0 | 3.4 | 443 |
| 49 | AmazonMixed workforceFounded: 1994. Founded before the online store opened in 1995. Founding-year source ↗ Front-end interview typesEmployer guide · Front-End Engineer; level and location may vary
Take-home: Not stated; an online assessment is documented, which is not the same as an app take-home. Employer describes an online assessment, live technical screen and final loop. React specifically is not required by this guide. Employer front-end guide ↗ · Source undated · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Mixed workforce: company reviews may include retail, warehouse, driver, delivery, or support roles; not a corporate-only score. Work arrangement: On-site. 5 days/week. Policy announced in September 2024, effective January 2025; exceptions and approved remote arrangements can apply. Confirm the current requirements for your offer. Work-mode scope: Corporate office policy. Checked 2026-10-26. Work-mode source ↗ Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Development Engineer. Salary samples: 535. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): Technical phone screen (60 min), then five final interviews (55 min each). Final-loop count excludes the technical screen and recruiter conversations. Prepare coding, system design, and Leadership Principles examples. Interview role / scope: Senior SDE / SDE III. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: Can I see corporate engineering feedback, and how many incidents does this team handle per week? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 1994 ↗ | On-site ↗5 days/weekEmployer policy · see details | 3.1 | $336K ↗US · GlassdoorUpdated Apr 10, 2025 | $196KSenior median base | 3.8 | 3.6 | 3.0 | 212,480 |
| 49 | RipplingFounded: 2016. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 50. Source updated: Apr 10, 2025. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What hours do successful teammates actually work, and what happens when a deadline is missed? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2016 ↗ | UnverifiedDays not verifiedAsk recruiter | 3.1 | $306K ↗US · GlassdoorUpdated Apr 10, 2025 | $218KSenior median base | 3.9 | 3.9 | 3.4 | 1,284 |
| 51 | RampSmall review poolFounded: 2019. Founding-year source ↗ Front-end interview typesCandidate report · Frontend Software Engineer; United States; one anonymous account
Take-home: Reported React assignment; one candidate said it took under an hour. This is not an employer time limit. Self-reported historical experience, hosted on Taro; not employer confirmation or a guarantee for another team. Read candidate account ↗ · Source dated 2024-12-03 · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: Standardized senior engineer band. Salary samples: Not verified. Source updated: October 19, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What does a normal week look like in hours, and how are evening or weekend requests handled? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2019 ↗ | UnverifiedDays not verifiedAsk recruiter | 2.8 | $650K ↗US · Levels.fyiUpdated October 19, 2026 | —Base not verified | 4.3 | 4.1 | 3.6 | 222 |
| 52 | CoinbaseFounded: 2012. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Senior Software Engineer. Salary samples: 247. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): Repo-based coding/debugging and leadership/behavioral evaluation are live; AI-assisted system design is in early testing. The current engineering post does not publish a round count. Prepare to use AI tools, critique their output, and explain your decisions; do not assume older interview guides describe the current loop. Interview role / scope: Engineering; July 2026 redesign. Guide dated 2026-07-13. Checked 2026-10-26. Employer guide ↗ Ask the team: What availability is expected during market volatility, and which in-person gatherings are mandatory? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2012 ↗ | UnverifiedDays not verifiedAsk recruiter | 2.7 | $346K ↗US · GlassdoorUpdate date not reported | $222KSenior median base | 4.2 | 3.4 | 2.8 | 1,193 |
| 52 | MetaFounded: 2004. Founded as Facebook; renamed Meta in 2021. Founding-year source ↗ Front-end interview typesCandidate report · Frontend Engineer; United States; one anonymous account
Take-home: Not reported. The report does not explain the front-end exercise or specify React. Historical self-report, not an employer guide. Read candidate account ↗ · Source dated 2024-08-01 · Checked 2026-10-26 Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Company-wide reviews across roles and locations; your team may differ. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Glassdoor title-specific modeled pay estimate, not a company payroll median. Total pay includes reported additional pay; missing equity reports can understate total compensation. Titles do not establish equivalent levels across companies. Role / level: Sr. Software Engineer. Salary samples: 23. Source updated: Not reported. Checked 2026-10-26. General hiring process (not front-end-specific): Full loop: 4–6 conversations of about 45 minutes covering coding, design, and behavioral topics. Employer-authored guide hosted on a third-party CDN; publication date not stated. Confirm the latest role-specific loop, screens, and AI-tool rules with your recruiter. Interview role / scope: Software engineer full loop. Guide date not reported. Checked 2026-10-26. Employer guide · mirror ↗ Ask the team: What are the performance targets, office requirements, and recent team changes? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2004 ↗ | UnverifiedDays not verifiedAsk recruiter | 2.7 | $449K ↗US · GlassdoorUpdate date not reportedOnly 23 salary reports | $223KSenior median base | 4.5 | 3.6 | 2.6 | 18,917 |
| 54 | OpenAISmall review poolFounded: 2015. Original nonprofit founding, before later corporate restructuring. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Small review pool: fewer than 500 total company reviews; WLB respondent count is not published here. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: Standardized senior engineer band (L4). Salary samples: Not verified. Source updated: October 19, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): Introductory conversations, skills assessment, then final interviews generally lasting 4–6 hours with 4–6 people across 1–2 days. The guide gives hours and interviewer numbers, not a fixed number of separate rounds. Ask which assessments, tools, and preparation apply to your role. Interview role / scope: Role-dependent hiring. Guide date not reported. Checked 2026-10-26. Employer guide ↗ Ask the team: What are the expected hours during launches, weekend obligations, and protected recovery periods? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2015 ↗ | UnverifiedDays not verifiedAsk recruiter | 2.5 | $760K ↗US · Levels.fyiUpdated October 19, 2026 | —Base not verified | 4.4 | 4.1 | 3.6 | 122 |
| — | AnthropicFounded: 2021. Founding-year source ↗ Front-end interview typesUnverified · Front-end engineering; team / level not verified Algorithms / LeetCode, JavaScript, React / UI builds, front-end system design and live coding: not verified. Take-home: Not verified. No front-end-specific interview format verified in this research pass. General SWE guides, role requirements and React usage are not treated as interview evidence. Questions to ask your recruiterIs the coding screen algorithms, JavaScript utilities, or a UI build? Is React allowed or required? Is there a take-home, and what is the time budget? What tools, documentation and AI assistance are allowed? Does seniority change the design round? Unranked: a comparable company-wide WLB category score was not verified from the primary review source. Third-party estimates were excluded. Work arrangement: Unverified. Days not verified. Confirm the exact office, required days, and remote eligibility with the recruiter. Work-mode scope: Role / team not verified. Checked 2026-10-26. Senior pay evidence: Source-reported median for a standardized senior level; includes equity and bonus. Senior-band salary sample count and base-only median were not verified. Role / level: Standardized senior engineer band (Lead Software Engineer). Salary samples: Not verified. Source updated: October 19, 2026. Checked 2026-10-26. General hiring process (not front-end-specific): A role-specific interview plan has not been verified for this directory. Ask the recruiter for the total live sessions, screens, final-loop breakdown, take-home hours, allowed AI tools, and expected timeline. Interview role / scope: Senior software engineering. Guide date not reported. Checked 2026-10-26. Ask the team: What are the normal weekly hours, launch-period expectations, and required office days? Glassdoor rating source ↗ Checked 2026-10-26. Confirm exact worksite and role requirements before applying. | 2021 ↗ | UnverifiedDays not verifiedAsk recruiter | —Unverified | $888K ↗US · Levels.fyiUpdated October 19, 2026 | —Base not verified | — | — | — | Not verified |
NYC includes Brooklyn. SF means San Francisco city; nearby campuses are not automatically included. Work modes and office days are scoped to the cited role or policy, not every employee; expand a company for details. “On-site” alone does not establish five days/week. Some employers also hire remotely; check each listing. A low score is a prompt for further questions, not a verdict on every team.
BEYOND THE RATING
Dropbox
Virtual First makes remote work the default, with planned in-person collaboration. Ask about core hours, travel, and your approved work location.
Read employer policy ↗Airbnb
Live and Work Anywhere allows home or office work and moves within the country of employment without a location pay change. International work needs approval; team gatherings remain part of the model.
Read employer policy ↗Spotify
Work From Anywhere options are specified by role. The recruiter should confirm the locations and work modes available for your offer.
Read employer policy ↗Adobe
The 2026 US rewards guide lists company breaks for June 29–July 3 and December 24–31. Ask whether your team needs coverage during those periods.
Read employer policy ↗BEFORE YOU SAY YES
Use the ratings to choose where to look. Use these conversations to decide whether the actual offer fits your life.
What hours did the team work last week? How many evening or weekend incidents occurred last month, and who covers them?
Which exact office, how many required days, and who can change that requirement? Does my manager work in the same time zone?
How many days did teammates actually take last year? Ask for paid leave eligibility, waiting periods, health premiums, and dependent coverage in writing.
Get base, bonus target, vesting schedule, refresh policy, and sign-on repayment terms. Ask how private equity can be sold; do not treat paper equity as spendable cash.
Is this a replacement or new headcount? Why did the last person leave? What changed in the team over the past year? Ask to meet two future peers.
Who owns onboarding? What does success look like at 30, 60, and 90 days? Ask for a recent promotion example and the written review criteria.
Coverage can grow. For more employers, explore Built In NYC and Built In SF. Directory listings are discovery leads, not WLB evidence.