How do you make that business mindset intuitive for people that are used to being technical workers?
I actually would not want to limit myself to one industry. Working at a digital agency has its short comings but one thing I enjoyed is the variety of clients we get.
For example, I have a mixed skill set of web development and graphics programming. That's allowed me to interview at companies from a variety of business problems that leverage the graphics skill set, such as CAD/CAM, indie video games, or space mission simulation.
I want to say "I solve these problems" without limiting myself to one industry but relying on my tech skill as the niche. Is that just as good?
Leetcode problems rarely come into play outside of tech hubs or quant firms. I live in Chicago and rarely encounter such problems in job interviews. And just Leetcode easies at that. They do ask you do take-home assignments, though.
The only reason I accepted is because the alternative is having no work. It's harder to bargain for a fair wage when you're unemployed.
When we were discussing rates, I proposed $60/hr which is perfectly passable in the city I'm in for a contractor with my experience, but they couldn't do higher than $35. I am seeking something new but I need a plan to live comfortably in the interim.
That's an interesting idea for a resume layout, although the columns will probably look very unbalanced with my set of jobs. I've only had two FT developer jobs, both of which are too old or too short to have made any meaningful impact or progress.
>Whats going wrong in the interviews? Do you ever get feedback from the companies that reject you? Are there questions they ask you that you stumble on?
Several problems were spotted through mock interviews I took, as well as real ones that gave feedback. With the mock interview, I dragged on too much explaining my past experience because of all the disparate jobs. With Triplebyte, I was told that I show breadth in talking about different topics but not much depth in any of them. And very little knowledge on large system design (which I want to get a beginner job at).
>It sounds like you have been working on fairly run-of-mill CRUD based applications that don't require that much thought. Can you be more picky about what jobs you take?
That is true, about 90% of the work I've done is CRUD web dev. The most in-depth project I worked on is for an indie game written on a C# .NET framework. This was a one-off opportunity that I got browsing job requests on Reddit, and I was given the offer based on some personal projects I had. But it didn't lead to more substantial game dev jobs. I suck at getting the ball rolling.
I have to just fall back on applying blindly as my networking game isn't very strong. Whenever a contract ends, I come off as too transactional when I speak to people about seeking work and that turns people off.
Even though Ruby on Rails has started to be past its peak popularity I like using it, and also want to use React and Vue more. I'm definitely not going back to CMS work. A colleague once forwarded me a Magento job because he became an expert in it, but had no interest in going back to that.
Web development jobs. Ranging from CMS-based websites using WordPress and Magento, and built in frameworks in stacks, LAMP-based to Ruby on Rails to using React.
These jobs all are underpaid, 1099 jobs. Made anywhere from $15/hr to $35/hr in a medium COL American city. I need work that is more stable and doesn't have me hopping around, and not having to live paycheck to paycheck.
All of these jobs are for small business clients, with usually me as the only developer. It sometimes feels more like consulting work, but I want more experience working in a dev team. I don't know how to pass interviews for FT jobs working in larger groups.
>Spending more than 2 years at Eng I or Eng II is considered a cause for serious concern.
Is this just for within Google or also from Google's perspective of hires from elsewhere? Because I have to admit I have not been past mid-level (which I guess is the Eng II equivalent) for over five years.
I have 10 years experience in my career and never held a senior position, officially. Do I miss out a lot in seniority by just being a permatemp and contractor for small shops?
Agreed. This has been an eye opener for me as someone who has worked mainly in smaller companies whose job levels didn't go beyond junior, mid-level, senior/lead in my profession. Granted, the concept of target schools still adds some bias to candidate hiring, but it's better than in many non-technical careers.
I am not sure how Leetcode would help out here in specific, for someone who already has years of proven programming experience with other companies. Any company who holds any water in what they do would substitute rote knowledge of algorithms with real world programming skills.
Usually I have considered internal recruiters from larger companies to be more serious than the typical messages from third party agencies who don't even disclose the name of the company you represent. I didn't know they do the same "spray-and-pray" tactics, but if that is true, that is rather disappointing to know, that they have gotten as flaky as agency recruiters.
What's interesting to me, though is that I've had far better experiences with Amazon's recruiting staff. They were very responsive, usually replying to my questions in the same day, and have gotten in the running for interviews twice with them. I have been as far as being selected for the on-site interview round, but made the mistake of saying I am not yet prepared to travel there at the time.
MSFT did not set me up with a programming test, just something to fill out. The pre-screening document was a questionnaire asking various background-related things like, what is your expected salary, have you worked for mS before, what project or accomplishment are you most proud of, etc. I guess they just didn't like my answers, and am more likely to be considered by Amazon than MS. In any case, I become a "cold" candidate very quickly in the MS recruiting radar.
>It seems little odd that at 35 you're still in the $25/hr range.
Don't underestimate the negative effects of having no job lined up when you're let go from your current one. You can't realistically negotiate for an ideal salary when you're currently making zero. Taking a less-than-optimal job offer is still better than being homeless, though.
For reference, my first web development job paid $12/hr (part-time) in 2007, in the Chicago area. I found this job by cold-emailing job listings on Craigslist.
I'm definitely choosing path 1, which is to become a senior dev. I prefer technical-focused jobs. Learn from mentor programmers, get into teams and learn formal development practices, and then help out programmers less experienced than myself. I've never held a senior title, never led a group, nor even been involved with the process of hiring other programmers.
I currently live in Chicago which is pretty good for COL/salary ratio, for the average programmer. Caveat: I am not average. I consistently get offers from very low paying jobs- as in "$25/hr on a contract" low. This comes from the tendency to being let go from jobs without having another one lined up, so I never could afford to wait much longer for a better offer to use as leverage. Also, I don't qualify for unemployment insurance.
That has put me in the bottom 15-20% of local jobs by total compensation. If I were to restart as a junior programmer at one of the better companies, I'd actually be getting paid somewhat more than at my last job (and with insurance benefits for once).
To be honest, I would rather take more algorithm-focused interview tests than be filtered through the HR perception that I don't qualify for Programming Language Y because I only have experience with Similar Language X. At least most of the companies that do algorithm-based tests are more agnostic about the languages you have used in the past.
Pair it up with the fact that I never look for jobs until I am let go from a job, and I have a double whammy for "hard sell". Something I didn't know that is a bad idea to do until much later in my career. But hey, it's not like we all know about all the things you should and should not do about careers. I just assumed that the only drawback of not having a job is that you have no income stream coming in.
I am able to get through interview rounds with Amazon, and also have gotten the attention of a few interesting companies from my Github projects. But somehow I do not get a good perception with local companies on my resume. Others have helped me out on fixing my resume and they've told me, it's too aimless. It does not have a clear sense of growth and direction, so I am trying out a new resume hoping that my job-searching experience will improve.
I'm mostly talking about people that, for one reason or another, appear to wander around with no clear career progression or direction, so it looks like they are "junior" in experience despite being "senior" in total years worked.
And I think that re-doing careers by switching professions (as you say, chemist -> QA) is different than re-doing career in the same profession. Something like the former is different because it's easier for companies to treat you as a clean slate if you switch to something that has little overlap with your former profession. But I want that clean slate treatement just re-attempting my profession.
For instance, maybe I want to re-do my entry level years because I never got into Computer Science, and would like to get an internship at a leading tech company, because that is a better start than my reality, which was just graduate with no internships, no support group of professionals, nor recommendations for good companies. It was just me going solo and blindly applying to local jobs at Craiglist for low-budget clients.
So yeah, I'm not talking about career switching into another profession, but more like hitting the reset button on one, to do it better the second time around.
I am trying to specialize more in graphics, though I still have to figure out how large is my skills gap between "doing solo graphics projects" and "full-time graphics programmer", especially in math. After getting advice on my resume on how to hide the slow career growth, I've been told to spin it to show I am interested in this niche and show direction towards that.
If you had been able to read my un-revised resume, it would probably read like a story that feels the same in the beginning as it is in the end, with no clear conclusion. So I am working on a new version with a different spin.
Thanks for the replies, everyone. Keep them coming! I didn't expect this topic to get this popular.
The reason I asked this question is that I am facing a career slump as a software engineer, and finding out that the software industry is brutal if you don't know how to carve a path for your own career.
And when I mean career slump, I really mean it. I'm living with my mom at age 35 which is quite the opposite of what someone expects of a software engineer at this age. Most people I know are buying/have bought houses and starting families. And I'm not at a point of self-sustainability yet. I can barely keep up with the insurance payments of my own car, and just keep the vision of having my own place to live in (once more, as I lived alone before things got tough) close to my mind. No longer be dependent of my family, get some privacy, some autonomy and instead of living every day switching between errand boy and going to a coffee shop for the free internet, to apply to jobs, or simply taking a break from my parents.
So that's pretty much me right now. I have 10 professional years of a "whole lot of nothing", no big signs of progression, maturity, or taking on more responsibilities. I didn't major in Computer Science, but I still expected my first programming job to be like, getting a mentor, working alongside a group of (in-house!) programmers, being able to ask them many questions and learn all about formal development practices.
Well, I got none of that in the places that I worked at. So seeing your stories gives me a good idea and hope that I can just move on from the past and have better companies approach me with hope and optimism, like I'm a bona-fide junior eager to learn.
Very difficult to move with only a few hundred dollars in the bank. Also it's generally not recommended to move to a place where you know very few people or no people, without first having a job lined up.