You'll get a lot of ownership of a piece of their product right away and be expected to drive the development on your own. There are lots of opportunities to go watch robots execute the software you've written, which I found super exciting. Nimble definitely embraces the "move fast and break things" mantra in the best way.
Also, the office is in SoMa in San Francisco and is easy to commute to from most of SF by bike, bus, or car, which allows you to live in some beautiful neighborhoods.
Lots of folks work well over 40 hours a week (also kind of a pro; your coworkers will push you to be better and believe in the company's vision). Although honestly most people generally drew the line in the 50-60 hours a week range, which still allows you to have a life outside of work.
Things can feel disorganized at times with priorities shifting radically week to week. Again, I think this is quite common with tech startups.
Sometimes discussions devolved into the blame game instead of cooperating on a solution. It would be more productive to skip pointing fingers, I think.
Call with recruiter - Mike1 hr technical screen with Hiring ManagerTake Home (Quite time consuming actually - well over estimated 4hrs)1 Coding Round 1 Domain Technical1 System DesignCEO roundFeedback for each round was within a day or two
Recruiter call asked common behavioral questions and background. Next was a coding challenge to complete in 72 hrs. The prompt doesn't have clarity on what all things they expect in the code. Got a feedback within 1 hr of submitting the challenge, an
The process had 2 take home coding challenges to be completed in 3 days each. The 1st is a software challenge, and the 2nd is a robotics challenge. In the first challenge, you have to simulate a bouncing ball and share frames of the ball using a spec
Call with recruiter - Mike1 hr technical screen with Hiring ManagerTake Home (Quite time consuming actually - well over estimated 4hrs)1 Coding Round 1 Domain Technical1 System DesignCEO roundFeedback for each round was within a day or two
Recruiter call asked common behavioral questions and background. Next was a coding challenge to complete in 72 hrs. The prompt doesn't have clarity on what all things they expect in the code. Got a feedback within 1 hr of submitting the challenge, an
The process had 2 take home coding challenges to be completed in 3 days each. The 1st is a software challenge, and the 2nd is a robotics challenge. In the first challenge, you have to simulate a bouncing ball and share frames of the ball using a spec