01
Systems analysis
Map the people, process, data, constraints, and decision points before choosing a technical answer.
Technical Consultant | Systems Analyst | Business Systems Analyst
I connect business context to requirements, data rules, implementation details, and practical documentation so the next decision is easier to understand and support.
Capabilities
I work across the boundaries between business analysis, implementation detail, technical validation, and operational handoff.
01
Map the people, process, data, constraints, and decision points before choosing a technical answer.
02
Turn ambiguity into explicit rules, scenarios, acceptance criteria, and implementation-ready definitions.
03
Preserve source meaning, route exceptions honestly, query controlled data, and reconcile reported results.
04
Connect decisions to work, tests, corrections, and documentation that technical and business readers can use.
Selected work
Together, the projects show how I move from workflow and data analysis, to implementation readiness, to integration reliability and troubleshooting.
Turn inconsistent intake into validated and review-required outputs without hiding uncertainty.
Focus: workflow analysis, data rules, Python and SQL processing, API contracts, testing, and traceability.
Connect a platform-neutral readiness model with a Jira and Confluence implementation covering requirements, dependencies, UAT, Bug correction, rollback, and handoff.
Focus: implementation judgment, Jira workflow design, validation, readiness decisions, and operational transition.
Exercise source-to-target contracts, mapping, idempotency, ordering, retries, dead letter, replay, reconciliation, and incident response.
Focus: executable integration reliability, structured diagnostics, recovery, and troubleshooting.
How I work
I treat analysis as a chain: the business question shapes the rule, the rule shapes the implementation, and the result shows whether the approach holds.
Identify the people, process, systems, source authority, constraints, and decision boundary.
Translate ambiguity into requirements, data rules, mappings, assumptions, and acceptance criteria.
Preserve exceptions, reconcile outputs, and distinguish supported facts from values that still need judgment.
Document the reasoning and decisions so another person can review, implement, or support the work.
Professional background
My background combines independent technical analysis with regulated business operations and years of client-facing problem solving. I translate that experience into requirements, data rules, technical documentation, and handoffs that business and technical teams can use.
That experience shapes how I work: clarify what a rule means, account for exceptions, document the decision, and leave the next person with something usable.
Tools and methods
The projects connect analysis to Python, SQLite, SQL, APIs, Jira, Confluence, structured tests, reconciliation, and support documentation.
Background
My education combines a business foundation with hands-on technical training that supports work across systems, workflows, data quality, and technical problem solving.
Business foundation
Associate of Arts with Business Designation, 2015
Technical training
Cybersecurity Boot Camp, 240-hour completed program, 2022
Coursework
Additional coursework at Colorado State University and the University of Northern Colorado
Review my work on GitHub or connect with me on LinkedIn.