No Code Tech Careers: Starting Out in VA or Technical Writing

The Spaces explored no‑code tech careers with a deep focus on Technical Writing and Virtual Assistance. Host Favor guided a practical discussion on choosing passion over trend‑chasing and making informed decisions. Technical writers Bruce Wisdom Namie and Joe DK shared entry paths, stressing rigorous research, niching down, building in public, and professionalism; Joe highlighted challenges like boundary setting with clients and starting with standard rates before raising prices as value is proven. Virtual assistants Steven Tukway Akovi and Abiodun Deinde detailed how VA is an umbrella role (admin, social media, e‑commerce, customer support), the importance of courses, mentorship, broad tool literacy, and referrals, plus confidentiality and strategic support mindset. Q&A covered pay expectations (focus on skills early), platforms and roadmaps (mentorship accelerates), cybersecurity track anxiety (research then decide), passion vs profit balance (know your worth, price by complexity/time, build systems), and whether coding helps (only within dev‑docs niches). Speakers closed with benefits: global connections, flexibility, and career mobility.

No-Code Tech Careers: Technical Writing and Virtual Assistance – Space Recap

Context and Purpose

• Host: Favor
• Theme: Exploring no-code tech career paths—Technical Writing (TW) and Virtual Assistance (VA)—for those who don’t code or prefer non-programming roles.
• Framing: Avoid the “shiny object syndrome” of hopping to whatever is trending. Choose a path aligned with your interests and strengths. Tech is broad and not “saturated” if you specialize and deliver value.
• Goal: Equip beginners with accurate, practical guidance on getting started, core skills, pitfalls, and how to make informed decisions.

Speakers and Roles

• Favor (Host/moderator)
• Steven Tukway Akovi (Virtual Assistant)
• Abiodinde (Executive Virtual Assistant)
• Bruce Wisdom Namie, aka “Tamara” (Software Engineer & Technical Writer)
• Georgia, referred to as “Joe / DK” (Technical Writer & Media Strategist)

Technical Writing

How They Got Started

• Bruce Wisdom (Tamara):
  • Discovered technical writing via YouTube (Technical Writer HQ) ~3 years ago.
  • Struggled applying programming; started writing to explain what he was learning.
  • Mentorship was pivotal—structured path, materials, topic-selection, pitching; landed first paid gig in ~2 months.
  • Writes on Hashnode and other blogs (e.g., developer platforms), focusing on complex topics made simple.
• Georgia (Joe/DK):
  • Began as a developer; frustration with elusive bugs led him toward explaining code and frameworks instead of building.
  • Built visibility by consistently posting breakdowns and commentary on WhatsApp groups, LinkedIn, Twitter.
  • First international gig came via LinkedIn DMs for documentation for an AI recruiting product; emphasizes thought leadership and sharing work publicly.

Challenges and Professional Boundaries

• Georgia (Joe/DK):
  • Early-stage exploitation risk: clients avoiding structured meetings, dragging via endless emails, extracting unpaid expertise.
  • Solution: Insist on professional process (meeting links, scopes), and recognize red flags of info-extraction without commitment.

What Technical Writing Involves (Beyond Coding)

• Purpose: Translate complex technical concepts into clear, user-ready documents for different audiences (beginners, intermediates, experts) and stakeholders (marketing, product, engineering, executives).
• Typical outputs:
  • Documentation: User guides, manuals, API docs, feature explanations.
  • Internal comms: Explainers that help cross-functional teams align.
  • Research and content: Articles, blog posts, long-form guides.
• Audience tailoring:
  • Beginners: Minimal jargon, foundational explanations.
  • Intermediates: Moderate technical depth, structured guidance.
  • Experts: Precise technical detail, domain-specific terminology.
• Writing standards:
  • Strong structure, grammar, clarity; consistent terminology.
  • Organized lists and sequences (often numbered or structured lists vs. uncontrolled bullets, depending on style guides).
  • Optimization for discoverability and internal reuse when appropriate.
• Tools most beginners will use daily:
  • Google Docs, Microsoft Word, WPS Office.
  • Additional: Google Sheets/Excel for tables, references; CMS/blog platforms (e.g., Hashnode); collaboration tools.

Skills and Success Factors

• Research depth: Thoroughly read documentation, reference materials, and related articles; investigate new domains (e.g., Kubernetes, Python frameworks) before writing.
• Subject-matter learning: Coding knowledge can help for code-centric tasks, but is not mandatory for many documentation and explainer roles. It’s an “edge” only within the coding-doc niche.
• Niche down:
  • Pick a domain (e.g., DevTools, cloud, cybersecurity, AI, web3) and a target audience to become known for something specific.
  • “If you’re for everyone, no one knows what to hire you for.”
• Build in public:
  • Share drafts, learning notes, and finished pieces. People value visible growth and will associate you with problems you solve.
• Mentorship & courses:
  • Accelerate learning and job readiness; structured feedback shortens time-to-breakthrough vs. going solo.
• Pricing & value (for beginners):
  • Start at standard rates for your level; overdeliver on value and consistency.
  • Use project complexity, time, and responsibility to guide pricing; raise rates after repeated excellence.
• Systems and discipline:
  • Rely less on motivation; create templates, workflows, and tools to reduce cognitive load and deliver consistently.

Virtual Assistance

How They Got Started

• Steven Tukway Akovi:
  • Studied civil engineering; wanted flexibility and time for other pursuits.
  • Transitioned from social media management to VA, driven by strong interest in media and online work.
  • Took courses and actively engaged with potential clients while learning to build credibility and a portfolio.
• Abiodinde:
  • 5+ years as an Executive Assistant; started in school doing assignments/projects/presentations for others, developed confidence and public speaking.
  • Built skills via research writing; first VA role came through that pathway.
  • Works across domains (startups, web dev, project management teams); emphasizes proactivity, stakeholder management, and anticipating CEO needs.
  • Growth via referrals: Do great work so clients mention you in rooms of opportunity.

What VA Covers and How to Specialize

• The “virtual assistant” label describes working virtually, not the specific job. Define your role clearly.
• Common VA niches:
  • Administrative EA/VA; Social Media Management; E-commerce operations; Customer Support; Project coordination; HR support; Sales ops.
• Strategy for beginners:
  • Identify your interests and strengths; select a niche.
  • Learn broadly enough to be versatile while building depth in your primary niche.
  • The field is not saturated; differentiation comes from reliability, breadth of knowledge, and specialization.
• Professional stance:
  • Be a “strategic support” partner, not a task taker.
  • Understand clients’ industries: If supporting web3 teams, learn basics like Discord usage, P2P, platform terms; for SaaS teams, know tools and processes.
  • Respect NDAs—build in public cautiously; share outcomes/achievements, not confidential work.

Tools and Continuous Learning

• Core tools (vary by niche):
  • Productivity: Google Workspace (Docs, Sheets), Microsoft Office.
  • Social Media: Meta Business Suite, analytics tools, Canva (for quick creatives).
  • E-commerce: Platform-specific dashboards and tooling.
  • HR/PM/CRM: Exposure to tools used by your clients; learn on the job via YouTube, courses, and communities.
• Mindset:
  • Determination and self-awareness (know your strengths, goals).
  • Courses + mentorship supply practical know-how and support.
  • Pitch early—even while learning—build a portfolio through small gigs.
  • Target referrals by doing excellent work consistently.

Audience Q&A Highlights

1) VA Learning Path and Courses

• Learn the core of multiple niches, then go deep in one primary niche.
• Use YouTube and online resources to learn tools you don’t yet know.
• Example for SMM niche: Learn analytics, business suite basics, Canva for designs, and reporting.

2) Expected Pay Ranges (Beginners)

• Host’s guidance: Focus first on building skill, portfolio, and credibility. Early stages may involve unpaid internships or low-paid gigs; compensation grows with demonstrated value.

3) Technical Writing Roadmap and Platforms

• Mentorship and courses accelerate progress compared to learning alone.
• Build in public (LinkedIn posts, Hashnode blogs, program-specific writing opportunities like Civo’s writer program).
• Freelance platforms (e.g., Fiverr) can work well when you niche down (e.g., scripting for game dev).

4) Switching Tracks (Cybersecurity anxiety)

• Do independent research into what the field entails; align choices with personal interest and capacity.
• Scholarship track changes may be possible later; make an informed choice, not fear-based.

5) Passion vs Profit Balance

• Wisdom (Tamara):
  • Passion helps sustain effort, but know your worth; don’t accept undervaluation.
  • Writing can also be personal—expressing how you’re feeling can support continuity.
• Georgia (Joe/DK):
  • Price by complexity/time/responsibility and the value you deliver.
  • For beginners: Start at a reasonable standard rate, overdeliver, and increase rates after showing consistent excellence.
  • Build systems to reduce effort; rely on discipline more than motivation.

6) Does a Technical Background Confer a Big Edge?

• Consensus: Coding/software knowledge is helpful for code-centric documentation but not mandatory for many TW outputs (user manuals, guides, cross-functional explainers).
• A technical background gives an unfair advantage only within that niche; expertise doesn’t automatically carry across unrelated domains.

7) First VA Gig

• Visibility matters: Regularly show what you do—even simple channels like WhatsApp status can lead to inbound gigs and referrals.

Practical Getting-Started Checklists

Technical Writing (Beginner Roadmap)

• Self-assessment: What domains interest you (e.g., AI, cloud, DevTools, cybersecurity)? Who do you want to write for (developers, PMs, marketers, end users)?
• Niche selection: Pick a domain and audience so you can become known for something specific.
• Research fundamentals: Read docs, articles, tutorials; build topic understanding before writing.
• Write and publish: Start with topics you know or are learning. Publish on Hashnode, personal blog, LinkedIn.
• Build in public: Share drafts, iterations, and lessons learned.
• Mentorship/courses: Enroll for structured guidance, feedback, and community.
• Tools mastery: Google Docs/Word/WPS Office; learn advanced formatting, style guides, and collaboration workflows.
• Professional boundaries: Use meeting links and proper scoping; avoid endless unpaid email exchanges.
• Tailor to audience: Create versions for beginner/intermediate/expert readers as needed.

Virtual Assistance (Beginner Roadmap)

• Self-awareness: Clarify what you enjoy (admin ops, social media, customer support, e-commerce, project coordination).
• Niche selection: Choose a primary niche; learn broadly enough to support cross-functional tasks.
• Courses & mentorship: Gain practical techniques, tools, and confidence; join communities.
• Tools fundamentals: Google Workspace, Excel/Sheets; niche tools (e.g., Business Suite, Canva). Learn additional tools as required by clients.
• Pitch early: Offer small services while learning; collect outcomes to build your portfolio.
• Professionalism & NDAs: Share achievements carefully; never disclose confidential work.
• Aim for referrals: Be reliable, proactive, and anticipatory; consistent excellence fuels word-of-mouth growth.

Common Pitfalls and How to Avoid Them

• Shiny object syndrome: Don’t chase trends solely for pay; pick a path that suits your interests and strengths.
• Building in private: In tech content careers, lack of visibility reduces opportunities. Publish and show growth.
• Exploitation risk: Watch for boundary-less clients (e.g., endless emails, avoiding formal meetings). Set structure.
• Burnout: Use systems/templates, and pace your learning; passion helps, but discipline and process sustain output.

Benefits Observed by Speakers

• Flexibility: Remote work, home-based productivity, schedule control.
• Cross-cultural exposure: Work with clients from multiple countries; learn different ways of working and cultures.
• Impact and ownership: Helping brands streamline operations and communicate complex ideas effectively.
• Network and opportunity: Conferences, travel, and recognition (e.g., Dubai tech invites, international awards).
• Income potential: Grows with specialization, visibility, and repeated excellence.

Suggested Resources and Platforms

• Content tools: Google Docs, Microsoft Word, WPS Office; Google Sheets/Excel.
• Publishing: Hashnode, personal blog, LinkedIn.
• Design & social: Canva, Meta Business Suite; analytics tools.
• Communities & learning: YouTube tutorials; reputable courses; mentorship programs.
• Freelance platforms: Fiverr (niche gigs); outreach via LinkedIn DMs.

Closing Notes

• Choose a path, specialize, and show your work. Both technical writing and virtual assistance reward consistent delivery, professional boundaries, and ongoing learning.
• When in doubt, get a mentor and join a community—structured guidance saves time and helps you avoid early-stage mistakes.
• For scholarship participants: Track changes are possible; final decisions should be research-driven and passion-informed rather than fear-driven.