About

I joined the founder as a co-founder and helped build the group from the ground up. For our Women’s Day conferences I coordinated about 10–15 volunteers and organizers. We ran a two-day conference with UT Tyler and other local women’s groups and raised around $5,000 (approximate).

More on Embark Women →

My co-founders and I made the events and the place for women in business to meet, learn, and find coaching. We ran business-building, brainstorming, and website-building workshops for small business owners and new entrepreneurs, and brought in community members who knew those topics. I organized access to coaching. I wasn’t the coach for all of it.

One-on-one sessions walking engineers through bugs they’d been stuck on, sometimes for days. I asked the obvious questions and had them treat me like a rubber duck that talks back. Sometimes a bug they’d fought for days got worked through in about twenty minutes. That happened sometimes. It’s not an average.

More on Zero-Gravity Thinker →

Merge requests were taking too long and people kept missing steps, like testing the code, checking the wording, or leaving specific comments. I found a checklist and adapted it into one place to check testing and review steps, for both preparing and reviewing merge requests. I took it to the CTO, who adopted it, and all engineers used it. The company has kept updating it for about five years. I saw merges go from weeks to days through fewer missed checks and less rework. That is what I observed, not a formally measured average.

• Debugged ESP32 firmware across error codes, serial port failures, and network-formation bugs, including a join-ordering bug fixed while working with Nordic hardware and the OpenThread stack.
• Configured and tested wireless IoT chips (ESP32, SiLabs, Nordic) for hardware validation, and flashed and provisioned devices across a 1,000+ node deployment and for partner demo kits.
• Wrote unit and firmware tests for embedded C, including checks that Python prototypes and their embedded C ports behave the same on target hardware.
• Contributed to the core sensor-detection algorithm and checked it behaves consistently across several chip platforms and operating systems (using virtual machines). Detailed performance results are confidential.
• Contributed to the ground-truth data collection pipeline: systemd services, Python (pandas, SciPy), InfluxDB, and Kafka.
• Ran technology trade studies and competitor evaluations before the team committed to a direction, and tested new microcontrollers as they arrived, including at-home Raspberry Pi setups for real-world usage data.
• Drew the algorithm and architecture diagrams (draw.io) that explained the design to the rest of the team.

• Took seven product concepts from loosely defined stakeholder needs to interactive prototypes in three weeks, using structured specs and a 19-check quality process, then presented them to company leadership and iterated on feedback.
• Found the code-level ordering bug behind a recurring field escalation for a partner deployment by testing motion triggers on site, then fixed it.
• Checked AI-generated guidance for embedded SDK work (Zigbee broadcast and signal-strength APIs) against verified documentation, using local models, before the team relied on it.
• Read internal and external docs end to end as a first-time user to catch gaps before customers or new hires did.

• Ran a cross-team engineering guidance program for 4+ years, with monthly focus themes and one-on-one rubber-ducking sessions supporting 5+ engineers outside formal reporting lines. Asking naive, outside-perspective questions often unstuck bugs people had been fighting for days.
• Wrote the team’s standard troubleshooting checklist for a recurring configuration bug.

• Content planning, analytics, and writing: blog posts, social posts, and the review workflow that routed drafts for approval by risk level (technical accuracy, product claims, IP sensitivity).
• Built videos and graphics (Canva), and proposed new content formats for the team to try.
• Coordinated day to day with the marketing co-lead on what to publish and when.
• Recommended positioning, content strategy, and market alignment based on competitor analysis and monthly and quarterly reviews of impressions, follower growth, engagement, website analytics, and demo inquiries.
• Worked with the CEO, CTO, and marketing co-lead to shape the company's voice (open, honest, approachable, occasionally snarky) and to translate RF-sensing, Thread, and 802.15.4 concepts into B2B messaging for technical, executive, partner, and non-technical readers.
• Specced and iterated a six-variant Sensify scrollytelling demo through rounds of C-suite feedback, reframing it around what partners needed to understand.
• Owned GA4 and OKR reporting from 2024: monthly audits plus quarterly and annual reports used to set content priorities.
• Drafted the Sensify OEM integration whitepaper and designed a seven-piece one-pager library for OEM product managers.
• Wrote three scenario-based visitor personas and a demo playbook for CES 2023 booth conversations. These were internal planning material, not customer research.

• Built the publishing system that the co-lead and I operated together, moving posting from little and irregular to roughly twice a week.
• Ivani's LinkedIn company page grew organically from about 1,000 to over 1,300 followers over about four years.
• The marketing work contributed to roughly 10 demo inquiries over about four years, tracked through LinkedIn messages, website contact forms, and prospects who mentioned the content directly.
• No paid advertising: free tools plus a paid Canva subscription.

• Wrote a multi-threaded Ruby tool that flashed firmware onto 400+ microcontroller boards remotely and at the same time, cutting deployment time and customer downtime.
• Debugged and fixed software issues in variable-speed drives (C/C++). Wrote failure scenarios and tested updates against them before they reached customers, because finding a problem in the lab beats finding it in the field.
• Designed and built embedded electrical systems that supported multiple microcontroller boards, with hands-on soldering and on-site debugging alongside field teams.