Contact
Let’s talk about systems, data, and the work that needs to get done.
Open to data analytics, data engineering, automation, BI, dashboarding, operational intelligence, and technical project conversations.
The best conversations start with a clear business problem: a manual process, a messy data source, a reporting gap, or an operational workflow that needs to become more reliable.
Start here
Send the context. I’ll connect the problem to the right kind of system.
Whether the conversation is about a role, a project, or a technical build, the goal is the same: understand the workflow, identify the data friction, and figure out what kind of system would create the most value.
omnidatajay28@gmail.com
Best for direct opportunities, project conversations, and follow-up.
Connect professionally
Best for recruiters, hiring managers, networking, and role conversations.
GitHub
Review public work
Best for viewing repositories, project structure, and technical build history.
Availability
Professional opportunities and focused build conversations.
Roles
Analytics, data engineering, BI, automation
Location
Remote / hybrid-friendly conversations
Best fit
Operational data systems and decision-support work
Best-fit conversations
The strongest fit is where data meets execution.
These are the kinds of conversations that match the work shown across Lopez Data Works.
Data analytics & BI roles
Power BI, DAX, SQL reporting, KPI dashboards, semantic models, operational analytics, and executive-ready reporting.
Data engineering & automation
Python pipelines, API extraction, SQL loading, workflow automation, file processing, and audit-ready operational systems.
Portfolio / project discussions
Conversations around the systems in this portfolio, how they were built, and how similar work could apply to another environment.
Consulting-style problem solving
If the problem involves messy files, repeated manual work, disconnected tools, or decision-making gaps, it is probably worth discussing.
What to send
Helpful details make the conversation faster.
Include the role, project, or problem you want to discuss.
Share the business context and the type of data or workflow involved.
Mention whether the need is analytics, engineering, automation, BI, or app/API work.
For opportunities, include location, remote/hybrid expectations, and timeline.
Professional note
This portfolio is intentionally built around proof of work.
If you are reviewing this site for a role, project, or technical conversation, the case studies show how I think through real systems: the business problem, the architecture, the automation logic, the reporting layer, and the operational value.
Reach out when the conversation needs someone who can bridge business process, data engineering, analytics, and execution.
Privacy and confidentiality
Please avoid sending private credentials, customer records, confidential exports, or sensitive business data through an initial contact message. A high-level description of the problem is enough to start the conversation.