Meet the HighAppler Team: Senior Engineers and QA in Bulgaria

A dedicated team of senior developers and QA engineers with 50+ years of collective experience building enterprise software.

Meet the People Behind HighAppler

We are a tight-knit team of senior engineers and QA specialists based in Bulgaria, serving companies in the United States. With over 50 years of collective experience in Java, Angular, iOS, Android, and quality assurance, we bring deep expertise to every project.

VG

Vladimir Gichev

Founder & Senior Java Backend Developer

10+ years experience
JavaSpring BootREST APIsMicroservicesCI/CDAWSDockerMavenPostgreSQLRedisKubernetesJenkinsSoftware Architecture
LinkedIn
KZ

Krasimira Zarankova

Senior Frontend Developer

15+ years experience
AngularTypeScriptJavaScriptRxJSHTML/CSSSASSBootstrapAngular MaterialNgRxResponsive DesignREST APIsGit
LinkedIn
SB

Stefan Boychev

Senior iOS Developer

10+ years experience
iOSSwiftSwiftUIObjective-CREST APIsPythonCore DataXcodeGitSoftware Architecture
LinkedIn
NI

Nikolay Ivanov

Senior Android Developer

5+ years experience
AndroidKotlinJavaJetpack ComposeSQLSQLiteRoomFirebaseREST APIsGit
LinkedIn
MM

Mariyan Marinov

Senior Manual QA

6+ years experience
Manual TestingSeleniumJIRAAPI TestingRegression TestingJavaPostmanTestRailAgile/ScrumSQL
LinkedIn
DD

Dilyana Dimitrova

QA Engineer

5+ years experience
Manual TestingTest PlanningBug TrackingQuality AssuranceJIRARegression TestingAgile/ScrumPostman

Our Tech Stack

JavaTypeScriptJavaScriptPythonC#SwiftKotlinPHPAngularReactVue.jsNext.jsRxJSNgRxTailwind CSSSpring BootNode.js.NETLaravelREST APIsGraphQLMicroservicesApache KafkaRabbitMQMuleSoftiOSAndroidSwiftUIJetpack ComposeFlutterReact NativePostgreSQLMySQLMongoDBRedisElasticsearchFirebaseAWSAzureGoogle CloudDockerKubernetesTerraformCI/CDJenkinsLinuxNginxApacheCloudflareOAuth 2.0OpenID ConnectVaultSonarQubeOWASPAES-256TLS 1.3GitMavenXcodeSeleniumPostmanJIRA

What Drives Our Engineering Practice

Our team is built around a small set of values that show up in every project we deliver. We believe in writing code we would be comfortable inheriting from someone else - readable, well-tested, and documented in places where the intent is not obvious. We treat estimates as commitments rather than aspirations, which means we invest the time up front to understand the scope, the unknowns, and the dependencies before we put a number on a delivery date. We push back when a request does not fit the architecture or the product strategy, and we propose alternatives based on what we have seen work across many similar projects in SaaS, construction technology, and civic tech. And we communicate proactively when something changes - a delay, a risk, a discovery that affects scope - because we believe surprises are a failure of communication, not a fact of software delivery.

How We Collaborate With Your Team

Most engagements involve close, daily collaboration with your in-house product, engineering, and stakeholder teams. We work Monday to Friday, 10:00-19:00 Bulgarian time (03:00-12:00 US Eastern), which gives about 3 hours of live overlap with a 9-to-5 US Eastern day. With European clients we share a full working day. We participate in your existing tools wherever possible: Slack or Microsoft Teams for communication, Jira or Linear for project tracking, GitHub or GitLab for code review, and your preferred design tools for UX collaboration. We assign a single point of contact on our side - usually a senior tech lead - who is accountable for delivery, communication, and any escalations. That person is on every standup, runs sprint planning and review, and is the one you call when something does not feel right. Behind that lead, the engineers, QA, and dev-ops contributors operate as one extended team rather than a remote vendor.

How We Hire and Grow the Team

Every engineer on our team has been hired through a structured process that includes a technical screen, a take-home or pair-programming exercise, an architecture conversation, and a final cultural alignment interview. We hire for senior judgment and the ability to communicate with non-technical stakeholders, not just for raw coding skill. Once on the team, engineers are paired with a senior reviewer for the first three months, attend internal architecture and code-review sessions weekly, and rotate across project domains so that knowledge does not concentrate in one person. We invest in continuous learning through paid conference attendance, internal book clubs on architecture and product topics, and protected time for engineers to work on internal tooling, open-source contributions, and skill development. The aim is a team that stays and grows together rather than turning over every twelve months.

Want to Work With Our Team?

Whether you need a full development team or individual specialists, we are ready to help you build your next product.

Get In Touch