Career Dashboard
- Current Target Role: Solutions Engineer (FinTech / Enterprise SaaS)
- Original Time-to-Hire Estimate: 90–120 days
- Current Time-to-Hire Estimate: 100–120 days (Adjusted upward due to market feedback)
- Confidence Level: Medium
- Remaining Skill Gaps: AWS Serverless ecosystem (Lambda/API Gateway), formal System Design interview frameworks, mock presentation delivery.
Today’s Objective
Gather qualitative feedback on my new resume and target market positioning through an informational interview with an active industry contact.
What I Worked On
I had a 45-minute virtual coffee chat with a former colleague who currently works as a Principal Solutions Architect at a mid-sized enterprise SaaS vendor. I also submitted my first batch of 5 highly tailored applications to local and remote Solutions Engineer positions to test my new resume layout against the market.
What I Learned
The informational interview provided crucial, unvarnished feedback on my strategy:
- The Good: My friend confirmed that my combination of development experience and Product Owner experience is highly attractive for Solutions Engineering. It means I can talk to developers without losing technical credibility while understanding business constraints.
- The Bad (The “Generalist” Penalty): He pointed out a major flaw in my resume presentation. While my bullet points were strong, the overall layout still looked like I was undecided between being a Dev, a Support Lead, or a Product Owner. He noted: “If an hiring manager thinks you actually want to be a software engineer and are just using SE as a fallback, they will skip you.”
- The Actionable Fix: I need to explicitly label my project sections to highlight the cross-functional communication, solution design, and customer proof-of-concepts I delivered, rather than focusing on the code execution.
Skills Acquired
- AWS Compute & High-Availability Database Scaling (EC2, Autoscaling, RDS):
- What it is: Deploying Elastic Compute Cloud (EC2) instances behind Application Load Balancers (ALBs), setting up Auto Scaling Groups, and configuring Relational Database Service (RDS) multi-AZ deployments for failover.
- Why I decided to learn: This forms the baseline deployment blueprint for almost every B2B SaaS application. As an SE, I must confidently explain to a client’s engineering team how our product ensures uptime and handles traffic spikes.
- Further delve required?: Yes, specifically how serverless computing (AWS Lambda) interacts with these relational databases, as modern SaaS leans heavily on serverless integrations.
- Material used: Ultimate AWS Certified Solutions Architect Associate by Stephane Maarek (Udemy) and official AWS Architecture Icons documentation for design mapping.
- Technical Stakeholder Translation:
- What it is: The communication framework of converting deep technical constraints (e.g., database latencies or system downtime) into executive business impacts (e.g., revenue loss, customer churn, or compliance risks).
- Why I decided to learn: My informational interview revealed that hiring managers reject pure developers who over-index on the “how” of code rather than the “why” of the business.
- Further delve required?: Absolutely. This requires active practice. I need to record myself delivering mock architecture pitches to eliminate engineering jargon when speaking to “buyer” personas.
- Material used: Direct critique and real-world scenario coaching from my industry contact (Principal SA at an Enterprise SaaS vendor).
Market Observations
Internal referral pipelines are currently the only reliable way to bypass the initial ATS screen in 2026. Blind applications have a single-digit response rate right now because companies are flooded with volume.
Resources Reviewed
(Logged in Skills Acquired above)
Progress Against Plan
Slightly behind. I am adjusting my time-to-hire estimate upward slightly. While my skills are there, the friction of the market and the necessity of focusing on networking over raw application volume means things will move slower than initially hoped.
Strategy Changes
- Adjustment: I am modifying my resume one more time based on today’s feedback to aggressively strip out pure development language and replace it with architectural design, integration work, and stakeholder alignment terms.
Next Steps
Refine the resume according to the feedback, finish the final blocks of the AWS certification preparation, and start mapping out 10 new network contacts for informational outreach.
Reflection
It was a bit deflating to hear that my resume still wasn’t quite hitting the mark, despite the hours I poured into it on Day 7. But this is exactly why we run the experiment. I’d rather discover this flaw through a friend over coffee on Day 10 than after 50 silent rejections on Day 40. This is a marathon, and the recalibration keeps me in the race.
