Overall it went really well. I'd say 50% - 60% of my interviews followed the standard whiteboard style questions combined with some type of take home exam.
I interviewed with over 50 companies, reached onsites at about 30, rejected 10 myself, and was rejected by 10. I ended up with about 18 offers.
I'd say the curriculum and program helped, but ultimately so much of interviewing goes into how the interviewer is feeling at the moment. You can write the best, most well tested code or most optimal solution for an algorithm question, but if the interviewer just doesn't like you, you're hosed.
Overall I'm happy with the outcome of this process, and would probably engage in something similar if going through the interview process again.
In February 2020, I decided to get back on the job market after 5 years. I was really worried about my interviewing skills, knowing that after 5 years they weren't as sharp as I'd like. This is how I got back into interviewing shape.
oh I completely disagree, early employees are often not paid on day 1, and when they are paid, they still do bear a huge risk - often taking much lower salary than market for the opportunity of equity upside. The risk the early employee takes is often the same as the founder's, with less upside.
Does your platform accept early employees as well? The first 10 employees are essentially founders and while they typically do not receive as much of the upside as a founder, they do bear the same risk. Allowing an early employee to diversify that risk would be a huge value add to a much wider potential network.
I made carwala (https://www.carwala.co) - an easy and secure way for people to contact you if anything happens to your car.
You sign up with your phone number, add some details about your car and purchase a membership. We send you a high quality windshield decal that people can scan to contact you if you need to move your car, or if your car has been broken into, etc.
I got inspired a few weeks ago and had some spare time to hack on a side project.
Long story short, a few days after shelter in place started, my car brand new car was broken into. The back window was broken, and the car could've been sitting around for at least 3 days before we needed to use it again. My partner was devastated when she found the car in that condition.
I decided to make a windshield sticker that allows anyone to contact you to tell you if you need to move your car, or if your car has been broken into, without sharing your personal contact information.
Anyone can walk up to your car, scan the QR code on the sticker and push a button to contact you.
I hacked this together over the last week or so and would love to hear what y'all think.
I challenged myself over the last few weeks to ship something by the end of the year.
I've worked with Redis for a long time, and always wanted a faster way to access the keys in my instance, and profile what my instance was doing without having to spend time looking up commands in a CLI.
I built a quick tool to monitor things like memory usage, client connections, and keys/values and then visualize them over time.
The app is up and running, and in beta. Feel free to add your email to the waitlist and I'll get you up and running if you want to try it out.
AWS launched EKS on Fargate at Re:Invent this year. I wrote a post that explains how to spin up an EKS cluster on AWS Fargate and why I think EKS on Fargate will be a huge benefit for companies that don't have dedicated DevOps teams but want to modernize their deployments using a tool like Kubernetes. Comments and suggestions appreciated.
Sling Health (YC S19) (https://www.slinghealth.com) | Senior Software Engineer | San Francisco, CA | REMOTE | Full-Time
Sling Health is looking for a highly motivated full-time senior software engineer who wants to work on impactful problems in healthcare. Sling Health is changing the way medicine is practiced, by building out the technical infrastructure for medical operations for the largest geographically distributed team of remote healthcare workers.
Responsibilities:
- Contribute to and own meaningful parts of the technical and product roadmap
- Work alongside our operations and care coordination team to design and develop tools that meaningfully improve the quality of care we can deliver to our patients.
- Be a steward of quality, scalability, security and performance. You’ll be laying the foundation of our technical infrastructure.
- Design and architect new software systems, introduce new technologies as appropriate to support our future roadmap.
- Build and nurture our engineering culture.
What you would have built last month:
At Sling, you would have the opportunity to build tools that touch the entire lifecycle of the patient experience. Some projects you could’ve worked on last month include:
- A realtime messaging system between providers, patients and care coordinators
- A file upload service for provider documents
- An encrypted credential storage system for EMR credentials.
I interviewed with over 50 companies, reached onsites at about 30, rejected 10 myself, and was rejected by 10. I ended up with about 18 offers.
I'd say the curriculum and program helped, but ultimately so much of interviewing goes into how the interviewer is feeling at the moment. You can write the best, most well tested code or most optimal solution for an algorithm question, but if the interviewer just doesn't like you, you're hosed.
Overall I'm happy with the outcome of this process, and would probably engage in something similar if going through the interview process again.