In a moment of Self Celebration/Ego, I asked ChatGPT to tell me about me based on projects that I have worked on and public sources. I take pride in what I have done, and frankly like what it had to say…
I dug through your blog, public LinkedIn snippets, patent records, press coverage, and a few third-party profiles. The clearest signal is that your public body of work is much broader than the headline projects people would normally associate with you. It is not just “embedded systems” in the generic sense. It is a long arc of platform-building across language computing, handhelds, defense tech, industrial wearables, AR, mobile infra-red, and low-level systems software.
The short version of my read: you are publicly legible as a systems architect who repeatedly entered categories before they were fashionable. In the 1990s that meant Indian-language computing, Windows internals, telephony, and anti-virus. In the early 2000s it meant Linux handhelds, battlefield digitization, and open-device platforms. In the 2010s it meant smartphone IR at massive OEM scale. In the 2020s it meant industrial assisted reality and enterprise AR wearables. That pattern shows up consistently across your blog, resume material, and outside mentions.
Here is the deeper analysis.
Your portfolio has three distinct eras
Era 1: low-level PC systems and Indian software infrastructure.
Before the projects most people would immediately name, your public record shows work on anti-virus systems, hardware-assisted anti-virus, on-line disk compression, device drivers, Windows internals, frame grabbers, PC telephony, and multilingual editing. Your 2024 career retrospective and resume explicitly describe Protector Plus anti-virus work, hardware add-on anti-virus protection, disk compression, Windows VxDs, and telephony software.
Era 2: handhelds, military systems, and early embedded Linux products.
This is where Simputer, SATHI, and related projects sit. Publicly, this is the phase where you look less like a programmer and more like a product/system owner working from concept through production, field validation, and platform software. Your own retrospective says you were responsible for multiple product lines at Encore and specifically “designed and built Encore’s VoIP Product Suite, Simputer, Chhota, SATHI.”
Era 3: volume productization and industrial wearables.
This includes Peel Smart Remote / SmartIR, then RealWear, then DigiLens. Publicly this era shows the same systems pattern, just at bigger commercial scale: patents, OEM integration, cloud/data infrastructure, and rugged enterprise hardware. Your resume and blog tie you directly to SmartIR / NoChip, then later to industrial head-mounted computing and AR-oriented device leadership.
Some significant projects
Kairali multilingual editing system
This is one of the most important “hidden” projects in your public history because it shows a very early instinct for solving real adoption bottlenecks, not just writing code. In your 2024 retrospective, you describe Kairali as a 1994 product that let users edit Hindi, Telugu, Malayalam, Tamil, and Kannada inside tools like PageMaker and Microsoft Word, despite the limitations of Windows 3.1’s 256-character font model. You say the solution “cut” and “stitched” characters so the languages would render and input correctly, and that the approach remained robust through Windows 2000. That is not just localization work; it is foundational text systems engineering for Indian-language publishing.
My read: Kairali matters because it reveals a recurring trait in your work. You repeatedly go after the missing substrate that prevents broader adoption. In this case the substrate was language tooling, not the application itself. Later, SmartIR follows the same pattern: remove the hidden cost/complexity layer so distribution can explode.
Simputer
Publicly, Simputer is one of the projects that most strongly marks you as early to an important idea. Your retrospective says you were the product manager for the Simputer, a low-cost Linux handheld, and that your work covered specification, hardware build, Linux porting, GUI environment, device drivers, and production. It also says the device eventually hosted GNU/Linux, Embedix, and Windows CE environments. An outside Rediff profile quotes you describing the feature set: smart card reader, USB host, modem, GSM/CDMA data, GPS, and substantial compute for the time.
My read: the public record makes Simputer look less like a one-off gadget and more like your first major expression of a theme you would revisit for decades: portable, rugged, task-oriented computing for constrained or specialized users. Simputer, SATHI, Chhota, RealWear, and ARGO all rhyme.
SATHI / BAAZ
This project has the strongest “vision ahead of its time” aura in your public footprint. Your blog says SATHI stood for Situational Awareness and Tactical Handheld Information, launched in 2004, and was earlier called BAAZ. You describe it as a rugged handheld with GPS and long-range radio intended to give soldiers shared battlefield visibility. Your retrospective says it was designed at the request of the Indian Army and demonstrated to President A. P. J. Abdul Kalam. Independent press coverage in 2005 described the Army deploying open-source-based Sathi, while a 2019 account explained that the Project Beta system provided GPS-based blue-force awareness, encrypted communications, and mesh-like relay behavior, but was later shelved.
What stood out most to me was not just the concept, but the blog post about the failure before the demo: devices dropping GPS-position transmission because of randomized RF backoff behavior. That story tells the public more about you than a polished product announcement ever could. It shows a leader operating at the level where product management, field reliability, protocol behavior, and emotional ownership all meet.
Ultrasound Robotic Scanning System
Your blog and resume make this a clear anchor project. You describe a robotic ultrasound scanning system used to inspect the composite wing skin of a fighter aircraft, and the resume says you wrote control software to ultrasonically scan an aircraft wing for manufacturing defects.
My read: this is one of the clearest examples that your career was never only consumer/mobile. It shows comfort with robotics, test/inspection, motion/control, and safety-critical industrial workflows. It also foreshadows later industrial wearables work because both domains care about hands-free operation, reliability, and task execution in unforgiving environments.
Peel Smart Remote and SmartIR
This is likely your most commercially scaled public achievement. Your 2024 SmartIR write-up says the technology eliminated the need for a dedicated microcontroller, using the main processor, SPI, and DMA to generate IR output, and that Peel Smart Remote plus SmartIR shipped in 650+ million phones. Your resume says SmartIR/NoChip dropped the cost of adding IR from over $1 to under 15 cents on a flagship device, with savings of over $40 million on one phone. Patent records show you as inventor on US9342475B2, “Generating infrared communications on a mobile device,” assigned to Peel, with publication in 2016. Your public materials also mention a related “FlashIR” module strategy and an IP-remote strategy for phones without IR hardware.
This is where your profile turns from “strong engineer” to “platform leverage architect.” The technical idea matters, but the real achievement was turning a hardware feature into something cheap enough to become default OEM behavior. Publicly, that is the hallmark of someone who understands both circuitry and business adoption mechanics.
RealWear Navigator 5xx and Z1
Publicly I could verify your association with RealWear through your own LinkedIn post, your resume, and your Google Scholar profile snippet that lists you as “VP of Engineering at RealWear.” Your LinkedIn post celebrated the launch of RealWear Navigator 500 in December 2021. Official RealWear pages describe the Navigator 500 line as hands-free industrial smart glasses for remote collaboration, digital workflows, and IoT visualization; the 520 page adds improved collaboration, AI-assistant positioning, and rugged frontline use; the Z1 pages position the device as intrinsically safe and oil-and-gas oriented.
My read: even where the public record doesn’t explicitly list your contribution device-by-device, the career continuity is obvious. Simputer and SATHI were early portable task machines; RealWear is the mature industrial form of that idea: wearable, voice-driven, field-centric computing.
DigiLens ARGO
Publicly, ARGO is now a major node in your profile. DigiLens’ official site describes ARGO as a rugged, all-in-one, “true AR and AI powered” smartglasses platform for enterprise/industrial workers, and the 2023 introduction positioned it as DigiLens’ first mass-market product. Later public DigiLens materials show ARGO as the center of an ecosystem strategy, including DigiSaaS and AI-partner integrations. Third-party coverage also described ARGO entering mass production.
My read: if Peel Smart Remote is your scale story, ARGO is your culmination story. It combines many threads from your history: embedded systems, rugged hardware, human factors, optics/display-driven usability, enterprise deployment, and the conviction that specialized compute devices should fit into real work rather than demand users adapt to them.
The “surprise me” section: projects you have talked about less, but that matter
These are the ones that stood out as under-discussed and genuinely revealing.
Chhota.
Your retrospective says Chhota was a microcontroller-based device for high-volume, low-cost use cases like bus ticketing, billing, and security systems, with an integrated printer, smartcard reader, RTC, and 40+ hour battery life. This is a very important clue: you were thinking not just about flagship devices, but about operational edge devices for transactional workflows long before that became a common product category.
Encore’s VoIP stack work.
Your public materials mention H.323, MGCP, SIP user agent stacks, T.38 fax support, ASN.1 code generation, multichannel gateways, and deployment into IP phones and residential gateways. This is substantial infrastructure work, not just application coding. It suggests that one of your hidden strengths is protocol and middleware architecture.
Medical transcription foot-pedal system.
This is maybe the most charming and revealing project in your archive. Your blog describes a 1995 two-week build: industrial push buttons on a footplate wired into the joystick port, plus Delphi software that attached to the foreground application, letting transcriptionists play/pause/rewind without leaving the keyboard. It sold for years and improved productivity directly.
Why it matters: this is a pure example of your product instinct. It is not glamorous, but it is elegant, pragmatic, and tightly coupled to user pain. In many ways it is a better illustration of your engineering taste than a flashy AR product.
CoreFone telephony software.
Your retrospective describes an integrated Windows telephony app combining address book, answering machine, data terminal, and fax, with TAPI driver development for a voice/fax modem. This sits at the intersection of UI, systems software, and comms stacks.
Windows display driver for a frame grabber card.
You publicly describe building a 4/8/16/24-bit display driver for a frame-grabber card that also functioned as VGA output, including picture-in-picture motion display. That is niche, hard, systems-heavy work, and it reinforces the point that your career foundation is at the driver/OS boundary, not only in product management.
Disk compression and Windows anti-virus internals.
Your public materials describe on-line disk compression software, Windows anti-virus protection mechanisms, an add-on-card debugger, and virus-detection systems using wildcard scanning for self-modifying viruses. These are not trivial footnotes; they suggest deep familiarity with low-level control, boot-time constraints, and hostile environments.
OMAP reference designs and ecosystem work.
Your retrospective says you helped Mistral become a strategic supplier for the OMAP3 EVM and that the company announced early ARM Cortex-A8 support. TI material also lists Samyeer Metrani / Mistral as part of TI’s design-network ecosystem. Your own retrospective describes building a phone-sized reference design with WLAN, GPS, GSM/GPRS, FM, Bluetooth, hard disk, camera, display, and BSP work.
Why it matters: this is ecosystem leverage again. You were not only building products; you were helping shape the reference platforms other products would be built from.
Kopin Golden-I, Motorola HMC, ODG SmartGlasses, Taser Axon, airline seatback systems.
These appear in your public resume materials as customer designs or programs connected to your Mistral period. That is a remarkable set because it spans head-mounted computing, body cameras, transport entertainment, and rugged industrial/consumer crossover systems.
Taken together, these “side projects” suggest that your less visible superpower is not one product category. It is the ability to work on new device categories before the market vocabulary fully stabilizes.
What the internet says your career pattern really is
The surface version is “engineering leader.” The deeper version is more specific.
You repeatedly show up where there is a hard boundary between:
- hardware and software,
- lab prototype and manufacturable product,
- standalone device and ecosystem/platform,
- visionary concept and field deployment.
That is why your public work can look unusually eclectic. It is not random. The common thread is instrumented, purpose-built computing in constrained environments. Kairali solved language-computing constraints. Simputer solved cost and portability. SATHI solved field awareness. The ultrasound scanner solved manufacturing inspection. SmartIR solved BOM cost and integration friction. RealWear and ARGO solve hands-free industrial cognition.
If I had to characterize your public reputation in one sentence
You look like a product-and-systems engineer who keeps building the enabling layer that turns ambitious device ideas into deployable reality.
A few specific things that surprised me
I did not expect your public trail to show this much depth in Indian language computing that early. Kairali is historically interesting, not just personally interesting.
I did not expect the medical transcription foot pedal to be such a perfect miniature of your design philosophy. It is one of the best public windows into how you think.
I also did not expect the amount of protocol/stack work in VoIP and telephony. That makes your later hardware leadership make more sense, because it suggests your base layer was always systems architecture rather than only device packaging.
And the biggest surprise was how coherent the line is from Simputer → SATHI → RealWear → ARGO. They look like different industries, but publicly they read as variations of the same long-term thesis about human-computer interaction in the field.
Samyeer Metrani 