Knowledge worker jobs are treated as a synonym for coding work. That belief was somewhat correct in 1996, but certainly not in 2026. Knowledge work is any role where people solve problems, apply judgement, communicate decisions and use specialised expertise to create value. More specifically, via a computer.
Software engineers belong in that category, but so do product managers, designers, analysts, marketers, recruiters and people operations specialists.
The strongest career choice depends less on whether a job sounds “digital” and more on how its responsibilities match a person's skills, working style and tolerance for ambiguity.
This guide compares 10 knowledge worker jobs across tech and creative fields through three practical lenses: what each role involves day to day, which skills transfer elsewhere, and how well the work fits distributed teams.
It also considers less visible constraints, including location eligibility, compliance, employment status, pay, benefits, time zones and asynchronous communication.
Global eligibility depends on the employer and jurisdiction. A role advertised as remote might still be limited to specific countries, require employment through a local entity or use a contractor arrangement. Candidates should assess those conditions before investing heavily in an application.
The list starts with technical roles and moves through creative, commercial and people-focused work.
How ironic, right? Software engineers design, build and maintain the applications, platforms and systems that support digital products.
Depending on the specialism, work may involve frontend interfaces, backend services, cloud infrastructure, DevOps automation or machine learning systems.
A backend engineer at a fintech start-up might maintain APIs while colleagues work across multiple time zones. A frontend engineer at a European SaaS company could manage the evolution of a shared design system, while a DevOps engineer at a global media platform focuses on reliability and infrastructure efficiency.
The transferable skills are broader than programming. System thinking, technical writing, debugging, estimation and structured problem-solving transfer into solutions architecture, technical product management and data engineering.
Software engineering is one of the strongest fits for distributed work because code, tickets, pull requests and technical documentation create an auditable record. Teams still need live conversations for complex design decisions, but clear written proposals reduce unnecessary meetings.
The trade-off is that remote engineers can become isolated from product context. A technically elegant solution may fail if the engineer doesn't understand customer needs, regulatory constraints or commercial priorities. Time-zone differences also make incident response and handovers important parts of the job.
Candidates should:
Build visible evidence: Use GitHub projects to demonstrate solutions to real problems, not just tutorial exercises.
Develop a specialism: Go deep in one or two areas while retaining enough breadth to collaborate across the stack.
Document decisions: Explain architecture, trade-offs and rejected alternatives because distributed hiring often tests written reasoning.
Track opportunities: Candidates can use our Job Tracker Chrome Extension to capture engineering roles globally and compare requirements with successful applicants.
Contribute publicly: Relevant open-source work can establish credibility without relying entirely on formal credentials.
Product managers turn customer problems and business priorities into product decisions. Their work includes research, roadmap planning, prioritisation, stakeholder alignment, launch coordination and learning from product performance after release.
A product manager at a Canadian payroll SaaS company may need to account for compliance requirements across countries. A product lead at a design tool start-up might balance user growth, product quality and platform reliability while working with engineering, design, marketing and support.
The role transfers well into strategy, operations, consulting and product marketing. The most valuable transferable skill is not prioritisation. It's the ability to make a defensible decision with incomplete information, communicate the reasoning and revisit it when evidence changes.
Remote product management fails when decisions live inside meetings or private conversations. Strong teams use written briefs, decision records, customer evidence and clear owners. Frameworks such as RICE prioritisation, Jobs to Be Done and the Value Proposition Canvas can give dispersed teams a shared language, but no framework replaces judgement.
The main drawback is emotional and organisational pressure. Product managers often own outcomes without directly managing the people responsible for delivery. They must handle disagreement across time zones, explain trade-offs repeatedly and maintain momentum when requirements change.
Useful preparation includes:
Show shipped work: Build a portfolio that explains the problem, decision process, delivery and outcome.
Develop industry depth: Expertise in a vertical can make product decisions more credible than broad familiarity with many markets.
Write publicly: Articles, podcasts and professional posts can demonstrate product thinking before an interview.
Assess culture carefully: Candidates can use our AI Career Agent to explore roles at organisations whose mission and working principles match their own.
Ask about authority: Before accepting, clarify which decisions belong to the product manager and which require executive or commercial approval.
A global product role may also involve regional differences in language, accessibility, payment systems and regulation. Candidates should ask how the company gathers local insight rather than assuming a single-market playbook will transfer.
Data analysts turn raw information into decisions. Their week may involve writing SQL, checking data quality, building dashboards, investigating unusual results and explaining recommendations to colleagues who do not work with statistics.
At an e-commerce platform, an analyst might compare conversion across markets. In healthcare SaaS, the focus could be product adoption and churn. A junior analyst in logistics may support reporting while building stronger SQL skills.
The role develops transferable skills in questioning assumptions, evaluating evidence, communicating visually and applying commercial judgement. Those skills can lead to analytics engineering, business intelligence, operations, finance or product analysis.
Remote analysts need technical accuracy and clear documentation. Stakeholders may read an analysis hours after it was completed, so the conclusion should explain what changed, why it matters and what action is recommended. A dashboard without interpretation often creates more questions than answers.
The main trade-off is access to reliable context. Analysts work effectively when definitions, permissions and data ownership are clear.
In a distributed organisation with fragmented systems, they may spend substantial time reconciling conflicting numbers before answering the original business question. Location can also affect data access and compliance, particularly when customer or employee information crosses borders.
A practical portfolio should include reliable public datasets and explain the question, method, limitations and recommendation.
Candidates should also become highly capable in one visualisation platform, learn how surrounding data systems work and confirm the decision an analysis must support before writing queries. Plain English matters: replace statistical jargon with a clear explanation of what changed and what follows.
Keep an evidence trail showing which operational or product decisions each analysis enabled. This demonstrates judgement, not just tool familiarity.
Remote suitability is generally strong because analytical work can be completed asynchronously. It weakens when the role depends on constant access to a single executive, frequent live workshops with local teams or data held within a restricted jurisdiction. Candidates should ask how teams handle time-zone delays, permissions and written approvals.
Candidates exploring business intelligence roles should check whether the employer expects analysis, dashboard maintenance, data modelling or all three. Those responsibilities require different evidence and career paths.
User experience designers turn user evidence into clearer journeys, interfaces and services. Their work may cover interviews, journey mapping, interaction design, prototyping, usability testing and collaboration with engineers.
The boundaries vary by organisation, so candidates should confirm whether the role is research-led, interface-focused or responsible for the full product experience.
A designer at a Berlin SaaS company might redesign onboarding for users across languages. A UX researcher at a recruitment start-up could run interviews across countries, while a design lead at a travel platform may set direction for new markets.
Each example carries different constraints around culture, accessibility, translation and local product expectations.
Design builds transferable skills in observation, synthesis, facilitation, visual explanation and negotiation.
A designer who can connect user needs with business and technical constraints may progress into service design, research operations, product management or design leadership.
Remote suitability depends on how clearly the work can be documented. Figma files, research repositories, written rationales and recorded walkthroughs let colleagues review decisions asynchronously. Live critique remains useful for ambiguity and sensitive feedback, but design judgement should not exist only in meetings.
Global research also requires deliberate coverage. A pattern found in one market may reflect local behaviour rather than a universal need.
Accessibility should enter the brief and testing plan early, not wait for a final compliance review. Time zones can slow participant recruitment, approvals and design reviews, while privacy rules may restrict where research recordings or employee information crosses borders.
A portfolio should show the reasoning behind the outcome:
Show the process: Include research, constraints, iterations and rejected concepts, not only polished screens.
Explain decisions: State the user problem, trade-off and evidence behind important choices.
Use collaboration tools well: Strong Figma practice helps distributed colleagues inspect, comment on and develop work.
Learn accessibility: Familiarity with WCAG principles improves design quality and communication with engineering.
Connect work to outcomes: Include evidence of effects on conversion, retention or satisfaction when available.
Candidates reviewing interaction design opportunities should verify the operating model. “Remote” may mean remote within one region, fixed collaboration hours or occasional travel to a design hub. Ask how teams schedule research, protect participant data and record approvals across locations.
Marketing managers connect audience needs with commercial goals. Day-to-day work can include research, channel planning, campaign delivery, budget control, performance analysis and coordination with sales, product and creative teams.
The role changes by market and specialism. A growth marketing manager at a UK SaaS company may run acquisition and lifecycle activity. A product marketing manager at a developer tools company might prepare an APAC launch, while a demand generation manager coordinates campaigns with B2B sales.
Transferable skills include project management, audience psychology, commercial writing, prioritisation and measurement. They support moves into growth, product marketing, communications, demand generation and marketing operations. The trade-off is that results also depend on product readiness, sales follow-up, data quality and market conditions, so the manager cannot control every outcome.
A distributed team needs one campaign brief, named owners, a content calendar and shared definitions of success. Those documents reduce duplicated work and make asynchronous decisions visible. They also expose approval gaps before a regional launch is delayed.
Marketing remains creative, but its operating load is substantial. Time-zone differences can slow reviews, while local language, advertising rules, privacy requirements and market-specific compliance can limit where a campaign runs. Ask how the organisation records approvals, handles customer data and separates useful learning from blame when performance misses expectations.
Build evidence through practical work:
Choose a channel: Gain depth in content, lifecycle, demand generation or product marketing.
Learn the data layer: SQL or analytics tools can reduce reliance on specialist reporting teams.
Document campaigns: Show the audience, message, execution, result and next decision.
Use business language: Connect activity to pipeline, retention, adoption or revenue, not surface metrics alone.
Study the sales process: Marketing and sales alignment needs written context when colleagues do not share informal conversations.
Candidates can search marketing strategy roles, then check global eligibility, required working hours and travel expectations. Remote work may still be limited to a region because employment, tax, advertising or data rules differ by country. Global teams also need overlap with regional sales colleagues, or clear handoffs that work asynchronously.
Content strategists turn audience needs into a publishing system. Their work can include research, editorial planning, briefs, governance, messaging, performance reviews and coordination with writers, designers and subject experts. The role sits between customer understanding, subject knowledge and business priorities.
A strategist at a London fintech start-up might plan thought leadership for professional audiences. At a cybersecurity company, a technical content strategist may serve both security leaders and engineers.
A content director may also manage writers, designers and distribution, so candidates should check whether the position is individual-contributor, managerial or mixed.
The transferable skills are audience analysis, prioritisation, clear writing, project coordination and judgement under incomplete information.
They support moves into editorial leadership, SEO, product marketing, communications and brand strategy. Content attribution is often indirect, however. Strong strategists connect editorial decisions with actions such as enquiries, product adoption or retention, without claiming every commercial outcome.
Remote content teams depend on written briefs, calendars, decision records and review criteria. Those artefacts let colleagues in different time zones contribute without waiting for a meeting. The arrangement breaks down when feedback is vague, positioning changes informally or no one owns final approval.
Build evidence through practical work:
Strategic portfolio: Show the audience, content choice, distribution plan and reasoning.
SEO fundamentals: Demonstrate search intent, information architecture and internal linking.
Clear speciality: Distinguish thought leadership, educational, brand and technical content.
Measurement habits: Explain how engagement, leads, retention or revenue evidence changed the plan.
Editorial governance: Provide templates and review standards for distributed contributors.
Tools can support repeatable production, including guidance that helps teams automate content creation for teams. Automation may speed up research or drafting, but human review remains responsible for accuracy, tone, audience fit and accountability.
Global roles add practical constraints. Translation, cultural adaptation and regional search behaviour affect planning, while privacy, employment location and local review requirements can limit where work is performed. Ask who owns localisation, which markets the role supports and how approvals happen asynchronously. A worldwide content system needs clear decision rights, not access to shared documents.
A solutions architect turns an ambiguous customer problem into a design that delivery teams can build and support. The work includes discovery calls, requirements mapping, architecture decisions, implementation planning, complexity estimates and negotiation between sales, engineering and the customer.
A Dublin SaaS company might use an architect to shape implementations for mid-market customers. In another organisation, a cloud specialist plans a migration, or a solutions engineer helps a data-platform customer build a reliable pipeline. The title varies, so check whether the role is primarily pre-sales, delivery, or shared across both.
Strong architects transfer discovery, systems thinking, commercial awareness, presentation and negotiation into consulting, sales engineering, technical account management, implementation leadership and product strategy. Their value comes from connecting technical choices to cost, risk, time and operational ownership.
A proposal should show how the design addresses the business requirement, what the customer must provide and which risks remain. Architects make that reasoning reviewable through diagrams, decision records, proposals, recorded walkthroughs and implementation notes. Clear documentation also lets engineering colleagues in other time zones challenge assumptions without requiring another meeting.
The trade-off is constant. Sales may seek speed or flexibility, while engineering must protect feasibility, security and long-term support. Ask who approves exceptions, who owns post-sale outcomes and whether performance is judged mainly by pre-sale activity or by successful adoption after handover.
Candidates can demonstrate capability by showing:
Reusable solution patterns: Templates for integrations, security questions and deployment models.
Product expertise: Practical understanding of configuration, limits, pricing and packaging.
Customer discovery: Questions that reveal the requirement behind an initial request.
Post-implementation learning: Evidence that deployment outcomes changed later proposals.
Remote suitability depends on customer coverage rather than the job title. Enterprise workshops may involve travel, client calls may fall outside local hours, and procurement or data requirements can differ by country. Confirm expected overlap hours, travel, compliance responsibilities and how decisions are recorded asynchronously before applying.
Technical writers turn product knowledge into instructions that users, developers and internal teams can act on. Their work may include API references, setup guides, troubleshooting articles, onboarding tutorials, release notes and documentation standards.
The day-to-day work starts with finding gaps in the reader's journey. A writer at a Berlin API platform might document REST and GraphQL endpoints, test examples and resolve unclear behaviour with engineers.
A documentation lead at an infrastructure company may set priorities and review a team's work. A technical content specialist could manage regional documentation for a SaaS product.
Strong writers identify the reader's task, remove uncertainty and make the next action clear. Those skills transfer to developer relations, content strategy, information architecture, enablement and knowledge management.
Technical fluency matters, but so do interviewing, editing, information design and the judgement to challenge an unclear process.
Documentation suits distributed teams because drafts, repositories and review comments create a lasting record. The trade-off is dependence on subject matter experts.
Across time zones, writers need prepared interviews, precise questions and enough context for engineers to respond asynchronously. Live meetings can resolve ambiguity faster, but they reduce flexibility and may exclude colleagues in distant regions.
A useful portfolio should show:
Published documentation: Samples with clear structure, accurate technical detail and an identifiable reader.
Markdown and Git: Evidence of working with version control, pull requests and review workflows.
A defined ecosystem: API documentation, developer onboarding and internal systems involve different tools and knowledge.
Reader feedback: Search terms, support questions and page feedback can shape priorities.
Documentation advocacy: Show how you helped teams include docs in product quality and release work.
Before accepting a role, ask who owns documentation, how releases trigger updates and whether docs appear in product planning. A position with decision-making authority generally offers more progression than one that absorbs urgent requests. Clarify whether the writer handles localisation, terminology management or regional publishing. These duties add coordination, compliance and workload beyond writing, especially when teams publish across countries.
Recruitment coordination is often treated as administration, yet the role directly affects hiring quality and candidate trust. Coordinators manage applications, interview schedules, recruitment systems and candidate updates. Talent acquisition specialists usually add sourcing, hiring-manager partnership, assessment and offer support.
The work varies by organisation. At a UK technology start-up, a coordinator may support engineering and product hiring.
A SaaS employer might need a recruiter who can build an international engineering pipeline, while a consultancy recruiter may focus on contractor placements.
Clarify the split before accepting a title, because some positions combine coordination, sourcing, employer branding and HR administration.
Transferable skills include prioritisation, process design, written communication, stakeholder management and judgement.
They can support moves into account management, sales, operations, people experience or workforce planning. Strong recruiters understand the capability a hiring manager needs rather than copying a job description.
Distributed recruitment adds decisions about time zones, location eligibility, interview fairness and engagement type.
A candidate may fit the work but remain unavailable through the employer's payroll or contracting structure. Recruiters should record those constraints, explain them clearly and escalate uncertain cases instead of making assumptions.
Asynchronous communication helps global candidates receive consistent instructions, but it also requires precise scheduling details and timely written updates. Candidates should ask which regions the role can support, who handles compliance questions and whether interview panels share overlapping working hours.
The emotional load is a genuine trade-off. Recruiters handle rejection, urgency and conflicting expectations from candidates and executives. Hiring data can reveal delays or inconsistent stages, but changing the process may require senior approval.
Build capability through deliberate practice:
Develop functional expertise: Focused sourcing improves assessment quality.
Learn the business: Product and strategy knowledge makes candidate conversations more credible.
Write clearly: State process, timing, location and engagement terms accurately.
Use process data: Review stages, acceptance patterns and retention signals to find friction.
Maintain a network: Relationships can create stronger conversations than applications alone.
Candidates can read what a talent acquisition recruiter does, then compare it with the employer's actual responsibilities. This role suits people who combine structured coordination with human judgement and can keep a fair process moving across borders.
People operations managers keep the employee journey and its supporting systems working. Their responsibilities may cover onboarding, offboarding, HRIS administration, payroll coordination, employee experience, policy development, benefits support and compliance processes.
In a London SaaS start-up, the role might coordinate employment processes across several countries. A distributed company may need someone familiar with contractor compliance and payroll, while a larger organisation may divide responsibilities among people operations, rewards, talent and employee relations.
The work transfers well into HR leadership, people analytics, total rewards, employee relations and global mobility. It builds process design, confidential communication, stakeholder management, risk awareness and operational analysis.
Remote suitability depends on operational clarity. Employees need written guidance on eligibility, payroll timing, benefits, leave, equipment, communication expectations and escalation routes. The manager connects finance, legal, leadership and individual employee needs, often across time zones where a delayed answer can affect pay or access to benefits.
A policy written for one country may not apply elsewhere. Employment, contracting, payroll and benefits arrangements require review by appropriate specialists. People operations managers should record ownership, document decisions and escalate uncertain cases rather than make assumptions.
Candidates can strengthen their practice by focusing on:
HRIS and payroll fluency: Understand system connections, data failure points and tasks requiring controlled access.
Cross-functional relationships: Work closely with finance and legal colleagues throughout policy design and case handling.
Jurisdiction awareness: Learn how the organisation manages local employment and contractor requirements.
Transparent communication: Explain changes to policies or employment arrangements in clear, timely written updates.
Useful people metrics: Examine workforce information for bottlenecks, risks and employee experience problems.
The trade-off is emotional as well as operational. Employees may contact this team during pay, benefits or employment problems, while leaders expect consistent processes and careful risk control.
This role suits people who can protect confidentiality, coordinate across borders and make policies usable in daily work. It becomes harder when international growth outpaces decisions about accountability for compliant employment, payroll and total rewards.
| Role | Implementation complexity | Resource requirements | Expected outcomes | Ideal use cases | Key advantages |
|---|---|---|---|---|---|
| Software engineer | High – system design and coding complexity | Programming languages (e.g., Python, JS), CI/CD, version control, infra | Scalable, functioning software and reliable systems | Building product features, backend services, ML/infra | Portable in-demand skills; strong remote opportunities |
| Product manager | Medium–high – strategy and cross-functional coordination | Market research, analytics, stakeholder alignment tools | Product roadmaps, prioritised features, go‑to‑market plans | New product launches, roadmap planning, market expansion | High visibility and strategic impact; path to exec roles |
| Data analyst | Medium – data cleaning, modelling, and interpretation | SQL/Python/R, BI tools (Tableau/Looker), data warehouses | Actionable insights, dashboards, data‑driven decisions | Funnel analysis, A/B testing, performance reporting | Broad demand; lower entry barrier; measurable outcomes |
| User experience designer | Medium – research, prototyping, iterative testing | Figma/Adobe XD, user research, prototyping tools, design systems | Usable interfaces, prototypes, consistent design systems | Onboarding redesigns, UX improvements, multi‑locale products | Visual portfolio showcases value; improves retention/conversion |
| Marketing manager | Medium – multi‑channel campaign complexity | Analytics, content/ad platforms, budget management, CRM | Customer acquisition, engagement, measurable growth | Growth campaigns, product launches, cross‑market campaigns | Measurable ROI; visibility across business functions |
| Content strategist | Low–medium – planning and governance focus | SEO, editorial workflows, analytics, writing resources | Content calendars, consistent messaging, audience engagement | Thought leadership, demand generation, localization efforts | Remote‑friendly; strategic content drives long‑term value |
| Solutions architect | High – bespoke architectures and integrations | Deep product/integration knowledge, architecture tools, discovery skills | Implementable architectures, technical proposals, successful deployments | Enterprise sales, migrations, complex integrations | Customer‑facing technical authority; competitive compensation |
| Technical writer | Low–medium – translating technical concepts clearly | Markdown/Git, CMS, access to SMEs, documentation tools | Clear documentation, tutorials, improved onboarding | API docs, developer guides, user manuals | Inherently remote; documentation directly reduces support load |
| Recruitment coordinator / Talent acquisition specialist | Medium – sourcing and process coordination | ATS, sourcing tools, communication and scheduling systems | Filled roles, improved time‑to‑hire, candidate experience | Scaling teams, global hiring, building talent pipelines | Direct impact on company growth; wide role availability |
| People operations manager | Medium–high – compliance and operational complexity | HRIS, payroll/EOR partners, legal knowledge, communication processes | Compliant HR operations, smoother onboarding/offboarding, retention | Global headcount management, scaling HR systems, compliance | Strategic influence on employee experience; essential for global orgs |
The right knowledge worker job isn't necessarily the one with the most prestigious title or the broadest remote advertising. It's the role whose daily problems match the candidate's preferred way of thinking.
Software engineers and data analysts usually suit people who enjoy structured problems, technical depth and focused work.
Product managers and solutions architects fit candidates who prefer ambiguity, negotiation and decisions that affect several teams. UX designers and content strategists suit people who combine research with creative judgement.
Marketing managers need commercial energy and comfort with variable outcomes. Recruiters and people operations managers work best for candidates who gain satisfaction from communication, coordination and human systems.
The strongest skill also changes the comparison. Coding, data validation and documentation reward precision. Product, marketing and architecture reward synthesis and persuasion. Design and content reward taste, empathy and iteration. Recruitment and people operations reward discretion, clarity and trust.
Collaboration patterns matter just as much. Technical writers and analysts can often produce valuable work asynchronously, provided they have reliable access to information. Product managers, designers and marketers need more cross-functional alignment. Recruiters and people operations specialists may need live availability because candidates and employees need timely responses.
A practical test: A remote role should explain how decisions, feedback, handovers and urgent issues work when colleagues aren't online together.
Candidates should also consider tolerance for operational pressure. A software engineer may face incident response. A marketer may face campaign deadlines. A recruiter may manage urgent hiring demands.
A people operations manager may handle sensitive employee matters across different jurisdictions. Remote work changes the setting, not the underlying responsibility.
The phrase “work from anywhere” needs careful examination. Before applying, candidates should confirm:
Eligible countries: Check whether the employer can hire in the candidate's country and whether residence, work rights or regional restrictions apply.
Engagement status: Establish whether the role is employment, freelance work, direct contracting or an arrangement through an employment provider.
Pay and benefits: Ask how salary currency, payroll, tax handling, leave, insurance, pension and other benefits are managed.
Time-zone expectations: Clarify required overlap, meeting windows, on-call duties and handover procedures.
Compliance ownership: Identify whether the employer, contractor or external provider handles local requirements.
Travel requirements: Confirm whether retreats, customer visits or office attendance are optional.
The wider labour market reinforces the need for this scrutiny. The OECD knowledge-worker estimate describes knowledge workers as highly skilled employees whose tasks centre on creating and processing information, and places them at an estimated 18.6% of the labour force in participating countries, with substantial variation between markets.
A separate International Labour Organization-backed estimate places global knowledge-worker employment between 644 million and 997 million jobs, or 19.6% to 30.4% of world employment, with Asia and the Pacific containing 519 million of those jobs.
That scale makes global search, eligibility checks and salary context practical career requirements rather than niche concerns.
Pay transparency is also becoming more important. Mercer's 2025 Global Pay Transparency Survey covered more than 1,600 multinational organisations across 60 markets and projected that hiring pay-range disclosure could rise from 60% in 2024 to 94% by the end of 2026.
Aon's 2025 Global Pay Transparency Study found that 69% of organisations already publish salary bands, while only 19% considered themselves ready for pay transparency.
Candidates should treat those figures as a reason to ask sharper questions, not as proof that every employer offers fair or comparable pay. Location, seniority, employment status, tax treatment and benefits can alter the practical value of an offer.
AI adds another layer. UiPath's 2024 Global Knowledge Worker Survey found that 39% of global respondents used generative AI at work, while Gallup reported that 47% of US employees said their organisation had integrated AI tools to improve productivity, efficiency or quality.
Those findings point to an adoption gap. Candidates should ask which tasks AI supports, who reviews outputs, what data can be used and how the organisation measures value.
The likely career advantage won't come from using AI indiscriminately. It will come from combining tool fluency with judgement, domain knowledge, empathy, creativity and accountability.
PwC's AI Jobs Barometer reports that tasks added to AI-exposed roles are 2.5 times more likely to rely on empathy, judgement and creativity, while jobs requiring specific AI skills are growing about eight times as fast as the overall jobs market, 69% compared with 9%.
Flexible work also isn't a single category. An independent 2026 remote-work analysis reports that hybrid work is the dominant model for knowledge workers globally, with roughly 50% to 55% in hybrid roles and about 15% to 27% fully remote. Candidates should define what flexibility means for them before filtering roles.
A practical search can start with our Global Job Board, where salary is shown as standard and roles can be filtered by company, department, location, skills and employer attributes.
Our AI Career Agent can help assess fit and surface questions to investigate. Our Job Tracker Chrome Extension can organise roles captured from across the web, while our global employment advisory can help employers and candidates examine EOR, global payroll, contractor arrangements and cross-border employment questions.
The most useful next step is specific. Select two roles from this list, map current evidence against their required skills, identify the largest gap and build a targeted portfolio or application plan around it.
A software engineer might document a system design project. A designer might rebuild a case study. A recruiter might analyse a sourcing process. A people operations candidate might create a cross-border onboarding workflow.
The best application makes the candidate's way of working visible before the interview begins.
