Front End Engineer Interview Experience - Seattle, Washington
Process
My timeline was very weird, so I'll put it in bullet points:
- Applied in July for an L4 position.
- Reached out to by a recruiter in August, was leveled up to an L5 position, and was asked for interview availability for a phone screen round (30 min behavioral - 30 min tech).
- Took 3 weeks to get my interview scheduled for the beginning of September. I cruised through the coding problem and had a lot of chemistry with the interviewer.
- A week after this interview, I was told they were no longer hiring for the position and received no additional info.
- The next day, another recruiter called me to schedule a virtual on-site for another team for an L4 role.
- A week later, I was told someone was hired before I could even schedule the interview.
- A few days later, I heard from another recruiter who wanted to schedule me for a virtual on-site, which we ended up scheduling for 3 weeks after.
- Had 2 interviews on Day 1 and 2 more on Day 2 as follows:
- Interview 1 (30 min behavioral - 30 min tech)
- Interview 2 (Bar raiser - completely behavioral)
- Interview 3 (30 min behavioral - 30 min tech)
- Interview 4 (20 min behavioral - 40 min tech)
- Heard back a week later that I wouldn't be getting an offer (first of November - an insanely long process).
The Bar Raiser round was brutal because they grilled me with about 7 behavioral questions and 2-3 additional questions on top of each of those. If you have a round like this and don't come in with at least 15+ solid STAR stories prepared, you're done for. I had to repeat answers across my interviews because I was told that 8 stories was more than enough. The tech questions were a breeze for me, and they would be for any decent FEE because they were very focused on front-end-specific things. I definitely botched this because I didn't have enough stories for the behavioral portion and ended up repeating myself too much.
Difficult interview, but the experience wasn't the best because of the scheduling difficulties (I was very open, and they still had trouble) and the fact that they don't give feedback.
I can give vague descriptions of interview questions.
Questions
Write the querySelectorAll method in JS.
Display data of a given JSON object using vanilla JS and allow users to search.
Dynamically build a file tree from a nested JSON object.
BFS with TypeScript and return nodes with certain attribute values.
Was this helpful?
Interview Statistics
The following metrics were computed from 4 interview experiences for the Amazon Front End Engineer role in Seattle, Washington.
Success Rate
Amazon's interview process for their Front End Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Amazon's Front End Engineer interview process in Seattle, Washington.
Amazon Work Experiences
- 2.0A great learning experience, but troubling for upper managementFront End Engineer • Current EmployeeSeattle, Washington, United StatesFebruary 9, 2024Pros: My colleagues are at the top of their field. My direct management was phenomenal. They were competent, on top of things, and personable. A lot to learn, and very little handholding. Working for Amazon looks great on the resume.Cons: Once hired, treatment takes a turn for the worse. Poor or no raises, even with stellar reviews. It's not uncommon to end with compensation less than you started. Very difficult and lots of bureaucracy to get promoted. Layoffs dropped out of the blue, despite the department turning a strong profit. The rest of the staff is required to pick up the slack. Anything HR or the recruiters promised you, forget it. Even if you have an agreement in writing, don't expect them to honor it. Tight deadlines while understaffed. Expected to have a full, functioning product before the requirements are fleshed out. Your management is partially in place to prevent you from addressing concerns to anyone who can actually do anything.
- 4.0Smart Problems, Dumb RtoFront End Engineer • Current EmployeeSeattle, Washington, United StatesAugust 27, 2023Pros: Smart people, interesting problems, good management.Cons: RTO is dumb and doesn’t fall in line with striving to be Earth’s best employer.
- 3.0Great for developers looking to learn and be challenged, but poor work-life balanceFront End Engineer • Former EmployeeSeattle, Washington, United StatesAugust 4, 2023Pros: Working with smart people on large projects. A lot of learning and growth opportunity. A strong culture that teaches very valuable skills.Cons: There is no avenue to address poor management. There can be a PIP culture in some orgs. Teams can have very disorganized processes, and there can be poor communication between PMs and devs.
Amazon Interview Questions
