Engineering Career

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

𝐓𝐡𝐢𝐧𝐤𝐢𝐧𝐠 𝐨𝐟 𝐲𝐨𝐮𝐫 𝐜𝐚𝐫𝐞𝐞𝐫 𝐚𝐬 𝐚 𝐥𝐢𝐧𝐞𝐚𝐫 𝐬𝐜𝐫𝐢𝐩𝐭 𝐢𝐬 𝐚 𝐛𝐮𝐠. It’s actually a 𝐝𝐢𝐬𝐭𝐫𝐢𝐛𝐮𝐭𝐞𝐝 𝐬𝐲𝐬𝐭𝐞𝐦 𝐩𝐫𝐨𝐛𝐥𝐞𝐦 requiring high availability and fault tolerance. I realized that choosing a specialization in tech—be it Cloud Architecture, DevOps, or Full Stack—follows the same heuristics we use for 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝐬𝐢𝐠𝐧. Here is the breakdown of the "𝐂𝐚𝐫𝐞𝐞𝐫 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞" protocol: 1. 𝗗𝗮𝘁𝗮 𝗜𝗻𝗴𝗲𝘀𝘁𝗶𝗼𝗻 (Know What You Like): Just as we analyze logs to understand system behavior, analyze your history. What topics do you advocate for during lunch? What GitHub repos do you star? This is your baseline telemetry. 2. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗣𝗿𝗼𝗳𝗶𝗹𝗶𝗻𝗴 (Heatmaps): In the sketch, I drew a heatmap matching "Good At" vs. "Like." In engineering terms, this is finding the sweet spot between 𝗧𝗵𝗿𝗼𝘂𝗴𝗵𝗽𝘂𝘁 (volume of work you can handle) and 𝗟𝗮𝘁𝗲𝗻𝗰𝘆 (how much drag you feel doing it). 3. 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗗𝗲𝗯𝘁 𝗔𝘃𝗼𝗶𝗱𝗮𝗻𝗰𝗲 (The 'Yuck' Stuff): This is crucial. Just because you are efficient at cleaning up messy legacy code doesn't mean you should specialize in it. If a task has high proficiency but low satisfaction, it represents future burnout—essentially, 𝒄𝒂𝒓𝒆𝒆𝒓 𝒕𝒆𝒄𝒉𝒏𝒊𝒄𝒂𝒍 𝒅𝒆𝒃𝒕. Deprecate these tasks early. 4. 𝗘𝘅𝘁𝗲𝗿𝗻𝗮𝗹 𝗔𝗣𝗜 𝗖𝗮𝗹𝗹𝘀 (Ask the Big Kids): Don't rely on cached data. Poll external nodes (Seniors, Principals). Ask about their daily stack, their leadership exposure, and their context switching overhead. 5. 𝗧𝗵𝗲 𝗖𝗔𝗣 𝗧𝗵𝗲𝗼𝗿𝗲𝗺 𝗼𝗳 𝗖𝗮𝗿𝗲𝗲𝗿𝘀 (Pick 2 & Look Closer): You usually have three metrics: 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴, 𝗙𝘂𝗻, and 𝗣𝗮𝘆. It is rare to get strong consistency across all three immediately. Analyze your "Career Castles" (A vs. B) and decide which trade-off is acceptable for this specific epoch of your life. 6. 𝗥𝗼𝗹𝗹𝗶𝗻𝗴 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 (Start): Analysis paralysis is the enemy of uptime. If the metrics are close, deploy the instance that you are leaning toward. You can always rollback or re-architect later. Your career isn't a waterfall model; it's agile. Iterate often. Don't worry about a path not working out, you can always roll back :) #CareerPath #SystemDesign #SoftwareEngineering #TechCareers #Sketchnote

Navigating career decisions isn't a walk in the park, especially when you have options and uncertainties. But don't worry, there's a way to bring clarity to the chaos with a structured approach that considers both logic and emotion. Let's dive in. 1. Clarify your decision: Start by pinpointing what decision you need to make. Are you choosing between job offers, or are you contemplating a new career path? Having a clear objective is crucial. 2. Define your priorities and values: List your top 4-7 priorities for your career, such as career growth, impact potential, and personal satisfaction. Also, identify your core values and what truly matters to you. These can guide you to choices that align with your long-term fulfillment. 3. Generate more options (if possible): Don’t limit yourself to a couple of choices. Use your priorities and values to brainstorm additional options, considering both immediate and long-term possibilities. Talk to people you admire, explore job boards, and think outside the box. 4. Rank and test your options: Once you have a list, rank them based on how well they align with your priorities. Then, dive deeper into your top options—talk to people you know, check YouTube, or even test the waters through short-term projects. This helps in reality-checking your assumptions and understanding the true landscape. 7. Assess risks, regrets, and reversibility (a critical step, in my opinion): Evaluate the risks and potential regrets tied to each choice. Consider what could go wrong and whether you're prepared to handle those challenges. Also, think about how easily you could switch paths if necessary and what opportunities you might miss by not choosing a particular option. As my wife wisely suggested, try tossing a coin and pay attention to your immediate reaction to the outcome—it can reveal your true preferences. 6. Incorporate emotional insights (gut feeling): Pay attention to your emotional responses and gut feelings. They can provide important insights into whether a decision aligns with who you are at your core. Balance these with your systematic analysis for a well-rounded decision. 7. Make your best guess and look ahead: At some point, you'll need to make a decision. Trust the process you’ve followed and don't look back. 8. Take action: Once you've decided, focus on execution. Break your plan into actionable steps and set milestones to track your progress. Career decisions are part of an ongoing journey of growth and exploration. They are not linear and don't have to be. Just focus on what is best for you and your life; the rest is just noise.

Should Engineers Stay Technical or Move to Management? 🤔 Most engineers hit this crossroad after 3–5 years. 👉 Stay technical and become a specialist? 👉 Or move to management and lead teams? Here’s the truth most people won’t tell you: Both paths pay well, but require VERY different mindsets. ⚙️ Technical Path (Specialist) You go deep. You become the go-to problem solver. High value = rare skills. Think: design expert, system architect, technical authority. 📈 Management Path (Leader) You go wide. You manage people, deadlines, stakeholders. High value = decision making & leadership. Think: project manager, department head, business driver. ⚠️ The mistake? Many engineers jump to management too early without strong technical foundation. Result: ❌ Weak decisions ❌ No respect from team ❌ Constant stress 💡 The smart move: Build solid technical credibility FIRST… Then decide if leadership is your game. Because in reality: 👉 Great managers understand technical depth 👉 Great specialists understand business impact You don’t choose blindly. You choose based on your strength. So… what’s your path? ⚙️ Technical Expert or 📈 Engineering Leader 👇 Drop your choice in the comments & tell me why. Follow for more real talk on engineering careers.

In my 20+ year career in Software Engineering, I’ve been an IC, a VP of Engineering, and now CEO. Here is what I tell  engineers who struggle to choose the right career path: 1. Soul search You have to be honest with yourself – do you want to go down the managerial path or continue being an IC? Either way is fine. Today, any good company values both tracks, and there’s no longer a need to move into management to progress in your career. 2. The modern IC path If you want to stay as an IC because you thrive in technical challenges and innovation, you can still rise to senior levels – some companies have ICs at VP, SVP, or even Fellow roles. This way, you can stay hands-on and do what you love most without the responsibilities of managing a team. 3. The managerial mindset The role of a manager goes beyond being the “smartest engineer” with people reporting to them. Managers need credibility, but more importantly, they need empathy and a mindset shift. The question becomes: "How can I bring out the best in my team?" rather than "How can I be the best engineer?" 4. The unseen work of management If you want to be a manager, understand that 90% of your work will be invisible to your team. You’ll be in meetings, managing schedules, and coordinating across departments. You’re there to unblock your team so they can do their best work. These accomplishments may be invisible, so you might go home some days wondering, “What did I really accomplish today?” That’s normal. 5. Test the waters If you’re curious about management, test the waters before you commit. Start as a lead engineer. Mentor a couple of people and see how you guide them through challenges. Great companies support new managers with training and mentorship – if your company doesn’t, seek support outside or be prepared to learn the hard way like I did.  Early on, I thought I had to be the smartest person in the room. However, my mistakes and guidance from mentors quickly taught me that real leadership is about empowering others, not proving yourself. 6. Cultural fit and company support Some companies support managers and value leadership qualities. They know that a great manager is there to build teams that can find solutions (not to have every answer themselves). And they contribute to the company’s bottom line and top line by bringing out the best in their teams. Final thoughts: Today, both paths can lead to a fulfilling career. I know successful ICs who built incredible careers without managing a single person. I also know outstanding engineering leaders who value helping everyone become the best version of themselves. So ask yourself: Who do you want to be, and what drives you?

I coach engineers who have strong reviews and weak direction. A few months ago, I sat on a call with a mechanical engineer. Good title. Good team. No spark. He told me he was tired of long cycles, pointless meetings, and endless status updates. He wasn’t lost. He was unmeasured. So we did something simple. No pep talk. No leap. We opened a blank sheet and started logging his work for 30 days. - Task. Time. Energy after each block from 1 to 5. - Dread before each recurring meeting from 1 to 5. - 3 peers to name his top strengths. Week 1 looked random. Week 2 showed a shape. Week 3 told the truth. His energy peaked in customer conversations and integration work. It sank in status meetings and politics. Peers kept naming the same skills he underused. We didn’t quit anything. We ran a test. He shadowed a teammate for 2 afternoons. He joined 1 cross-functional sprint. He took a short consulting project. That was enough signal. He moved into Solutions Engineering. Same person. Different job. Better fit. This is what most #engineers miss. - You manage projects with data. - You try to manage your career with hope. My latest article for the Engineering Management Institute lays out the exact process we used. 1. What to track for 30 days. 2. How to run small, low-risk tests. 3. How to read the signal and choose your next #career move. Career Pivots in Engineering: A Data-Driven Approach to Change https://lnkd.in/gvqR5ADW What’s the one task on your calendar that gives you energy every time? Start measuring that. Then test around it. Engineer Your Mission

A lot of early-career engineers are worried about picking the right role. Here are 5 tips to make sure you're headed in the right direction. With so many industries and job titles, it’s easy to feel stuck or worried about making the wrong choice. Here’s the good news: You’re not locked in. Many engineers switch industries and roles over time. 𝟭. 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝗪𝗵𝗮𝘁 𝗘𝘅𝗰𝗶𝘁𝗲𝘀 𝗬𝗼𝘂 Think back to your coursework, internships, or projects. What got you excited? CAD design? Circuit analysis? Manufacturing processes? 𝟮. 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵 𝗪𝗵𝗮𝘁’𝘀 𝗶𝗻 𝗗𝗲𝗺𝗮𝗻𝗱 Check job boards, LinkedIn, and industry reports to see what roles are in high demand. The more openings, the better your chances of landing a job faster. 𝟯. 𝗖𝗼𝗺𝗽𝗮𝗿𝗲 𝗬𝗼𝘂𝗿 𝗦𝗸𝗶𝗹𝗹𝘀 𝘁𝗼 𝗝𝗼𝗯 𝗗𝗲𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻𝘀 Pick 10-15 job descriptions that interest you and highlight the most common skills. If you’re missing key skills, start learning them now. 𝟰. 𝗧𝗮𝗹𝗸 𝘁𝗼 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗶𝗻 𝗧𝗵𝗼𝘀𝗲 𝗥𝗼𝗹𝗲𝘀 Message engineers on LinkedIn, ask questions about their roles, and learn from their experiences. You’ll get insights no job description will tell you. 𝟱. 𝗦𝘁𝗮𝗿𝘁 𝗔𝗽𝗽𝗹𝘆𝗶𝗻𝗴 & 𝗔𝗱𝗷𝘂𝘀𝘁 𝗮𝘀 𝗬𝗼𝘂 𝗚𝗼 You don’t need to have everything figured out, just start applying now. The process itself will teach you a lot about what roles fit you best. Your first role won’t define your whole career, but choosing a focused path will help you land offers faster.

The hardest part of career decisions is not choosing a lane. It becomes about integrating what you already know. Here is a simple 4-step process: 1/ Collect your raw material: Write down six experiences that shaped you. ↳For each, note one outcome you drove and one skill you used. 2/ Spot your throughline: Underline what repeats, strengths you always lean on, problems you always solve, and Contexts where you thrive. ↳That’s the throughline of your career. 3/ Test options quickly Shape three paths: ↳Go deeper where you are ↳Advisory or consulting ↳Hybrid portfolio For each, have five conversations and run two small experiments. Look for signal 4/ Decide with guardrails: Check each option against your non-negotiables: energy, income, values, time. ↳If it fits, commit to a 30-day sprint and review. Which piece of your raw material deserves more weight in your decision? #reframe #careers #leadership