<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>VP of Engineering (remote) - Phoenix Global Search RSS Feed</title>
    <link>https://jobs.co.uk/job/vp-of-engineering-remote-phoenix-global-search--d1059507-675e-415b-afc7-cb636c6878c3</link>
    <description>RSS feed for VP of Engineering (remote) at Phoenix Global Search.</description>
    <language>en-gb</language>
    <lastBuildDate>Thu, 08 Oct 2026 04:58:53 GMT</lastBuildDate>
    <item>
      <title>VP of Engineering (remote) - Phoenix Global Search</title>
      <link>https://jobs.co.uk/job/vp-of-engineering-remote-phoenix-global-search--d1059507-675e-415b-afc7-cb636c6878c3</link>
      <guid>https://jobs.co.uk/job/vp-of-engineering-remote-phoenix-global-search--d1059507-675e-415b-afc7-cb636c6878c3</guid>
      <pubDate>Mon, 05 Oct 2026 23:00:00 GMT</pubDate>
      <description>Location: London | Salary: Negotiable | Type: Permanent | VP of Engineering: Java Open-Source Data Infrastructure    Package: -175k - -217k base + 15% bonus + options    Location: UK remote-first.     My client, a profitable, Series-D software company (circa 110 people, $40-45M ARR) behind one of the most widely-used open-source real-time data platforms in the world are looking for a VP of Engineering with a strong technical / Engineering background (ideally in Java).    The person will own the engineering direction and execution. It''s the top engineering seat: 40 engineers, 3 engineering managers reporting in to you,     Person Specification:   You''re an architect-leaning technical leader who can run a bigger organisation. Technical depth is your anchor you''ve never traded it for scope. You can still name the domain you''re genuinely excellent at, unprompted, three levels deep: distributed systems, low-latency engineering, JVM performance, stream processing, or storage and replication internals.    You''ve probably written or contributed to Java open source, spoken at conferences, and within the last couple of years you''ve personally worked a hard technical problem, not just funded one.    You''ve also made the hard personnel calls: ...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>