Engineering Career Guidance

YOUNG ENGINEER: WHY ARE YOU SPECIALIZING SO EARLY? I always find it fascinating when I sit down with fresh graduates in Civil Engineering. The conversation often goes something like this: “I’m interested in roads.” “I want to work in water.” “Structures are my passion.” And my next question is always: “So why did you choose Civil Engineering in the first place?” Don’t get me wrong—focus is important. But in a small economy like ours, where opportunities are already limited, narrowing your scope too soon can mean closing doors you haven’t even seen yet. Civil Engineering is vast, and boxing yourself into one corner at the start of your career can reduce your chances before you’ve even begun. My Own Journey When I graduated from university, I made a deliberate decision: I would learn everything I could, across the board. I started in roads, then moved into water and sanitation, then into structures. Over time, I mastered structural designs, water treatment plant designs, sewage lagoon designs, and pipeline designs. I became comfortable moving from one discipline to another, learning not just the theory, but the practical skills each field demanded. The Results of Staying Versatile Fast-forward 20 years, and I can confidently say it was the best professional decision I ever made. I have worked across multiple disciplines of engineering. Not once in 20 years have I been jobless. I’ve been part of over 200 projects, both small and massive in scale. When a road project comes—whether design or construction supervision—I work like a roads specialist. When a large water project lands, I take it on like a water expert. I’ve delivered irrigation projects, supervised bridges, contributed to hydropower designs—you name it. That flexibility has kept my career not only stable but exciting. It has also made me an asset to clients and employers who value professionals that can adapt to any engineering challenge. My Advice to Young Engineers In the early years of your career, don’t rush into a narrow specialization. Instead: Expose yourself to all areas of the profession—roads, water, structures, geotechnics, environmental engineering, and more. Learn by doing—seek diverse projects, even if they push you out of your comfort zone. Build a wide skill base—so that no matter the project, you can confidently say, “I can do that.” There will be plenty of time to specialize later, once you’ve built a solid foundation. But in the beginning, aim to be versatile. In a world where change is constant, versatility is not just an advantage—it’s survival. So, I ask again: Young Civil Engineer—why are you specializing so early? Joel Aita Chairman, Joadah Consult

A common question I get from PhDs - should you go deep or go wide with your research. Here is the advice I wish I had received on day one. First, choose your preferred destination after your PhD. Academia, industry, or consulting all require slightly different skill sets. Academia: Master one method you can defend at viva depth, then show you can integrate other tools (like TEA/LCA/optimisation) to answer “so what?”. Industry/consulting: Be T-shaped. One core method that delivers results, plus adjacent skills to quantify impact and risk. Here's how my career path developed. I went deep into process modelling and optimisation during my PhD. Reviewers asked for TEA/LCA. I learned both. It was the best detour I took that has defined my career. Stack your skills like a service package and follow a simple plan: 1. Pick one core method to master. 2. Add two adjacent methods that make results decision-ready. TEA and LCA are classics. 3. Define a narrow problem within one theme and stick to it. 4. Package outputs as assets: models, datasets, figures, and reusable workflows. Do this and any committee or client will know precisely why you matter. Your turn: What is your destination after the PhD, and what will be your core method? #Research #Science #Scientist #Academia #Career #Professor #CarbonCapture #CareerStrategy

Feeling Stuck in Your Career? It Could Be a Competency Gap! 🚀 A few years ago, I worked with a team member, who was frustrated about being stuck in his role. He was technically skilled but couldn't figure out why promotions were passing him by. 💥That’s when we turned to competency mapping. 🔍 Together, we identified the key skills his position and future roles required—things like communication, leadership, and strategic thinking—which are critical competencies for growth. While he excelled in technical work, his communication skills needed refinement to step into leadership. By aligning his personal development with these competencies, we created a clear roadmap for his growth. Within a year, he sharpened his communication skills and was promoted to Team Lead. Competencies aren't just about what you’re good at now, but what you need to master for future success. Think of them as the blueprint for your career development. 💡 Key Competencies You Should Focus On: 💢Technical Expertise: Mastering the core skills required for your current role. 💢Communication: Expressing ideas clearly and collaborating with teams. 💢Leadership: Guiding teams and driving performance. 💢Strategic Thinking: Seeing the big picture and aligning with long-term goals. 💢Collaboration: Problem-solving and creating synergy within teams. 🔑 Key Action Points: 🖊️Identify the competencies needed for your next career step. 🖊️Compare your current skills with those required competencies. 🖊️Develop a plan to close any gaps through learning and experience. Feeling blocked in your career? It might be time to assess your competencies and create a growth plan. 📝 Start mapping your competencies today and take the first step toward unlocking your potential! #CareerGrowth #Leadership #CompetencyMapping #PersonalDevelopment #LifelongLearning #SkillDevelopment #LeadershipSkills #CommunicationSkills #ProfessionalGrowth

I asked 7 levels of engineers to share the most important skill for their level. L3 New Grad (Uriel Sejas): 🏋♀️ Skill: Learn from existing patterns to solve common problems. 🦉 Advice: Leverage engineers on other teams who may help unblock you. L4 Mid-level Engineer (Dipika Tiwari): 🏋♀️ Skill: Efficient log analysis to identify and debug issues. 🦉 Advice: Keep notes on your work so you become increasingly self-sufficient. L5 Senior Engineer (Richard Chen): 🏋♀️ Skill: Align project expectations and ensure projects benefit both the company and your growth. 🦉 Advice: Build strong relationships with people you work with, helping them where possible. L6 Staff Engineer (Sam Nguyen): 🏋♀️ Skill: Level up your team and ensure they internalize feedback to become independent. 🦉 Advice: Learn the problems in the org by talking to many people. L7 Senior Staff Engineer (Kaushik Gopal): 🏋♀️ Skill: Instead of just doing eng work, spend time identifying, executing, and measuring impact. 🦉 Advice: Talk to different stakeholders (business, customer support, PM) to identify areas where the company struggles. L8 Principal Engineer (Chantat Eksombatchai): 🏋♀️ Skill: Effective technical communication to delegate tasks effectively and collaborate with others. 🦉 Advice: Principal engineers are role models for an entire org and therefore determine the culture. L9 Distinguished Engineer (Andrew Zhai): 🏋♀️ Skill: Combine strong business acumen with technical expertise to lead large, impactful projects. 🦉 Advice: Pursue the most impactful projects and navigate the company to make them happen. Full video: https://lnkd.in/gbCKPPji

Your career has broadly 3 phases: 1. Early Stage (0–5 years) In this phase, companies hire primarily for attitude. They look for: > Are you willing to put your head down and work on what’s assigned? > Are you eager to learn, adapt, and stay dependable? You may not have absolute clarity on your long-term path — and that’s okay. At this stage, it’s your coachability and curiosity that matter most. You grow by: → Obsessing over learning and absorbing from every opportunity → Making career switches every ~2–3 years for exposure and acceleration → Job application mix: ~80% job boards, 20% referrals ⸻ 2. Mid Stage (5–12 years) Now, you’re expected to have clarity: on the role, domain, location, and the kind of company (startup, MNC, etc.) you want to work with. Hiring managers are more conservative with lateral hires — they want proof of outcomes, not just potential. You grow by: → Building deep expertise in your chosen space → Learning to showcase your work — online and within the org → Making internal or external moves every ~3–6 years → Job application mix: ~50% job boards, 50% referrals ⸻ 3. Leadership Stage (12+ years) At this stage, no company is waiting on Naukri or LinkedIn hoping someone applies. Opportunities are created through trust, visibility, and networks. You grow by: → Expanding your strategic thinking and decision-making impact → Building influence — inside and outside the company → Investing in relationships that open doors Job application mix: ~20% job boards, 80% referrals/network pull ⸻ Every phase demands a different version of you. What phase are you in? And are you playing the right game for it? #career #growth #jobsearch #leadership #careeradvice

One of the best moves I made early on in my career was finding mentors. Not just one but three; if you’re going to learn, you might as well get a full panel of judges. I believe in a 360° approach to everything. One with way less experience than me; because fresh eyes see what veterans overlook. One a few years ahead; because they just fought the same battles I was facing. One who was an executive board member; because why not get advice from someone who is where you hope to get to, and who makes the big decisions? Now, I didn’t just slide into their DMs and say, “Hi, can I pick your brain?” (Please, don’t do this. Ever.) I earned my mentors. Earned. They saw my diligence, my hard work, my intelligence, and my commitment. They saw that I actually listened, applied their advice, and took action. I wasn’t just looking for a free roadmap. I was willing to do the work. And I gave back, too. I shared insights from my own experiences. Yes, everyone can learn from anyone. I connected them with people and resources they found valuable. I helped with projects, research, or anything that made their lives easier. I showed up prepared, engaged, and ready to execute on their advice. Moral of the story? Find mentors at different levels. You need wisdom from above, below, and right next to you. Don’t just slide into their inbox with a generic ask. Stand out. Be specific. Show initiative. Offer something in return. Mentorship is a two-way street, not a charity. Be consistent. Real mentorship isn’t a one-off convo; it’s a relationship. Follow up. Show growth. Actually do the work. A mentor’s advice is useless if it just sits in your notes app. And then there are the silent mentors, the ones who don’t even know they’re mentoring. I call this Ghost Mentoring. Have you had any experience with mentors, officially or in ghost mode? #CareerMentor #TalentManagement #PersonalDevelopment

Career paths are linear. You study something, you become that thing. The reality: Before Mr. Bean existed, Rowan Atkinson was an electrical engineering postgraduate at Oxford. His master's thesis examined self-tuning control systems. He started a PhD. Then he dropped out. To become one of the highest-paid comedians in British history. What this actually demonstrates: Atkinson did not waste his engineering education. He applied it differently. Watch any Mr. Bean sketch closely. The timing is algorithmic. The physical comedy is iterative, testable, reproducible. Every facial expression is calibrated for maximum effect. Richard Curtis, his collaborator, described his first unrehearsed performance at Oxford as "pure genius." It was also pure precision. Engineering teaches you to optimize systems. Comedy is a system. Audience response is a feedback loop. The structural insight: The question is never whether your training was wasted. The question is whether you can identify transferable mechanisms. Atkinson did not abandon engineering. He redeployed it. The implication: If you are a PhD student in a field that no longer fits, or a scientist whose industry is contracting, the path forward is not to discard your training. It is to recognize that analytical precision, systems thinking, and iterative problem-solving are transferable assets. The domain changes. The methodology does not. It is never too late to redeploy what you know into what you love.

The job market has evolved, and so must we. Simply showcasing a portfolio of finished projects isn’t enough anymore. Employers want evidence—proof of how you think, solve problems, and continuously learn. 🚀 In my latest blog, I share why traditional approaches to landing a tech job no longer work and introduce an evidence-based framework for success. This strategy focuses on creating polished artifacts that: ✅ Showcase your decision-making process. ✅ Highlight your technical and problem-solving skills. ✅ Build meaningful connections in your network. At Vets Who Code, we have seen this approach transform careers. Participants have achieved faster job placements, expanded their professional networks, and become empowered veterans who stand out in the tech world. 💡 Whether you are just starting or looking to stay ahead in a competitive market, this framework can help you take your career to the next level. 👉 Read the full blog here: https://buff.ly/40sVwaI Let’s start creating artifacts that tell our stories, showcase our skills, and prove our value in real time. The future belongs to those who can demonstrate their worth.

I Was Wrong—And You Are Too (Or, The Lies Experience Tells You) I started as an engineer, hired for my ability to build things and solve problems. But when I moved into management, something shifted. I wasn’t writing code anymore—I was making decisions that shaped teams, projects, and strategies. Over time, what people valued most wasn’t my technical skills, but my judgment: recognizing patterns, making good decisions, and bringing perspective. That’s what we usually mean by wisdom—not just knowing things, but knowing what works and what doesn’t. But here’s the catch: technology moves fast. And some of the patterns I relied on turned out to be wrong. Not because they were never true, but because I wasn’t questioning them often enough. For years, I believed speed and reliability were in conflict. Move fast, and you’d sacrifice stability. Optimize for reliability, and you’d slow down. And at the time that was mostly true—continuous deployment was immature, testing was inconsistent, observability was limited. But things changed. Today’s top teams balance speed and reliability by designing for resilience, automating deployments, and utilizing advanced monitoring and rollback mechanisms. My thinking hadn’t kept up with this evolution. That’s the real danger of wisdom—it feels like truth when it’s just outdated experience in disguise. You’ve seen something fail before, so you assume it always will. You’ve seen something work, so you treat it as a universal rule. Just because something didn’t work five years ago doesn’t mean it won’t work now. And just because a pattern held true in the past doesn’t mean it always will. The real problem isn’t having strong opinions. It’s not revisiting them. I’ve caught myself doing this more times than I’d like to admit. A new idea comes up, and my first reaction is skepticism: I’ve seen this before. I know how this ends. But if I’ve learned anything, it’s this: being too sure is dangerous. The best engineers and leaders I know aren’t just wise—they’re curious. They don’t just rely on past experience; they keep learning, questioning, and re-examining their assumptions. They use experience as a guide, not a rulebook. Wisdom is valuable—until it isn’t. The best decisions come not just from experience, but from staying curious, challenging assumptions, and staying open to new ideas. Technology moves forward. If you’re not rethinking old assumptions, you’re falling behind.

𝗪𝗵𝗶𝗰𝗵 𝟱 𝘀𝗸𝗶𝗹𝗹𝘀 𝘄𝗶𝗹𝗹 𝗺𝗮𝘁𝘁𝗲𝗿 𝗺𝗼𝘀𝘁 𝗳𝗼𝗿 𝗔𝗜/𝗠𝗟 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗶𝗻 𝟮𝟬𝟮𝟲—𝗮𝗻𝗱 𝘄𝗶𝗹𝗹 𝘀𝘁𝗶𝗹𝗹 𝗺𝗮𝘁𝘁𝗲𝗿 𝗶𝗻 𝟮𝟬𝟯𝟬+? As AI grows exponentially, the focus is shifting from building demos to shipping outcomes. Roles are getting merged. 𝗧𝗲𝗮𝗺-𝗼𝗳-𝗼𝗻𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 are becoming the norm. To survive and thrive, we need to move from focusing just on tech to a hybrid stack of tech + business + leverage. Here are the top 5 skills that we need to build for sustained career growth. 1. 𝗔𝗜 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 & 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗔𝗰𝘂𝗺𝗲𝗻 ( 𝗼𝘂𝘁𝗰𝗼𝗺𝗲-𝗳𝗶𝗿𝘀𝘁 𝗘𝗻𝗴𝗴.) : Stop asking which model. Start which workflow + what outcome + which metric + what ROI? 2. 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝘃𝗲 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 & 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝘀𝘁𝗼𝗿𝘆𝘁𝗲𝗹𝗹𝗶𝗻𝗴 (𝗜𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝗰𝗹𝗮𝗿𝗶𝘁𝘆) : Write business memos, explain tradeoffs, translate model metrics to business metrics, create alignment. 3. 𝗖𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 (𝗦𝗵𝗶𝗽𝗽𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗽𝗲𝗼𝗽𝗹𝗲, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗰𝗼𝗱𝗲) : You will now spend more time communicating than coding. Learn collaboration techniques, negotiation, conflict resolution, stakeholder alignment, cross-team rollouts. 4. 𝗣𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 & 𝗔𝗜-𝗡𝗮𝘁𝗶𝘃𝗲 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗶𝘁𝘆 (𝗯𝘂𝗶𝗹𝗱 𝘆𝗼𝘂𝗿 𝗼𝘄𝗻 𝗹𝗲𝘃𝗲𝗿𝗮𝗴𝗲): Your fastest ROI is in automating your own work. Leverage AI based generators, copilots, automation and collaboration. 5. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻-𝗚𝗿𝗮𝗱𝗲 𝗔𝗴𝗲𝗻𝘁 𝗦𝘆𝘀𝘁𝗲𝗺𝘀 (𝗲𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 & 𝗿𝗲𝘀𝗶𝗹𝗶𝗲𝗻𝘁) : Focus on distributed architectures, evaluation, observability, scale, safety, security and cost controls. As more and more technical tasks get automated, individual engineers need to step up to execute multiple roles and drive outcomes. 𝗜𝗳 𝘆𝗼𝘂 𝗰𝗮𝗻 𝘀𝗶𝗻𝗴𝗹𝗲-𝗵𝗮𝗻𝗱𝗲𝗱𝗹𝘆 𝘀𝗵𝗶𝗽 𝗮𝗻 𝗮𝗴𝗲𝗻𝘁 𝗶𝗻𝘁𝗼 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻, 𝗺𝗲𝗮𝘀𝘂𝗿𝗲 𝗶𝘁, 𝘀𝗲𝗰𝘂𝗿𝗲 𝗶𝘁, 𝗮𝗻𝗱 𝗲𝘅𝗽𝗹𝗮𝗶𝗻 𝗶𝘁𝘀 𝗥𝗢𝗜 𝗰𝗹𝗲𝗮𝗿𝗹𝘆... 𝘆𝗼𝘂’𝗹𝗹 𝗯𝗲 𝗶𝗻 𝘁𝗵𝗲 𝘁𝗼𝗽 𝘁𝗶𝗲𝗿. Thoughts? What is the #1 skill you are prioritizing in 2026... and why? #AI #MachineLearning #GenAI #AIAgents #LLMOps #ProductManagement #Leadership #CareerGrowth