13 ms·
It's not a good job market, but it doesn't seem normal to spend six months applying and only get _one_ interview. It might be worth asking friends or former co
by rsynnott 3y ago
It's not a good job market, but it doesn't seem normal to spend six months applying and only get _one_ interview.
It might be worth asking friends or former colleagues, ideally people who actually are involved in recruiting (hiring managers etc) to take a look at your resume and LinkedIn profile and see if there's anything glaringly wrong with them.
Is your resume in a weird format, or is it structurally weird/overdesigned? For instance, a recent trend in resumes was to show (programming) languages known in a pie chart (do not do this; it is nonsensical). In many companies, the text from your resume is going to end up in a standard format anyway; they'll have tools for this and if their tool can't extract your text they may not bother. Unless you're a graphic designer or something, you probably want a boringly-designed resume.
Are you applying jobs for which you are dramatically underqualified? One thing to keep in mind is that some small companies (if you're coming from one) have _wild_ title inflation; a small startup might call someone with 5 and a half years experience their director of frontend engineering, say, whereas everyone else would call that person a junior engineer.
Does anything particularly unfortunate come up if people Google your name? For instance, a real-life version of that Seinfeld episode where Elaine's dating a guy who has the same name as a notorious local serial killer.
- whiddershins 3y agoNo, no one calls someone with 5.5 years of experience a junior engineer.
- Aeolun 3y agoThat depends entirely on their skill. I’ve seen people with 10 years of experience that were still junior.
- arghwhat 3y agoOne should definitely have outgrown a junior title after say 3 years of relevant experience, as that is more than sufficient time to be trained into a normal (non-senior) status. It could last longer if your company does not have a normal title (i.e., they consider junior == !senior), but someone with 10 years of relevant experience should have earned a seniority title of some sort.
- ehnto 3y agoI think you have found the issue to be honest, I think most people are expecting to be "senior" in place of "not junior" as soon as they prove they are good programmers. The senior title has been quite diluted by that. Seniority is about experience and not skill in my opinion, we see many talented developers who don't qualify as senior because they simply haven't experienced enough situations. I expect a senior to have some war stories and a breadth of notable situations that they can walk me through, to demonstrate their ability to predict common issues and pitfalls, and to show how their experience helps their troubleshooting and informs their choices. If I had told 20 year old me this, 20 year old me would have balked. 20 year old me was an excellent programmer, but he didn't know shit about long term software development.
- lowercased 3y ago> I expect a senior to have some war stories and a breadth of notable situations that they can walk me through, to demonstrate their ability to predict common issues and pitfalls, and to show how their experience helps their troubleshooting and informs their choices. Yep. I've been doing this for... almost 30 years now, and... interacting with 'seniors' with 2 years of experience is really weird. My recollections from the 90s having worked inside a few places was that 'senior' had a lot more weight/heft to it. It indicated, at the very least, long experience (8-10 years or more) and some ability to at least work with other tech people (non-tech was a bonus). Can't quite figure out when this shift started, but have definitely noticed title inflation as a regular thing over the last 10-15 years. Have you ever taken down a database by mistake? Dealt with bad backups, "on production only" issues, rounding errors in historical data, security breaches, multibyte character set conversion issues? "Coding" is eventually only a small part. Better coding skills up front can help prevent or mitigate some of the potential issues listed above, but only to a point. You're not always even the author of all the code in use; learning how to deal with that, maybe under pressure of "prod is slow/down", has an impact on how you consider these issues going forward. EDIT: tangential story I was at a meetup years ago, and one of the "senior dev/architect" folks at the company hosting the meetup was talking informally about IDEs. I jumped in a bit as I'd recently started with IntelliJ (this was... 2010, I think) and was excited to share a few bits that were new to me. As I listened more, the guy was lecturing the meetup folks that "IDEs were really for juniors and newbs". Specific language is somewhat lost to the mists of time, but the gist was "This is your code, you've written it, you should know it inside and out; fumbling with slow IDE just burns productivity, wastes time, and just shows you don't really know the codebase." I eventually interjected that it might be reasonable for him, personally, to know all the code in a system that he'd built up from scratch over the last 7-8 years. However, for anyone new coming in to the codebase, an IDE is invaluable because it makes the entire thing far more discoverable. Jumping around between sections helps you learn and narrow down bugs/issues much faster. "Well, you should just be asking your senior if you have questions" was the main response, and IDEs were still beneath him. I realized a bit later he was actually giving a small pitch; as host of the meetup, they had an intro period, and they were recruiting. I'd heard about this company before - growing, funded and in a space I had some experience in. Had 0 desire to work there after talking to him. But "the senior architect" always knows best in many places. :/
- rsynnott 3y agoEh, maybe an "engineer", if they have junior, null, senior grades. A lot of places wouldn't consider that sort of experience level automatically senior; they'd have to be exceptional.
- Silhouette 3y agoNot automatic but historically a good but not exceptional developer would expect to make senior after maybe 5-8 years of experience. Someone who was still needing close supervision - which is what "junior" traditionally meant - after 5 years would be exceptional and it wouldn't reflect well on either the developer or the places they worked at the start of their career. Of course this is about the level the employee is capable of operating at in absolute terms but hiring is relative. In an employee's market someone might be able to land a "senior" role before they're really ready for it. In an employer's market the average candidate who gets hired as a "senior" might have 10+ YOE. We've gone from one to the other recently and everyone's expectations will need to adjust accordingly.
- vsareto 3y agoThis is why software is not a serious profession: it has no consistency in progression and recognition. I think I would drive myself mad if I tried to live up to the crazy expectations of senior from most internet commenters.
- re-thc 3y ago> I think I would drive myself mad if I tried to live up to the crazy expectations of senior from most internet commenters. And maybe that's the point of it. Senior without the title inflations is meant to be an actual high level position - not 50-100% of the company. A lot of places have just replaced senior with staff/principal engineers instead, but senior used to be a well respected and unique title back in the days.
- Silhouette 3y agoI agree with half of what you say. Senior should be a high-level position. It's a recognition of someone with solid skills and the ability to get things done. But suppose a senior is someone who can work mostly autonomously under general direction from their management and tech leadership, which I'd say is a reasonable basic definition of what "senior" level has historically meant in software development. We would expect to see a lot more people reaching that level and sticking around on a tech career path now because of the rapid growth in the industry and the greater awareness that people can be a high-level IC but not have much interest in formal leadership or management roles. Moreover there is no rule that says an employer should hire mostly juniors, some mids and only a few seniors. Good seniors are almost always disproportionately cost-effective if you can manage to hire them. The trend for rapid job-hopping has left juniors as an almost worthless hire in many cases because they probably won't be around long enough to make a good contribution in return for all the early overheads they incur. There is definitely a longer formal tech track in large organisations now. I'd say it used to be more that you reached senior and then any other responsibilities like leading a team or dealing with large-scale software architecture issues were kind of attached. So historically you'd associate those higher responsibilities with "senior" people where today those with the skills and experience to do them probably have higher job titles like lead/staff/principal instead. So I'm not sure senior has been deflated or replaced by staff etc. It's just that senior used to be the top of three levels for many employers but now there's more recognition that your development doesn't just stop after a few years and "senior" today mostly means "first few years as a senior" in old terminology.
- cientifico 3y agoI do, and quite frequently. After more than a 2 decades in software development (rails/web/...), for me to consider a developer to be a senior it needs to: * Communicate: For example: can explain tech concepts to non tech people, or inform on Monday that the sprint will be unlikely to be done in time. * Can estimate and adapt to changes. Be boring and predictable. * Can work/collaborate/teach with other devs. I got tired of interviewing tech people that though that to be senior is the same as to be specialist (or worse even, that it was related with the number of years).
- ZephyrBlu 3y agoYou think it takes 5+ years to acquire those skills?! Man, I would be driven insane in an environment like that. Such a long time and a relatively low bar.
- H8crilA 3y agoI think the point is that some people don't acquire it within 5 or even more years. Think of a typical checked-out worker, without any specific ambition in professional life. There's plenty of people like that.
- jacquesm 3y agoSome, possibly even most, never do.
- reverend_gonzo 3y agoI know people with 20y that can’t do that.
- FemmeAndroid 3y agoNot who you’re asking, but it can take almost no time, or decades. It has nothing to do with years.
- pc86 3y agoI have worked with people who have 8-10 years of experience and are still mid-level in both skill and professionalism, know that they are, and are fine with it. They get their joy from other things in life and are totally fine coming into the office and doing the bare minimum to get by and going years without raises or bonuses because of it. Again, this is a conscious choice these people are making, they're not being taken advantage of or anything.
- animuchan 3y agoThat's exactly what the parent comment says: title inflation. I sometimes get even funnier CVs, where a person with 2-3 years of experience (usually from the Army) is already in a tech lead / architect position.
- ZephyrBlu 3y agoTech is very strongly bi-modal or even tri-modal in terms of both compensation and skill. Some people with 2-3 YOE will operate better than some people with 10 YOE.
- thaumasiotes 3y ago> Some people with 2-3 YOE will operate better than some people with 10 YOE. That's true of every field, and doesn't really relate to the claim of bimodality. If ability followed a perfect normal distribution, it would still be true that some people with 2-3 years of experience are better than some other people with 10-15 years of experience.
- ZephyrBlu 3y agoIn most fields this is extremely rare. In tech it's relatively common. The difference is the kind of environment you're working in (E.g. high growth tech company vs non-tech company) and the learning rate in that environment, which is where the modality comes into play.
- thaumasiotes 3y ago> In most fields this is extremely rare. For example? In pretty much any field I can think of, it is definitely not rare. The norm is that some people pick things up quickly and other people don't. It is normal for good musicians with 3 years of experience to be better than bad musicians with 10 years of experience. It is even more normal for good secretaries with 3 years of experience to be better than bad secretaries with 10. My mother once partnered with a local university to offer students internships clerking in her medical office. She remarked that the students, with their zero years of experience, were more effective in this generic, unskilled role than anyone she was able to hire into it. (Those people had many years of experience.) The partnership with the university wound down and she went back to hiring no-hopers with plenty of experience. According to her, that was the best she could hope to do for the dead-end position she was offering.
- washywashy 3y agoI think the issue is that people sometimes incorrectly assume job titles are standard and used the same across different companies. At some companies titles are more about pay bands. I’ve worked places with a bunch of “senior” engineers, but that was mainly because the company pay bands couldn’t compete with the market for junior engineers so they’d hire them as seniors. It’s bad too because sometimes once an employee gets that title they expect it at other companies even if the experience level isn’t there yet, which limits their mobility because they refuse to take a backward step in their career, even if the pay is better
- scarface_74 3y agoI took three backward steps since 2016 - dev lead - non tech company responsible for one “team” of two developers and a bunch of contractors on another team - “Senior Software Engineer” - no reports and I actively refused a promotion to be a team lead. I was already the de facto “cloud architect” over the “application modernization” efforts via no more than influence and reputation. - mid level “cloud consultant” - full time job working remotely at BigTech.
- disgruntledphd2 3y agoAs my Dad always said, it doesn't matter what they call you, it matters what they pay you.
- shultays 3y agoI worked with a person for about 3 years (and he had previous experience as well) and I wouldn't even call him a fresh-grad level or trust him more than I trust an intern. Some people are immune to learning
- artificialLimbs 3y agoWe have a 14 year junior engineer. She refuses to learn new tech, is difficult to work with, and makes a mean bowl of spaghetti code. She does it so quickly though and has so much institutional knowledge that it’s pretty much mandatory she stays.
- baobabKoodaa 3y agoWhen did we arrive at a point where terms like "junior" became derogatory terms similar to "idiot" or "asshole"? No, you don't have a "14 year junior engineer". You have a senior engineer who is difficult to work with and is (according to you) bad at their job.
- artificialLimbs 3y agoHer official title is literally Junior Engineer with the company. Did I say that it was a derogatory term or use the title idiot or asshole or say they were bad at their job? Bro you should get that chip on your shoulder examined.
- pcthrowaway 3y agoHas she been with your company for 14 years? Because if so, this really calls some of your companies practices somewhere into question. That being said, if she got hired as a junior in the last 5 years (despite tangentially having some programming experience) and never got promoted, I guess I can understand that, but really, why even keep someone on who refuses to learn new things, is difficult to work with, and consistently writes poor code
- morelisp 3y agoWhy? Because there are also 14 year junior managers (except they get retitled to something like "team lead")...
- VoodooJuJu 3y ago>but it doesn't seem normal to spend six months applying and only get _one_ interview. At this point in time, it's completely normal for people breaking into the industry.
- yodsanklai 3y ago> _wild_ title inflation I'm wondering if it's important to put a specific title on one's resume. I assume many companies don't have any titles at all and everybody is just a "software engineers", whether they are a fresh graduate or 10 years of experience tech lead. What is more relevant is the scope of the job done which should be listed in a job description.
- Macha 3y agoI think yes. While many companies have unprefixed titles, others have just plain "Software Engineer" as one step above graduate and even some otherwise decent companies will discard resumes applying for senior/lead positions when a HR drone does a first pass and decides "no senior level experience", even if your descriptions are full of business impact and leadership experience.
- tough 3y agoI think it's also important to know what you're applying to too. If you're applying to a Frontend Engineer Position, and you're a Software Engineer who's comfortable with both parts and the full stack, you just shut up, put frontend engineer in the CV, and let them choose you, you can always tell them you also know to do backend stuff on the interview.... First passes are pretty simple, they just match their job position with the stuff recieved. ATS filter you based on keywords before a human does
- rsynnott 3y agoYeah, honestly if I was coming from a startup that called everyone the Vice-President of Whatever (or indeed a large multinational bank; some of those also have silly title inflation) I'd be inclined to just put engineer.
- blitz_skull 3y ago> whereas everyone else would call that person [with 5 years experience] a junior engineer I’ve met people with 3 years experience who I’d consider more senior than myself (8 years). Some folks just learn really fast and/or don’t do much else other than work. Not sure time is relevant to your skills or title after about 2-3 years.
- tough 3y agoIt's such an old-fashioned way to look at skills and experience. Tbh there should be real ways to measure all this but there aren't. If you can code by your own without handholding, are you a junior at that point anyways?
- flagrant_taco 3y agoI've never really considered the ability to write the code without handholding to be the line between junior/senior. If anything that's more the line of being a competent developer with a particular toolset. I may be a competent framer that can stud out the plans for a house, but I may not totally understand why the walls are positioned that way or how the roofline will work with the landscape to avoid water issues later. They're just different skill sets, I'd actually also expect the architect who can design the house wouldn't be particularly useful with a framing nailer. Ive never actually liked drawing solid lines between skill levels because it is so contextual, but here's the closest I can get. Any developer should be able to write code when it's already known what it needs to do. The next level for me is being able to write code with an eye towards testability, maintenance, and flexibility based on where you expect requirements to change later. I'd expect a senior to be able to go beyond that, starting from a set of product requirements and designing the code to work for those needs. Beyond that it starts to get really gray, and you likely lose more of the earlier coding skills, but that's where I'd be looking for someone who can help define what the product requirements even are, considering technical risks and limitations of how they might even build and host the product.
- tough 3y agoI see it like the most abstract up the ladder you get, the more senior you are. Anyone can fix a button's css. Not anyone can refactor big parts of a codebase into something better, or help them create from scratch in a cohesive, modular, future-proof way. Every time I get into a new job I get a various degrees of this. The more business-context you have, the better you can solve business requirements with tech, the better tech toolset you have available, the better choice you can make on what solution to use or not to use to such problems. True seniority means understanding how all the system works, regardless of getting into the grunt work of each of the steps, but being able to do so and understand it at the lower level too if/when needed. It's a hard act.
- ryanbrunner 3y ago5 years for junior for better or worse is well out of step with the industry - while you're right that you can get some massively inflated titles that are out of step with the norm, the norm is that you're an intermediate developer at a minimum and most likely a senior after 5 years. It's dumb, but it is the standard nowadays.
- pc86 3y agoIntermediate/mid for sure, but if I get a resume from someone whose first programming job was 2018 and they're calling themselves senior, I'm throwing that in the trash unless like you said they're from VC-funded startups that are going to have massive title inflation and they're applying for a realistic (mid-level) role.
- ryanbrunner 3y agoSure, I guess my point is to consider the context of the person applying. If they are coming from a place with title inflation, it's not their fault that the company they worked for inflated titles. If you're exclusively hiring seniors and they are an inflated "senior", for sure you're under no obligation to hire them, but if you're open to intermediates, I think it's worth explaining how your titles might differ from their experiences and that intermediate is a better fit.
- bigbinary 3y agoAnyone tossing resumes because of title/time spent not matching up with their expectations is out of touch
- School-Cotton 3y agoIt wouldn't be unusual to be an E5 at Facebook (err, sorry, "Meta") after 5 years, which is considered "senior" level. The point I'm making is that this title inflation has happened more broadly than just at VC-funded startups.
- 3y ago
- collaborative 3y agoI haven't looked for jobs in nearly 9 years now. Is a LinkedIn profile essential nowadays? I have dropped all social media and LinkedIn is one of the most invasive. I really dislike how it notifies you for everything
- willsmith72 3y agoYou can turn off any notification settings
- collaborative 3y agoIt just bothers me that people get notified whenever I'd do anything on it. As for myself, I simply make notifications go to my spam folder I prefer to share my information when I want and with whom I want, but LinkedIn feels like a meat market. If FB was personal marketing 101 (only sharing what makes you attractive), linkedIn feels like an advanced course on being fake. It kind if disgusts me
- pc86 3y agoIf you're looking for work (at least in programming, in the US), respectfully you need to get over it. This mindset is well in the minority and will actively hurt you while job searching. Not saying you won't find stuff without it, but why make it harder than it needs to be?
- willsmith72 3y agoWhat do you mean by "It just bothers me that people get notified whenever I'd do anything on it"? You don't have to notify anyone when you update anything, it's just a setting. Most people don't. The "fake" ones are the people trying to become linkedin-fluencers, I agree I'd never want to do that. But setting up your profile is basically a copy paste of your resume, and leads to an in-flow of recruiters you can always go back to when it's the right time. I can't really believe I'm preaching for linkedin because I barely spend any time on it, but it's a tool, and when I've decided to move companies, it's made life far easier than it would've been manually applying to companies. That's without making public posts or sharing public updates to my role
- dorfsmay 3y agoHave you looked for a job recently? I don't know about you personally, but people in my social circles and employed think the job market is the same as it was from 2015 to 2020. They have no data point and assume their 2+ year old experience of looking for work is relevant today. The market is bad. I was getting calls from recruiters in 2020. I looked and found work (contracts) twice in 2022, the first time was not easy, the second time was very difficult. 2023: I am available, contacts and links to resume, linkedin, etc... in my profile!
- Workaccount2 3y agoIt's strange because economically, tech is roaring back and the job market is tight as ever. Are employers hedging against this perpetually 6 month away recession? Is there a shift from growth mindset to value mindset?
- rpearl 3y agoFor private VC tech, interest rate increases mean the next funding round will be much harder to get
- deleted 3y ago[deleted]
- Tostino 3y agoThere was also a concerted effort from major tech employers to depress wages to control costs. They don't need to directly talk to each other to plan it, they state it in their earnings calls.
- throwaway2037 3y agoThe most economically efficient companies in my career always make it insanely hard to add head count to the team. They tease you with "might get a head count next quarter". Then frequently freeze the head count during your search. They are trying to squeeze as much as they can. I'm not saying this is a pleasant working environment, but it is very good for the bottom line. Also, it is sometimes more efficient for them to give modest pay rises to best performers off-cycle to motivate them to work even harder.
- pwpw 3y ago> whereas everyone else would call that person a junior engineer. Does anyone have advice on what I should call myself? I was a senior in public accounting (~3 years of experience) when I switched into software development after self-teaching for 5 years on the side. I settled for an entry-level role to get my foot in the door, but after 7 months I was made the lead of one of a few teams with the rest being led by principal engineers. I think it’s fair to say im clearly not a recent college graduate and am performing like I have already been a software engineer for a few years now. I now have 2 engineers below me. My technical skills have grown much stronger than an entry level, and my non-technical skills are on par with the other principal engineers. My team has been thriving and has received quite a bit of recognition from the company. I’m coming up on a year and ready to ask for a raise since I believe I’m vastly outperforming an entry-level role compared to my peers, but I don’t know what to push for since these job levels are less clear than they are in accounting. Level II? Level III? Senior? It’s tough to rank the experience gained from my CPA and accounting background (that would be very valuable if I were still an accountant of course). Naturally engineers want to devalue it (fair enough), but it’s clearly paying dividends in my ability to deliver the company value.
- nicoburns 3y agoPossibly "Engineering Manager"
- isbvhodnvemrwvn 3y agoNot with 2 people, and it's not even clear if they are their line managers and manage them in terms of promotions, raises, hiring and so on.
- pwpw 3y agoThat’s a good thought, but I do want to stay on the technical side for now. Perhaps that would be to my detriment, but I find the actual developing and problem solving so exciting! The company said they needed an in-house invoicing system, and I had a blast designing it, creating it, and finally delivering it this past week.