Edge ML / Embedded Engineer

<p><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;"><strong>Data Ideology</strong></span></span></p><p><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">At DI, we provide Data & Analytics expertise to drive measurable business outcomes, often solving complex business problems for our clients. Our data analytics advisory services enable our customers to transform data into insights by driving a culture of empowerment and ownership of results. Our team consists of highly motivated individuals passionate about learning, understanding, collaborating, and intellectually curious.  For more information about Data Ideology, visit <a href="http://www.dataideology.com/">www.dataideology.com</a> </span></span></p><p>Edge ML / Embedded Engineer<span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;"><span style="line-height:115%;"><b>- </b></span><strong>(Contract 1099)</strong></span></span></p><p>We are seeking a specialized Edge ML / Embedded Engineer to join our team on a contract engagement at the intersection of constrained hardware and on-device machine learning. This is a discovery, architecture, and feasibility engagement — the primary output is a validated technical architecture and a constrained proof-of-concept demonstrator that shows the core concept works, not a production system. The right candidate thrives in ambiguous early-stage technical work, is energized by the challenge of making AI run on hardware that was never designed for it, and produces clear written findings when the answer is ‘it depends on specs we don’t have yet.’ For more information about Data Ideology, visit www.dataideology.com </p><p>Key Responsibilities </p><ul><li><p>Assess target edge hardware against the requirements of an on-device inference loop: evaluate processor architecture, available memory, OS and runtime environment, and whether candidate edge runtimes (such as IoT Greengrass or equivalent) can be supported. </p></li></ul><ul><li><p>Evaluate candidate edge inference frameworks for CPU-only SLM deployment — including TensorFlow Lite, ONNX Runtime, llama.cpp, and equivalents — assessing quantization approaches, inference latency, and memory footprint against feasibility targets confirmed during discovery. </p></li></ul><ul><li><p>Assess real-time data ingestion feasibility from operational subsystem interfaces, evaluating candidate patterns for consuming concurrent data streams within the memory and compute constraints of the target hardware. </p></li></ul><ul><li><p>Design and evaluate local data store options for the on-device SLM context, including storage formats, retrieval latency, and update mechanisms appropriate for the edge environment. </p></li></ul><ul><li><p>Build a constrained feasibility demonstrator on laptop or workstation hardware using simulated data feeds. The demonstrator validates the interaction model and core architectural approach — it is not a production prototype and does not connect to operational systems. </p></li></ul><ul><li><p>Implement a small number of scoped interaction flows in the demonstrator, integrating the voice interface pipeline with the SLM inference and local data retrieval components as agreed through the engagement scope. </p></li></ul><ul><li><p>Collaborate with the AI/ML Architect on SLM selection, domain restriction approach, and inference pipeline design — providing hardware and runtime constraint inputs that shape what is architecturally feasible. </p></li></ul><ul><li><p>Collaborate with the AWS Solutions Architect on the edge-to-cloud data channel, identifying what can realistically be buffered and transmitted from a constrained edge device under variable connectivity conditions. </p></li></ul><ul><li><p>Document hardware assessment findings, framework evaluations, and architectural trade-offs as Architecture Decision Records (ADRs) with explicit rationale. Clearly flag where recommendations are conditional on hardware or interface specifications not yet confirmed. </p></li></ul><ul><li><p>Communicate technical constraints and feasibility findings clearly to both technical architects and non-technical client stakeholders throughout the engagement. </p></li></ul><p>Supervisory Responsibilities: None </p><p>Qualifications </p><p>Education and Experience: </p><ul><li><p>Bachelor’s degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent professional experience in embedded systems or edge computing. </p></li></ul><ul><li><p>5+ years of hands-on experience in embedded systems engineering, edge computing, or on-device machine learning, with demonstrated work on constrained hardware environments. </p></li></ul><ul><li><p>Expert-level proficiency with at least one edge ML inference framework: TensorFlow Lite, ONNX Runtime, llama.cpp, or equivalent. Experience optimizing and quantizing models for CPU-only inference is required. </p></li></ul><ul><li><p>Strong understanding of memory management, real-time data stream handling, and concurrent processing in resource-constrained environments. Experience with C++, Rust, or Python with tight memory management is strongly preferred. </p></li></ul><ul><li><p>Experience with embedded Linux or equivalent OS environments, including ARM-based processors, limited RAM, and environments without GPU availability. </p></li></ul><ul><li><p>Familiarity with real-time data ingestion from hardware interfaces or industrial systems — including serial protocols, message bus architectures, or event-driven pipelines at the edge. </p></li></ul><ul><li><p>AWS familiarity preferred, specifically IoT Greengrass as a candidate edge runtime and IoT Core for device-to-cloud connectivity. Hands-on implementation experience is not required but direct familiarity strengthens the candidate’s ability to evaluate candidate architectures. </p></li></ul><ul><li><p>Experience with voice-to-text or text-to-speech pipelines in offline or low-connectivity environments is a plus. </p></li></ul><ul><li><p>Comfortable operating in a Phase 0 discovery and feasibility mode — producing assessment findings, ADRs, and a constrained demonstrator rather than production-ready software. </p></li></ul><ul><li><p>Strong written communication skills with the ability to document hardware constraint findings, framework evaluations, and architectural trade-offs in formats usable by both technical architects and client stakeholders. </p></li></ul><ul><li><p>Experience working in consulting or client-facing project environments is preferred. </p></li></ul><p>If you are an embedded systems or edge ML engineer who is energized by early-stage technical discovery work — evaluating what is feasible before committing to what will be built — and you bring deep hands-on experience making AI work on hardware that was never designed for it, we invite you to apply. </p><p><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">Work Environment: </span></span></p><ul><li><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">Remote work from home. </span></span></li><li><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">Hours of work and days are generally Monday through Friday. Specific business hours will depend on client needs. </span></span></li></ul><p><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">Physical Demands: </span></span></p><ul><li><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">Must be able to remain in a stationary position 50% of the time. </span></span></li><li><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">The person in this position must occasionally move about inside the office to access file cabinets, library stacks, office machinery, etc. </span></span></li><li><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">Constantly operates a computer and other office productivity machinery, such as a calculator, copy machine, and printer. </span></span></li><li><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">The person in this position frequently communicates with clients and coworkers. Must be able to exchange accurate information in these situations. </span></span></li></ul><p><span style="font-size:14px;"><span style="font-family:Arial, Helvetica, sans-serif;">Data Ideology is an EEO Employer</span></span><br><br> </p>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...