Career path advice, i feel stuck as a Computer Engineering graduate.?
Hello, i am in BOTSWANA, recently graduated with a BEng Honours in Computer engineering degree and now i don't know what to do next.
i was looking to progress on a field which won't make me feel like an imposter as a comp engineer. i don't want to feel like i abandoned my field to hope onto other professions like telecoms, networking and IT fields which seem to be for comp science or IT graduates.
The internet suggest that the usual path is along the embedded systems which i find really interesting and makes sense for my field, i want to be unique and true to my profession. i believe i studied Comp Engineering for a reason.
now I'm at a crossroad, i don't know much about the industry's employability. demand for embedded professionals or even if it's worth it.
i am limited in the following ways:
- financially (currently unemployed)
- location (Botswana does seem to have any offers/ need for comp engineers)
- information (i don't know the realistic review of the field, sounds excited from theory)
i have narrowed down my other possible options
1. Embedded hardware/software/systems
2. Cloud Engineering
3. ICS (Industrial Control Systems) security
4. someone recommended ITIL certs
Finding a job is difficult so i don't have cashflow to afford things which is the major thing affecting my choice.
most suggest cloud because it's easier to get into though I think it's too congested just like cyber security.
embedded seems rightful but it's expensive to even start.
Other fields make me feel like an imposter to Comp Science professionals.
What i thought i wanted was to be unique, to create and design/ make custom electronic at a hardware/firmware level. i already have friend in electrical, web dev, coding, mechanical. i want to have a firm and recognised stance in my field.
Perhaps im asking the wrong questions, perhaps i have analysis paralysis, or im overthinking things.
maybe i should do what pays bills instead.
Any advice would be appreciated, maybe I could reach clarity.
Thank you
8 answers
Yoav’s Answer
Emre’s Answer
Let me tell you MY story because I feel that yours resonates well.
I myself has also graduated as a 4-year Computer Engineer in Turkey in 2009 and all I was considering was doing software engineering because all of my class mates were already employed as one if they didn't pursue post-graduation path.
I was feeling like an odd-one-out and exactly how you described, and I needed to earn money myself so I began my career as my first paid job as a Telecom network monitoring specialist answering phones from field teams. But it helped me to build on it and used my coding skills to develop scripots to speed up processes, as well as learning about a new type of network that I wasn't familiar with. Telecom network is just another type of computer networks.
This experience helped me to jump to a global HW/SW company as a field technician/engineer. I visited 100s of corporate customers , see their small/big/large system rooms and datacenters, troubleshooted HW problems, installed 100s of servers/routers/switches. I realized HW was my passion as I wanted to touch the hardware and when the LEDs turn green from fault red/amber, I'm the happiest man on earth. I learned how to talk with external customers in that job.
It made it possible for me to jump to a global cloud company as a deployment technician building Edge POP locations all over the globe. I travelled a lot in Europe, I learned time and stress management, acting in urgent situations, seeing how your deployments impacted the company's overall goals made it quite satisfactory then I decided I should be the project manager doing this and coordinate the activities from now on.
Long story short;
I don't mean you should/will follow the same steps as me but you can find your real enjoyment along the way. Don't feel you're prisoned to one field and you're stuck with it. If you're willing, you'll learn from each experience and either use it for the next career step or find out new opportunities you never thought of. I've had many colleagues and friends who switched fields between seemingly unrelated fields but what helps doing so is on top of your hard skills (technical skills), it's your soft skills (project coordination, communication with others, risk taking/management so on so on).
See my proposed steps below for you, I wish you the best of luck in your career!
Emre recommends the following next steps:
Chinyere Okafor
Chinyere’s Answer
First, let me be clear: what you're experiencing is a perfectly logical reaction to a challenging market, scarce resources, and a strong professional identity, not confusion or failure. Your degree in computer engineering wasn't "wasted," and you have good reason to stick with it. In fact, I can tell you're thinking like an engineer rather than aimlessly since you're struggling with fit, integrity, and long-term positioning.
Let's take a broad view of the situation. You are currently attempting to maximize three conflicting limitations:
(1) identity alignment; (2) employability/cash flow; and (3) access (money + location).
It's a basic trade-off problem, not analysis paralysis. Planning your steps strategically is more important than finding the perfect path right away.
Regarding the "imposter" issue: Computer engineering is multidisciplinary by nature. Computer engineering can legally occupy a range that includes embedded systems, ICS, firmware, networking, cloud, and even IT governance. By working next to your field, you are expanding its surface area rather than leaving it. The industry favors applied competence rather than purity. Early in their careers, many embedded and controls engineers transition between IT, networking, and systems roles without losing their credibility.
Let's now explore your practical rather than theoretical possibilities.
Embedded systems are a perfect fit for your long-term goals and identity. Firmware, real-world constraints, and hardware–software co-design are areas where computer engineering excels. You are correct, though, in that there is a greater barrier to entry (hardware, tools, fewer junior posts, limited local demand). This does not mean that embedded is a poor option. It indicates that it's often a medium-term venture rather than a zero-income beginning. With inexpensive simulators, open-source firmware projects, and microcontroller emulators, you may gradually establish trust without having to buy pricey hardware up front.
Many engineers fail to recognize that ICS, or industrial control systems, particularly security, is a very powerful middle ground. It is globally relevant (energy, utilities, mining, manufacturing—all relevant to Southern Africa), has less saturation than general cybersecurity, and fits in nicely with computer engineering. You don't have to start getting security certifications right away. You already stand out if you understand PLCs, SCADA principles, and industrial networking. "Unique and hard to replace" is a reasonable description for this niche.
]You are not betraying your degree by pursuing cloud engineering, but your intuition regarding congestion is sound. Although it's congested at the junior level, cloud computing is accessible. Nevertheless, compared to general DevOps roles, cloud roles that touch on IoT, edge computing, or systems integration are much more in line with your experience. The cloud is not your permanent identity, but it can stabilize your cash flow.
To put it plainly, ITIL certifications are not a top priority at this time. They won't address your identification or employability issues at this point, but they will be helpful in the future for process or management tasks.
The strategy change I would suggest is as follows:
"What sequence gets me income and credibility?" is a better question to ask than "Which field should I choose forever?"
A practical, low-risk way would resemble this:
- In the short term, look for any systems-related position that pays bills and develops professional experience, such as IT support, junior systems, networking, or technical operations. This is a runway, not a failure.
- Parallel track: use learning, little victories, and initiatives to advance toward embedded or ICS. Simply show improvement; you don't have to be an expert.
- Reposition yourself as a computer engineer with applied systems and embedded/industrial experience in the medium term. This is much more appealing than calling oneself a "junior cloud engineer" or an "entry-level IT generalist."
Your desire to design and create at the hardware/firmware level is proper, but very few people, especially outside of major tech hubs, start there right away after graduation. Most get there by building credibility rather than jumping right in.
Lastly, regarding the fear of "doing what pays bills now," this is not the same as giving up your long-term direction. Financial stability buys you optionality, not identity loss. Engineers who become stuck are not the ones who detour; rather, you're not lost; you're still in the transition phase.
You don't have the wrong questions. While you're still in the transition stage, you're only asking end-state questions. And that's all right. You are in the early stages of the optimization cycle; therefore, you are not lost.
Best wishes!
Clayton’s Answer
Siva’s Answer
I just want to add one important perspective.
Botswana is actually one of the strongest and most promising tech ecosystems in Africa.
You should be proud of where you are, not apologetic about it.
While the market may look small from the outside, there are real companies and startups building serious technology—especially in enterprise software, embedded systems, IoT, industrial automation, and applied engineering. A few examples you can start researching and reaching out to:
* SmartBots Lab
* Embedded Systems Engineering (Pty) Ltd
* BCX Ultimate Software
* Ked-Liphi (Pty) Ltd
* HorizonRealm
* IoT Communications
* Motheo Technologies
* Innowave (Pty) Ltd
…and many more emerging startups that don’t always advertise roles publicly.
Here’s the mindset shift I’d encourage:
1. Stop waiting for the perfect role to appear: Early in your career, the goal isn’t the title—it’s exposure. Look for internships, graduate roles, or junior positions to get into the field.
2. Prepare yourself for the market you want to enter: Sharpen embedded fundamentals (C/C++, microcontrollers, RTOS basics) and maintain an active GitHub profile that shows real work.
3. Reach out directly: Don’t wait for job postings. Contact companies, founders, and engineers to start conversations.
Botswana’s tech scene needs engineers who think like you—and with the right preparation, you’ll find your place in it.
Vanam’s Answer
Gwen’s Answer
Congratulations on graduating with honors! That's an amazing achievement. Do you have a LinkedIn profile? It's a great place to connect with IT professionals who can help you. LinkedIn offers a large network of IT and software experts, and you might find networking events there to attend. You can also take extra courses to expand your skills. Many companies look for graduates on LinkedIn, and you might find an internship that leads to a full-time job. Keep your skills current while you search for opportunities. Don't wait for a job to find you—take the initiative and network. You've got this!