CandorBrief

Professional overview

Give a concise factual introduction to the professional’s stated focus, experience, and capabilities.

You are helping a reviewer understand a professional profile for a fair hiring, recruiting, staffing, consulting, or engagement discussion.

SOURCE BOUNDARY
Evidence mode: Supplied profile evidence only.
Use only the supplied professional profile evidence and the visitor-provided context in this prompt. Do not use or rely on prior chats, account memory, earlier searches, unstated personal knowledge, or assumptions. If information is not established by the permitted sources, say that it is not established.
Do not retrieve, introduce, or rely on public information beyond the permitted supplied profile evidence and visitor context.

TASK
Summarize the supplied profile evidence into a factual professional overview.

SUPPLIED PROFESSIONAL PROFILE EVIDENCE
Professional: Milo Sparks

Professional headline: Inventor-founder, chief tinkerer, and builder of useful things that occasionally hum

Professional snapshot:
Inventor-founder and engineering leader with 19 years of experience building unusually practical hardware, resilient energy systems, and teams that can explain their decisions without a 90-slide deck. Known for turning moonshot prototypes into field-ready products, asking inconveniently useful questions, and treating reliability as a team sport.

Relevant experience:
- Founder and Chief Tinkerer | Brilliantly Overbuilt, Inc. | April 2021 - Present
  - Founded a clean-energy product company making modular power systems for places that cannot afford for the lights to have a personality.
- Took the flagship product, the Very Serious Power Box, from garage prototype to four paid pilot deployments with fictional manufacturers, community facilities, and research campuses.
- Built a 37-person team across electrical engineering, firmware, mechanical design, field service, operations, and customer partnerships.
- Created a weekly 'What Did the Machine Teach Us?' review that turns field evidence, safety findings, customer feedback, and supplier surprises into roadmap decisions.
- Raised fictional capital by explaining technical tradeoffs in plain language and refusing to call a spreadsheet a strategy.
- Chief Technology Officer | Plausible Deniability Systems | January 2018 - March 2021
  - Led technology strategy for industrial microgrid controls used by fictional hospitals, food distribution centers, and delightfully remote research stations.
- Combined firmware, controls, data, and field engineering into one product organization with shared reliability measures and fewer meetings about whose spreadsheet was correct.
- Reduced pilot-to-production handoff time by introducing architecture reviews, serviceability checklists, and a rule that field technicians get a vote before launch.
- Presented deployment risk, product tradeoffs, and recovery plans to the board, strategic partners, and enterprise customers without hiding the difficult parts.
- Hired and coached engineering directors and principal engineers through a period of rapid growth and one memorable office espresso-machine incident.
- Co-Founder and Vice President of Engineering | Good Enough Robotics | August 2014 - December 2017
  - Co-founded an industrial robotics company making inspection equipment for places people would rather not crawl into.
- Led the first field-ready autonomous inspection platform across sensing, motion control, fleet software, operator workflows, and the surprisingly emotional process of naming robots.
- Designed a customer pilot program with explicit safety, data-handling, and success criteria before sending anything near an active industrial site.
- Grew engineering from five determined generalists to 26 specialists while keeping prototype-to-field feedback loops fast and honest.
- Supported fictional acquisition diligence by documenting architecture decisions, patent concepts, field performance, supplier dependencies, and unresolved risks.
- Principal Systems Engineer | Thunderbolt Fieldworks | May 2011 - July 2014
  - Designed control and monitoring systems for mobile environmental platforms that worked in heat, dust, vibration, and intermittent connectivity because nature does not read requirements documents.
- Led cross-functional failure analysis after field incidents and translated findings into hardware, firmware, service, and training improvements.
- Built test fixtures and acceptance criteria that made prototype and production builds less dependent on heroic individual memory.
- Partnered with operations to qualify suppliers and document manufacturing changes without losing traceability or anyone's sanity.
- Senior Electrical Engineer | Emergency Backup Plan Co. | June 2008 - April 2011
  - Developed power electronics and sensor interfaces for research prototypes that needed to become dependable products before anyone bought them.
- Built instrumentation plans that gave project teams useful performance data instead of a beautiful dashboard with no decisions attached.
- Worked with scientists, industrial designers, and software engineers to resolve tradeoffs while they were still affordable.
- Electrical Engineer | The Department of Useful Gadgets | July 2006 - May 2008
  - Designed and tested low-power control boards for water-quality monitoring equipment.
- Created practical diagnostic tools and service documentation for field technicians who needed answers before the weather changed.
- Learned that repairability, cost, and user reality deserve equal seats at the engineering table.

Core capabilities:
- Inventing and shipping
  - Zero-to-one product strategy: frames the problem, field constraints, and smallest credible first build before anyone orders celebratory stickers.
- Hardware-software systems design: connects circuitry, firmware, mechanical realities, and the person who eventually has to repair it.
- Rapid prototyping: makes testable things quickly, with enough labels that tomorrow's Milo can still identify the wires.
- Field deployment: plans commissioning around actual sites, actual operators, and the weather's strong opinions.
- Reliability engineering: turns failures into design evidence instead of folklore or increasingly elaborate blame diagrams.
- Turning 'interesting' into 'useful': translates promising experiments into products people can operate, maintain, and budget for.
- Leading grown-up engineering
  - Engineering organization design: builds teams with clear ownership, healthy disagreement, and fewer mysterious handoffs.
- Technical decision-making: uses decision records, evidence reviews, and a polite suspicion of the loudest spreadsheet.
- Hiring and mentoring: develops practical leaders who can explain both the plan and the uncomfortable tradeoff.
- Product and operations alignment: keeps engineering, product, operations, and customers in the same reality whenever possible.
- Board and investor communication: explains technical risk in ordinary language without sanding off the important sharp edges.
- Healthy escalation: creates clear paths for raising concerns before they become expensive surprises with pastries.
- The unglamorous work that makes things real
  - Safety reviews: makes safety evidence visible early, not only after somebody asks the very reasonable question.
- Supplier qualification: checks whether suppliers can make the part, support the part, and recognize the part in a hurry.
- Manufacturing readiness: prepares designs, fixtures, instructions, and checks for the moment prototypes have to grow up.
- Customer discovery: listens for the useful problem behind the first request, especially when it arrives in all caps.
- Failure analysis: follows evidence across hardware, software, process, and assumptions until the story becomes actionable.
- Writing down what happened: leaves a record future teammates can use without summoning the original author from vacation.

Skills and tools:
- Systems that make the lights stay on
  - Power electronics: designs conversion, protection, and monitoring approaches that remain legible after the enclosure is closed.
- Embedded C: writes and reviews embedded code with an eye toward deterministic behavior and field diagnostics.
- Python: uses scripts for test automation, data cleanup, fixture control, and removing small amounts of recurring misery.
- Control systems: models feedback, stability, and operating boundaries before the physical prototype gets theatrical.
- Industrial communications: works across CAN, Modbus, and other industrial protocols without assuming every device read the same manual.
- Systems modeling: connects requirements, simulations, test evidence, and field observations into one useful technical picture.
- From sketchbook to field site
  - Product discovery: turns interviews, site visits, and observed workarounds into product questions worth answering.
- Roadmap development: sequences technical uncertainty, customer value, and operational readiness rather than treating a backlog as destiny.
- Stage-gate reviews: prepares evidence-led checkpoints that make tradeoffs discussable before the calendar makes them urgent.
- Manufacturing transfer: plans the move from clever prototype to repeatable build with fewer heroic late-night interpretations.
- Field reliability: organizes failure signals, service findings, and recurring questions into product improvement work.
- Supplier management: evaluates capability, communication, and change control alongside price, because all three eventually send invoices.
- Making the room smarter
  - Executive communication: gives leaders and partners an honest view of decisions, constraints, and what the evidence still cannot say.
- Technical writing: creates technical narratives, decision records, and field guides people can actually use.
- Hiring and mentoring: helps engineers grow their judgment, not just their collection of approval-seeking calendar invites.
- Facilitation: designs conversations that make room for evidence, dissent, and the quiet expert near the back wall.
- Investor diligence: prepares practical technical materials for people who need to understand both the opportunity and the wiring.
- Partnership negotiation: finds agreements that respect technical reality, customer needs, and the fact that everyone brought a lawyer.

Selected projects:
- The Very Serious Power Box
  Fictional modular energy storage and automated load-management product designed for facilities that need resilient power without needing a full-time wizard on staff. Milo led product strategy, field commissioning, and reliability reviews. The work included service-friendly diagnostics, operator handoffs, and an unusually serious relationship with enclosure labels.
- Rover McRoverface Inspection Platform
  Fictional autonomous inspection platform for hard-to-reach industrial assets. Milo co-led the architecture across sensing, robotics, fleet software, operator review, safety boundaries, and a name the team could not outvote. It also produced clearer mission-review checklists, recoverable failure states, and at least one robot with a name tag.
- The 'Tell Us Before It Breaks' Reliability Toolkit
  Fictional set of test methods, field checklists, and decision templates that helped engineering and operations teams spot deployment risk before it became an expensive story at an all-hands meeting. Teams used it to turn vague concern into testable questions, assigned owners, and fewer postmortems that began with 'well, that was unexpected.'

Certifications:
- Certified Builder of Things That Should Not Catch Fire
  Fictional demonstration credential. Covered safety-minded design reviews, thermal and protection checks, and the solemn responsibility of not calling a near miss a feature.
- Functional Safety for Industrial Control Systems
  Fictional demonstration credential. Focused on hazard analysis, verification evidence, and explaining safety boundaries before the demo is scheduled.

Education:
- M.S. - Electrical and Systems Engineering | Institute for Extremely Practical Technology | 2004 - 2006
  Fictional graduate research in distributed control systems, fault-tolerant power electronics, and explaining difficult things with diagrams.
- B.S. - Electrical Engineering | Coastal State University | 2000 - 2004
  Fictional capstone project: modular sensor network for watershed monitoring, built with more optimism than sleep.

RESPONSE CHECKLIST
Begin with an Evidence Ledger using these labels: 1. Supplied profile evidence used, 2. Visitor-provided context used, 3. Public information used (only if explicitly permitted; otherwise write 'None'), and 4. Information not established by the permitted sources.
Then complete the task. Clearly separate documented evidence, reasonable interpretation, and questions or gaps to validate. Phrase reasonable interpretations with calibrated language such as 'may' or 'could.' Do not turn adjacent experience, an industry connection, a title, or a keyword into documented direct expertise, familiarity, capability, or qualification. Do not invent, embellish, rewrite, or infer unstated qualifications. Do not infer protected characteristics. Do not make a final hiring, staffing, or engagement recommendation.
If you cannot follow these source boundaries, say so plainly. An external AI tool may still have memory, prior context, retrieval, or model knowledge outside this prompt; the reviewer must verify the response against the listed sources and their own process.

You are helping a reviewer understand a professional profile for a fair hiring, recruiting, staffing, consulting, or engagement discussion.

SOURCE BOUNDARY
Evidence mode: Supplied profile evidence only.
Use only the supplied professional profile evidence and the visitor-provided context in this prompt. Do not use or rely on prior chats, account memory, earlier searches, unstated personal knowledge, or assumptions. If information is not established by the permitted sources, say that it is not established.
Do not retrieve, introduce, or rely on public information beyond the permitted supplied profile evidence and visitor context.


TASK
Summarize the supplied profile evidence into a factual professional overview.

SUPPLIED PROFESSIONAL PROFILE EVIDENCE
Professional: Milo Sparks

Professional headline: Inventor-founder, chief tinkerer, and builder of useful things that occasionally hum

Professional snapshot:
Inventor-founder and engineering leader with 19 years of experience building unusually practical hardware, resilient energy systems, and teams that can explain their decisions without a 90-slide deck. Known for turning moonshot prototypes into field-ready products, asking inconveniently useful questions, and treating reliability as a team sport.

Relevant experience:
- Founder and Chief Tinkerer | Brilliantly Overbuilt, Inc. | April 2021 - Present
  - Founded a clean-energy product company making modular power systems for places that cannot afford for the lights to have a personality.
- Took the flagship product, the Very Serious Power Box, from garage prototype to four paid pilot deployments with fictional manufacturers, community facilities, and research campuses.
- Built a 37-person team across electrical engineering, firmware, mechanical design, field service, operations, and customer partnerships.
- Created a weekly 'What Did the Machine Teach Us?' review that turns field evidence, safety findings, customer feedback, and supplier surprises into roadmap decisions.
- Raised fictional capital by explaining technical tradeoffs in plain language and refusing to call a spreadsheet a strategy.
- Chief Technology Officer | Plausible Deniability Systems | January 2018 - March 2021
  - Led technology strategy for industrial microgrid controls used by fictional hospitals, food distribution centers, and delightfully remote research stations.
- Combined firmware, controls, data, and field engineering into one product organization with shared reliability measures and fewer meetings about whose spreadsheet was correct.
- Reduced pilot-to-production handoff time by introducing architecture reviews, serviceability checklists, and a rule that field technicians get a vote before launch.
- Presented deployment risk, product tradeoffs, and recovery plans to the board, strategic partners, and enterprise customers without hiding the difficult parts.
- Hired and coached engineering directors and principal engineers through a period of rapid growth and one memorable office espresso-machine incident.
- Co-Founder and Vice President of Engineering | Good Enough Robotics | August 2014 - December 2017
  - Co-founded an industrial robotics company making inspection equipment for places people would rather not crawl into.
- Led the first field-ready autonomous inspection platform across sensing, motion control, fleet software, operator workflows, and the surprisingly emotional process of naming robots.
- Designed a customer pilot program with explicit safety, data-handling, and success criteria before sending anything near an active industrial site.
- Grew engineering from five determined generalists to 26 specialists while keeping prototype-to-field feedback loops fast and honest.
- Supported fictional acquisition diligence by documenting architecture decisions, patent concepts, field performance, supplier dependencies, and unresolved risks.
- Principal Systems Engineer | Thunderbolt Fieldworks | May 2011 - July 2014
  - Designed control and monitoring systems for mobile environmental platforms that worked in heat, dust, vibration, and intermittent connectivity because nature does not read requirements documents.
- Led cross-functional failure analysis after field incidents and translated findings into hardware, firmware, service, and training improvements.
- Built test fixtures and acceptance criteria that made prototype and production builds less dependent on heroic individual memory.
- Partnered with operations to qualify suppliers and document manufacturing changes without losing traceability or anyone's sanity.
- Senior Electrical Engineer | Emergency Backup Plan Co. | June 2008 - April 2011
  - Developed power electronics and sensor interfaces for research prototypes that needed to become dependable products before anyone bought them.
- Built instrumentation plans that gave project teams useful performance data instead of a beautiful dashboard with no decisions attached.
- Worked with scientists, industrial designers, and software engineers to resolve tradeoffs while they were still affordable.
- Electrical Engineer | The Department of Useful Gadgets | July 2006 - May 2008
  - Designed and tested low-power control boards for water-quality monitoring equipment.
- Created practical diagnostic tools and service documentation for field technicians who needed answers before the weather changed.
- Learned that repairability, cost, and user reality deserve equal seats at the engineering table.

Core capabilities:
- Inventing and shipping
  - Zero-to-one product strategy: frames the problem, field constraints, and smallest credible first build before anyone orders celebratory stickers.
- Hardware-software systems design: connects circuitry, firmware, mechanical realities, and the person who eventually has to repair it.
- Rapid prototyping: makes testable things quickly, with enough labels that tomorrow's Milo can still identify the wires.
- Field deployment: plans commissioning around actual sites, actual operators, and the weather's strong opinions.
- Reliability engineering: turns failures into design evidence instead of folklore or increasingly elaborate blame diagrams.
- Turning 'interesting' into 'useful': translates promising experiments into products people can operate, maintain, and budget for.
- Leading grown-up engineering
  - Engineering organization design: builds teams with clear ownership, healthy disagreement, and fewer mysterious handoffs.
- Technical decision-making: uses decision records, evidence reviews, and a polite suspicion of the loudest spreadsheet.
- Hiring and mentoring: develops practical leaders who can explain both the plan and the uncomfortable tradeoff.
- Product and operations alignment: keeps engineering, product, operations, and customers in the same reality whenever possible.
- Board and investor communication: explains technical risk in ordinary language without sanding off the important sharp edges.
- Healthy escalation: creates clear paths for raising concerns before they become expensive surprises with pastries.
- The unglamorous work that makes things real
  - Safety reviews: makes safety evidence visible early, not only after somebody asks the very reasonable question.
- Supplier qualification: checks whether suppliers can make the part, support the part, and recognize the part in a hurry.
- Manufacturing readiness: prepares designs, fixtures, instructions, and checks for the moment prototypes have to grow up.
- Customer discovery: listens for the useful problem behind the first request, especially when it arrives in all caps.
- Failure analysis: follows evidence across hardware, software, process, and assumptions until the story becomes actionable.
- Writing down what happened: leaves a record future teammates can use without summoning the original author from vacation.

Skills and tools:
- Systems that make the lights stay on
  - Power electronics: designs conversion, protection, and monitoring approaches that remain legible after the enclosure is closed.
- Embedded C: writes and reviews embedded code with an eye toward deterministic behavior and field diagnostics.
- Python: uses scripts for test automation, data cleanup, fixture control, and removing small amounts of recurring misery.
- Control systems: models feedback, stability, and operating boundaries before the physical prototype gets theatrical.
- Industrial communications: works across CAN, Modbus, and other industrial protocols without assuming every device read the same manual.
- Systems modeling: connects requirements, simulations, test evidence, and field observations into one useful technical picture.
- From sketchbook to field site
  - Product discovery: turns interviews, site visits, and observed workarounds into product questions worth answering.
- Roadmap development: sequences technical uncertainty, customer value, and operational readiness rather than treating a backlog as destiny.
- Stage-gate reviews: prepares evidence-led checkpoints that make tradeoffs discussable before the calendar makes them urgent.
- Manufacturing transfer: plans the move from clever prototype to repeatable build with fewer heroic late-night interpretations.
- Field reliability: organizes failure signals, service findings, and recurring questions into product improvement work.
- Supplier management: evaluates capability, communication, and change control alongside price, because all three eventually send invoices.
- Making the room smarter
  - Executive communication: gives leaders and partners an honest view of decisions, constraints, and what the evidence still cannot say.
- Technical writing: creates technical narratives, decision records, and field guides people can actually use.
- Hiring and mentoring: helps engineers grow their judgment, not just their collection of approval-seeking calendar invites.
- Facilitation: designs conversations that make room for evidence, dissent, and the quiet expert near the back wall.
- Investor diligence: prepares practical technical materials for people who need to understand both the opportunity and the wiring.
- Partnership negotiation: finds agreements that respect technical reality, customer needs, and the fact that everyone brought a lawyer.

Selected projects:
- The Very Serious Power Box
  Fictional modular energy storage and automated load-management product designed for facilities that need resilient power without needing a full-time wizard on staff. Milo led product strategy, field commissioning, and reliability reviews. The work included service-friendly diagnostics, operator handoffs, and an unusually serious relationship with enclosure labels.
- Rover McRoverface Inspection Platform
  Fictional autonomous inspection platform for hard-to-reach industrial assets. Milo co-led the architecture across sensing, robotics, fleet software, operator review, safety boundaries, and a name the team could not outvote. It also produced clearer mission-review checklists, recoverable failure states, and at least one robot with a name tag.
- The 'Tell Us Before It Breaks' Reliability Toolkit
  Fictional set of test methods, field checklists, and decision templates that helped engineering and operations teams spot deployment risk before it became an expensive story at an all-hands meeting. Teams used it to turn vague concern into testable questions, assigned owners, and fewer postmortems that began with 'well, that was unexpected.'

Certifications:
- Certified Builder of Things That Should Not Catch Fire
  Fictional demonstration credential. Covered safety-minded design reviews, thermal and protection checks, and the solemn responsibility of not calling a near miss a feature.
- Functional Safety for Industrial Control Systems
  Fictional demonstration credential. Focused on hazard analysis, verification evidence, and explaining safety boundaries before the demo is scheduled.

Education:
- M.S. - Electrical and Systems Engineering | Institute for Extremely Practical Technology | 2004 - 2006
  Fictional graduate research in distributed control systems, fault-tolerant power electronics, and explaining difficult things with diagrams.
- B.S. - Electrical Engineering | Coastal State University | 2000 - 2004
  Fictional capstone project: modular sensor network for watershed monitoring, built with more optimism than sleep.

RESPONSE CHECKLIST
Begin with an Evidence Ledger using these labels: 1. Supplied profile evidence used, 2. Visitor-provided context used, 3. Public information used (only if explicitly permitted; otherwise write 'None'), and 4. Information not established by the permitted sources.
Then complete the task. Clearly separate documented evidence, reasonable interpretation, and questions or gaps to validate. Phrase reasonable interpretations with calibrated language such as 'may' or 'could.' Do not turn adjacent experience, an industry connection, a title, or a keyword into documented direct expertise, familiarity, capability, or qualification. Do not invent, embellish, rewrite, or infer unstated qualifications. Do not infer protected characteristics. Do not make a final hiring, staffing, or engagement recommendation.
If you cannot follow these source boundaries, say so plainly. An external AI tool may still have memory, prior context, retrieval, or model knowledge outside this prompt; the reviewer must verify the response against the listed sources and their own process.

Career narrative

Understand the documented progression, pivots, and recurring themes across this professional’s experience.

You are helping a reviewer understand a professional profile for a fair hiring, recruiting, staffing, consulting, or engagement discussion.

SOURCE BOUNDARY
Evidence mode: Supplied profile evidence only.
Use only the supplied professional profile evidence and the visitor-provided context in this prompt. Do not use or rely on prior chats, account memory, earlier searches, unstated personal knowledge, or assumptions. If information is not established by the permitted sources, say that it is not established.
Do not retrieve, introduce, or rely on public information beyond the permitted supplied profile evidence and visitor context.

TASK
Describe the documented career progression and themes without inferring motives or future potential.

SUPPLIED PROFESSIONAL PROFILE EVIDENCE
Professional: Milo Sparks

Professional headline: Inventor-founder, chief tinkerer, and builder of useful things that occasionally hum

Professional snapshot:
Inventor-founder and engineering leader with 19 years of experience building unusually practical hardware, resilient energy systems, and teams that can explain their decisions without a 90-slide deck. Known for turning moonshot prototypes into field-ready products, asking inconveniently useful questions, and treating reliability as a team sport.

Relevant experience:
- Founder and Chief Tinkerer | Brilliantly Overbuilt, Inc. | April 2021 - Present
  - Founded a clean-energy product company making modular power systems for places that cannot afford for the lights to have a personality.
- Took the flagship product, the Very Serious Power Box, from garage prototype to four paid pilot deployments with fictional manufacturers, community facilities, and research campuses.
- Built a 37-person team across electrical engineering, firmware, mechanical design, field service, operations, and customer partnerships.
- Created a weekly 'What Did the Machine Teach Us?' review that turns field evidence, safety findings, customer feedback, and supplier surprises into roadmap decisions.
- Raised fictional capital by explaining technical tradeoffs in plain language and refusing to call a spreadsheet a strategy.
- Chief Technology Officer | Plausible Deniability Systems | January 2018 - March 2021
  - Led technology strategy for industrial microgrid controls used by fictional hospitals, food distribution centers, and delightfully remote research stations.
- Combined firmware, controls, data, and field engineering into one product organization with shared reliability measures and fewer meetings about whose spreadsheet was correct.
- Reduced pilot-to-production handoff time by introducing architecture reviews, serviceability checklists, and a rule that field technicians get a vote before launch.
- Presented deployment risk, product tradeoffs, and recovery plans to the board, strategic partners, and enterprise customers without hiding the difficult parts.
- Hired and coached engineering directors and principal engineers through a period of rapid growth and one memorable office espresso-machine incident.
- Co-Founder and Vice President of Engineering | Good Enough Robotics | August 2014 - December 2017
  - Co-founded an industrial robotics company making inspection equipment for places people would rather not crawl into.
- Led the first field-ready autonomous inspection platform across sensing, motion control, fleet software, operator workflows, and the surprisingly emotional process of naming robots.
- Designed a customer pilot program with explicit safety, data-handling, and success criteria before sending anything near an active industrial site.
- Grew engineering from five determined generalists to 26 specialists while keeping prototype-to-field feedback loops fast and honest.
- Supported fictional acquisition diligence by documenting architecture decisions, patent concepts, field performance, supplier dependencies, and unresolved risks.
- Principal Systems Engineer | Thunderbolt Fieldworks | May 2011 - July 2014
  - Designed control and monitoring systems for mobile environmental platforms that worked in heat, dust, vibration, and intermittent connectivity because nature does not read requirements documents.
- Led cross-functional failure analysis after field incidents and translated findings into hardware, firmware, service, and training improvements.
- Built test fixtures and acceptance criteria that made prototype and production builds less dependent on heroic individual memory.
- Partnered with operations to qualify suppliers and document manufacturing changes without losing traceability or anyone's sanity.
- Senior Electrical Engineer | Emergency Backup Plan Co. | June 2008 - April 2011
  - Developed power electronics and sensor interfaces for research prototypes that needed to become dependable products before anyone bought them.
- Built instrumentation plans that gave project teams useful performance data instead of a beautiful dashboard with no decisions attached.
- Worked with scientists, industrial designers, and software engineers to resolve tradeoffs while they were still affordable.
- Electrical Engineer | The Department of Useful Gadgets | July 2006 - May 2008
  - Designed and tested low-power control boards for water-quality monitoring equipment.
- Created practical diagnostic tools and service documentation for field technicians who needed answers before the weather changed.
- Learned that repairability, cost, and user reality deserve equal seats at the engineering table.

RESPONSE CHECKLIST
Begin with an Evidence Ledger using these labels: 1. Supplied profile evidence used, 2. Visitor-provided context used, 3. Public information used (only if explicitly permitted; otherwise write 'None'), and 4. Information not established by the permitted sources.
Then complete the task. Clearly separate documented evidence, reasonable interpretation, and questions or gaps to validate. Phrase reasonable interpretations with calibrated language such as 'may' or 'could.' Do not turn adjacent experience, an industry connection, a title, or a keyword into documented direct expertise, familiarity, capability, or qualification. Do not invent, embellish, rewrite, or infer unstated qualifications. Do not infer protected characteristics. Do not make a final hiring, staffing, or engagement recommendation.
If you cannot follow these source boundaries, say so plainly. An external AI tool may still have memory, prior context, retrieval, or model knowledge outside this prompt; the reviewer must verify the response against the listed sources and their own process.

You are helping a reviewer understand a professional profile for a fair hiring, recruiting, staffing, consulting, or engagement discussion.

SOURCE BOUNDARY
Evidence mode: Supplied profile evidence only.
Use only the supplied professional profile evidence and the visitor-provided context in this prompt. Do not use or rely on prior chats, account memory, earlier searches, unstated personal knowledge, or assumptions. If information is not established by the permitted sources, say that it is not established.
Do not retrieve, introduce, or rely on public information beyond the permitted supplied profile evidence and visitor context.


TASK
Describe the documented career progression and themes without inferring motives or future potential.

SUPPLIED PROFESSIONAL PROFILE EVIDENCE
Professional: Milo Sparks

Professional headline: Inventor-founder, chief tinkerer, and builder of useful things that occasionally hum

Professional snapshot:
Inventor-founder and engineering leader with 19 years of experience building unusually practical hardware, resilient energy systems, and teams that can explain their decisions without a 90-slide deck. Known for turning moonshot prototypes into field-ready products, asking inconveniently useful questions, and treating reliability as a team sport.

Relevant experience:
- Founder and Chief Tinkerer | Brilliantly Overbuilt, Inc. | April 2021 - Present
  - Founded a clean-energy product company making modular power systems for places that cannot afford for the lights to have a personality.
- Took the flagship product, the Very Serious Power Box, from garage prototype to four paid pilot deployments with fictional manufacturers, community facilities, and research campuses.
- Built a 37-person team across electrical engineering, firmware, mechanical design, field service, operations, and customer partnerships.
- Created a weekly 'What Did the Machine Teach Us?' review that turns field evidence, safety findings, customer feedback, and supplier surprises into roadmap decisions.
- Raised fictional capital by explaining technical tradeoffs in plain language and refusing to call a spreadsheet a strategy.
- Chief Technology Officer | Plausible Deniability Systems | January 2018 - March 2021
  - Led technology strategy for industrial microgrid controls used by fictional hospitals, food distribution centers, and delightfully remote research stations.
- Combined firmware, controls, data, and field engineering into one product organization with shared reliability measures and fewer meetings about whose spreadsheet was correct.
- Reduced pilot-to-production handoff time by introducing architecture reviews, serviceability checklists, and a rule that field technicians get a vote before launch.
- Presented deployment risk, product tradeoffs, and recovery plans to the board, strategic partners, and enterprise customers without hiding the difficult parts.
- Hired and coached engineering directors and principal engineers through a period of rapid growth and one memorable office espresso-machine incident.
- Co-Founder and Vice President of Engineering | Good Enough Robotics | August 2014 - December 2017
  - Co-founded an industrial robotics company making inspection equipment for places people would rather not crawl into.
- Led the first field-ready autonomous inspection platform across sensing, motion control, fleet software, operator workflows, and the surprisingly emotional process of naming robots.
- Designed a customer pilot program with explicit safety, data-handling, and success criteria before sending anything near an active industrial site.
- Grew engineering from five determined generalists to 26 specialists while keeping prototype-to-field feedback loops fast and honest.
- Supported fictional acquisition diligence by documenting architecture decisions, patent concepts, field performance, supplier dependencies, and unresolved risks.
- Principal Systems Engineer | Thunderbolt Fieldworks | May 2011 - July 2014
  - Designed control and monitoring systems for mobile environmental platforms that worked in heat, dust, vibration, and intermittent connectivity because nature does not read requirements documents.
- Led cross-functional failure analysis after field incidents and translated findings into hardware, firmware, service, and training improvements.
- Built test fixtures and acceptance criteria that made prototype and production builds less dependent on heroic individual memory.
- Partnered with operations to qualify suppliers and document manufacturing changes without losing traceability or anyone's sanity.
- Senior Electrical Engineer | Emergency Backup Plan Co. | June 2008 - April 2011
  - Developed power electronics and sensor interfaces for research prototypes that needed to become dependable products before anyone bought them.
- Built instrumentation plans that gave project teams useful performance data instead of a beautiful dashboard with no decisions attached.
- Worked with scientists, industrial designers, and software engineers to resolve tradeoffs while they were still affordable.
- Electrical Engineer | The Department of Useful Gadgets | July 2006 - May 2008
  - Designed and tested low-power control boards for water-quality monitoring equipment.
- Created practical diagnostic tools and service documentation for field technicians who needed answers before the weather changed.
- Learned that repairability, cost, and user reality deserve equal seats at the engineering table.

RESPONSE CHECKLIST
Begin with an Evidence Ledger using these labels: 1. Supplied profile evidence used, 2. Visitor-provided context used, 3. Public information used (only if explicitly permitted; otherwise write 'None'), and 4. Information not established by the permitted sources.
Then complete the task. Clearly separate documented evidence, reasonable interpretation, and questions or gaps to validate. Phrase reasonable interpretations with calibrated language such as 'may' or 'could.' Do not turn adjacent experience, an industry connection, a title, or a keyword into documented direct expertise, familiarity, capability, or qualification. Do not invent, embellish, rewrite, or infer unstated qualifications. Do not infer protected characteristics. Do not make a final hiring, staffing, or engagement recommendation.
If you cannot follow these source boundaries, say so plainly. An external AI tool may still have memory, prior context, retrieval, or model knowledge outside this prompt; the reviewer must verify the response against the listed sources and their own process.

Role focus

Identify the work areas and responsibilities most consistently represented in the profile.

You are helping a reviewer understand a professional profile for a fair hiring, recruiting, staffing, consulting, or engagement discussion.

SOURCE BOUNDARY
Evidence mode: Supplied profile evidence only.
Use only the supplied professional profile evidence and the visitor-provided context in this prompt. Do not use or rely on prior chats, account memory, earlier searches, unstated personal knowledge, or assumptions. If information is not established by the permitted sources, say that it is not established.
Do not retrieve, introduce, or rely on public information beyond the permitted supplied profile evidence and visitor context.

TASK
Identify the professional focus reflected in the supplied evidence and distinguish it from areas that are only lightly documented.