Back to jobs

Senior Principal Java Software Engineer - Ciklum

HelpwareRemote (Argentina, Brazil, Mexico)Posted 1d ago
Senior Software Engineer
Full Time
Remote
Craft my tailored resume free

Free to start · No card

Job description

Principal Software Engineer

Key Responsibilities: 

Own architecture across product and platform 

Define and evolve platform and application architecture, including service boundaries, integration patterns, data modeling, and API standards. 

Lead architecture reviews and influence roadmaps to balance near-term delivery with long-term simplicity, maintainability, and performance. 

Identify systemic product/platform opportunities (simplification, modularization, shared services) and drive cross-team execution. 

Introduce new technologies and best practices 

Evaluate and introduce new technologies responsibly pilot, measure outcomes, document learnings, and scale adoption where valuable. 

Establish best practices in design, testing, secure coding, CI/CD, and production readiness; create reference implementations and templates. 

Raise engineering quality through clarity: design docs, decision records, coding standards, and measurable technical KPIs. 

Solve the hardest cross-team problems 

Partner across teams to unblock complex initiatives: modernization, major refactors, performance tuning, data migrations, and distributed systems challenges. 

Drive alignment across stakeholders making tradeoffs explicit and decisions durable. 

Help teams debug and resolve high-severity production issues; codify learnings into better patterns and guardrails. 

 

Global cloud and regulated environment leadership 

Guide architecture for global cloud deployments (multi-region strategy, DR, availability, and operability). 

Support FedRAMP/government cloud certification readiness by shaping technical controls implementation plans with Security/Compliance. 

Mentor and coach across the organization 

Mentor engineers across teams; coach technical leads on design quality, execution, and engineering judgment. 

Build learning mechanisms: architecture guilds, tech talks, post-incident reviews, and hands-on design workshops. 

 

About You:

Technical breadth (multi-stack) 

Ten years of overall experience, with at least five years as a Staff or Principal engineer at B2B SaaS startups 

Strong working knowledge across: Java/J2EE, Oracle, Postgres, AWS, GCP, Azure, and modern frontend frameworks (React, Vue.js). 

Ability to move between systems-level architecture and hands-on problem solving, deep where needed, broad by default. 

Experience building and operating modern B2B SaaS applications with strong engineering fundamentals. 

Architecture leadership 

Proven success setting architectural direction across multiple teams and making durable technical decisions. 

Strong systems design skills: scalability, reliability, performance, data consistency, and operational maturity. 

Ability to drive alignment, influence roadmaps, and lead through ambiguity with pragmatic tradeoffs. 

Global cloud + FedRAMP experience 

Experience with global cloud systems and production operations at scale (multi-region deployments, DR/BCP, observability). 

Experience supporting FedRAMP/government cloud certification and/or comparable regulated environments. 

Mentorship and communication 

Strong written and verbal communication; able to author clear design docs and influence across engineering, product, and leadership. 

Track record of mentoring and coaching engineers across teams, improving quality and raising the technic al bar. 

 

Education:

A bachelor's degree in computer science or a related field

Master's degree preferred

 

Nice to Have 

Experience designing shared services (identity/auth, platform APIs) and driving adoption through developer experience improvements. 

Experience with Kubernetes, service meshes, and platform tooling that improves developer productivity. 

Experience leading large-scale modernization of legacy Java/J2EE systems. 

Experience in commercial real estate software 

Originally posted on Himalayas

Prepare your application

Use the description above to assess your fit for Helpware. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.

Match requirements to evidence

Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.

Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.

Check the working arrangement

Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.

Review before submitting

Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.

Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.

Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.