Work across boundaries
The useful solution often crosses code, infrastructure, data, delivery, and the human workflow around them.
Polyglot engineering · Automation · Developer tools · Security
Bob Heineman.
I build reliable software for complex, real-world systems.
From distributed applications and cloud infrastructure to security automation and AI-assisted workflows, I turn operational friction into tools teams can trust.
01 / Philosophy
The specialty changes. The engineering instinct stays consistent.
I’ve built full-stack systems across product interfaces, backend services, infrastructure, data pipelines, delivery automation, operational tooling, and developer experience. I’m not a specialist visual designer, but I participate in frontend work whenever the product needs it—and I care deeply about making customer and operator workflows understandable. Today, I apply that range to security.
Make complexity legible
A platform should help people see the system: what matters, who owns it, and what should happen next.
Encode the good path
Policies become durable when they are expressed through reusable modules, workflows, and sensible defaults.
Build for operators
Reliability includes the human system: observability, safe failure, traceability, documentation, and ownership.
02 / Full-stack work
I’ve always built across the stack.
From enterprise web applications and consumer signup experiences to operational dashboards, self-service tools, and public sites, frontend work has been part of the job whenever it helps complete the system.
Shipped project · Built for my son’s business
Reid & Ricky Landscaping
I built and shipped a responsive public website for my son’s local landscaping business. The work spanned helping translate a young entrepreneur’s real service offering into product framing, information architecture, frontend implementation, imagery, customer flows, structured metadata, integration, and production delivery.
- Product work
- Translated my son’s services into clear trust signals, process, reviews, and contact flow
- Frontend
- Responsive layouts, navigation behavior, imagery, accessibility, and interaction
- Platform
- Astro, static generation, Google Forms, S3, and CloudFront
- Learning model
- AI-assisted framework ramp-up with human architecture, review, and validation
AI helps me get oriented in a new framework quickly. The engineering work is understanding how the pieces fit, making the product decisions, and owning what ships.
Visit rrl.cx Astro · JavaScript · Responsive UI · AWS
EnterpriseMVC applications, public sites, services, and workflow enginesSogeti · Healthcare
ConsumerRetail and device signup experiences at global scaleAmazon Prime
OperatorDashboards, configuration tools, reports, and self-service workflowsGaming · Fetch · Security
Vendor cost avoided over four years$800KFour properties · approximately $50K each
Full-stack system · Rush Street Gaming
A survey platform designed around employee trust.
In my first two weeks, I rebuilt a multi-tenant annual survey system for four casino properties. The web applications produced detailed organizational reporting, while a separate property-level printing program generated one-time anonymous codes.
Employees selected a printed code from their organization’s shared bucket. That physical choice made the privacy model understandable: the company retained the category needed for reporting without individually assigning a response identity.
03 / Operating model
Breadth becomes leverage when the system crosses boundaries.
Security is one of the clearest examples: the work touches cloud systems, application context, data integration, ownership, delivery workflows, reporting, and the teams responsible for change.
04 / Selected impact
Generalist range, applied to consequential systems.
The work matters when the operating model changes: fewer manual handoffs, clearer ownership, safer delivery, and systems that keep producing value after the first launch.
15+years building and operating production systems
Polyglotsoftware, infrastructure, data, and workflow engineering
$800Kvendor survey fees avoided over four years · $200K per year
Safer releasescontrolled rollout, rollback, traceability, and lower operating overhead
End to endarchitecture, implementation, automation, hardening, and enablement
01
Service registry · Multi-brand, multi-cloud governance
Unified a fragmented cloud estate around services and accountable owners.
Built a cohesive service registry spanning Wonder's brands and cloud environments. Its dynamic resolution layer combines authoritative organizational data, resource tags, naming rules, structural relationships, and weighted similarity strategies to map services to owners. A tiered confidence model automates trustworthy matches while routing ambiguous results for review.
BeforeCloud resources, services, brands, and ownership records described the organization differently.AfterOne evidence-based registry connects technical assets to services, owners, findings, and remediation paths.
What changed1,455 services evaluated in one run1,222 were classified, 233 gaps were surfaced for action, and 13 downstream projects were synchronized through the trust-aware mapping workflow.
02
Security reporting · Decision support
Made reporting a reusable product instead of a recurring manual exercise.
Built reporting workflows, source adapters, renderers, exports, and operator guidance that aligned posture information with services, ownership structures, and the audiences responsible for action.
BeforeFragmented inputs and repeated effort to assemble decision-ready security views.AfterRepeatable, service-aware outputs for technical operators and leadership audiences.
What changedFrom posture data to accountable decisionsTechnical findings became easier to understand, route, discuss, and incorporate into a repeatable operating rhythm.
03
Platform modernization · Fetch
Made a tightly coupled production system safer to change and easier to operate.
Decoupled e-receipt infrastructure into independently deployable components, introduced controlled rollout and rollback, improved release traceability, built self-service configuration tooling, and automated lifecycle work.
BeforeCoupled releases, harder rollback and investigation, and engineer-dependent routine operations.AfterIndependent delivery, gradual rollout controls, self-service workflows, and clearer production traceability.
What changedSafer change at production scaleTeams gained independent deployment, controlled rollout and rollback, clearer traceability, and less operational friction.
04
Engineering leverage · Technical leadership
Raised the engineering baseline around every system delivered.
Paired implementation with least-privilege access, secret management, safer input handling, observability, testing, retries, deployment controls, modular infrastructure, operator documentation, and mentoring.
BeforeImportant behavior concentrated in individual implementations and individual engineers.AfterReusable standards, clearer operations, stronger defaults, and teams better equipped to extend the work.
What changedFrom shipped code to sustainable systemsNew capabilities became more operable, reviewable, transferable, and resilient instead of stopping at first implementation.
05
Full-stack product · Privacy · Operations
Replaced a costly survey vendor with a system employees could trust.
Built a multi-tenant survey web application for four casino properties, detailed reporting aligned to organizational structure, and property-level printing software for anonymous one-time access codes.
BeforeFour properties each paid approximately $50K annually for an external survey service.AfterA repeatable in-house platform, annual operating workflow, and privacy model that preserved useful reporting without assigning employee identities.
Annual cost replaced$800K / 4 yrsInitial system delivered in approximately two weeks and operated for repeated yearly survey cycles.
06
Regulated healthcare · Cloud modernization
Improved the engineering system around critical healthcare APIs.
At physIQ, paired scalable Python API design with containerized development, stronger testing, and cloud monitoring in an FDA-regulated environment. At divvyDOSE, extended that foundation into modular AWS services, Terraform, automated delivery, monitoring, and zero-downtime practices.
physIQMade regulated API changes more consistent, reviewable, testable, and observable.divvyDOSEMoved service delivery toward reproducible cloud infrastructure and safer automated releases.
Career progressionFrom API engineering to cloud-native deliveryThese roles made infrastructure automation, delivery safety, testing, and observability part of the product rather than supporting concerns added later.
07
Global consumer systems · Amazon Prime
Carried a core customer journey across devices, markets, and major launches.
Built and operated exceptionally high-volume Prime endpoints across retail and multiple device generations, managing more than 300 EC2 instances and virtual IPs. Developed Prime signup for unreleased Kindle hardware inside a restricted-access downtown Seattle facility, and contributed to the company-wide Prime price change and international Prime Instant Video launches.
Customer surfaceKept signup behavior coherent across retail and multiple generations of Amazon devices.Delivery disciplineMoved work through rigorous design reviews and visible, tightly managed sprints with TPM, product, engineering-management, and engineering partners.
What changedFrom feature delivery to end-to-end ownershipMajor launches joined customer experience, services, security, instrumentation, documentation, and operational readiness into one engineering responsibility.
05 / Engineering mindset
I look for the system behind the symptom.
A manual report may actually be an ownership problem. A noisy queue may be missing context. A brittle deployment may reveal an unclear contract. The useful question is rarely “How do we do this task faster?” It is “What system would make this task naturally reliable?”
Good platforms don’t hide complexity. They organize it into decisions people can make.
06 / Path
A software engineer’s path into security platforms.
Fifteen-plus years across consumer systems, gaming, healthcare, pharmacy technology, advertising technology, and enterprise cloud security.
Explore the early development years- Senior Security EngineerGrubhub / Wonder
Moved from platform onboarding and reporting modernization through enterprise cloud-security rollout, then built enrichment, hierarchy, ownership, governance, and routing capabilities that make security data operational. Oversees finding SLAs and coordinates follow-up with accountable teams across the organization.
- Senior Software EngineerFetch
Built receipt-processing, deployment, observability, and lifecycle systems. Decoupled infrastructure, introduced rollout and rollback controls, improved release traceability, and created self-service tools that reduced routine operating work.
- Independent ConsultantOlcott Plastics
Improved Java delivery with Jenkins, documentation automation, containerized workflows, and streamlined continuous deployment.
- Cloud & security consultantRush Street Gaming
Reviewed AWS infrastructure, automated idle-resource cleanup, improved security-event alerting, and enhanced internal Python applications.
- Senior Software EngineerdivvyDOSE
Modernized Python APIs into modular AWS services backed by Terraform and automated delivery. Improved containerized development, monitoring, alerting, and zero-downtime practices so releases became more repeatable and production changes safer.
Milestone Infrastructure as code and cloud-native delivery become core tools - Lead EngineerphysIQ
Designed scalable Python APIs in an FDA-regulated environment while improving the engineering system around them. Introduced containerized development, stronger testing practices, and cloud monitoring so changes were more repeatable, reviewable, and observable.
Milestone Made regulated API delivery more testable and operable - Senior / Lead Software EngineerRush Street Gaming
Led casino-management systems, concurrent data pipelines, and internal platforms. Deployed Kubernetes, migrated applications to AWS, and built CI/CD workflows.
Milestone Built multi-property survey platform · $800K avoided over four years ($200K/year) - Software Development Engineer, PrimeAmazon
Built and operated exceptionally high-volume Prime endpoints across retail and Amazon devices, managing more than 300 EC2 instances and virtual IPs. Developed signup for unreleased Kindle hardware in a restricted-access Seattle facility and delivered through rigorous design reviews and disciplined cross-functional sprints.
Milestone Service ownership at scale · trusted unreleased-device development ↗ - Software DeveloperHealthcare clearinghouse engineering
Built configurable healthcare-data transfer services, claims workflows, monitoring, alarms, and operational dashboards for production integrations.
Milestone Production workflow ownership ↗ - Consultant / Senior ConsultantSogeti
Built enterprise applications, services, and workflow tools; led requirements and design work; improved delivery practices; and earned recognition for technical training leadership.
Milestone First promotion & leadership recognition ↗ - Global Information Systems InternAbbott
Automated server management, deployment, data normalization, and ETL support using Python, Jython, Unix scripting, C++, and infrastructure tooling.
Milestone Automation mindset begins ↗ - B.S. Computer ScienceNorthern Illinois University
Built the systems foundation that connected software design, databases, operating systems, and infrastructure with hands-on professional experience.
07 / Toolkit
A polyglot toolkit for problems that do not respect team boundaries.
Build
Python · Java · Go · Ruby · JavaScript
Platform
AWS · GCP · Azure · Terraform · Kubernetes · Helm · Docker
Secure
Cloud governance · IAM · Secrets · CSPM · AppSec · Automation
Operate
CI/CD · Observability · Event systems · APIs · Data pipelines
08 / Beyond software
The systems mindset follows me out of the terminal.
I’m also a father, maker, vehicle enthusiast, 3D-printing hobbyist, audio tinkerer, and persistent rearranger of rooms that are not working hard enough. The projects change. The questions do not: what is the real constraint, how will this be used, and can it survive the next revision?
Explore the projects and process
MachinesDiagnosis, teardown, and rebuilding complex systems
Fabrication3D printing, electronics, and useful custom parts
Growing systemsAutomation with an edible outputWorkshopOpenSCAD, functional prints, electronics, fabrication, and tools
MachinesCars, motorcycles, diagnostics, maintenance, and build concepts
SpacesGarage systems, industrial rooms, home theater, audio, and lighting
IdeasProducts, brands, community projects, monsters, and useful oddities
Build the system behind the outcome.
Let’s make complex engineering work easier to operate.
I’m interested in staff and lead roles where automation, developer tools, platform engineering, cloud infrastructure, and security meet.