Senior Software Engineer

Perpetuals.com Group (NASDAQ: PDC) delivers next-generation, AI-powered prediction and financial markets infrastructure for global participants. The company combines deep regulatory expertise with advanced technological capabilities to build a secure, compliant environment for asset and capital movement. Its platform is designed on a fully regulated, institutional-grade foundation, appealing to organizations that require reliability and scalability. Team members work at the intersection of finance, regulation, and cutting-edge technology to support efficient, data-driven decision-making across markets. Company Description Perpetuals.com Group (NASDAQ: PDC) delivers next-generation, AI-powered prediction and financial markets infrastructure for global participants. The company combines deep regulatory expertise with advanced technological capabilities to build a secure, compliant environment for asset and capital movement. Its platform is designed on a fully regulated, institutional-grade foundation, appealing to organizations that require reliability and scalability. Team members work at the intersection of finance, regulation, and cutting-edge technology to support efficient, data-driven decision-making across markets. What you would be working on We build and operate a deterministic matching engine in C# on .NET 10, running a regulated multilateral trading facility. It carries central limit order books and request for quote markets, and serves member firms over REST, WebSocket and FIX 4.4. Around it sit our trading and front end in Angular, a broker suite, a member portal, an admin console, a back office covering regulatory reporting and surveillance, and the services that move trade and client data between the venue, partner venues and our ERP. The five surfaces you would work across The role covers both the engine core and the screens a client uses. A change such as a new instrument type, or a change to how a contract closes early, runs from engine command through wire contract, documentation, broker router and front end, and we expect one person to be able to follow it the whole way. The retail front end will move onto our own venue; that integration is not built yet and is part of this work. What you will do Design and ship features that cross the engine, the gateway and the front end, including the wire contract change, the member facing documentation and the tests that pin the behaviour. Work within strict correctness constraints: a deterministic core, integer fixed point arithmetic for money, and versioned compatibility for anything already written to disk. Produce regulatory and partner evidence to external deadlines. Transaction and reference data filings, surveillance case records, and client records requested by a regulator or a payment partner. This work sometimes arrives with a few days notice, and it is part of the role. Hold the latency and throughput budget. Profile, remove allocation from hot paths, reason about garbage collection settings, and prove the result with the load and latency probes. Build and maintain the Angular front end so it stays responsive under a live market data stream, including change detection and state management at high update rates. Own the cache tier. Hot pricing and order state in Redis, and an edge layer that distributes market data to clients. The design decisions sit with you: cache aside against write through, expiry, invalidation, and how much read load the database carries. Own integrations end to end, including WebSocket and FIX sessions, sequence cursored backfill, idempotent replay and reconciliation. Build the development machinery. The automated review panel on every pull request, our shared continuous integration actions, and the guardrails that govern what coding agents are permitted to do. Review other engineers' work, including the automated review output, and mentor the junior developer on the determinism and journal compatibility rules. Take part in the operational rotation for the venue and its portals, and keep the runbooks current. What we look for Six years or more building production C# on .NET, including systems where correctness under concurrency was a primary requirement. A bachelor's degree in computer science, software engineering, mathematics or a related technical field, or equivalent professional experience. Financial technology experience, ideally exchange, broker, market data or payments. You should already know what an order book, a fill, margin and a mark price are, and be comfortable with the idea that a regulator can ask for the record of a specific order two years later. Real low latency work: profiling and removing allocation, cache and memory layout awareness, lock free or single writer designs, garbage collection tuning, and measuring at the p99 rather than the mean. High input and output work: sustained WebSocket fan out, event streams, backpressure, batching and fsync behaviour, and databases under continuous write load. Front end strength in TypeScript with a component framework, Angular preferred. React or Vue experience also counts if you can point to substantial work. SQL fluency on PostgreSQL, including indexing and query plans. Caching in production. Redis or equivalent, keys and expiry you picked on purpose, and a working understanding of invalidation and staleness. Be ready to discuss how you decided what to cache and for how long. Writing. We need you to take a complex situation, for example several open pull requests, a migration conflict and an investigation still in progress, and write the one paragraph a colleague who was not there can act on. We give you a real one from our tracker in the interview and ask you to do it. Experience working with people in other countries: partner teams abroad, several time zones, and markets under different regulatory regimes. Also useful FIX protocol experience, or another exchange or venue wire protocol. Flutter and Dart, including the app store release process. Another cross platform mobile framework in production also counts. MiFID II or MiFIR reporting, RTS 22, 23, 24 or 27, market surveillance, or DORA. Edge compute platforms, for example Cloudflare Workers. Identity verification and onboarding integrations, or OAuth2 and webhook integrations, including their reconciliation. Windows Server operations, OpenTofu or Terraform, Ansible, Azure, GitHub Actions with self hosted runners. Python, since a meaningful part of our integration fleet is Python. Consensus systems in practice, Raft or similar. Digital asset custody, HSM based signing, or Ethereum and Solana, which is where our tokenised stocks service lives. #J-18808-Ljbffr