I've liked every engineer I've worked with.
We had layoffs and no one dares talk about it for fear of being put on the list for next time. Budget cuts on silly parties and things came way too late, and they've even brought back some of that less than a year after firing 70+ people.
Management doesn't know how to measure engineering performance and it shows. Some people get promoted for just showing up and some people work like crazy and never get promoted. Engineers have slowly been moving more and more to adding extra time-wasting processes to everything we do just so they can put it on their performance review.
Engineering experts take no responsibility for the extra work they give to junior engineers, only credit for "mentoring" them. When people misunderstand the senior engineers, it's their own fault for not asking more questions.
Our value statements are no longer about what we prefer in Lucid employees, they're just an excuse to penalize people who speak up against unfair practices.
Lucid leadership constantly tells us that our pay is competitive, but they hold back promotions from people who are obviously taking on more responsibility than their title implies. Also, a quick search on LinkedIn will tell you that our pay is falling far behind what other companies offer. For some reason, HR refuses to hire from states that require companies post the pay range on job postings, and I think it's pretty clear why.
Transparency, transparency, transparency. Either tell us what our numbers have to be to be promoted, or stop telling us that our promotions are based on merit. Tell us what the pay range is for our roles. Tell us when our performance is not adequate so we can do something about it. Keep the budget cuts, engineers don't need to be flown across the country for parties; engineers need to pay bills.
First round was a HackerRank challenge - just one question that is supposed to take about an hour. You have 7 days to send the zip of the code but the challenge is open for 10 days from when you start.
Technical interview is difficult. Did the first round which consisted of a few questions that I hammered out in under 5 mins total and then a larger problem which you are not expected to finish but has multiple parts. I recommend making sure that yo
First round is an OA, second round was 2 LeetCode easy and game implementation, third round was algorithm + class design. The OA contains 4 questions and you complete these questions within 75 minutes.
First round was a HackerRank challenge - just one question that is supposed to take about an hour. You have 7 days to send the zip of the code but the challenge is open for 10 days from when you start.
Technical interview is difficult. Did the first round which consisted of a few questions that I hammered out in under 5 mins total and then a larger problem which you are not expected to finish but has multiple parts. I recommend making sure that yo
First round is an OA, second round was 2 LeetCode easy and game implementation, third round was algorithm + class design. The OA contains 4 questions and you complete these questions within 75 minutes.