You get a cool project to work in a team of 2 (sometimes 3). These projects are often more interesting than the work that your mentor does day-to-day.
You participate heavily in the architectural design process and get to understand cutting-edge tools/techniques. On the application side, many interns worked with Kubernetes, ELK, and AWS. On the system side, interns have gotten to use cutting-edge compression, encryption, parsing, and replication techniques. This can feel a bit daunting, but your mentor and other team members are willing to help.
Managers are very reasonable with intern work hours. Even though you work on a challenging project, the expectations are rational.
If you're looking for a place to really grow through working on an open-ended, technically-interesting project, Pure Storage is a great place to consider. I personally feel like I was able to gain a lot of experience with project scoping, architectural design, and managing expectations that will hopefully help me later on if I reach more senior technical positions.
This is an opportunity to grow, but the lack of clarity may feel overwhelming, even with mentors around.
Overall, the engineering org as a whole tries to emphasize good communication, but it's not often that efficient (meetings can get sidetracked by the most powerful member(s) even in a mostly-flat org).
I wrote a lot here, but my rating is still 5*. An engineer-driven culture is mostly a good thing for many SWEs, and the problems that arise are tradeoffs.
Contacted by a recruiter. Talked to the founder to learn more about the company. Completed an online quiz, followed by a phone screen, and then an internal interview. Unlike many other interviews, where you spend a lot of time chatting about what yo
It's true! Just like other interviewees mentioned, it seems they are interviewing just for fun's sake or to train their engineers. I went onsite for a two-hour interview, one coding and another design. The coding question was purposely very hard. I
A recruiter reached out to me. The first round was a HackerRank link with two coding questions and ten multiple-choice questions. The coding questions were simple. Onsite interview #1 followed immediately, and then onsite interview #2. Two days la
Contacted by a recruiter. Talked to the founder to learn more about the company. Completed an online quiz, followed by a phone screen, and then an internal interview. Unlike many other interviews, where you spend a lot of time chatting about what yo
It's true! Just like other interviewees mentioned, it seems they are interviewing just for fun's sake or to train their engineers. I went onsite for a two-hour interview, one coding and another design. The coding question was purposely very hard. I
A recruiter reached out to me. The first round was a HackerRank link with two coding questions and ten multiple-choice questions. The coding questions were simple. Onsite interview #1 followed immediately, and then onsite interview #2. Two days la