Human drivers that are at fault face repercussions that affect the rest of their lives. Robot drivers that are at fault face repercussions of a minuscule fine and a "sorry... again" press release.
No one thinks that peanuts and vegetable oil combine into some magic superfood, yet Plumpy'nut is concretely beneficial to keeping people fed and healthy. Now, consider this same rationale into to a kind of poverty close to home. There is plenty of evidence that milk in school lunches is often the only reliable daily source of calcium and protein for millions of impoverished children worldwide.
Contextualized one way, milk is a meal replacement or nutrition supplement, and one that is more practical than most other options. A serving of whole milk requires zero on-site prep time, is relatively portable once packaged, and perhaps more importantly, it is often the most palatable option for picky eaters. Public health is complicated.
Its impossible to have a sane conversation about nutrition, especially in a historical context, when addressing folks' anecdotal cultural notions of what foods make their body feel good. Whatever point you're trying to make is meaningless without offering science or anthropological-historical context to back it up.
If this is the case, you are merely writing a piece of "our interview process is entirely average." I don't know about you, but 5-6 hours is standard. What's the point of breaking out your day-of process into 4 bullet points if its just the same as your normal engineering interview? Fluff.
Finally, realize that your candidates (just like your Eng org) spend much more time prepping for your interview than you quantify on paper. However much they choose to is up to them, but don't pretend you're doing them a favor.
To start, thanks for the self-submitted promo piece on your company. If you want publicity, earn it. You ought to make a statement about this fact in the comment section. Or, submit this using an official account.
Here is basically how it goes:
- Phone screening
- Take home assignment
- "Resume” interview
- Technical interview
- Product interview
- Interview with another team
- Finalizing the hire
This might seem that there are a lot of steps… and maybe it’s true. However we feel that it’s good for both parties if they get a good look at what working together would be like.
Are you kidding me? That is more time spent interviewing with you than the legal French work week. Who has time for that? I don't know about Paris, most candidates would laugh in the face of your recruiter. Those that don't are push-overs with nothing better to do.
Put yourself in someone else's shoes and imagine going through 7 days of 1-4hr interviews, concurrently, with a half dozen other companies at the same time. What makes your company so elite? Prove it.
Dear Blaine/Solve-employee, we know this is you. Be honest with us and just post on the OP account. Faking it is even worse than self-promotion spam. :)
Oakland, CA is a strong contender if you step back. Especially for one of a Stephensonian-styled second-wave cyberpunk. It even plays a part in Neuromancer.
It has its dark parts along with strong facets of common cyberpunk themes: drastic social stratification, the social acceptance of regular drug usage, urban decay meets technocratic renewal, a renewed definition of suburbia, and a greater acceptance of non-binary genders.
> How do you do that without some basic understanding of computer science-y stuff?
> How do you define "scalable", how do you measure it? How can you have some intuition about a design before we spend 3 months and many sprints building it first?
> How do I know when to cache stuff? Does it matter if I have calls to a remote cache in a tight loop? Should I be using an in-process, out-of-process, or remote cache for a particular piece of data?
You're proving the above poster's exact point. You are putting your weight in applied questions that rest upon the developer's specific experience. This method is the opposite of evaluating people for their ability to memorize a half dozen algorithms and data structures.
In my experience interviewing candidates, asking people to implement a caching algorithm is a distraction to both parties. A much better evaluation is their ability to provide box-arrow diagram and talk it through. This is much more effective towards understanding their thought processes and knowledge. It is also much, much closer to the _real_ day to day of a today's engineer: communication, advocacy, and breadth of knowledge. Code is cheap. Business should screen employees for an interest.
CS textbook questions introduce enormous amounts of bias, especially in panel interviews. It is a dangerous trap that companies use to further entrench their team cliquiness and departmental monoculture. It is ripe for Simple Sabotage. Simply put, its lazy.
In my experience, a familiarity with the command line along with the associated general systems/server exposure will elevate your career faster than anything. For those with such exposure already I'd recommend diving deeper and become an expert in the tools your existing team uses for systems, release, and deployment. These skills also open up new career paths you may opt for in the future.
While most of us are probably comfortable enough running make/grunt/gulp/etc, that comfort typically stops there. Knowing how to set up and manage your own systems will both make you more useful on your team and visible in the org. This is especially true for junior front-end folks.
California's damming of the Sierras and construction of the aquifers were primarily about flood control. Supporting the growing population came secondary (that's the easy part). An enormous effort was put into diverting melting snowpack into mountain valleys. This essentially created the northern and middle parts of the Central Valley, on top of creating sustainable year-round sources of fresh water for the developing coastal cities.
Downstream destruction is of concern because that entire region depends on flood control. The habitability and agricultural production of the corridor between Oroville and Sacramento relies upon, and was created by, the flood control of Plumas, Yolo, Butte, etc counties. There are a number of canals, diversions, and reservoirs both above and below the Oroville to further control flow the dam as it reaches our rivers. However, most of the re-routing is also man-made and thus untested for such an event.
Overflow over the top of a dam this size and type will almost certainly result in complete structural failure. The overflow we've seen so far is a secondary canal diverting excess water away from the main dam.
When the product succeeds and you get offers to exit, would you sell to the uber-wealthy? They will exploit your user's data and collect the gains.
Those are the questions you should be honestly asking yourself when considering your own ethics. What's your price?