New requirements opened this month
Requirements entering the ecosystem from MyResource companies and Recruiter partners.
Opportunities · August 2026
See where new professional requirements are opening across Kenya, and which are being planned for later.
Contents
01 · This month
At the start of each month this panel summarises real activity across the ecosystem. Nothing appears here until there is enough data to make a reliable statement, rather than overstating how busy the market is.
Requirements entering the ecosystem from MyResource companies and Recruiter partners.
Organisations currently reviewing contractors, whether named publicly or not.
Programmes in planning that have not begun active sourcing.
Ranked from measured requirement volume, never from impression.
Requirements from outside Kenya reachable by a professional based here.
Verified agencies with live mandates in the ecosystem.
These are the sectors this publication tracks. The order will change each month according to measured activity, so it is deliberately alphabetical here rather than implying a ranking we cannot yet support.
02 · Companies hiring now
Where a company is willing to be identified publicly, it should appear as something more useful than a logo and a job count. "Company XYZ, six jobs" tells a contractor nothing about whether to spend their afternoon on it.
Below is the structure each company entry follows once real requirements are flowing. The values shown are the template, not a real organisation.
Each entry carries a short explanation of what the organisation is actually doing: which programme is expanding, why the requirement exists, and which professionals it is relevant to.
It then says what to do. For example: professionals whose contracts end within one to three months may want to review the requirement now and confirm their profile reflects the relevant experience, rather than waiting for a formal advertisement.
03 · When we cannot name the company
Not every organisation wants its future workforce planning publicly attached to its name, and that is a legitimate commercial position. It should not stop you receiving useful market intelligence.
So these are published as anonymised summaries, and labelled as market signals rather than dressed up as advertised jobs. The distinction is the whole point.
Contractors whose availability begins inside the expected project window can update their profile so they can be considered as requirements become active. This is early sourcing, not an open vacancy.
04 · Read the phase, not the title
This is the most useful habit a contractor can build, and it costs nothing. A job title tells you what a company calls the role. The project phase tells you whether they are likely to engage you at all, and when.
| Project stage | Who tends to be engaged | What it signals for you |
|---|---|---|
| Planning and design | Architects, business analysts, solution designers, planning engineers | Requirements appear here first and are rarely advertised. This is the phase you reach by publishing availability early. |
| Build and configure | Developers, functional consultants, engineers | The largest volume phase, and where mid-level professionals most often enter. |
| Test | QA leads, test analysts, functional testers | Short, intense and frequently under-resourced. A reliable route into a programme you can then stay on. |
| Cutover and go-live | Data migration, cutover leads, technical support | Highest pressure, most specialist, best paid. Companies engage people who have done it before. |
| Post go-live and hypercare | Support specialists, trainers, adoption and change | Often overlooked in planning, then needed urgently. Worth watching if you can mobilise quickly. |
A six-month cloud migration needs a team the company will not need permanently. That is not instability. That is the market you work in.
05 · Sectors
Open a sector for the professional areas requirements tend to appear in, and why sector experience changes how a company reads your profile.
Technology projects suit contracting because companies need particular skills for particular phases. A six-month cloud migration requires a team the organisation will not need permanently. An ERP implementation needs data migration specialists intensively and then far less after go-live.
This is why requirements here should always be read alongside the project stage rather than the job title alone.
Ask what stage the programme has reached before anything else. It tells you whether they need your specialism now, in four months, or not at all.
Weak: Applying to every technology requirement listed
Strong: Targeting the two programmes whose current phase matches your specialism
Financial services generates highly specialised requirements because projects combine technology, compliance, finance and operational knowledge in the same programme.
Sector experience genuinely changes how your profile reads here. A developer who has built financial systems is more immediately useful on a banking programme than someone with the same language and no exposure to a regulated environment.
Record industry experience on your profile, not only technical skills. In this sector the industry context is half the qualification.
Weak: Backend developer, five years
Strong: Backend developer, five years, payments and reconciliation in a supervised environment
Manufacturing creates requirements across technology, engineering and operations at once, usually triggered by a new enterprise system, a factory modernisation, a supply chain programme, automation or expansion.
The strongest contractors here hold both the system and the operation. Functional configuration alone is widely available. Configuration plus plant reality is not.
Name the module and the operation together. It is the clearest differentiator available in this sector.
Weak: SAP MM consultant
Strong: SAP MM plus procurement and inventory operations, two plant implementations
Engineering projects have defined start and end dates by nature, which makes contractor availability unusually important and unusually valuable.
This is the sector where the availability timeline converts most directly into work. An engineer may be committed until March. Another company knows its project begins in April. Those two facts should meet before the first engineer starts looking.
Publish your project completion date, not just your availability status. In this sector timing is a qualification.
Weak: Available for engineering roles
Strong: Current phase completes February, available 1 March, commissioning experience
Energy and renewable projects create highly specialised demand, but the stage matters more here than almost anywhere. A project at feasibility needs entirely different expertise from one entering construction.
Requirements should therefore state whether they relate to feasibility, design, procurement, implementation, construction, commissioning or operations, so professionals can judge whether their experience is genuinely relevant.
Match your experience to the stage rather than the sector. Feasibility and construction are different professions wearing the same job title.
Weak: Renewable energy professional
Strong: Grid-connected solar, design through commissioning, two projects
Kenya's telecommunications and digital infrastructure market creates requirements across network engineering, fibre, RF, cloud, security, software and field delivery.
Professionals with both technology depth and telecom-sector experience are particularly relevant where a project needs someone to understand an existing operational environment quickly.
State the vendor environments and network scale you have worked in. Operators hire against familiarity with their stack.
Weak: Network engineer
Strong: Core network engineer, multi-vendor, national rollout experience
Kenya's position as a regional commercial hub creates steady demand, and supply chain transformation is now as much a systems programme as an operational one.
Companies increasingly want the process and the platform together rather than one or the other.
Pair the operational discipline with the platform. That combination is what most transformation programmes are actually recruiting for.
Weak: Supply chain professional
Strong: Warehouse operations plus WMS implementation, regional distribution
Professional projects in pharmaceutical and healthcare organisations create specialist temporary requirements, particularly around quality, regulatory work, validation and enterprise systems.
These are distinct from regulated clinical staffing, which requires compliance infrastructure we would need to build deliberately before offering. This page covers professional and technical project work only.
Be explicit about the regulatory frameworks you have worked to. In this sector unverified claims are found out quickly and expensively.
Weak: Quality professional, healthcare
Strong: Quality assurance and validation, named frameworks, audit-tested
Consulting, audit, technology and professional service firms engage contractors when client demand rises faster than their permanent capacity, which happens more often than their staffing models admit.
For a Kenyan contractor this can be one of the better routes to varied transformation exposure across multiple clients in a short period.
Firms hire for utilisation against a named client need. Describe your experience in the client's language, not the firm's.
Weak: Consultant, various projects
Strong: Finance transformation consultant, manufacturing and FMCG clients, four programmes
Where opportunities are genuine, professional project demand from public sector, development and NGO programmes belongs in the same ecosystem, published to the same standards of transparency and verification as private-sector work.
Donor-funded programmes in particular are shaped almost entirely around defined periods and deliverables, which is contract work by definition.
Name the funder type and reporting regime you have worked under. It is the closest thing this sector has to a technical qualification.
Weak: Development sector professional
Strong: Programme M&E, multi-donor reporting, health and education programmes
06 · Planning windows
The 30-day view is for professionals who are free now. The 90-day view is the one that matters more, because it is the only one useful to someone still delivering a contract. If you have three months left, a requirement starting in 60 to 90 days is more relevant than anything demanding immediate availability.
Each entry will carry sector, professional area, expected start date, location, working model, likely experience level, and whether the route is direct or through a recruiter.
Each entry will carry the project, expected hiring period, expected start, professional areas and how it matches your published availability.
Signed in, this becomes specific: your contract ends 30 November, and three upcoming requirements align with your December availability.
07 · How demand breaks down
"We need cybersecurity contractors" is not enough information to act on. These four breakdowns turn a statement into something you can measure yourself against, and all four come from platform data or not at all.
Junior, mid-level, senior, lead or architect, and programme or advisory. Published as counts per professional area so you can see whether the market fits your actual career stage.
On-site, hybrid, remote within Kenya, international remote, and travel required. Increasingly the deciding factor for professionals with family commitments.
Nairobi, Mombasa, Kisumu, Nakuru, Eldoret, other counties and remote. Reported honestly, including when the answer is that almost everything is in Nairobi.
Under three months, three to six, six to twelve, twelve or more, and deliverable-based. No duration is better than another. Visibility is what matters.
On location specifically: we will not manufacture county-level statistics to look thorough. If activity is concentrated in Nairobi, the page will say that plainly. If remote work within Kenya is growing, it will explain the trend rather than publish a map with three data points on it.
08 · Hiring route
Every requirement states its engagement route. This prevents the situation where a professional is submitted somewhere they did not expect, by someone they did not authorise.
The company engages you through the MyResource workflow. You know the client, and the client knows you.
An approved recruitment or staffing partner manages the introduction or the commercial relationship. You should know which agency and for which opportunity.
The company can only engage through a specific supplier relationship, usually for procurement reasons. Worth knowing before you invest time.
Where an agency is actively sourcing and has authorised us to say so, this section shows the professional areas, client sector and expected hiring period, so you understand why a recruiter is contacting you before you decide whether to engage.
09 · Hard to fill
Potentially the most valuable section on the page, and the easiest to get wrong. Where several companies repeatedly struggle to find a particular combination, that is worth reporting. It is not worth inflating.
"Several companies within the Contractor ecosystem are currently reporting difficulty identifying professionals with this combination."
Precise, attributable, and limited to what we can actually see.
"Kenya faces a national shortage of this skill."
Three companies in one ecosystem struggling to hire is not a national shortage, and treating it as one would send people retraining on bad information.
No hard-to-fill combinations are published, because no requirements have yet flowed through the platform to observe.
10 · Both ends of the market
Not every project suits someone entering contracting for the first time, and pretending otherwise sets people up to fail publicly. This section identifies requirements where companies are genuinely open to developing professionals.
We help junior professionals prepare for appropriate opportunities. We do not describe junior experience as senior experience, and we will not help anyone else do it either.
Senior professionals generally want fewer, more relevant requirements rather than hundreds of generic listings. These are the categories worth a fast route.
11 · Editorial standard
Applied to every company story and every requirement, so the page stays useful instead of drifting into announcements.
A new requirement or project entered the ecosystem, or an existing one moved stage.
Which professions, experience levels and locations are actually relevant. Naming everyone helps nobody.
Is the company hiring now, or planning ahead? These demand completely different responses from you.
Apply, update availability, strengthen the profile, monitor the project, complete a certification, or attend guidance. One clear action.
Active opportunity, planned requirement, or early market signal. Stated every time, without exception.
A planned workforce requirement must never be made to look like a guaranteed vacancy. That single rule protects the credibility of everything else here.
12 · Acting on it
Review projects expected to begin around your availability date rather than only searching what is open today. The 90-day view exists for you.
Make sure your profile describes your genuine experience and project history clearly. Demand you are invisible to does you no good.
Check whether you already have it and simply have not listed it. If not, review certifications or refresher learning before assuming you are excluded.
Do not panic, and do not retrain on one month of data. One month is not a career forecast. Look at longer-term updates and adjacent areas first.
Understand time zone, language, eligibility and client expectations before applying, not after a first interview.
Start with the junior routes above and the readiness guidance, and take a scoped engagement you can deliver well rather than the most senior one that will accept you.
Contract opportunities do not begin the day an advertisement appears. Projects are discussed, budgets approved and teams designed long before most professionals hear about them.
Contractor Opportunities is published by Contractor, part of the MyResource ecosystem. Requirement information is provided by companies and recruitment partners and is subject to change. A planned or anticipated requirement is not an offer of work, and inclusion here is not a guarantee that a project will proceed or that any professional will be engaged.
This edition contains no live requirement data and names no companies. Counts, company entries and listings will be populated from real ecosystem activity once Contractor is live.