You are missing the point that a director level resource, could only apply to a relatively smaller number of roles. Entry level IC might not be worth applying.
So despite what they say, the limitation factor might also be number of posted jobs.
I know they said they applied to anything - but still anything for that profile might be a bit more broad - entry level IC to FANG may be which pays better or a role that is open to leveling or start up or any other combos.
Thats certainly invalid. People with 20 years of experience or more, are asked questions based upon the role they are interviewing for.
If you are applying for a principal or higher engineer role and your job involves coding, you are asked coding questions. May be not just focused on a complex bookish algorithm only, but rather more close to a real life distributed programming / synchronization problem etc. for example.
Every body is asked some thing close enough. At higher levels, often focus is not on coding, but enough depth of design where a person of such profile might end up educating the interviewer - while satisfying their requirements.
That being said, ability to solve coding problems efficiently (not necessarily spit A* graph algo in sleep), but a decent close to real life coding challenge is fair game.
The last part might not be true. Though i won't generalize, let's just say that i have been writing industry code for almost a decade, 90% C (because of domain) and at least a quick review tells me, porting this to a couple of major platforms could be very practical and useful IF IF, it does not sacrifice the performance.
Well coming from an industry c programmer (embedded, networking, high throughput stuff, where c is the only choice), i am really thinking this could be of a great use. Specially for large products developed and maintained for many years and have big teams, this could be priceless if actually ported / extended. I would probably look at this and try to contribute when i can. Thank you so much, great work
you said must be eligible to work in Canada. Do you mean that you cannot process people who are say on closed work permit in Canada and would need a new permit to work for you?
Until we find a way to truly achieve network neutrality which also means (from service provider's perspective) to throttle and keep in reasonable usage limit applications such as video streaming, specifically illegal torrent usage which chokes carriers bandwidth and prevents normal users too, this debate will continue. I don't see any thing principally wrong with providers point of view (i might be biased because i work in the industry that provides these tools/software. But logically, the word "neutral" to me should equate both sides - not prioritizing some high paying customer's traffic, but at the same time not allowing a regular user to eat every one else's bandwidth to download his favorite pirated content. I feel the discussion on the topic is mostly targeted at the former only. A side effect of such capability could also be better utilization of network resources i.e. charging customers ONLY when and what they use - there by decreasing costs as well.
Moreover, the concept is quite abstract and has many similar applications. I used to work in a scenario when there was a specific gateway resource that was needed to be run by every developer for executing his code, was very expensive and people would annoy each other by suddenly remote logging into machine and disturbing others. Then we came up with a resource locking / waiting and current state showing software, along with estimates of when which machine would be free, so you could request a reserve slot. Some sophistication included things like how much of it was actually used by you vs reservation time so it could adjust appropriately.
I know they said they applied to anything - but still anything for that profile might be a bit more broad - entry level IC to FANG may be which pays better or a role that is open to leveling or start up or any other combos.