Earlier quoted context omitted.
> salary Colorado now requires job postings to include something more or less like a "reasonable salary range". It hasn't been perfect, for example there are some companies who now just restrict their online job postings to say "except Colorado" instead of adding a salary. But as someone living in Colorado it's been nice to know the salary range up-front more often and to have confidence that I can ask them for a sal…
In California recruiters are legally obligated to disclose the salary range upon request.
Rethinking Triplebyte
371–380 of 463 posts
Re: Rethinking Triplebyte
#372Earlier quoted context omitted.
In California recruiters are legally obligated to disclose the salary range upon request.
Source?
(c) An employer, upon reasonable request, shall provide the pay scale for a position to an applicant applying for employment.
[1] https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml...
Re: Rethinking Triplebyte
#373Earlier quoted context omitted.
> If your desired comp number actually is $1M/year, will that just flag you as a joke to Triplebyte companies? With post-pandemic stock price increases a lot of engineers at FAANGs are making more than that now. For any reasonable definition of "a lot", no they absolutely are not. A lot of people with 2+ years of experience who've either been promoted once and received a strong annual review, or switched jobs as a mi…
Stock price for most of the FAANGs has gone up by about 2.5x in the last year. If you had $200K base, $50K bonus, and $300K stock compensation in 2019, you're now making $1M today. That's roughly L6/E6/ICT6 (staff) level.
They’re all doing well, but even Amazon hasn’t doubled their stock since prepandemic.
There are definitely more people making 1m/yr at FAANGs than their were last year, but I agree with others that it’s not “a lot.”
Re: Rethinking Triplebyte
#374Re: Rethinking Triplebyte
#375Earlier quoted context omitted.
I never, ever, ever give anyone a number until the salary negotiation stage of the interview (ie. after I've been given a job offer), and even then I only give the company a number as a counter to their offer. I always do this negotiation myself, and never let anyone else negotiate for me. Almost all recruiters have been fine with that, but a couple haven't. To such people I wish a good day and go my own way. There a…
A particular problem with doing that is discussed in the post; you risk everyone's time being wasted if the company will never be able to meet your target.
Re: Rethinking Triplebyte
#376My random Triplebyte anecdote is that I did good on the quizzes and gave a solid interview, but they declined to represent me. They were transparent about their reasoning: they saw me as somewhat of a specialist in parsing, and they didn't know how to place someone with that peculiar skillset. Which turned out fine. I found a job where my pre-computer programming work experience was relevant, and here a couple jobs l…
I would think big tech companies wouldn't touch companies who might fold in the next 6 months with a 6 foot pole.
Re: Rethinking Triplebyte
#377I applied through Triplebyte in 2015 & again in 2018, and got to know Harj & Ammon a bit. They, along with Gilluame, all struck me as remarkably smart and incredibly dedicated to their vision. So if after 6 years that lot haven't "cracked the code," that's reason enough to abandon hope for there ever being a sane recruiting process, anywhere. My takeaway from my experience finding a SW engr job was that actual techni…
That capable people failed to make one solution work, doesn't mean no solution can work. Now they're going to try another.
Re: Rethinking Triplebyte
#378I'm personally very excited to see this change by an industry leader! I think that there's a seismic shift waiting to happen w.r.t. engineer hiring. The "old guard" of hazing, quizzing, and gotcha-style interviews are slowly losing ground. The most friction when switching jobs is the interview process -- and the question is why? I've been writing code for a decade+ now, working on startups, for known tech companies,…
* The blog post complains that even experienced engineers they interviewed couldn't write some simple code on paper. Did anyone stop and think that maybe it's writing code on paper in an interview setting that's the problem? Stop and think about this. Imagine writing code like you usually do in a text editor. And then writing code with pen and paper. Backspace? Can't do that. Copy/paste some line to move code? Can't do that. Add some newlines? Can't do that. Run the code using the compiler? Can't do that. Of course most developers, even experienced ones, will do poorly under these conditions, this is not how code is normally written. On top of the already stressful situation of an interview, there's this suddenly completely foreign and limited way to write code.
* Even the blog post only mentioned fizzbuzz as a quick, easy question to filter out zero coding ability. Another way to say this, it was meant to filter out coding skill <= 0. Not skill <= 50 or skill <= 90. Zero. After that, the interview was supposed to move on to things that actually matter for software engineering. The present day interview has strayed extremely far from this. These days, you get asked two leetcode questions during an interview and even if you perfectly answer the first one, if you don't get the second one then you're an automatic fail. That was certainly not the intent of the original fizzbuzz, since answering any leetcode clearly shows coding ability. And the interview never has a chance to move on to the part that actually discusses software engineering skills. Or even if it does and they do very well on those interviews, the failure of only getting 1/2 leetcode questions correct overrules everything else since they must avoid "false positives".
Re: Rethinking Triplebyte
#379Earlier quoted context omitted.
Fair comment. I certainly don't think of us as a market leader. LinkedIn is the market leader. Honestly, the last year has been pretty hard for us (COVID and the problems with our model that I talk about in the post). That said, I think a hiring process that puts engineers in control (no ghosting, get data on when a recruiter looks at your application, search ranking by whether companies lie to candidates) is somethi…
Fair warning. There is a large pool of people who think that they are programmers, but are not. This is exactly what the infamous fizzbuzz test was intended to weed out. I personally know a top notch recruiter who credits her success due to learning early in her career how to filter most of the junk out. For example a "Perl programmer" who listed Microsoft Word as a skill was probably not worth looking at. (Note, thi…
& maybe I'm wrong but I thought the entire value proposition of TB was that their pre screening and testing process made the whole process much less noisy for your hiring managers. If you still end up needing technical interviews and aren't guaranteed that all the candidates you get have gone through some technical screening, what's the point?
Re: Rethinking Triplebyte
#380I see a lot of people in the comments describe triplebyte as a “market leader” and discuss how good they are. I can’t believe how gullible everyone is especially on a startup forum. Let me spell it out to y’all, nobody pivots and changes their entire business model if they are crushing it. So the implication is that triplebyte are not crushing it. So, this probably has gone the same way as lots of other tech startups…
Fair comment. I certainly don't think of us as a market leader. LinkedIn is the market leader. Honestly, the last year has been pretty hard for us (COVID and the problems with our model that I talk about in the post). That said, I think a hiring process that puts engineers in control (no ghosting, get data on when a recruiter looks at your application, search ranking by whether companies lie to candidates) is somethi…
I am looking forward to progress toward a hiring process that puts engineers in control, such as by allowing them to accurately record their current role in their profile.