|
Emacs Headroom posted:What are they issueing in RSU? it's something like 165-170 in seattle, and around 180 in sf. less elsewhere in the country/world. an sde 1 is probably making around ~10-20% of their total income off RSUs, whereas an sde 2 is closer to 40% and sde 3 is 50+. from what i saw on glassdoor for seattle last time i looked, these ranges seem to include either pretty out of date info or people who only put in their salary.
|
#
¿
Jan 11, 2018 17:53
|
|
|
|
| # ¿ Sep 16, 2024 22:44 |
|
|
i dunno, how much do they need to reduce their run rate by to make it to next month
|
|
#
¿
Jan 11, 2018 20:03
|
|
|
Trimson Grondag 3 posted:just curious, do they cap like that for managers/directors etc or just for high paid individuals? Amazon caps everyone, but you can’t even hit the cap until you’re senior/principal because of the salary/rsu ratio. looking to buy this 900k place in Capitol Hill and knowing I still don’t have to touch like 60% of my income is p needs suiting though EDIT: first against the wall, etc. FamDav fucked around with this message at 04:11 on Jan 16, 2018 |
|
#
¿
Jan 16, 2018 04:00
|
|
|
Star War Sex Parrot posted:Systems-y stuff: drivers, embedded, file systems, recently expanding that to DBMSs (working on an in-memory database project currently and finding it cool) dm if youre interested in filesystems in boston, dbs/system runtimes in seattle
|
|
#
¿
Feb 14, 2018 19:53
|
|
|
dividertabs posted:I like most of the questions from that list but this one: yeah for any company greater than 50-100 people the implementation of whatever values your company has are going to vary quite a bit team to team. I'd probably ask a list of questions like "What are your team's primary values?" "How much would you say those values are shared with other teams? leadership?" "How often do you ignore those values?"
|
|
#
¿
Feb 25, 2018 00:08
|
|
|
dividertabs posted:I wouldn't even ask about the team values; what they supposedly value doesn't (in my experience) correlate well with how decisions are made. I would drop the two questions: so that's why you need to follow up with a question that asks them about when they've had to compromise on their values. if they can't think of a time when they've had to compromise or explain well why they never have to compromise, then thats super suspicious to me. i do like your question tho
|
|
#
¿
Feb 26, 2018 19:25
|
|
|
Shaman Linavi posted:so i guess there are now literal tournaments to get job interviews? why is touching computers so bad if you aren't located in south america or eastern europe, i dont think youre the target audience
|
|
#
¿
Mar 3, 2018 20:30
|
|
|
Fiedler posted:Ah, yes, that's right. I forgot some humans enjoy living in hives. a thing a normal person says
|
|
#
¿
Mar 11, 2018 21:32
|
|
|
why do you always end up working in awful situations
|
|
#
¿
Mar 20, 2018 19:02
|
|
|
lol if you define your job prospects by a specific language but if you are pick English and java
|
|
#
¿
Mar 24, 2018 03:19
|
|
|
Progressive JPEG posted:whoops, minor point release upgrade just wiped out the cluster, oh well kubernetes is javascript is rails. a lot of good stuff and superficially easy to start using, marred by the lie (by omission) that it can be hard to maintain and has quite a few sharp edges. much like anything successful. cargo culting doesn’t mean you made a bad decision, it just means you’re an idiot who doesn’t know why you do anything (much like windows developers)
|
|
#
¿
Mar 25, 2018 13:31
|
|
|
freeasinbeer posted:Don’t disagree that this is major issue with k8s, the devs basically code to a pretty far departure of what traditional sysadmins are comfortable with. But to me fighting it to fit your legacy network design is a fools errand. I’ve also gotten in some pretty nasty fights with this in the grey forums, but I tend to agree with the vision that k8s has set forth for designs and think that maybe legacy design patterns need a shake up. people are running containers in production happily; they aren’t running docker in production with the same kind of joy. docker has encouraged a culture of never upgrading past a version that has been stable for you because who knows what they’ve broken in the intervening time. the company just can’t wrap its head around the fact that backwards compatability and stability are what the paying customers want. ipv6 is more or less broke with recent versions of docker, and apparently exec (and especially docker health checks since they’re just repeated execs) will lock up docker and make it completely unresponsive. docker will stick around as the dev tool of choice and we’ll continue to see it in build farms for a long time. docker in production is heading out the door within the next few years.
|
|
#
¿
Mar 25, 2018 17:47
|
|
|
Sapozhnik posted:is it better to start with k8s and deploy something that is literally used to manage google's millions of servers when you have 1 server and 0 users or do you migrate to it painfully later on (borg is not k8s, btw) containers are becoming a new deployment layer, so soon rather than later your 1 server will just be your 1 application container running on some cloud provider. eventually we’ll even see VPS’ running super oversubscribed container platforms for deploying Wordpress and poo poo.
|
|
#
¿
Mar 25, 2018 18:02
|
|
|
Sapozhnik posted:quarter mil household income there’s quite a few people in yospos who bring home 250-500k tho the best part is Pollyanna has already been given most of the advice you need to get there.
|
|
#
¿
Mar 25, 2018 18:08
|
|
|
TimWinter posted:Hey can someone recommend me any one of the many container solutions that exist as a viable alternative to docker? I don't want to derail the thread so I'm asking for literally one example here. so others have mentioned rkt (though imo i see it petering out), or with k8s they have cri-o available in beta that can target runc and clear containers. the reality is that you should probably be running docker in production because nothing else has been as rigorously tested up to this point. its not so much that docker has bugs that's the problem, because everything has bugs and people generally only complain about them because they're actively using something. the reason most people are tired of docker is because of their stewardship, and how the runtime itself has become such a commodity that nobody wants a lot the stuff that docker has had shoved into it.
|
|
#
¿
Mar 25, 2018 23:47
|
|
|
also all your containers are going to start running in microvm's sooner or later so get loving in
|
|
#
¿
Mar 25, 2018 23:48
|
|
|
TerminalRaptor posted:It's amazing how stressed I was able to get myself in undergrad. In retrospect it was silly, but at the time it felt like the world was ending. I wished I had goofed off more during college. depending on your college, workloads have also increased over the past decade. some of it is the classes, and some is the escalating need for differentiating activities/credentials in this hosed up capitalist hellscape. my college (after I left) had to tell professors to chill the gently caress out on their workload after a string of suicides/attempts in one semester  .
|
|
#
¿
Mar 27, 2018 15:12
|
|
|
things they're probably dinging you for, in order of how likely it was the thing * you're managing the list of open streams as a list and ordering them after every iteration instead of using a heap. you're doing O(k log k) work instead of O(log k) on every iteration. * lineToRead is superfluous or misnamed. you can easily determine it from StreamReader.EndOfStream. * The tuple stuff is hard to read, especially with a random primitive int and string. if you dropped lineToRead and made a "PeekableLineReader" I think the code would be easier to read.
|
|
#
¿
Apr 3, 2018 20:01
|
|
|
Space Whale posted:I've been told that you should expect back and forth about it and iterate, not just do it optimally from the start. I would be concerned about taking this approach with an assignment vs something like an hour interview session. i would kind of expect for a take-home that you iterated a few times already and produced something good/great. quote:There's also the fact that reading from disc is way slower than sorting 5000 items in memory. You are right but, wth? yeah this is the lovely and annoying part of most interview questions, which is that for whatever synthetic problem they give you the scaling considerations are just as synthetic. Whatever zip file they gave you will probably see minimal performance improvement from switching from sorting to using a heap, but it's not technically the "optimal" solution. quote:Also, would a sortedlist or sortedictionary be best for "use a heap" but not reinvent the wheel? no idea, I don't know c#.
|
|
#
¿
Apr 4, 2018 03:02
|
|
|
Shaman Linavi posted:i think amazon did at one time, and i remember the online coding thing i did for them had a bunch of poo poo i had to agree to you should have seen the internal e-mail thread that blew up when people found out recruiting had started that spyware coding app thing. that initiative was shut down very quickly i get the appeal from a recruiting perspective (a way to effectively screen candidates without trying to constantly wrangle SDEs to do phone screens!) but you just explode trust by forcing spyware on people. almost better to let the cheaters through anyways and have them get filtered at a phone screen Steve Jorbs posted:Lol @ having a family and working at Amazon. Pick one. I know teams/projects where it is pretty darn hard to balance work/family, but in my org (fairly large AWS service) there's quite a few people who have families of various sizes and shapes and they seem pretty content. ymmv
|
|
#
¿
Apr 10, 2018 04:36
|
|
|
qhat posted:the fact that cheating is an effective method of getting an interview at amazon shows how utterly worthless 1hour online tests or whatever are at screening out candidates. spend half an hour talking to them on the phone and you'll screen out 90% of the idiots, as opposed to like 20% from an online exam. i agree, and they still had a phone screen anyways. really it was just filtering out the bottom NN% of candidates at the expense of pissing off all of the candidates.
|
|
#
¿
Apr 10, 2018 07:03
|
|
|
Gazpacho posted:BEFORE I would add to during "don't be a dick". Even if the candidate is bombing at minute 5 in a 60 minute interview, don't mentally check out. best case, they recover and maybe you change your mind. Worst case they get rejected but feel like things went fairly and they were treated with respect. Fiedler posted:This is a half-step removed from asking "what's your greatest weakness." a weakness is a self-reflective ongoing thing, whereas technical/social conflicts and challenges are events.
|
|
#
¿
Apr 19, 2018 02:34
|
|
|
qhat posted:Your advice is highly specific to generalized programming roles where the team isn't fixed, like if you're hiring new grads. If you're hiring experienced people, what you want is extremely specific. I never hire someone experienced thinking "well they suck wrt the job description, but hey Paul's team might need him in 12 months". you still shouldn't be a dick. even if they're not a fit for your specific position, they probably know someone who is and they're going to ask how your interviews go.
|
|
#
¿
Apr 19, 2018 06:26
|
|
|
Notorious b.s.d. posted:you would be surprised how many sysadmins can't code this past phone interview was exactly that .jony neuemonic posted:"devops" as a position is a massive signal that the company doesn't actually understand what it is. on the other side of it, interviewing people who put devops on their resume has gone fairly poorly for us over the past year. maybe the answer is most companies/candidates aren’t so great
|
|
#
¿
Apr 23, 2018 02:16
|
|
|
Notorious b.s.d. posted:process and formal communication are not free; they're not a tickbox on "we're a big boy company now" its actually Apache Kafka-esque
|
|
#
¿
May 5, 2018 04:08
|
|
|
Notorious b.s.d. posted:yep that happens sometimes just because your company is dysfunctional in this particular way doesnt mean all other companies are or have to be
|
|
#
¿
May 5, 2018 04:18
|
|
|
Notorious b.s.d. posted:i fuckin hate it when this comes up in techie forums now this is something i completely agree with. after your entry level hiring and maybe your first promotion, your ability to do introverted coding tasks becomes a smaller and smaller component of your overall value as a software developer. its replaced by your ability to lead increasingly larger groups of people on projects of increasingly complexity, while growing people's skillset at the levels below you. if all you want to do is the introverted tasks then there is probably a place for you most anywhere, but you're going to hit a job level and pay cap pretty quickly. this is also why i'd say its best to work at the headquarters of your company unless they are really all-in on distributed/remote working. I'd be surprised if there is a real study on this, but my anecdata suggests that its 2-3x harder to get a promotion to a job level in a company location if nobody at that location has held that job title before, and its because you're missing out on the facetime and mentorship from the level above you.
|
|
#
¿
May 5, 2018 20:39
|
|
|
Progressive JPEG posted:kafka is extremely good op but people who use kafka are frequently p bad
|
|
#
¿
May 5, 2018 22:46
|
|
|
to give nbsd the benefit of the doubt, the version of remote work where offshoring at lowest cost isn't the usual desired outcome is a recent thing. and every company i've seen does a cost of living adjustment for your salary, where have you seen otherwise? though that can be very different from pegging salary to the local market rate for software developers, which is another difference between hiring remote and offshoring.
|
|
#
¿
May 6, 2018 17:02
|
|
|
jit bull transpile posted:Apple does it. It's p common because this is the United States of America. everywhere does it. mononcqc gave an example of how to get around it because most companies won't cut your salary on a move (though its more likely if you switch countries). the difference is the good places pay you a % of the rate in SF/Seattle/NYC, and not the rate you'd normally get in wherever the heck you are.
|
|
#
¿
May 6, 2018 18:26
|
|
|
here's the buffer calculator if you wanted to find out how much of a haircut you'd have to take to live in the same place https://buffer.com/salary/director-of-engineering-systems/high i appreciate the honesty in telling me I'd get paid 70% less. that takes courage
|
|
#
¿
May 6, 2018 19:19
|
|
|
ADINSX posted:Those salaries seem pretty low across the board... both of them are targeting median salary in SF for the position.
|
|
#
¿
May 6, 2018 19:47
|
|
|
ADINSX posted:I was looking at the software/senior software developer salaries. Idk what directors usually make the two red flags are: targeting across all companies as opposed to a set of peer companies that you want to remain competitive with. there’s a lot of people with your job title equivalent that are getting paid awful wages. also, median salary and what good devs are paid do not (and often are not) the same number. targeting median. the only people who are enticed by your salary are the ones making worse than average salary. if you want to compete for good people, you need to offer better than median.
|
|
#
¿
May 6, 2018 20:14
|
|
|
Fiedler posted:Translation: Do not ever work for this company or use their products. gitlab is riding high on the k8s and “let’s run everything ourselves what do those github guys know?” bandwagon surprisingly they are even worse at operations and infrastructure than their customers
|
|
#
¿
May 7, 2018 01:18
|
|
|
qhat posted:Welp just spent 3 hours on leetcode trying to come up with a good algorithm for validating a binary tree, managed it, then checked other people's solutions and realised I could've just done in order traversal and checked the current value against the previous. I guess I'll be putting off that Amazon assessment for another day. three hours does seem long my favorite way for validating a bst is you start at the root with a clopen range [-inf,inf), verify that the root is in the range, then split the range by the root for the left and right nodes respectively and recurse
|
|
#
¿
May 13, 2018 05:56
|
|
|
TimWinter posted:Although, CI is continuous integration which is easy to do several times a day even with large codebases. CD is the continuous deployment part, which does suggest several daily deploys. flaky tests are an issue, but if you have an automated full CD deployment pipeline why does it matter if the turn around time is 8 minutes or 8 hours so long as your test coverage and deployment velocity is acceptable for what you need
|
|
#
¿
May 25, 2018 15:24
|
|
|
this aviation place isnt in oregon is it
|
|
#
¿
Jun 7, 2018 15:40
|
|
|
Space Whale posted:Nah. ok good because I had a job that was in exactly that domain 5 years ago and it was awful
|
|
#
¿
Jun 8, 2018 03:06
|
|
|
Space Whale posted:I believe I'm at their rear end kicking competitor. Did your job name start with a J? no this was flight optimization for the Air Force
|
|
#
¿
Jun 9, 2018 16:25
|
|
|
|
| # ¿ Sep 16, 2024 22:44 |
|
|
Notorious b.s.d. posted:amazon is famous for violating OSHA rules with respect to toilets per worker, especially for their white collar programming hives this was specifically in Blackfoot, which is an awful rear end leased building that I cannot wait for us to leave. all of the amazon built buildings are much saner about everything. the spheres are very 👌 btw, ask your lunch buddy during the interview to take you there.
|
|
#
¿
Jun 24, 2018 15:45
|
|