Software Engineer - Backend / Platform

Title: Software Engineer - Backend / Platform

Location: New York, NY, US

### Why GhostEye

GhostEye is building an automated social engineer that tests how attackers could deceive employees and gain access to company systems. Our customers include **government organizations and Fortune 100 companies**.

We operate our own fine-tuned model, voice synthesis, and self-hosted phone infrastructure. We are extending the platform into **post-click compromise and downstream access testing**, helping security teams establish what access an attack enables, which defenses intervene, and whether a fix holds when tested again.

Our founder previously led BlackRock’s red team and worked in offensive cyber operations at MITRE. The engineering work draws on that experience, with problems spanning real-time communication, controlled execution, and reliable evidence collection.

### The role

You will build the backend services that turn our existing capabilities into complete product workflows. This includes coordinating calls and messages, managing campaign execution, connecting services, and making results available to the product.

You will work closely with product and frontend engineers to define service behavior, resolve integration issues, and carry projects through to production. You should be comfortable explaining how a system works, where it can fail, and how you would investigate it.

### What you will work on

• Backend workflows connecting campaign configuration, scheduling, execution, and results.
• Phone and SMS systems, including routing, delivery status, recording, and provider integrations.
• State management, cancellation, retries, and recovery for long-running operations.
• Event processing that handles duplicate, delayed, and out-of-order events.
• Services for scoped account, session, and downstream access checks.
• Authorization, tenant isolation, AWS deployments, and operational monitoring.
• Latency and failure handling across model responses, speech generation, and call delivery.

### Your first 90 days

**First 30 days: Understand the execution path and ship a backend workflow**

Trace a campaign from its initial API request through execution and reporting. Work with the team to select and ship a scoped backend flow using existing services. Document its dependencies, failure behavior, and remaining limitations.

**By 60 days: Own a workflow across services**

Take responsibility for a larger execution flow, including its service contracts, state transitions, and integrations. Verify cancellation, retries, uncertain provider responses, and status reporting. Add the tests and monitoring needed to operate it.

**By 90 days: Carry a product initiative through to production**

Own backend delivery for a complete customer workflow. Help product and frontend engineers understand what is ready, what remains unfinished, and which decisions are blocking release. Break the work into manageable releases, resolve integration problems, and follow up on production behavior.

### What we are looking for

• Experience building and operating production services in **TypeScript or Rust**, with the ability to work across both.
• A solid understanding of concurrency, asynchronous execution, API design, and data modeling.
• Experience with AWS or comparable cloud infrastructure.
• A methodical approach to debugging across services, networks, and external providers.
• Sound judgment about permissions, failure recovery, and operational complexity.
• Tests that cover meaningful failure cases and verify the behavior the product depends on.

Experience with telephony, streaming audio, model serving, enterprise identity systems, or security tools is valuable.

### Communication matters

We expect clear design notes, documented service behavior, and direct explanations of technical tradeoffs. Ask questions when requirements are incomplete and communicate dependencies and blockers early.

During production issues, explain the impact, what is known, what remains uncertain, and how the fix will be verified. Keep product and frontend engineers informed when backend behavior affects what customers can do.