Skip to content

Balance ๐Ÿ’ผ/๐Ÿก

Balancing work and life to focus on what matters.

Template Version: 2.1 | Last Updated: 2025-06-01

The following are my work-life balance preferences. They may evolve over time, so check back occasionally.

โš–๏ธ TL;DR: Message me anytime, anywhereโ€”no need to use delayed sending. I'll respond appropriately. Please minimize meetings. My response times vary, especially during crunch periods. I have an unconventional working style, often sending messages and emails at all hours, but I'm adaptable to anyone's communication style. I value directness, candor, and honesty over diplomacy.

Communication

My preferred communication channels, in order:

  1. ๐Ÿ’ฌ Chat
  2. ๐Ÿ“ฉ Email
  3. ๐Ÿ“… Meeting

๐Ÿ’ฌ Chat

  • Message anytimeโ€”during meetings, PTO, or outside typical work hours is completely fine.

  • Avoid using delayed sending services; I prefer quick pings and will manage responses appropriately.

    • However, I'll use delayed sending for non-work-related topics.
  • I don't expect immediate replies unless it's critical.

    • Generally, I reply within a week, though this might extend to two weeks or a month if I'm in deep-focus mode.
    • I keep messages marked unread when they contain action items.
  • Please avoid messages that only say "hello".

๐Ÿ“ฉ Email

  • I typically don't check emails outside of working hours, but do send emails anytime.
  • I greatly appreciate a clear TL;DR at the top.

Core hours represent my standard availability window when you can reliably expect me to be online and responsive. These are the designated times during which:

  • Iโ€™m consistently available for meetings
  • I maintain regular communication and respond promptly
  • My work schedule is most predictable

Please note: While I may occasionally be available outside of core hours, availability during these times is less guaranteed and subject to variability. For time-sensitive matters or scheduled meetings, I recommend booking within core hours to ensure reliable connectivity.

My core working hours (PST):

Day From To
Monday 10:00 16:00
Tuesday 10:00 16:00
Wednesday 10:00 16:00
Thursday 10:00 16:00
Friday 10:00 16:00

Preferences:

  • Schedule at least a 5-minute break between meetings.
  • Provide at least 12 hoursโ€™ notice before scheduling meetings.
  • Always include permission to modify the event.
  • I prefer walking meetings whenever possible.
  • I use metadata for the following:
    • #moveable for meetings easily rescheduled (e.g., 1:1s).
    • ๐Ÿ”„ for recurring meetings

Working

  • I typically...

    • complete code reviews within 24 hours.
    • review tickets within 24 hours.
      • respond to tickets within 8-24 hours.
  • Plain, direct communication suits me best. I tend to speak very straightforwardly, which can occasionally come across bluntlyโ€”this isn't intentional, just my natural style. If subtlety or context cues are unclear, be direct. It helps everyone stay aligned.

    • Honesty over diplomacyโ€”clarity and truthfulness lead to better outcomes.
  • I prefer detailed and accurate world models. Expect me to ask probing questions about technical topics to ensure full understanding.

  • I occasionally have irregular working hours. If my schedule or timing is problematic, please let me knowโ€”Iโ€™m flexible.

Interviewing

  • I complete initial interview ratings within 24 hours and provide full feedback within 48 hours.

  • I use "TC" (The Candidate) to anonymize feedback and minimize bias.

  • My rating system uses the following markers:

    • + Positive trait
    • - Negative trait
    • -+ Mixed (positive and negative)
    • * Additional comment or context
  • Example rating could be:

+ Correctly identified the optimal data structure [XOR Linked List]
+ Choose optimal algorithm [Bogosort],
  + weighted pros [ฮฉ(1) runtime] and cons [O(โˆž)] of algorithm

- Got the average ฮ˜(n ร— n!) runtime incorrect,
	+ but TC got the memory complexity correct O(1),
	+ and correctly explained why constant space: sorts in-place

-+ Got 75% of the unit tests cases correct, 
   which is average for this problem

* TC had internet issues for 5 minutes in the beginning,
  granted them 5 extra minutes for problem (with TC's permisson)

Interview Feedback Template:

# ---------------------------------------------- Boilerplate
You can find more info about this template at 
starikov.co/balance#interviewing

<SCRIPT>
Hi, my name is Illya! Is this <TC>? Excellent!
Today we'll be conducting a 
<INTERVIEW TYPE: programming, leadership, system design> interview.

- Confirm programming language.
- Are you comfortable? Water, break?
- Any questions?
</SCRIPT>

# ---------------------------------------------- Question Asked
<Fizz-buzz>

# ---------------------------------------------- Interview Notes
- 00:00 Interview start:
-

# ---------------------------------------------- Candidate Code
// Candidate's code below verbatim


# ---------------------------------------------- Candidate's Questions
<SCRIPT>
I'm going to complete the interview.
We have a couple of minutes left,
I'd be happy to answer any questions you may have.

<CANDIDATE'S QUESTIONS>
- 

Thank you for your time today, 
your recruiter will be in touch with next steps.
Take care!
</SCRIPT>

# ---------------------------------------------- Additional Notes
- [Context, special conditions, or other comments]

Changelog

  • 2.0 | STAR๐ŸŒปKOV implementation
    • 2.1 | Proofreading via ChatGPT GPT-4.5. Added interview template.
  • 1.0 | Google implemenation