If you show up saying you can develop apps and also manage servers, handle complaints, etc., they will often hand you a lot of responsibility to do things yourself.
Not great for advancing as an engineer unless you actively challenge yourself, but I’m just suggesting that it’s a field out there.
I did this for an education company. Been employed over a year, developed a few web apps for them, basically been handed keys to the kingdom, and they love my work.
Most of my best times as a software engineer was when I worked at non-techy firms. When I worked at a local NPR affiliate station, I was able to both solve new problems and improve existing things without a lot of the buffoonery seen at a lot of hip tech firms. As a mid level developer at the time, I had lots of room to try things and could afford to fail, yet my seniors actually had time to help.
A lot of people not happpy with their careers should consider non-tech over hip startups, Silicon Valley, and fintech. You will still encounter headaches, but you may also avoid a lot of the mental agony from the big tech world.
I run an ecommerce business, which is at best tech-adjacent (honestly I would say a farm using fairly advanced technology for their industry is more of a tech company than me using Shopify to sell dog treats online), and people love hearing about it.
Honestly, part of why I left enterprise software was because I found a lot of the SMB customers I worked with really inspiring. They were doing something... real/physical/tangible, and of course the ones who were looking at our software were the smart, tech-savvy types who I could relate to.
While I have very little desire to go back into enterprise software, sometimes I do get pings from recruiters hiring for companies that do stuff like agtech, and I think that working on something like that (as opposed to making software for call centers, which I have done) might be worth getting back into the working world for.
LOL! Quote of the day. And it’s true. Farmers got techy before most other industries. I remember seeing farmers around 1990 getting weather and crop reports online daily, when most families hadn’t yet bought their first PC, let alone connected to a BBS.
This is how I make money. I create products that serve real needs of real businesses / people. Bit of warning - I am not a direct employee for those businesses, I have my own company that does product design / development and contract as such. Still I get much satisfaction looking at my products doing something real
It gets exhausting having to repeatedly say "we are going over budget due to unforseen complications as a direct result of low quality code".
It gets exhausting having to constantly rework solutions to fit the boneheaded design decisions made with zero forward thinking.
My previous job was Generic Startup 7,923™ with a company-provided snack table, and company-provided lunches once every week. The other devs there were decent people. My boss certainly expected too much though. Now I know what not to look for in a job.
I think that's true when joining a young startup (e.g. company less than 2-3 years old).
But there are plenty of 15-40 person "startups" that have been around for 5+ years and are profitable - I would say these types of companies are good to join (if they've had a stable and consistent management team) since after 5 years, the company would have worked out most culture / HR kinks.
PS - things like "are you profitable" and "tell me about the management team/culture" are very acceptable questions to ask during an interview.
Edit: "how many employees were there 1 year ago" is also a good barometer for how hastily the company is scaling. If they're 100 today but were 50 a year ago, I'd steer clear. As another commenter mentioned, go for slow and steady growth startups rather than high/fast growth.
I think the distinction has more to do with the culture / vision of the company than just company age.
Neither really have much to do with age. An agency can be doing contract work for 10 years looking for a business model, and it could technically be a startup.
Honestly never understood why joining startups is meant to be so amazing unless 1) They are working on exactly the niche that YOU personally want to work in and 2) The startup's company culture is exactly your kind of weird/niche culture too. IMO unless it's a perfect match, you're going to have a bad time as there is less stability and diversity of ideas/experience in small startups.
I love large orgs because there are tons of characters, experienced professionals and frameworks designed to support and enable me. I can always move projects when I get bored or something isn't right.
I would join a startup however if there is something very very specific I want to build and I want to circumvent all the corporate barriers/rules to move fast and ship something. But so far, I've not felt that yet.
This comment is so underrated. In most big companies, if your manager is an asshole or the project is boring, you can always move to a different role.
People who switch faster either have very accommodating leads or they feel secure enough to give an ultimatum.
Meanwhile, investors reward the company for "traction" and regardless investors both private and in the public markets reward growth at whatever expense and first-mover / big-mover advantages.
The sweet spot are those financially stable, slowth growth companies with enough employees so that people aren't worn too thin but not too many that the wheels are coming off. Often that's around 100-300 or so, could be less a bit more.
It sort of sucks, but idk - in my late twenties I'd like to think I have a much better understanding of what makes me happy now.
I'm actually trying to pass FAANG interviews and it sucks, but at the same time I've realized just optimizing for TC over the next few years is something I actually prefer.
I happen to be close to some people who work at the CDC tabulating death statistics. You know what one of their greatest success stories over the past few years was?
Updating their death-reporting from once-per-year to once-per-month (albeit preliminary / unreliable statistics, but monthly reports nonetheless). They still revise the numbers up to a year out but it turns out that having this project done _BEFORE_ COVID19 hit helped a lot, since decision makers at the White House (and other parts of the country) got the statistics they needed faster.
And before you say its easy: the 50 states have 50 different death certificates. The information is standardized but the data-entry and reporting methodologies are non-standard. Plus territories (ex: Wash DC, Puerto Rico, Guam also have their own death certificates). Pushing for more standardization (ex: the rules for how to report COVID19 deaths and on what line) and pushing that training out to doctors also results in partisan bickering, as you might expect.
----------
Doing these kinds of things is a massive undertaking in general. If computers were easy, everyone would do it. A lot of it is just growing up and realizing that the Iron Man movies you watched 10 years ago are unrealistic crap, and that the daily grind to make small bits of progress are hugely important.
Other bits are to truly celebrate these accomplishments, even in the face of widespread disdain. There's a ton of people giving crap about the CDC's death statistics with regards to COVID19 (some legitimate criticisms due to the accelerated release schedule they've got behind monthly statistics). But a lot of the criticism is just partisan bickering that no one really takes seriously. Everyone basically agrees that monthly-reporting (though less accurate) is better than waiting a whole year.
Still, its hard to argue against progress or the usefulness of this "monthly death statistic reporting" project. Originally created in response to Hurricane Maria (where US Newspapers reported a different death number than the CDC), the whole project was launched just in time for COVID19 (and was online for part of the opioid epidemic as well).
EDIT: That goes to show what a "real success" is like. Its like lighting in a movie: if you do it perfectly, no one notices. If you make the slightest mistake, a ton of people online make a big stink about it. High risk, low / non-existent reward. But its hard to deny the importance of the project. This is the prototypical "easy job but not really" scenario, everyone just expect it to get done, people don't really realize how hard it is to do (50+ states with 50+ different formats. In the case of the Opioid Epidemic, there was new language being used on Death Certificates that didn't exist before, words like Fentanyl, and people just expected the CDC system to automagically detect these words, new-misspellings and collate results together despite no one actually asking for that feature, etc. etc.)