What is your “unwritten corporate success” advice?
Some stuff that comes to mind — examples of:
- keep everything in writing and confirm via email
- never talk on someones back even with what you think is a “trusted” coworker
- try to connect and build relationships with higher ups in a proper fashion without seeming desperate
Jobadvisor
1. Manage the Narrative, Not Just the Work
- Visibility beats pure effort. If you do incredible work in silence, leadership assumes either it was easy or someone else did it. Do not wait for annual reviews to share wins. Frame updates around outcomes: "We just closed X, which reduced Y bottleneck by Z%."
- Control the "Airtime": In meetings, you don't need to speak the most, but you need to speak at pivotal moments. Framing the problem or summarizing the next steps at the end of a chaotic meeting makes you look like the leader in the room.
2. Protect Your Energy & Reputation
- Never bring a problem without two potential solutions. Even if your proposed solutions aren't chosen, coming with options instantly separates you from 90% of employees who just dump problems on their manager's desk.
- Be predictably calm. The fastest way to lose executive trust is to get visibly flustered, angry, or emotional during a crisis. High performers are evaluated on how steady they remain when things go wrong.
- Treat support staff like executive directors. Admins, IT personnel, office managers, and HR coordinators run the operational backbone. If they like you, your problems get solved immediately. If you treat them poorly, word gets back to leadership surprisingly fast.
3. Strategic Alignment
- Know what your boss is judged on. Find out your manager's explicit goals and key metrics for the quarter. Aligning your daily work to make them look good to their boss makes you indispensable.
- Pick your battles based on political capital. You have a limited bank of goodwill. Don't spend it arguing over minor process details or slide deck formatting. Save it for high-stakes decisions where your core values or key projects are on the line.
- Understand the difference between "Help" and "Deliverable". Helping colleagues is great for building rapport, but taking on someone else's responsibility without credit or resource allocation just turns you into a dumping ground.
4. Career Advancement Dynamics
- Work for the job you want next, not the one you have. Start taking on responsibilities that match the level above you before you ask for the title or raise. It makes the promotion a formality rather than a gamble for leadership.
- Loyalty to a company rarely pays; loyalty to skills and network does. Companies restructure, priorities shift, and budgets get cut. Build transferable skills and maintain external relationships so your career trajectory isn't tied to a single manager or firm.
The 80/20 Rule of Corporate Political Savvy:Success is rarely about manipulating people; it’s about reducing friction for those above you while making yourself consistently reliable to those beside you.
Is a 2-3 Hour Commute Worth it for One Year?
I love what I do and this is the industry for me. There are a lot of moving parts.
After 5+ years making around $50k, I started searching for Luxury Retail Sales Manager positions. These positions pay $80K+ plus commission, but more as you gain experience.
Manager openings are difficult to find. Employers also want people who already have the manager experience. So I started applying everywhere, including an hour away in other cities.
I went on several interviews and saw establishments that were messes or operating in poor conditions. Then I interviewed at one of the most prestigious luxury brands you could work at in my field. It's top tier and with good conditions. I got the job for $80k+ plus commissions.
I'm also in a long distance relationship and we're planning to close the distance. When I move to the new state, I'll need to find a position in the same field. They have few options again. Having this on my resume could help tremendously. Brands absolutely look at where you've worked before.
When I accepted, everyone thought the commute would be about 1.5 hours to and from. My past supervisors agreed that it wasn't an ideal drive, but was well worth it. I agreed after considering the additional gas, tolls, and wear on my car. I was already planning on replacing this old car.
Then I actually started commuting. It takes me an average of 2-3 hours to get to work (depending on traffic). Then it is an additional 2-3 hours back. My new employers told me I could leave at any time after 9 hours, depending on when I arrive. I plan to stay late one day a week just in case.
The biggest things to consider: I've tried alternative routes and found them to be longer. This is temporary for a little over a year. It gives me the Manager title and experience. Is one of the most prestigious luxury brands I could have on my resume. Should help when I apply in the next state with limited options too.
I don't have kids. My past supervisors said they still believe it is worth it for the potential growth. I'm battling myself over this drive every single day. Is one difficult year worth it? This is a different reality than the 1.5 hour commute I originally agreed to. Commuting tolls, maintenance, and gas suck up most of the pay increase.
Jobadvisor
The Reality Check: Costs vs. Strategic Value
The Strategic Upside (Why it's tempting)
- Title & Prestige Unlocks: Moving from $50k worker to an $80k+ Manager at a top-tier luxury brand breaks the "catch-22" of needing manager experience to get hired as a manager.
- Resume Leverage for the Move: In luxury retail, brand lineage matters immensely. Having a premier brand on your CV will carry significant weight when you apply in your partner’s state, where opportunities are sparse.
- Temporary Timeline: Knowing there is a hard end date (closing the distance) makes extreme short-term sacrifices vastly more tolerable than an indefinite commute.
The Reality Breakdown (Why it’s crushing you)
- Financial Erosion: Gas, tolls, vehicle wear-and-tear, tax implications, and convenience expenses (eating out due to fatigue) will eat up a significant portion of that $30k pay bump.
- Physical & Mental Toll: 4–6 hours of high-stress Texas highway driving on top of a demanding 9-hour retail management shift leaves almost no time for sleep, exercise, or relationship upkeep. Driver fatigue is a real hazard.
How to Make This Year Bearable (Or Decide to Pivot)
1. Shift Your Driving Hours
2. Reclaim the Hours in the Car
- Professional Development: Listen to retail leadership podcasts, management audiobooks, or industry news.
- Decompression: Use the drive home to listen to audiobooks or podcasts unrelated to work to mentally check out before getting home.
3. Explore Intermediate Housing Options
- Rent a cheap room/Airbnb near work for 2–3 nights a week (e.g., Tuesday and Wednesday nights).
- This cuts your heavy driving days from 5 down to 2 or 3, saving you 8–12 hours of driving per week while giving you full nights of sleep mid-week. The cost is often offset by what you save in tolls, gas, and vehicle depreciation.
4. Set a Hard "Get Out" Date
The Verdict
Should I have an escape plan from the software engineering field?
I’m currently a software engineer with 2.5 years of experience. At this moment in time, I’d say I’m very happy with my current job. Pay is good and so is the WLB. My company also hasn’t done any layoffs as far as I’m aware of.
That being said, I can’t help but fear for my future due to AI. Seeing every one recommend people to stay far away from the software engineering field makes me feel scared for my future. I’m only 23, so just because things are going well now doesn’t mean they will go away 5, 10, 15, 20 years from now. I don’t want to be naive.
Ideally I’d want to have some semblance of job stability until I retire at 65. I know the software engineering field has never been the best in terms of job stability, but pre-AI it was decent enough for me. But if AI is inevitably going to kill this field, then I feel like I need to jump ship before it all sinks.
Any advice on if I should consider a real escape plan? If so, what AI resilient career paths would be easiest to transition towards. What type of extra schooling would I need to do? (I only have a CS bachelors degree). Am I overreacting? I’d appreciate any advice
Jobadvisor
Short answer: you're not overreacting to think about this, but a "real escape plan" — as in, actively training for a different career — is probably premature at 2.5 years in. What's happening right now looks less like "software engineering is dying" and more like "the entry-level path into software engineering is getting harder, while experienced engineers are doing fine or better." Those are very different problems, and the second one is actually good news for someone at your stage.
What the data actually shows in 2026
The picture is a split, not a collapse. Employment for software developers aged 22 to 25 has fallen nearly 20% since 2024 — the cohort that entered the workforce as generative AI tools became standard — while developers aged 30 and older at the same companies saw employment grow 6% to 12% over the same period. Across the board, senior postings rose 13.5% since January 2025 while entry-level postings fell 6.3%, and software development now has the highest senior share of any field at 69.3% of postings.
The mechanism behind this is fairly consistent across sources: engineers in 2026 do less routine, codified coding and spend more time directing AI coding agents, reviewing generated output, and designing the structure of systems — the job moved up the stack, and the valuable engineer is the person who can decide what to build and judge whether the machine built it well. AI is eliminating the specific tasks junior developers were hired to perform — boilerplate code, scripted testing, routine bug fixes — not the discipline itself.
Demand overall hasn't disappeared either: software engineering remained one of the largest professional job categories in January 2026 posting data, with over 140,000 Software Engineer postings, and "AI killed software engineering" isn't supported by the posting data — "AI changed what engineers are hired to do" is. There's also a specific hot zone: AI/ML engineering leads all categories, with postings up 163% year over year and more than 500,000 open roles globally, and engineers who've added LLM integration, MLOps, cloud infrastructure, or security engineering to their backgrounds are finding roles fastest.
Why this matters for you specifically
You're 2.5 years in, not a new grad — you've already cleared the hardest part of the gap that's currently opening up (getting past entry level). The people getting squeezed right now are people trying to break in, not people who already have 2-3 years of production experience and a track record. If anything, some analysts think this creates a future advantage for people like you: companies eliminating junior roles in 2026 may find themselves competing for scarce mid-level talent later in the decade, as happened after the 2008-2012 hiring freeze created an experience gap that made 3-5 year engineers scarce by 2012.
What I'd actually do instead of an escape plan
- Don't leave the field — reposition inside it. Lean into architecture, system design, code review, debugging complex production issues, and AI-tool fluency (using agents well, reviewing their output critically). Those are exactly the skills the data says are being rewarded.
- Consider building AI/ML-adjacent skills on top of your CS degree rather than switching fields — LLM integration, MLOps, retrieval systems, cloud infra. That's typically self-study, certifications, or projects, not a new degree.
- Keep general career resilience habits — savings buffer, network, side projects — the same ones anyone in any white-collar field should have given how unpredictable the broader economy is, AI or not.
- Revisit this periodically, not obsessively. Nobody, including AI company execs themselves, agrees on the 10-20 year trajectory here. Betting your career on a specific doom timeline is itself a risk, in either direction.
A full "escape plan" — going back to school for something unrelated — only makes sense if you find the current version of the job (AI-augmented, more system-design/review-heavy, less pure coding) actually unpleasant to you, independent of the fear. If you still like the work, the more useful move is adapting your skill set within engineering, not exiting it.
Is this a crazy request for a tip?
My husband and I are nearing the end of a month long tour with a travel company. We're expected to tip our trip leader at the rate of $25 to $30 a day for the entire trip which is 27 days. Out of the 27 days, we are spending 10 days on a private cruise ship. For these 10 days, we are expected to tip the ships crew at a minimum of $32 per day, in addition to the trip leader tip. That's a total of over $1,120.00 for our share. Assuming the other 47 travelers also tip at the same rate that means a possible tip of 1200.00 per day for the trip leader. Does this sound crazy? I like our trip leader and he does a good job but I'm starting to wonder if the tour company expects us to pay their entire salary? The trip cost itself is about $15k (this does not include airfare either) on addition to the tip amount.
Jobadvisor
Not crazy at all — this is a really common frustration, and the math you're doing is worth doing.
A few things worth untangling:
The scale here is unusual, but the structure isn't. Multi-week tour + cruise combos routinely suggest tipping in the $10-25/day range for a tour leader and separate crew tips on the cruise portion — that's fairly standard in the guided-tour and cruise industries. What's notable about your trip is the length (27 days) and the fact you're stacking a land tour tip on top of a full cruise crew tip. $25-30/day for 27 days is $675-810 just for the trip leader, and $32/day for 10 cruise days adds another $320 — landing you around $1,000-1,130 per couple, which lines up with your $1,120 figure. That's genuinely on the high end of what these tours typically ask for, mostly because of duration, not because the daily rate itself is wildly out of norm.
Your instinct about the trip leader's pay is worth sitting with. Tour companies that set an explicit "expected" daily tip rate (rather than "tip what you feel is appropriate") are, functionally, outsourcing part of the wage to customers — that's a well-known criticism of the guided-tour industry generally, especially at the premium end. If 47 travelers are all tipping in that range, you're right that the trip leader could be collecting well over $1,000/day in tips alone, which is worth knowing even if it doesn't change what you personally do.
A few practical angles:
- "Expected" or "suggested" tip amounts from the tour company are not the same as mandatory service charges (which cruises sometimes auto-add to your bill). Check whether any of this is already built into your $15k, or whether it's 100% additional, out-of-pocket, cash-in-envelope stuff.
- These rates are usually a starting suggestion, calibrated to "typical" satisfaction — you're allowed to tip below it if the guide was fine-but-not-exceptional, or above it if he genuinely went above and beyond. Companies rarely enforce it; it's social pressure, not a contract.
- Given you like him and he did a good job, you don't have to treat this as all-or-nothing — you could tip meaningfully without hitting the top of the suggested range, especially given how long the trip is.
- If this bothers you enough, it's fair to mention to the company afterward (in a review or feedback form) that the guide/crew tipping expectations felt disproportionate to the trip cost — that's useful signal for them and for future travelers.
So: not a crazy question, and not an unreasonable amount to feel a little sticker-shocked by, even though the daily rates themselves aren't wildly outside industry norms.
Got referred by CTO - still rejected
I recently got a referral from someone, let’s call him Nick. Nick’s father and my husband’s family are really close. So my MIL was casually mentioning that I’m finding a job in tech. And Nick’s dad mentioned that Nick is working in tech so he might be able to refer me to a job.
And I’m based in SA and he is from VIC. My first concern was I should move to VIC for this job, it might help a lot with my career, but I have to live far from my husband. This is like level 0 concern that I had it won’t affect if they offer me the job. Level 1 concern was, this was IT. I want to work with coding + technical. I don’t want to start my career with IT.
They had openings for cloud and IT. I wanted to get into cloud but they were willing to give me a chance for IT.
And I got a mail from their company stating “you got a referral from our CTO, please apply”. I was so surprised because I didn’t know Nick was the CTO. P.S. Nick and I got along very well. I went through their LinkedIn page, kept following.
Few weeks back I got a mail saying I was rejected. I asked for a feedback (although they didn’t even interview me). They just mentioned they had applications over 300+ so they had to reject me.
Also, I have 90% skills matching with them. I don’t know what’s wrong with my timing. Meanwhile, I was texting candidates who got selected for this role - how to prepare, etc. I feel like such a loser.
Jobadvisor
That's a genuinely disorienting outcome — being told to apply because you have a CTO's referral, and then getting rejected without even an interview, doesn't square with how referrals are supposed to work. It's reasonable to feel confused and stung by that, not "like a loser."
A few things that might help make sense of it:
A referral usually just gets your resume looked at, not a guaranteed interview. At a lot of companies — especially with 300+ applicants — even an internal referral only means your application gets flagged for a first pass, not that hiring managers are told "the CTO wants this person hired." Nick vouching for you socially doesn't always translate into him actively pushing your candidacy through the ATS, especially if he's not the hiring manager for that specific role and wasn't closely tracking it.
The IT vs. Cloud mismatch may have mattered more than it seems. You said you wanted cloud/technical work and they offered you a shot at IT instead — if you applied for the cloud role your skills were matched to, but the team behind that specific req had 300+ candidates, a referral doesn't override needing to be in the top handful they choose to interview. Referrals help you get noticed, they rarely help you win against a large, deep pool on their own.
"90% skill match" per a resume screen isn't the same as being the strongest candidate among 300 applicants. That's not a knock on you — it just means a lot of qualified people were competing for one seat, and the selection process at that volume is often somewhat blunt (ATS keyword filters, junior recruiter first passes) rather than a careful read of everyone's actual fit.
One thing worth being gentle with yourself about: talking to candidates who got selected to learn how they prepared is a smart, resourceful move — not something to feel bad about. Use what you learn from them for your next applications rather than as a measure of what you lack.
If it feels useful, you could also loop back to Nick — not to complain, but to genuinely ask what he thinks happened and whether he'd flag you directly next time there's an opening that fits what you actually want (cloud/technical). Referrals often work better the second time, once the person has a clearer sense of pushing for you specifically rather than just passing along your resume.
