Software engineer | Game engines, systems programming, native software, and GPU architecture

I build a mix of software: native game engines and tools, gameplay systems, GPU architecture research, backend APIs, and lead generation software. What keeps me interested is figuring out how the underlying systems work and making them efficient and dependable. I care about performance on ordinary hardware, clear interfaces, repeatable validation, and being able to show what actually works.

I work with C, C++, C#, .NET, Java, Python, and TypeScript. I choose languages for the work rather than defining myself by one of them. My experience also includes web and backend development, especially software built around a specific business problem. General website development and e-commerce aren't the direction I'm looking to pursue.

Open to remote, full-time software engineering opportunities. I'm most interested in game engines and games, rendering, native and systems development, GPU-related engineering, and simulation. I'm also interested in moving into robotics and developing experience with sensors, controls, and physical systems. Purpose-built backend services and lead generation platforms remain part of the work I enjoy.

Selected work · How I work · Contact

The projects below are publicly accessible and are presented with their actual maturity and limitations.

A business-owner inquiry website focused on Virginia and North Carolina. It provides state-specific information about selling a business, practical owner guides, and a confidential inquiry form. The application is built around a lightweight PHP deployment rather than a hosted website framework.

Maturity: Public website is live. Lead administration and post-launch corrections are still being verified, so the deployment should not be treated as fully completed.

What to inspect: Live website · Homepage screenshot

An incident intake and response application. It groups repeated alerts into incidents, records status changes, and lets operators review, acknowledge, and resolve them in a browser. The current source also includes scoped ingestion credentials, operator permissions, and retry recovery for optional notifications.

Maturity: v1.0.0 released for local evaluation. Further hardening is merged on main but has not been independently verified as a new release. It is not an internet-ready monitoring or paging service.

What to inspect: Dashboard screenshot · Engineering walkthrough · API contract

A demonstration transfer ledger for handling repeated requests safely. PostgreSQL coordinates requests sharing an idempotency key and commits balance updates, ledger entries, and the saved response in one transaction. A matching retry reuses its receipt; a different request with the same key is rejected.

Maturity: Local technical demonstration with simulated credits, not a payment service. The full Maven and Testcontainers suite is provided but has not yet been verified by a completed run.

What to inspect: Application and API · Transaction and failure model · Local verification

A lightweight command-line tool for filtering and summarizing structured application logs without a database or server. The source handles timestamp and severity filters, standard input, malformed records, and deterministic error summaries. Local text validation, integration tests, and release verification scripts are included.

Maturity: Source implementation merged. Rust compilation, integration tests, and release behavior have not yet been verified; dependency lockfile generation remains pending.

What to inspect: CLI and input format · Rust source · CLI tests · Validation contract

A document retrieval and evidence workspace for indexing Markdown and plain text, finding source passages, and inspecting citations. It includes a browser interface, optional model-generated answers, and reference-based retrieval evaluation.

Maturity: Local technical demonstration. API tests cover the temporary backend; a completed PostgreSQL integration test run is not yet documented.

What to inspect: Application screenshot · Overview and setup · Evaluation cases

A REST API for creating, searching, updating, and reporting on leads. It separates HTTP contracts, services, persistence, and database migrations. The repository documents validation with H2-backed tests and PostgreSQL integration tests using Testcontainers.

What to inspect: API and setup · Validation contract · Portfolio scope and limits

An engineering reference for a compact GPU architecture, covering execution, memory, scheduling, graphics, power, and the prototype path. The repository includes design contracts and validation material.

Maturity: Architectural and prototype design. No custom ASIC has been fabricated. Performance figures are targets, not measured hardware results.

What to inspect: Engineering specification · Project status · Validation

An early-stage game engine with a native editor, rendering, terrain, physics, asset authoring, persistence, and headless runtime foundations. Its documentation distinguishes working capabilities from unfinished or planned features.

Maturity: Active engine development, not a finished commercial game engine.

What to inspect: Capability matrix · Current capabilities · Build instructions

A local-first browser extension for reviewing job listings and preparing application field suggestions. Its form-fill process requires user approval and keeps final application submission manual. The implementation emphasizes validation of persisted data, safe field handling, and page identity checks.

What to inspect: Overview and usage · Roadmap and known limits

• Boundaries first. Define what a component owns, what callers can assume, and how invalid input is handled.
• Test evidence over optimistic claims. Keep validation instructions, limitations, and failure cases visible. A design target is not a benchmark, and a test plan is not a passing test.
• Practical performance. Favor restrained dependencies, maintainable code, and support for machines without expensive hardware.
• Non-destructive changes. Use source control, reviews, reproducible builds, and targeted regression checks to protect existing work.

The repositories are independent projects with different release stages and contribution policies. Check each README for its current scope, licensing, and setup instructions.

I'm based in Illinois and open to remote software engineering roles involving game engines, gameplay systems, native applications, rendering, graphics, simulation, and systems programming. I'm also interested in growing into robotics, and I remain open to substantial backend or lead generation engineering work.

• Email: brandon@brandonconnell.com
• LinkedIn: Brandon Connell

You can explore the public repositories for additional work.