Mactores is the agent-native AWS modernization firm. Most modernization work doesn't ship, it stalls in pilots, slips a year, or lands at three times the budget. We exist to ship it: production systems running, legacy retired, outcomes measured. Our delivery is built on Aedeon, the agent platform built by Mactores' founders' sister company, which absorbs the repetitive 60–70% of engagement work, discovery, dependency mapping, validation, test generation, that traditional consulting bills human hours against. Forward-deployed engineers own the rest: architecture, judgment, and cutover, on dates we commit to in the contract. Mactores has 21 public case studies and 200+ published blogs. Most consultancy content sounds the same — capability lists, stacked adjectives, claims without baselines. Ours can't. Our positioning voice is flat, declarative, and engineering-led: pain named before capability, numbers with baselines, one contrarian claim per piece that a sharp reader would bookmark. Writing in that voice, at L300/L400 technical depth, for US B2B buyers — that's this job.
As our Technical Content Writer, you'll turn complex cloud and data engineering work Apache Iceberg lakehouses, Oracle-to-Aurora migrations, Spark optimization, cloud-native DataOps into deeply technical, visually sharp content that ranks, resonates, and drives enterprise pipeline in the US market. This is not a generalist writing role. You'll go deep technically, and you'll bring marketing judgment to everything you produce: a piece has to land with a data engineer, an IT director, and a CFO evaluating cloud ROI without being rewritten for each. You'll own content from research through publication long-form blogs, whitepapers, case studies, social copy, and the diagrams that make the argument legible.