A career belongs to you. Removing barriers is shared work.
This hub centres women’s experiences and welcomes anyone who finds it useful. Your interests, experience and circumstances should shape your route. Gender does not decide which technical role suits you.
01 / Choose your starting point
What would move you forward?
These are starting points, not fixed categories. Switch whenever your needs change.
Choose a task before choosing a course.
You do not need to decide your whole career today. Compare the daily work in two roles, try a small task and use what you learn to choose your next step.
01
Explore two kinds of work
Compare support and troubleshooting, infrastructure and cloud, software and data, or security and governance. Read responsibilities and entry expectations. Cyber security and cloud titles do not always mean beginner roles.
02
Try one bounded task
For support, write a troubleshooting guide for a problem you can reproduce. For data, clean a small public dataset and explain one check. For infrastructure, sketch a simple network and explain an access decision. Use a safe lab and label it as practice.
03
Check the route against your constraints
Read three current vacancies in your location. Separate essential responsibilities from desirable tools. Compare time, total cost, entry requirements and assessment before buying training. Ask what evidence of learning a course will leave you with.
Try putting it into words
Illustrative first step: spend 45 minutes testing a Wi-Fi troubleshooting guide on your own equipment. Ask someone to follow it. Record what confused them and revise the guide.
Which part of this task did I enjoy, what could I explain, and what would I need help to do safely?
TechWaymark editorial guidance. Examples are invented; adapt them to your own work. The My Waymark demo is free; saving a personal workspace requires membership.
Beyond getting through the door
Progression deserves as much attention as entry.
The 2025 Lovelace Report describes barriers around advancement, recognition and support among the women who participated. It draws on a survey of over 500 women, roundtables and 20 interviews with senior women. [3]
Our response is practical: ask about access to technical work, transparent progression criteria and who will act on a development plan. A personal learning plan cannot, by itself, resolve an unfair workplace.
02 / Find support that fits
A useful connection starts with a specific need.
Choose learning, a peer conversation or a return opportunity. These are independent providers; their eligibility, prices and availability can change. UK and international coverage is labelled below.
Explore coding
Code First Girls
Online · check location and sponsor eligibility
Free, self-paced Coding Kickstarter courses introduce programming or data through eight modules, with up to eight weeks to finish. No previous coding experience is required.
Before you commit: Beginner coding option. Confirm eligibility and available subjects. Introductory classes are not directly linked to a job opportunity.
A return route for experienced engineers through paid client projects with technical guidance. Suitable projects trigger an invitation to apply; the provider currently specifies a career break of at least six months.
Before you commit: Not a beginner course or women-only service. Confirm project availability, location, right-to-work requirements and selection criteria.
A BCS specialist group for women interested in computing, including people studying, working or taking a career break.
Before you commit: Check current events, membership requirements and charges. Choose an activity where you can discuss a specific technical or career question.
WiCyS offers a professional mentorship programme for professional members, alongside its wider cyber security community.
Before you commit: Professional membership is required for this programme. Check fees, application dates and fit; mentoring is not an immediate placement promise.
Make a small, answerable ask: “I’m comparing support and infrastructure roles. Could you help me understand one task your team expects a new starter to handle?” You do not need to ask someone to map your entire career.
03 / Evaluate the opportunity
Ask for examples you can judge.
Use the same questions in an interview, returner discussion or internal move. An answer becomes more useful when it names a process, a person or a recent example.
Progression+
What evidence was used for the last promotion on this team?
Look for clear criteria, a review process and examples beyond length of service.
Technical ownership+
How are design work, incident leadership and stretch projects allocated?
Ask how a newcomer gets access and who will review their work.
Working arrangements+
What hours, location and on-call commitments does this role actually involve?
Ask how the stated arrangements work on this specific team; get agreed terms in writing.
Support and accountability+
Who would I go to if I needed support or experienced inappropriate behaviour?
Look for a clear route, named responsibility and an explanation of follow-through.
Returning after a break+
What would the first 30, 60 and 90 days look like?
Ask what is paid, what training is provided and how expectations change during onboarding.
These are TechWaymark discussion prompts, not a workplace rating or legal advice. You decide which questions matter for your situation.
04 / Leave with something useful
One next step. Written down.
Focus: Start your career. Make the action small enough to start, and specific enough to review.
Which part of this task did I enjoy, what could I explain, and what would I need help to do safely?
Your draft stays in this page only and is not sent to TechWaymark. Download it before refreshing or leaving. Avoid confidential work or personal details.
05 / Recruiters, managers & educators
Create access. Make expectations clear.
These are our suggested practices, informed by the barriers described above. Do not infer someone’s skills, availability or ambitions from their gender or a career break.
Recruiters & hiring managers
Separate day-one responsibilities from skills the team can teach. Explain how each essential requirement will be assessed.
Give candidates the format, criteria and preparation time in advance. Use consistent, role-relevant questions and a shared assessment rubric.
Ask every candidate about role requirements and working arrangements without making assumptions about caring responsibilities.
Explain the salary range, onboarding, support and progression process. Review where candidates leave the process and investigate the reasons.
Show women doing varied technical work: operations, design, security, software and leadership. Use real, attributed stories when discussing lived experience.
Offer a concrete task, safe practice environment and useful feedback. Make room for people with different starting points.
Make project allocation and progression criteria visible. Agree who owns each action in a development conversation.
Ask participants what was useful and what made access difficult. Change the activity in response; attendance alone does not show career impact.
Written by TechWaymark. Sources and provider pages checked 25 September 2026. Research findings are attributed; exercises and employer prompts are our editorial guidance. Listing a provider does not imply a partnership or endorsement. The hero is an AI-generated illustration, not a photograph of contributors.
Survey of over 500 women, roundtables and 20 senior-women interviews. Findings describe participants; they are not population-wide prevalence estimates.