About
With over 20 years in technology services and executive recruiting, I help Robotics, AI…
Services
Activity
37K followers
-
Mark Wallace posted thisSenior TPM - Remote US only/ EST or CST - Contract with strong CTH possibility. No Third Parties!!! The hardest subscription problems aren't growth problems. They're systems problems. Someone signs up on mobile. Pays through Apple. Logs in on web. Hits a paywall. Gets an email from Braze. Triggers events in analytics. Updates consent preferences. And somehow all of those systems need to work together flawlessly. Most companies discover the complexity after they've scaled. I'm working with a digital media company looking for a Senior Technical Product Manager to own the infrastructure behind subscriber acquisition, monetization, retention, identity, analytics, and customer lifecycle systems. This is not a backlog-management role. This is for someone who understands how subscription businesses actually work under the hood. You'll work across: • Subscription and billing systems • Apple & Google in-app purchases • Identity, authentication, OAuth, OpenID Connect • Braze, Piano, lifecycle automation • Analytics, event instrumentation, conversion funnels • Consent management, GDPR, CCPA • API integrations and cross-platform data flows Strong fit if you've built products in: • Digital media • Publishing • Streaming • SaaS subscriptions • Membership platforms • Consumer subscription businesses Remote role. East Coast preferred. Contract position with a clear path to full-time conversion. US Citizen or Green Card holders only. If you've spent your career making complex subscription ecosystems actually work, I'd like to connect.
-
Mark Wallace posted thisMultiple Founding Engineer needs. San Fran.. Most robotics companies are optimizing the wrong thing. Everyone wants bigger models. Bigger VLMs. Bigger datasets. Bigger clusters. But in the real world, robots don't fail because the model wasn't smart enough. They fail because the system wasn't deterministic enough. Latency spikes. Dropped packets. Sensor synchronization issues. Timing drift. Data pipelines that behave differently under load. Hardware and software teams blaming each other. The reality is this: A 5% better model rarely matters if your robotics stack isn't reliable. The teams that win will be the ones that can make real robots behave predictably in messy environments. That means: • Kernel engineers • Embedded software engineers • Systems engineers • Infrastructure engineers • Robot learning engineers • VLA researchers who actually deploy The future of robotics won't be built by people publishing papers. It will be built by people who can close the loop from data → training → deployment → autonomous improvement on real hardware. We're helping a well-funded robotics startup hire founding engineers across both domains: 1 year of Robotics from a top company or degree from top university. • Founding Software Engineers (Rust, C++, Linux, embedded systems, infrastructure) • Founding ML Engineers (VLA, diffusion policies, imitation learning, RL, robot learning) Small team. Real robots. Massive ownership. If you've shipped systems where failure had consequences outside of a simulator, I'd love to connect. #Robotics #PhysicalAI #EmbodiedAI #MachineLearning #RobotLearning #SystemsEngineering #EmbeddedSystems #AutonomousSystems #VLA #ArtificialIntelligence
-
Mark Wallace posted thisA huge percentage of robotics problems eventually become firmware problems. Latency. Synchronization. Motor control. Sensor timing. Board bring-up. Fault handling. Real-time reliability. This is the layer where “the robot should work” becomes: “the robot actually works.” And the number of embedded engineers who can operate at a high level in modern robotics environments is incredibly small. Especially people with experience around: •real-time systems •low-level C/C++ •motor control •CAN / SPI / I2C / EtherCAT •hardware bring-up •custom PCB integration •edge compute •synchronization across sensors, cameras, and actuators I’m currently working with several robotics and physical AI companies hiring Senior and Staff-level firmware/embedded engineers. These are highly technical, high-ownership environments where firmware is directly tied to robot capability and deployment reliability. Most roles are: •Bay Area •highly on-site •well-funded •building real deployed systems Comp is strong. Equity is meaningful. I’m also opening referral incentives for exceptional embedded and firmware talent. If you know engineers who thrive at the hardware/software boundary, I’d love to connect. #Firmware #EmbeddedSystems #Robotics #MotorControl #PhysicalAI #RealtimeSystems #EmbeddedEngineering #HumanoidRobotics
-
Mark Wallace posted thisMost robotics companies do not fail because the demo looked bad. They fail because the robot cannot survive the real world. The actuator overheats. The wiring harness breaks. The board spins take too long. The motor control loop is unstable. The sensor stack drops frames. The robot works in the lab, then falls apart in a manufacturing or logistics environment where uptime, latency, thermal behavior, signal integrity, and mechanical durability actually matter That is why hardware roles in robotics are becoming some of the hardest searches in the market right now I’m working with a stealth autonomous robotics company in San Francisco that is building robots for industrial deployment. Not research theater. Not a nice demo for a funding video. Real robots that need to operate in real environments, with real reliability expectations. They are hiring across three critical hardware areas: Senior/Staff Mechanical Engineers This is for builders who can own actuator design, end-effectors, load-bearing assemblies, full robot integration, CAD, FEA, prototyping, fabrication, and DFM. Strong fit if you have taken mechanical designs from concept through manufacturing and deployment, especially in robotics, autonomous systems, aerospace, consumer hardware, or high-performance electromechanical products. Electrical Engineers This is for engineers who can own PCBAs, power systems, motor drive integration, sensor electronics, robot wiring architecture, signal integrity, EMC/EMI, and board bring-up. Strong fit if you have designed and brought up real electronics from schematic through deployed product, including complex multilayer boards, robotics electronics, Nvidia compute modules, industrial comms, or high-speed digital systems. Senior Firmware Engineers This is for firmware engineers who can own the embedded layer between custom hardware and the software stack. C/C++, RTOS or bare-metal, motor control, PID/FOC tuning, CAN, SPI, I2C, UART, USB, EtherCAT, PCB bring-up, hardware debugging, latency, synchronization, and real-time control systems. Strong fit if you can debug with a scope, read schematics, tune control loops, and own firmware end-to-end on real robot hardware. The company is early, well-funded, and moving extremely fast. Small team. High ownership. On-site in San Francisco. Comp is $200K–$350K+ plus equity depending on level. Visa sponsorship and relocation are available for some roles. The bar is not “worked near robotics.” The bar is: Can you build? Can you move fast? Can you own real hardware? Can you point to things you personally designed, debugged, shipped, or deployed? If you are a mechanical, electrical, or firmware engineer who wants to help build the hardware foundation for autonomous robots in industrial environments, message me. These are not passive, low-intensity roles. They are for people who want to build at the edge of what currently works. #Robotics #ElectricalEngineering #MechanicalEngineering
-
Mark Wallace posted thisEveryone talks about AI models in robotics. Almost nobody talks about the infrastructure required to ship them. But in real robotics teams, DevOps is not just “cloud stuff.” It is the difference between: A researcher waiting 45 minutes for a build A robotics engineer losing a day to a broken pipeline A release getting blocked because packaging is messy A hardware team unable to run reliable HIL tests A robot sitting idle because software deployment is painful That is why some of the most important hires in robotics right now are not always ML researchers or controls engineers. They are the people building the systems that let those teams move faster. I’m working on multiple Senior DevOps / Build Infrastructure roles with frontier robotics companies right now. Locations include Austin, TX and San Mateo, CA. These teams need people who can work close to the actual engineering stack: Bazel / Skylark CI/CD Kubernetes Terraform / Ansible Linux systems Python / Bash Artifact distribution Release engineering SIL / HIL testing ARM / aarch64 cross-compilation Cloud plus on-prem infrastructure Developer tooling for robotics teams This is not traditional IT. This is the infrastructure layer behind robot software getting built, tested, released, and deployed in the real world. One team is building humanoid robots. Another is building general-purpose robotic intelligence. Both need DevOps engineers who understand that faster builds, cleaner releases, and better developer tooling directly impact how quickly robots get into the field. If you are a Senior DevOps, Platform, Build, Release, or Infrastructure Engineer who wants to work closer to robotics, I’d like to talk. Especially if you’ve worked in embedded systems, robotics, autonomy, hardware-heavy environments, or large multi-language codebases. Comp can reach up to 200-$300K depending on fit and level. message me directly.
-
Mark Wallace posted thisMost robotics companies do not fail because the demo looked bad. They fail because the robot cannot survive the real world. The actuator overheats. The wiring harness breaks. The board spins take too long. The motor control loop is unstable. The sensor stack drops frames. The robot works in the lab, then falls apart in a manufacturing or logistics environment where uptime, latency, thermal behavior, signal integrity, and mechanical durability actually matter That is why hardware roles in robotics are becoming some of the hardest searches in the market right now I’m working with a stealth autonomous robotics company in San Francisco that is building robots for industrial deployment. Not research theater. Not a nice demo for a funding video. Real robots that need to operate in real environments, with real reliability expectations. They are hiring across three critical hardware areas: Senior/Staff Mechanical Engineers This is for builders who can own actuator design, end-effectors, load-bearing assemblies, full robot integration, CAD, FEA, prototyping, fabrication, and DFM. Strong fit if you have taken mechanical designs from concept through manufacturing and deployment, especially in robotics, autonomous systems, aerospace, consumer hardware, or high-performance electromechanical products. Electrical Engineers This is for engineers who can own PCBAs, power systems, motor drive integration, sensor electronics, robot wiring architecture, signal integrity, EMC/EMI, and board bring-up. Strong fit if you have designed and brought up real electronics from schematic through deployed product, including complex multilayer boards, robotics electronics, Nvidia compute modules, industrial comms, or high-speed digital systems. Senior Firmware Engineers This is for firmware engineers who can own the embedded layer between custom hardware and the software stack. C/C++, RTOS or bare-metal, motor control, PID/FOC tuning, CAN, SPI, I2C, UART, USB, EtherCAT, PCB bring-up, hardware debugging, latency, synchronization, and real-time control systems. Strong fit if you can debug with a scope, read schematics, tune control loops, and own firmware end-to-end on real robot hardware. The company is early, well-funded, and moving extremely fast. Small team. High ownership. On-site in San Francisco. Comp is $200K–$350K+ plus equity depending on level. Visa sponsorship and relocation are available for some roles. The bar is not “worked near robotics.” The bar is: Can you build? Can you move fast? Can you own real hardware? Can you point to things you personally designed, debugged, shipped, or deployed? If you are a mechanical, electrical, or firmware engineer who wants to help build the hardware foundation for autonomous robots in industrial environments, message me. These are not passive, low-intensity roles. They are for people who want to build at the edge of what currently works. #Robotics #ElectricalEngineering #MechanicalEngineering
-
Mark Wallace posted thisThe best robotics engineers are rarely applying to jobs. They’re usually: •deep in a lab •debugging hardware at 11 PM •tuning controllers •optimizing inference •bringing up sensors •dealing with production failures •fixing systems that broke in the real world Which is exactly why some of the hardest engineering hires right now are happening almost entirely through trusted networks. I’m currently hiring for multiple Senior and Staff-level roles across: •humanoids •embodied AI •robotics infrastructure •autonomy •controls •embedded systems •perception •manipulation •electrical systems And honestly, some of these searches are brutal. The people who can truly build and ship these systems are extraordinarily rare. So I’m doing something simple: I’m opening referral incentives across many of these roles. If you know exceptional engineers who: •ship real systems •thrive in high-intensity startups •like difficult technical problems •want to build things that matter …I want to talk to them. Strong compensation. Strong equity. Mostly on-site. Mostly frontier robotics and physical AI. Meaningful referral fees available for successful hires. DM me privately. #Robotics #PhysicalAI #EmbodiedAI #Engineering #HumanoidRobotics #EmbeddedSystems #ArtificialIntelligence #Hiring
-
Mark Wallace posted thisMost full-stack engineers never get close to the physical world. They build dashboards. They build internal tools. They build observability systems. They build real-time workflows. But usually the consequence of failure is a bad user experience. In robotics, it is different. A broken alert can stop a deployment. A laggy video feed can make intervention impossible. A weak dashboard can hide a robot failure until the customer sees it first. A bad internal tool can slow down an entire fleet. This is why full-stack engineering in robotics is becoming one of the most underrated roles in autonomy. The robots do not just need better models. They need the infrastructure around the models to actually work in production. Fleet management. Observability. Monitoring. Teleoperation. Live camera feeds. Robot controls. Deployment workflows. Real-time debugging tools. Customer operations systems. That layer is what turns a robotics demo into a robotics company. I’m hiring Full-Stack Engineers for a stealth autonomous robotics company in San Francisco building bimanual manipulation robots for real manufacturing and logistics environments. This is not research-only. They are deploying into industrial sites. They own hardware, ML, and deployment infrastructure end-to-end. The team is 14 people with roots from Palantir, xAI, Mercor, Ramp, Midjourney, and Founders Fund. The environment is intense. 6 days per week in office in San Francisco. Very long hours. Not a 9-to-5 role. Not remote. Not for someone looking for a balanced corporate environment. But for the right builder, this is a chance to own the real-time product layer that keeps autonomous robots operating in mission-critical environments. Stack: React TypeScript Python PostgreSQL Docker Kubernetes Strong signals: Startup product engineering Real-time systems Streaming video WebSockets Cloud infra Internal tooling Operator-facing tools Robotics, autonomy, or logistics systems Comp: $200K to $350K base Competitive equity H-1B transfers considered case by case San Francisco, onsite If you are a full-stack engineer who wants to build software that touches the real world, not just another SaaS workflow, this is worth a conversation. DM me or comment “robotics” and I’ll send details. #Robotics #PhysicalAI #FullStackEngineering #AutonomousSystems #EngineeringHiring
-
Mark Wallace posted thisThe next bottleneck in AI is not generating text. It’s making intelligence work in the physical world. That means: •perception that survives outside controlled environments •models that run in real time •systems that can reason over action and motion •robots that can adapt to unseen situations •inference that works on edge compute •training infrastructure that scales And the people capable of building those systems are becoming incredibly scarce. I’m working with several high-bar robotics and physical AI companies hiring: •Senior AI Researchers •Staff ML Engineers •Embodied AI Researchers •World Model Engineers •VLM/VLA Engineers •Real-Time Inference Engineers •Robotics Foundation Model Researchers These are not “research playground” roles. These teams are deploying systems into the real world. Most roles are: •Bay Area •NYC •Austin •Houston •Boston •highly on-site •extremely well funded Comp can reach well into the mid/high six figures with equity for the right people. I’m opening generous referral incentives for these searches as well. If you know engineers or researchers who have actually built and deployed embodied AI systems — especially in robotics, AV, edge AI, or real-time inference — I’d love to connect. DM me. #EmbodiedAI #PhysicalAI #Robotics #MachineLearning #WorldModels #VLM #VLA #ArtificialIntelligence #DeepLearning #Inference #RoboticsAI
Mark Wallace commented on a post
21h
It's awful now.
Mark Wallace replied to a comment
1d
Corey Yesavage Disagree. It has been the gold standard for most industry leaders in all verticals. Now it all influencer BS and making up lies about yow great you are. You used to be able to build an amazing connected network if you were talking to the right people in your industry.
-
Mark Wallace liked thisMark Wallace liked thisI've been reading about Facebook's decline for a while. Now I can see it firsthand — on LinkedIn. The boomers have migrated. And they brought everything with them: cat videos, political rants, and motivational quotes that smell suspiciously like ChatGPT had a bad day. Half the content on my timeline right now would have been unremarkable on Facebook circa 2016. On LinkedIn in 2026, it's just... confusing. Two questions for the cat video crowd: 1. How much free time do you actually have? 2. Do you think a recruiter seeing that is going to call you faster? I'm not the LinkedIn police. Post what you want. But maybe — just maybe — do the rest of us a favor and think twice before hitting publish on that "Monday morning, I need coffee ☕😂" carousel. We're all out here trying to find signal in the noise. You're adding noise.
-
Mark Wallace liked thisMark Wallace liked thisIt's only a matter of time before the first human sets foot on Mars - and we're excited about it. Here's what it would take to actually make Mars habitable: https://lnkd.in/gi7ZY58x
-
Mark Wallace liked thisMark Wallace liked thisWhy don’t we put solar panels over parking lots instead of fields? Parking lots are already covered in concrete, sit under the sun all day, and could generate electricity while also providing shade for cars. The catch is that solar parking canopies are much more expensive to build. A solar farm in an open field is cheaper, simpler, and easier to maintain at scale. That is why we see so many solar farms on land instead of above existing infrastructure. Still, it raises an interesting question about how we use space. Should energy infrastructure compete with farmland and open land when millions of parking spaces already exist? Perhaps the answer is neither. Countries are already experimenting with floating solar farms on lakes and reservoirs, offshore solar, solar integrated into buildings, and even concepts for solar power in space. One thing is certain: we are going to need far more energy than ever before, and somehow it still never feels like enough. Follow Endrit Restelica for more.
-
Mark Wallace liked thisMark Wallace liked thisCould robot soldiers actually make us safer? Our CEO Sankaet Pathak's answer might not be what you expect. https://lnkd.in/gs9KuF_7
Experience & Education
-
i-Hire Inc
View Mark’s full experience
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Licenses & Certifications
-
Informatica Data Integration Velocity Accredited Partner
-
Issued
Volunteer Experience
-
-
-
General Member Board
University of Miami Hurricanes Club
Organizations
-
Atlanta Friends and Family of the University of Miami
Board Member
- PresentPurpose. The propose of the Club is to establish and maintain mutually beneficial relationships between the University of Miami, hereafter referred as the “University,” the UMAA and its alumni residing or working in the greater Atlanta area, and persons with an interest in the welfare of the University of Miami. The Club links alumni, the University, the UMAA, and the friends of the University through sponsoring a wide variety of programs and benefits that foster a spirit of loyalty…
Purpose. The propose of the Club is to establish and maintain mutually beneficial relationships between the University of Miami, hereafter referred as the “University,” the UMAA and its alumni residing or working in the greater Atlanta area, and persons with an interest in the welfare of the University of Miami. The Club links alumni, the University, the UMAA, and the friends of the University through sponsoring a wide variety of programs and benefits that foster a spirit of loyalty, involvement, and life-long commitment to the University of Miami.
Recommendations received
10 people have recommended Mark
Join now to viewOther similar profiles
Explore more posts
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top contentOthers named Mark Wallace
1231 others named Mark Wallace are on LinkedIn
See others named Mark Wallace