<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Career Paths on Curiosettee</title>
    <link>https://curiosettee.net/career-paths/</link>
    <description>Recent content in Career Paths on Curiosettee</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <atom:link href="https://curiosettee.net/career-paths/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI &amp; Knowledge Work</title>
      <link>https://curiosettee.net/career-paths/ai-knowledge-work/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://curiosettee.net/career-paths/ai-knowledge-work/</guid>
      <description>AI changes tasks faster than it changes the need for judgment. Many emerging roles will not fit neatly into “technical” or “nontechnical.” They will involve knowing how to work with information, tools, systems, people, and AI at the same time.
This is the territory I mean by AI-enabled knowledge work.
It can include documentation systems, research workflows, knowledge management, technical communication, AI-assisted analysis, operations, governance, content systems, internal enablement, and new combinations that do not yet have tidy job titles.</description>
    </item>
    <item>
      <title>Data Analytics</title>
      <link>https://curiosettee.net/career-paths/data-analytics/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://curiosettee.net/career-paths/data-analytics/</guid>
      <description>Data becomes useful when it helps someone see more clearly. Data analytics is about turning raw information into something people can understand and use. Depending on the role, that can mean cleaning datasets, writing queries, building dashboards, investigating anomalies, defining useful metrics, or explaining what the numbers do and do not support.
I came to analytics through engineering, GIS, Python, marketing, HR systems, and operational reporting rather than through one perfectly linear route.</description>
    </item>
    <item>
      <title>FinOps</title>
      <link>https://curiosettee.net/career-paths/finops/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://curiosettee.net/career-paths/finops/</guid>
      <description>A technology career can ask you to learn finance, too. FinOps is a cross-functional discipline concerned with making cloud spending visible, understandable, and useful for decisions. It lives in the membrane between engineering, finance, procurement, operations, and leadership.
I came to FinOps from an engineering and technology background, which meant some of the finance and accounting language initially felt foreign. Learning it reminded me of a principle I keep returning to: uncertainty is not a verdict.</description>
    </item>
    <item>
      <title>GIS and Geomatics</title>
      <link>https://curiosettee.net/career-paths/gis-and-geomatics/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://curiosettee.net/career-paths/gis-and-geomatics/</guid>
      <description>Sometimes the most useful question is simply: where? GIS and geomatics are broad fields concerned with location, measurement, spatial information, and the technologies we use to understand the physical world. They can connect maps, fieldwork, databases, engineering, remote sensing, software, infrastructure, environment, and public decision-making.
This was one of my earliest professional worlds. I studied Geodetic Engineering and later worked with surveying, GIS, spatial data, web mapping, infrastructure, research, and disaster-related applications.</description>
    </item>
    <item>
      <title>Technical Project Management</title>
      <link>https://curiosettee.net/career-paths/technical-project-management/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://curiosettee.net/career-paths/technical-project-management/</guid>
      <description>Complicated work rarely moves forward by itself. Technical project management sits between the people building something, the people who need it, and the many decisions, dependencies, risks, and misunderstandings that can slow everyone down. The work is not only about schedules or meetings. It is about creating enough shared clarity for a technical initiative to keep moving.
My own career has repeatedly placed me in these in-between spaces: engineering projects, data and software work, business analysis, vendors, cloud initiatives, documentation, executive reporting, and cross-functional technology teams.</description>
    </item>
    <item>
      <title>Technical Writing</title>
      <link>https://curiosettee.net/career-paths/technical-writing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://curiosettee.net/career-paths/technical-writing/</guid>
      <description>What if your technical skill is explaining technical things well? Technical writing sits between subject-matter expertise and the person who needs to understand or use it. The work can include software documentation, API references, tutorials, knowledge bases, architecture explanations, user guides, standards, and internal technical knowledge.
You might enjoy it if you like understanding how systems work asking the question everyone else assumed was obvious organizing messy information writing clearly without flattening the complexity translating between technical and nontechnical people learning unfamiliar tools and domains What can transfer into it Writing, teaching, engineering, support, business analysis, QA, research, product work, data, operations, and subject-matter expertise can all become useful raw material.</description>
    </item>
  </channel>
</rss>
