There is a focus on delivering for clients rather than following processes.
I have about an hour of required meetings a week, 15-30 minutes technical meetings where people bring up any tech roadblocks or things where they need help, and a 20-45 minute sprint planning meeting. There's one monthly "show cool stuff" meeting for the whole company where everybody can voluntarily show something interesting they made. The rest of the time, I'm writing code, documentation, helping coworkers, talking to clients, stuff like that.
There is very high trust, e.g. people make honest effort estimates and there's no punishment or bad feedback if they're missed. There's a wide variety of skills because it's hard to attract top performers. This makes it easy to get hired (they immediately invited me for an interview after I sent them my CV, and made an offer after talking to me for 30 minutes), and it also means there's a culture of helping people and being patient and understanding when people are making an honest effort, but don't quite get things on the first try.
I'm working eight hours a day, five days a week, and when I'm done with work for the day, I don't think about it until the next day. It's nice.
Meetings are work.
I can’t say this enough - not all work can be done on your own in an editor or IDE.
And no, it’s often not just busywork. It depends on the domain you’re in and what level of experience your colleagues have.
If you work in anything touching public sector, you’re going to need a lot more meetings to get alignment on even small decisions than if you work on a trading floor. It’s the nature of the beast and how “compliance” is interpreted by different cultures.
Meetings are work.
This sounds like a place I'd enjoy working at.
Email is HN username at gmail.
Thanks
What I would do is look at local governments, at local municipalities. They often have public calls for bids for software projects, like digitizing some forms or processes. Stuff that's too small for big corporations to care about. Look at the companies that apply for these projects. They're often small, local, stable, and starved for good software engineers.
Oh, well said there. Worked consulting for 13 years, and this was the main source of stress. You feel like it's your fault—and are sometimes treated by management like it's your fault—because you're on salary and they have nothing for you to work on. Emphasis on 'they'. That feeling of being on the chopping block, unsure of whether you'll be laid off or not, recurred independently about 3-6 times a year.
Did your firm just never get any extensions to projects? My firm tries pretty hard to get those any chance they get. Or were they all like due diligences or something?
I need to figure out if I go back to professional services again as it can be a strain and I’m late stage career principal/ enterprise architect that joining a company to work on “cool projects to put on your cv” is not a selling point any longer
Try: https://www.crunchbase.com/hub/software-companies-late-stage...
But I also think it’s really personal. Since turning 40 I tried: moving into management at a ~100 dev company; IC at a big tech firm (first time I’d worked somewhere really big as a dev); and now I’m back to running tech side of things at a startup.
I don’t think I could have known in advance which of those was going to work for me. There were a lot of positives to the first two, even though I ultimately left. Turns out I actually do prefer a) small places and b) a mix of management and IC work. But I’m absolutely sure that’s not true for everyone.
OP might feel like they want something very different from running their own startup – I also felt pretty burnt out on that after 7 years of my own – but once they’ve had some time they might remember why they went that way in the first place!
I’m on mobile but try this: https://www.crunchbase.com/hub/software-companies-late-stage...
I work at the Government Contracting arm of Accenture called Accenture Federal and it is by far the best place I've ever worked ( I worked in submarines for a decade so probably nowhere to go but up from there). It ranks highly in those marketing pieces "best places to work" if you're into that sort of thing.
anyway, I highly recommend Accenture Federal. Great projects, benefits, and WLB
It's also important to note that I have a small network of people also working for companies like this who have helped me and sometimes have outright hired me.
> under continuous competitive pressure so it is far from a snoozy place to serve out time - it's a mission and a struggle every day, things change often, the pace is fast
How do you reconcile these 2 statements? Maybe there's something else you mean by work/life balance?
A healthy (what I meant by "good") work/life balance means you work, and you have a life. You have mostly normal hours excepting maybe an occasional crunch or need to travel to a client; you can go to the doctor if you need to; nobody complains if you have to take a few minutes' break to mediate a fight between your kids during the school holidays; PTO is taken by most people and isn't a big deal - that sort of thing.
The second statement is about what the work side is like. There are jobs where you show up, punch a clock, maybe do a code review or make some pointless changes to a CRUD app, but mostly sit around collecting a paycheck. At least for me, that's soul destroying: feeling like you're doing nothing of value, not even contributing to whatever bullshit purpose statement your employer has invented. Then there are jobs where you are flogged to within an inch of your life, abused daily, have your priorities shifted without any input, have to deal with multiple conflicting managers directing what you do, are subject to politics, maybe pay comes late... Awful.
I'm describing a middle way where you are very obviously aware that you're part of a team facing real challenges, your work has noticeable impact, there's effective competition and sometimes they win and everyone feels it. Your days go by quickly, meaningful stuff gets done (at least, within the context of the company if not solving world hunger), the triumphs take effort and the defeats hurt. The problems you're solving are meaty, you're under reasonable but fairly continuous expectation to deliver high quality work and other people and teams are relying on you to do that.
I've been mostly getting away with just over 40 hour weeks, although if I was on any other client at the company I'd be expected to bill 45 hours. PTO is very flexible as long as I'm meeting my utilization for the year (working 85% of potential hours) and can get approval from the client (which for me hasn't been an issue). Even the year where I was a bit under my utilization due to no fault of my own (they didn't have me staffed on a client for six weeks so I wasn't billing anything and then when they finally did at first I could only bill 10-20 hours a week) it didn't stop them promoting me that year and giving me a pretty decent bonus.
Also the only job I've ever had where I can expect an annual bonus worth a damn. I had one for one other job briefly but it was small and they took all bonuses away after two years to save money.
They do encourage working extra hours on internal initiatives and things like that, but I mostly haven't and it hasn't hurt much (maybe I get a slightly somewhat lower bonus and I'm getting promoted a bit slower).
While there's a lot of younger people at the firm, there's several older engineers here too, including a few guys in their 50s.
I'm also like 99% WFH. I go into the office every once in a while for quarterly parties or for some important in-person event, but otherwise I'm fully WFH. Which has been especially important this year as I've been having some issues with my legs and have had to have several medical procedures on them and work on the couch a lot to keep them elevated.
I don't think I could work for one of the Big 4, though, those sound completely exhausting. I hear 60+ hour weeks is often the minumum expectation there. I've got a life outside of work, including games I'm coding in my spare time, I don't need that shit.
Where I am now we're not expected to bill quite as much for this reason. Although I did once work somewhere where there was a requirement for 2250 hours/year billed. Which doesn't seem *to* bad until you take PTO into account and the aforementioned bio breaks.
That being said, I don't worry about tracking bathroom breaks, or the occasional mental break here and there. My client is happy, I'm getting done what they're wanting to get done when they're wanting it to be done, I just bill 8 hours for the day and it's not a big deal (obviously it isn't, they've been willing to pay for me for almost three years at this point on two different projects and I get glowing reviews whenever I request feedback from them to pass along to my boss).
I work 8:30 to 5:30 so that includes an extra hour for lunch, by the way, so that's not counted, no. But I'm at home, so it doesn't feel like work anyway, just an hour to relax, have a sandwich, let the dogs out, and maybe throw a recipe in the slow cooker for dinner.
I'm actually in the middle of a 3.5 week break because I had so much built up time at the end of the year. I knew my client does a two week furlough for consultants at the end of the year so I was already planning for that, and also was planning a week for a wedding trip for a wedding ceremony/reception that had to be cancelled because a recent hurricane pretty much destroyed the town it was going to be held in. And I took a week off for vacation earlier this year.
At least in my case, the quality of my work as a consultant is no worse than any work I've done in industry (and almost certainly better, as I got exposed to more modern practices and worked with a wider variety of people), and I had industry jobs for like 16 years before this job.
My client also requires code reviews with engineers that work for the company internally (technically just other people on the team, but there's a couple internal people on the team that usually do the reviewing), so pretty much everything I write gets internal approval before it gets merged into the codebase.
If I got questioned about that in the interview, I could just tell them that.
Also because my firm is smaller they might not realize it's a consulting firm to begin with just from the name on the resume. It isn't something easily recognizable like Deloitte or Accenture.
It's definitely true for some people I've met, but it's definitely *not* true for others I've met. But if you're interviewing, how does the potential employer know which you are?
I really appreciate my consulting experience just from the sheer diversity of cloud environments and languages I've had to deal with but who knows!
There's about a bajillion C/D+ stage 100-500 person software companies in any B2B vertical you could mention who would fight hard for your type of experience. Not necessarily SaaS click-and-drool tools for corporate drones, but unique and opinionated products that have some significant engineering innovation inside. Those companies have essentially no ability to attract talent organically, anyone interested in FANG would turn up their noses, and their number one problem is quality people. In many cases the CEO/CTO leadership is incredibly strong and smart; the colleagues are happy, motivated, intelligent, and disciplined; and the work/life balance is good for the middle aged. They're vital to their customers but under continuous competitive pressure so it is far from a snoozy place to serve out time - it's a mission and a struggle every day, things change often, the pace is fast. It can be very rewarding and compensation is decent. The tradeoff is the big exit is vanishingly unlikely.
Second idea is go into consulting/professional services. Not Accenture or anything horrible like that, but dozens of boutique/smaller firms with decently inspiring leadership and a very high standard of colleague. Work is variable in interest and environment, pressures are somewhat unfairly around whether you are billable or not which is not really in your control as an engineer.